When the customer says yes, the quotation converts to an Order Acceptance — the confirmed order. Check it, release it, complete it — then hand the same document to the factory to build and to accounts to invoice. One Party, one document chain, nothing re-typed.
The order carries the same lines, prices and terms as the quotation it came from — so the moment a deal closes, nobody re-types the order into the factory's system.
When a customer confirms, you shouldn't re-enter the deal. The won quotation converts to an Order Acceptance (OA) that inherits its item lines, quantities, agreed prices, terms and references — or you import the customer's purchase order straight onto the same document. The OA references the source QT, so the enquiry → quotation → order chain is intact and auditable.
An unchecked order is a rework waiting to happen. Every OA runs through a defined lifecycle: it is drafted, checked, released and completed. The checker confirms the order against the quote before it goes live; release turns it into the factory's order; completion closes it out. Each transition is written to the order's status history, so nobody has to ask "is this order approved yet?"
Not every confirmed order is a straight production run. A sample order (SMOA) for NPD approval and a tooling order (TOA) for fixture or die development are tracked as OA sub-types, each with its own follow-up dashboard. They run through the same check, release and complete discipline, but they are chased on their own timelines — so a sample awaiting customer sign-off never gets lost behind bulk orders.
This is where a document-driven CRM pays off. The released OA is not a message to another team — it is the actual order object the rest of the suite consumes. Fast Production turns it into a process sheet and work order; Fast Billing dispatches and invoices against the same OA. One Party, one document chain from enquiry to invoice — so an OA-versus-invoice report reconciles itself and nothing is re-entered on the way to the shop floor or the ledger.
Convert the won quotation to an Order Acceptance, or import the customer's purchase order straight onto the OA — the lines, prices and terms carry across intact.
A checker verifies the order, release turns it into the factory's live order, and completion closes it out — with every transition on the status history.
Sample orders (SMOA) and tooling orders (TOA) tracked as OA sub-types, each with its own follow-up dashboard so NPD and tooling never slip.
Prioritise confirmed orders High, Medium or Low and re-sequence the queue on the Change Order Priority screen — sales and planning agree what gets built first.
The Order Execution view tracks each order's subject, planned hours, priority and due date, while the order-status dashboard rolls up progress across the book.
The released OA feeds production's work order and Billing's dispatch and invoice — one document chain, reconciled by an OA-versus-invoice report.
When the order lives in an email or a spreadsheet, someone re-keys it into production and accounts — and errors creep in. Here is what a real order document changes. New to the pipeline? Read what is CRM software?
An Order Acceptance is the confirmed customer order — the point where a won quotation becomes a real order (Order Received, status 35). It is created by converting the quotation or importing the customer PO, so the OA carries the same item lines, prices, terms and references as the quote. The released OA is the single document that Fast Production builds and Fast Billing invoices against, with no re-keying.
Every order moves through a disciplined gate: a checker verifies the OA — items, quantities, prices, delivery dates and terms — the order is then released so it becomes the factory's order to plan and build, and it is marked complete when fulfilled. Each transition is recorded in the order's status history, so you always know whether an order is drafted, checked, released or completed.
Yes. Sample orders (SMOA) and tooling orders (TOA) are handled as sub-types of the Order Acceptance, each with its own follow-up dashboard. So NPD sample builds and tooling development are chased on their own timelines while still running through the same check, release and complete lifecycle as a standard production order.
Yes. Because the OA is a real document in the shared engine, the released order is the exact order Fast Production builds — it feeds the process sheet and work order — and Fast Billing dispatches and invoices against the same OA. One Party, one document chain from enquiry to quotation to order to invoice; nobody re-types the order into the next system. See the ERP & Billing hand-off.
Yes. Confirmed orders can be prioritised High, Medium or Low and re-sequenced on the Change Order Priority screen, and the Order Execution view tracks each order's created-for, subject, planned hours, priority and due date. This lets the sales and planning teams agree what gets built first without leaving the order chain. Progress can also be surfaced in Dhruv AI dashboards.
Live demo on your own pipeline — your quotes, your order checks, your priority and hand-off rules. Cloud or on-premise, standalone or with the full Fast Suite.
