BurtonSoftware01 Orders to fulfillment
- OMS receives orders through a validated channel connection, webhook, polling, or agreed import process.
- Operations checks the customer, items, addresses, delivery requirements, and channel-to-internal SKU mapping.
- WMS checks available inventory and releases the order for execution.
- Warehouse teams pick, pack or label as required, and stage goods. Floor tasks and scans provide execution records.
- Authorized users confirm the physical shipping result, carrier, quantities, and tracking. Required channel acknowledgments are checked separately.
- OMS receives fulfillment results and returns tracking or inventory updates through the agreed connection.
- Billing uses completed work, quantities, and approved rules to prepare invoice records for review.
A planned load or scheduled loading status is not proof of shipment. Shipping completion requires confirmation of physical dispatch and any required channel acknowledgment. Review partial shipments and failed callbacks before closing an order.
02 ASN to stocked inventory
Before goods arrive, ASN records connect BOL references, containers, buyer or consignee, ETA/ETD, destination, and shipment documents. Commercial invoices, packing lists, transport documents, and other required files should match the same shipment reference.
Warehouse teams use that information to prepare receiving. They verify actual SKUs, cartons, pieces, pallets, and discrepancies, record devanning and labels, then put stock into locations. Receiving posting and the resulting inventory history confirm what was actually received; expected ASN quantities alone do not create usable stock.
POD and missing-document follow-up remain linked to the shipment. Document visibility helps coordination; regulatory filings and external exchanges require their own confirmed scope.
03 Warehouse work to an explainable invoice
| Evidence | What to verify |
|---|---|
| Completed receiving, outbound, storage, return, relabeling, or work-order service | Customer, date, completion status, and related shipment or order. |
| Quantity and unit | Pieces, cartons, pallets, time, or another agreed billing unit. |
| Approved charging rule | Rate, applicable service, effective period, and exceptions. |
| Invoice record | Charges reconcile with the service evidence and agreed billing period. |
Compare the invoice with operational records before releasing it. Accounting exports or external finance synchronization depend on the validated integration; creating an invoice does not by itself mean the external ledger is reconciled.
04 A useful end-to-end check
Choose a representative shipment and order. Confirm that customer identifiers, SKUs, units, quantities, status transitions, shipment evidence, and invoice rules remain consistent at every handoff. Include a shortage or failed callback so the exception path is tested as well.
See WMS standard operating flow, ASN receiving handoff, and integration planning.