Orders
Route: /org/ecom/orders · Permission: View customer orders for the e-Commerce store
Module: org_ecom_orders — 9 permissions, the widest in the category
1. What the orders screen is
The store's fulfilment workbench, not a passive ledger. Orders are grouped by date, each date carrying its own order count, item count and tax total, and the default scope is the work that is still open — so the page doubles as the sheet a kitchen or packing bench works from.
Its defining feature is a view-mode switch that changes what "date" means:
| Financial · Order date | Operations · Delivery date | |
|---|---|---|
| Filters on | When the order was placed | When the customer wants it delivered |
| Answers | What did we sell on Tuesday? | What must go out on Tuesday? |
| Layout | Date-grouped ledger | Board grouped by delivery date and section |
| Export PDF | ✅ | ❌ |
This is not a display toggle. Financial filters on placed_at; Operations filters on the items'
requested_date. An order placed Monday for Friday delivery appears under Monday in Financial
and under Friday in Operations.
Two people looking at "this week" in different modes will legitimately see different orders and different totals. Always say which mode you mean.
2. How an order moves through the module
3. The workbench — step by step
Step 1 · Choose the view mode
Financial · Order date or Operations · Delivery date. The label states the date basis, which is the whole point of the control.
Step 2 · Scope with the status pills
| Pill | Scopes to |
|---|---|
| Active (default) | PLACED + CONFIRMED + SHIPPED — the open work |
| All | Everything |
| Delivered | DELIVERED |
| Cancelled | CANCELLED |
| Refunded | Orders with a processed refund |
Two further toggles sit beside them:
| Toggle | Scopes to |
|---|---|
| COD to collect | Cash-on-delivery orders whose payment is still PENDING |
| Refund pending | Orders with a refund awaiting a decision or gateway settlement |
Refunded is history — money already returned. Refund pending is a worklist — something needs a human. They are separate filters because they are separate jobs.
Step 3 · Narrow further
| Filter | Notes |
|---|---|
| Order date from / to | The label follows the view mode |
| Method | Delivery method — All methods by default |
| Section | Fulfilment section — All sections by default |
| Requester | Free text over Name, email, phone |
A reset control returns everything to the default scope.
Step 4 · Read a date group
Each date header carries a summary: "6 orders · 11 items · Tax collected ₹57.14".
Step 5 · Read an order card
| Element | Holds |
|---|---|
| Order reference | e.g. ORD-KITC-000021 — the prefix is the project's configured order-number prefix |
| Status badge | Placed · Confirmed · Shipped · Delivered · Cancelled · Refunded, each colour-coded |
| Delivery method | e.g. Delivery |
| Payment chip | COD · PAID or COD · TO COLLECT |
| Customer and item count | |
| Money | Total, then Product and Tax beneath |
| Time | Placed time |
4. Field reference
The six statuses
| Status | Badge colour |
|---|---|
PLACED | Amber |
CONFIRMED | Blue |
SHIPPED | Violet |
DELIVERED | Emerald |
CANCELLED | Slate |
REFUNDED | Rose |
See order lifecycle for what moves between them.
The nine permissions
| Permission | Gates |
|---|---|
| View customer orders for the e-Commerce store | The page |
| Show the Orders link in the e-commerce sidebar menu | The sidebar entry |
| Create Manual Orders | Create order |
| Edit order details (notes, internal flags) after placement | Notes and internal flags after placement |
| Review and act on customer orders (status transitions) | Status transitions |
| Export or print the e-Commerce orders fulfillment page | Print and export |
| Send Invoice to COD order after manual payment acknowledgement | Sending an invoice |
| Manage Refund Request of Customer | Raising a refund on a customer's behalf |
| Approve Refund Request | Approving a refund |
review changes an order's status; refund.approve returns money. Both are separate from edit,
which only covers notes and internal flags — a user with edit alone can annotate an order and
change nothing about it.
The result cap
The list requests up to 500 orders at a time. A store past that in the selected scope needs a narrower filter — there is no pagination control on this screen.
5. The admin contract
| Prerequisite | Without it |
|---|---|
| View customer orders for the e-Commerce store | No access |
| A selected project | "Select a project from the top bar to view orders." |
| Payment gateways | Nothing can be paid for |
| Order printing | The Default print row has no format |
| Fulfilment sections | The Section filter is empty |
6. Downstream
| Action | Effect |
|---|---|
| Status change | The shopper's my orders view |
| COD collection | Payment status, and the invoice |
| Refund approval | A credit note |
| Receipts and job orders |
7. Don't confuse this with…
| Screen | Route | Whose view |
|---|---|---|
| Orders (this page) | /org/ecom/orders | The store's, all customers |
| My orders | /account/orders | One shopper's own |
| Preorder requests | /org/ecom/preorder-requests | Requests, not orders |
| Credit notes | /org/ecom/credit-notes | Refund documents |
| Sales & Outbound | Inventory | Stock leaving, not orders |
8. Troubleshooting
| Symptom | Cause |
|---|---|
| "Select a project from the top bar" | No project selected |
| An order is missing | The Active pill excludes delivered and cancelled |
| Totals differ between two people | One is in Financial, the other Operations — different date basis |
| Fewer orders than expected | The 500 cap; narrow the filter |
| Cannot change a status | Missing Review and act on customer orders (status transitions) |
| No Export PDF | It is Financial-only, and needs Export or print the e-Commerce orders fulfillment page |
| Refunded and Refund pending disagree | They are different questions — processed versus in-flight |