Order execution overview

Order execution is where a confirmed deal is manufactured, dispatched and invoiced. Most orders arrive here automatically when a Won offer is converted; some are created directly from a customer PO. Every order then travels through the 12-stage execution lifecycle.

The overview

The order-execution overview is the entry point to the module. Its KPI strip shows active orders, due this week, overdue, completed this period and revenue booked for the current tenant and period, with the overdue tile flagged when it isn’t zero. Click a KPI card to open the list filtered to that slice, or use the navigation to jump to the list kanban or create flows. Numbers are shown in your tenant’s display currency, and the overview is visible only to roles with order-execution read permission.

Finding orders

List view

The list is the primary working surface, a paginated, server-sorted table with columns for work-order id, reference, customer, contact, employee reference, stage, status, owner, value created date, due date and last activity. Stage and status badges are colour-coded, overdue rows are flagged, and deleted orders never appear. An empty list offers a “create order” call-to-action. Click any row to open the order.

Kanban view

The kanban groups orders into columns by execution stage. Drag-and-drop is allowed only on stages where a manual move is permitted; system-driven stages reject a drop with a clear message, and if the server rejects a move the card snaps back to its source column. Cancelled orders appear as a status filter, not a column. Overdue cards are flagged and each column scrolls on its own.

Search & filters

Search matches partial values across work-order id, customer name, source-offer reference and current stage (case-insensitive). A no-match query shows a clear message.
Filter by stage, status, owner, date range, business unit, due-date band (overdue / this week / this month), product category, currency and ship-to warehouse. Filters combine appear as removable chips, and clear all at once.

You can bookmark or share the link to reopen the same searched-and-filtered view.

Creating a sales order

Choose New order.
Select the customer from active customers in the customer master.
Add at least one line item: product, quantity, price, discount and tax. Tax is calculated per line using your tenant’s GST rules. You can’t confirm until at least one line exists.
Optionally set a source-offer reference; when present the lines, terms and customer pre-populate and are read-only by default.
Save. The order number is generated from the configured series, the order lands at the Sale Order stage, and the detail page opens.

At save the customer’s credit-limit policy is enforced (see Amendments, holds & returns) and a non-standard discount or terms routes the order through approval first.

Currency carries over from the source offer when the order was converted, otherwise it defaults to your tenant’s base currency, and the exchange rate is locked when the order is created. Only roles with sales-order create permission can create orders, creation is audited, and a new order shows up in analytics and search within about half a minute.

The work order detail

The detail page is where you act on one order with every related record in reach:

Header: customer, owner, dates, business unit. The header locks once dispatch begins.
Line items: product, quantity, price, tax, and per-line fulfilment status (planned produced, dispatched). A line locks as soon as it is dispatched.
Execution stages: the stage tracker showing which stages are done, current and pending, plus the stage controls (gated by role).
Linked artefacts: the source offer, linked purchase orders, factory orders, invoices delivery notes and e-way bills, each clickable.
Timeline: a chronological history of every transition and event (see below).
Attachments and the audit log.

You can download a PDF order summary from here. An order that belongs to another tenant or one that has been deleted, shows a clear “not found” message.

The order timeline

The timeline shows every event on the order, stage transitions, linked-artefact events (PO raised, factory order started, invoice issued, dispatch), status changes and manual notes each with a timestamp and the person responsible. It’s ordered newest-first by default, with a toggle for oldest-first, can be filtered by event type, and exports to PDF with the order detail.

The order checklist: offer vs customer PO

Before an order is released for execution, a coordinator verifies the customer’s PO against the final offer.

Open the order’s Checklist tab. A two-column, side-by-side view compares the final offer with the customer PO across product specifications, quantities, prices, delivery dates, terms and conditions, and payment terms.
Any field that differs is highlighted as a deviation.
Capture a remark against each deviation.
Where deviations exist, approval is required before the order can proceed. An authorised person signs off: the sign-off is recorded with user and timestamp, and the deviation history is retained.

An order whose PO matches the offer on every compared field completes the checklist cleanly with no approval step needed. The checklist’s completion status is tracked on the order, and the deviation history is kept and auditable.

Bulk actions

An ops manager can act on many orders at once from the list: select rows to reveal a batch-action toolbar, then reassign owner, set tags or export the selection. Bulk actions are restricted to ops manager / admin, any per-row failures are summarised without aborting the batch, and every bulk action is audited.

Attaching documents

Attach supporting files, a customer PO scan, a signed agreement, drawings, dispatch instructions, to an order so they travel with it across stages. Each document carries a type is validated for size and format (PDF and common image formats), is stored under your tenant’s area, and its upload and deletion are audited.