Order fulfillment in manufacturing: release, ship and close
Work through a 100-valve order: verify release, approve a split, reconcile dispatch and delivery, and retain evidence before closing the work.
Order fulfillment is the work of getting a customer's order from an accepted requirement to the goods the customer receives. It includes preparing supply, processing the order, picking, packing and shipping, with delivery and returns handled under the agreed process. Oracle NetSuite's overview describes that wider chain.
For a manufacturer, the question at the shipping cutoff is specific: which units can leave now, what evidence permits their release, and what will still be owed afterward? A green order status cannot answer all three. Work through one order's quantities and handoffs before calling it complete.
Where does fulfillment start and end?
This guide follows a confirmed manufacturing customer order through operational delivery closure. Order management can also include quotations, commercial acceptance, invoicing, payment and after-sales service. Those obligations need their own controls; a delivery check does not settle them.
Warehouse fulfillment often emphasizes pick, pack and ship. Manufacturing adds dependencies before those steps: components, production capacity, testing and the documents required for release. The sequence depends on whether you build to order, assemble from available components or ship finished stock. The checkpoints below are a working method, not universal ERP status names.
| Checkpoint | Evidence to check | What it does not establish |
|---|---|---|
| Confirmed customer requirement | Order line, configuration, quantity, destination and agreed arrival date | Material or capacity is available |
| Feasible production plan | Usable components after other allocations, dated receipts and verified operations | Finished goods have passed testing |
| Released for dispatch | Identified units, required quality approval and release documents | The carrier collected them |
| Dispatched | Actual handoff record, quantity, shipment reference and time | The customer received them |
| Delivered and reviewed | Receipt evidence, quantity and unresolved shortage, damage or acceptance conditions | Invoicing, payment or later obligations are closed |
Start with the sales order when the customer's requirement changes. Use the clear-to-build check for the production dependencies. Here, the customer has not requested a different quantity or an earlier date; the issue is delivering the existing commitment.
Worked example: 100 valves due on Friday
This is a hypothetical example, not a customer result. All dates are in 2026. Customer order SO528 calls for 100 valves arriving on Friday, November 6. There are no cancellations or returns in the example.
At noon on Thursday, November 5, the team checks these mutually exclusive quantities. Units reserved for other customers are already excluded.
| Position at the cutoff | Valves | Can they enter this shipment? |
|---|---|---|
| Finished, allocated to SO528 and released, with required documents | 70 | Yes, after the shipping checks and authorized partial-delivery decision |
| Finished but awaiting the required test and quality release | 10 | No; the test and release remain open |
| Not yet built | 20 | No; components and production work remain open |
| Total customer requirement | 100 | 70 + 10 + 20 = 100 |
Each of the 20 unbuilt valves requires two components, so that part of the build needs 40 components. For simplicity, assume no scrap allowance and that all other materials are available. Capacity and the required operations still need checking.
The supplier says those 40 components have shipped. That is evidence of a supplier statement, not evidence of receipt, inspection or production completion. Do not add them to the 70 released valves. Purchasing obtains the shipment reference and expected arrival; receiving verifies the actual goods; quality applies the required checks; planning verifies when the 20 valves can be built and tested. See receiving inspection for the incoming-material decision.
The immediate answer is 70 released, 30 not yet released for dispatch. Neither a supplier's “shipped” message nor a production target makes that 100 ready.
Who can approve the recovery?
Logistics confirms that the 70 released valves can reach the customer's receiving location on Friday. A possible balance delivery is 30 valves on Tuesday, November 10: the 10 held valves after successful testing, plus 20 newly built valves after the components arrive and the required work is completed.
Treat Tuesday as a proposal until its dependencies are verified. A receipt forecast alone does not reserve production capacity or authorize quality release. If a dependency fails, escalate it and revise the option before presenting it as a commitment.
| Decision | Responsible role in this example | Evidence retained |
|---|---|---|
| Release the 10 held valves | Authorized quality role | Test result, unit or lot identity and release record |
| Complete and release the remaining 20 | Planning, production and quality within their authority | Component receipt/release, checked production slot, completion and test records |
| Approve extra freight and offer a split | Authorized commercial owner, with logistics | Cost approval, feasible transport and the proposed 70/30 schedule |
| Accept the split | Customer through the agreed change process | Acceptance of quantities, arrival dates and any conditions |
Use your company's actual authorities. A coordinator collects the decision; that does not give the coordinator every approval right. An internal approval also does not replace customer acceptance.
Microsoft Business Central's partial-shipment guidance illustrates the system side: customer acceptance of partial shipments controls the shipping setting, and shipping and invoicing can be recorded separately. Check your own ERP configuration and process rather than copying a status label.
If the customer requires all 100 together, the 70 available are not permission to send an unapproved partial shipment. Keep them allocated while the authorized team resolves the delivery plan, including any effect on other orders.
Track the balance after the first shipment
Suppose the team verifies the dependencies, obtains the required approvals and the customer accepts 70 on Friday and 30 on Tuesday. In this illustrative outcome, testing passes, the components arrive and are released, and production completes the remaining 20 in time for Monday's collection.
The actual events then look like this:
| Verified event | Cumulative dispatched | Cumulative received by customer | Still to receive |
|---|---|---|---|
| Thursday, November 5: carrier collects 70 | 70 | 0 | 100 |
| Friday, November 6: customer receipt of 70 recorded | 70 | 70 | 30 |
| Monday, November 9: carrier collects the final 30 | 100 | 70 | 30 |
| Tuesday, November 10: customer receipt of the final 30 recorded | 100 | 100 | 0 |
On Monday, nothing remains to dispatch, but 30 still remain to be received by the customer. An open-to-ship report and an open-to-deliver report can therefore show different balances without either being wrong. Name the event each report measures.
A packing list or printed label is not an actual carrier handoff. Tracking shows transport progress; retain the receipt evidence your customer and process require. If receipt shows a shortage or damage, open the exception against the affected quantity instead of treating the planned quantity as delivered.
Close the right work, with the right evidence
Keep a short record for each unresolved handoff: order and line, unit of measure, quantity, current state, source and timestamp, required evidence, owner, approver where needed, deadline and next check. Link the original commitment and any accepted changes.
A supplier-confirmation task can close when the promised answer and its exceptions are recorded. The customer order may still be waiting for production, transport or acceptance. Close the operational delivery work only after reconciling the quantity and the required documents, receipt and remaining issues. Keep unresolved claims assigned under your agreed process. Finance controls billing and payment separately.
Software can allow administrative closure without physical completion. For example, Danea Easyfatt's documentation permits forcing an incompletely fulfilled order to a concluded state. That is why a status needs an understood rule and supporting evidence.
In Cartograph, linked records connect the orders, parts and suppliers behind the issue. Inbox tasks keep an owner, plan, communications and approval history together. Scout Agent can work supplier follow-up within your configured permissions. ERP updates require a configured write-back for the mapped fields and an authorized action. Planning, quality and commercial owners still make their respective release and customer-commitment decisions.
Define the measure before reporting success
For SO528, define units received by the original customer-arrival date. That gives 70 ÷ 100 = 70% on Friday. Now define orders received in full by their original arrival date: one order was due, and none was received in full, so 0 ÷ 1 = 0%.
Both calculations describe the same example. They answer different questions. Neither is a universal “fulfillment rate,” and a one-order example is not a performance benchmark.
The revised schedule has two accepted deliveries. If both arrive as agreed, that is two of two revised delivery commitments met. Report it separately from the original-date measures, with its different baseline and denominator. Preserving the original result lets the team investigate the miss while recognizing a successful recovery.
Questions teams ask
Is order fulfillment the same as shipping?
Shipping is one stage. This guide also checks material, production and release before dispatch, then customer receipt and unresolved delivery issues afterward. Define the endpoint your own status or report uses.
Can you ship a partial order when the balance is uncertain?
Only under the applicable approvals and customer agreement. State the confirmed portion, the uncertain balance and the next update. Do not present an unchecked balance date as a promise or remove the outstanding quantity from the order.
Does a closed supplier task mean the customer order is complete?
No. It can mean the supplier question was answered or escalated. Production release, physical dispatch, customer receipt and operational closure require their own evidence and owners.
Which fulfillment metric should a manufacturer use?
Choose the decision first, then define the unit, physical event, due-period population, baseline date and treatment of partials. Keep original-commitment performance separate from revised recovery commitments and use more than one order to assess a trend.