What sales order management means
Sales order management is the controlled path from a customer's first enquiry to a reconciled, paid invoice. In a manufacturing ERP the chain is explicit: enquiry captured and followed up, quotation raised and approved, the confirmed order recorded as an Order Acceptance (OA), the OA checked and released, production and purchasing driven off the released order, goods inspected and dispatched on a delivery challan, a GST invoice raised, and order-versus-invoice reconciliation proving that everything ordered was billed.
The reason this deserves its own discipline is simple: for a manufacturer, the sales order is not a record of a sale — it is the cause of everything the factory does next. Manage it loosely and the looseness propagates into planning, purchasing and dispatch; manage it as a controlled document and the whole downstream chain inherits that control.
Before the order: enquiry and quotation
Order management starts before the order exists. The Sales & CRM module captures the enquiry and tracks its follow-up through pre-sales stages — from enquiry received to order received — so the pipeline is a queue with owners and dates, not a memory. Quotations are raised against the enquiry, compared where several revisions or competing options exist, and approved before they go out; a quotation comparison dashboard keeps the commercial history in one view.
When the customer confirms, the winning quotation converts into the Order Acceptance — carrying its items, prices and terms forward so the order starts life consistent with what was actually offered. Enquiries that do not convert remain data: follow-up dashboards show where the pipeline leaks and which quotes died waiting.
The Order Acceptance — the sales order itself
The Order Acceptance is the sales order: a header-and-lines document recording the customer, their purchase-order reference, the items and quantities, prices, taxes and delivery expectations. Every line references the shared item master, and the customer references the party master — so the order automatically agrees with the masters that stores, production and accounts will use later. There is no re-keying between "what sales sold" and "what the factory sees", because both are the same record.
The OA is also where traceability begins. Dispatches, invoices, work orders, material plans and purchase requisitions raised for this order all carry its reference. Months later, one order number pulls the whole story — which is exactly what a customer query or an audit demands.
Statuses and approval: draft to released
| Stage | What it means | Who acts |
|---|---|---|
| Draft | Order entered; editable, commercially uncommitted | Sales executive |
| Checked / verified | Lines, prices and terms reviewed against the quotation | Sales / commercial reviewer |
| Released / approved | The commitment event — production and purchasing may act on it | Approver via the approval screen |
| Short-closed | Open balance deliberately closed; no further supply expected | Sales / management |
| Cancelled | Order withdrawn; downstream demand removed | Sales / management |
The approval gate is not bureaucracy — it is the boundary between "quotation optimism" and "factory commitment". Because rights are role-based, who may enter, check and release orders is configured per user, and every status change is recorded in the document's history with the audit trail the platform keeps on every write.
What release actually triggers
Release is the single most consequential click in the system. From the released OA:
This is what the pillar guide calls the released order being the hub: production, planning, purchasing, quality and finance are all reading one object from different angles, so there is nothing between them to reconcile.
Order types: development, component and child orders
Real order books are not uniform, and the OA comes in variants to match. A development OA covers new-product development work — where the deliverable includes engineering, and engineering changes can be raised against the development order itself. Component or child OAs sit under a parent order when a customer schedules parts of a larger scope separately. And BOM-against-OA means even a standard item can carry an order-specific structure — a different finish, a substituted fitting — without touching the master BOM.
Can you trace one order from enquiry to payment today?
Bring a real order — we will run it through quotation, acceptance, release, dispatch and invoice in a 30-minute session, and show you the reconciliation at the end.
Dispatch: inspection, challan, stock
When finished goods exist, the order's outbound half begins. Pre-dispatch inspection is the last quality gate — nothing leaves unchecked. Dispatch goes out on a delivery challan, and the movement posts through the same store engine as every other stock transaction, so dispatching decrements real inventory rather than a parallel sales record. Partial dispatches are normal: each one references the OA, and the system tracks ordered, dispatched and open balance per line automatically.
GST invoice and reconciliation
The GST invoice is raised against the order with tax drawn from the configured GST and HSN masters, and amount-in-words in Indian statutory format. It posts to Tally as a sales voucher, so accounts and operations stay in step without re-entry, and payment receipts close the commercial loop.
The quiet hero of order management is the order-versus-invoice report: ordered value against billed value, order by order. Under-billed orders, dispatches never invoiced, and open tails that should be short-closed all surface here — the difference between discovering revenue leakage at year-end and seeing it this week. It works because dispatch and invoice descend from the same OA; there is no matching exercise, just a chain being read.
How Fast ERP runs the sales order
Fast ERP implements this lifecycle in the Sales & CRM module, wired into the rest of the system:
- Enquiry follow-up and quotation control — staged pre-sales tracking, quotation approval queues and a comparison dashboard.
- Order Acceptance entry and approval — draft, check and release under role-based rights, with development and component/child order types and BOM-against-OA.
- Release-driven downstream — explosion, plans, requisitions and work orders all created against the order's reference.
- Pre-dispatch inspection, dispatch entry and delivery challan posting through the one store engine.
- GST invoicing with amount-in-words, Tally posting and OA-versus-invoice reconciliation — plus invoice and summary reports for the month-end view.
Because the order, the factory and the accounts share one database, sales order management stops being a departmental activity and becomes the spine of the business — the same quote-to-cash pattern proven at deployments like Nikhtish Engineering.
Frequently asked questions
What is sales order management in an ERP?
Sales order management is the controlled path from a customer's enquiry to a reconciled, paid invoice. In a manufacturing ERP the chain runs: enquiry captured and followed up, quotation raised and approved, the confirmed order recorded as an Order Acceptance (OA), the OA approved and released, production and purchasing driven off the released order, goods inspected and dispatched on a delivery challan, a GST invoice raised, and order-versus-invoice reconciliation confirming everything ordered was billed.
What is an Order Acceptance (OA)?
The Order Acceptance is the sales order — the document that records the customer's confirmed order inside the ERP: items, quantities, prices, delivery terms and the customer's reference. It starts life as a draft, passes through checking and approval, and on release becomes the hub of the system: the BOM is exploded against it, the material plan and work orders descend from it, and every later dispatch and invoice references it. Fast ERP also supports development OAs for new-product work and component or child OAs under a parent order.
What happens when a sales order is released?
Release is the trigger event of the whole manufacturing cycle. The released OA drives three things at once: the multi-level BOM is exploded against the order, giving production its work orders and routes; the explosion feeds MRP, whose netting produces the raw-material and component plans; and the shortages those plans reveal start the purchase spine as requisitions, purchase orders and goods receipts. Quality then gates the flow, and finance closes it — all referencing the same released order.
How does dispatch and invoicing work against a sales order?
Finished goods pass pre-dispatch inspection before anything leaves. Dispatch goes out on a delivery challan, decrementing stock through the store engine, and the GST invoice is raised against the order — with tax from the configured GST and HSN masters and amount-in-words for Indian statutory format. The invoice posts to Tally as a sales voucher, and the order-versus-invoice report reconciles what was ordered against what has been billed, exposing under-billing and pending quantities immediately.
Can one sales order be delivered and billed in parts?
Yes — partial dispatch and billing are normal in make-to-order work. Each dispatch and invoice references the same Order Acceptance, so the ERP always knows ordered quantity, dispatched quantity, billed quantity and the open balance per line. That is exactly what order-versus-invoice reconciliation reads. Orders that will not complete can be short-closed, so the open balance is a deliberate decision rather than a forgotten tail.