B2B Order Flow Failure Map
When an order goes missing, trace the first state that cannot be verified. A transport receipt can show that a message arrived. Order acceptance, inventory reservation and fulfillment each need evidence from the system that owns that step.
Suggested citation · TechSupport Team, “B2B Order Flow Failure Map.” Version 1.0. Reuse under CC BY 4.0.
Use the TechSupport Team B2B Order Flow Failure Map to tell an ERP, OMS, warehouse or application owner exactly where the transaction stopped.
Failure map
| Checkpoint | Snapshot to compare | Evidence and typical owner |
|---|---|---|
| Purchase order sent | Order or 850 purchase order accepted by the sending system | OMS order ID, external PO reference, sent time and partner ID. SaaS connector or order platform owner. |
| Document received | Endpoint receipt or applicable EDI acknowledgment such as 997 | Message or control ID, transport result and syntax status. Integration gateway or EDI owner. |
| Order accepted or rejected | ERP order state or partner business response such as an 855 | Downstream order ID, validation errors and business status. ERP or trading partner owner. |
| Goods shipped | Warehouse shipment status or 856 ship notice | Shipment ID, lines and quantities matched to the order. Warehouse or fulfillment owner. |
| Invoice posted | Billing or ERP invoice record, such as an 810 | Invoice and order IDs, approved totals, and unmatched exceptions. Billing or ERP owner. |
Transaction sets and acknowledgment rules vary by trading partner. Use the partner’s implementation guide and the relevant X12 transaction set. X12 transaction sets · X12 supply chain transaction flow
How to use the map
1. Copy the checkpoint table into your runbook and name the actual owner and system for each step.
2. Pick a transaction and record its IDs on both sides of each boundary. Start with the latest confirmed state.
3. Record the first gap, count similarly affected records and assign the next check. If the transaction already exists downstream, assess reconciliation before proposing a replay.
Illustrative example. The EDI gateway shows a syntax acknowledgment for PO 1046. The ERP has a validation hold and no final order ID. The ERP owner confirms the hold reason and the disposition. The integration team records the downstream state before anyone resubmits.
| checkpoint | current_system | upstream_id | downstream_id | evidence | confirmed_state | owner | next_check |
|---|---|---|---|---|---|---|---|
| Purchase order sent | SaaS order platform | PO-1046 | OMS-1046 | Order accepted for export | Sent 14:10 UTC | Connector engineer | Match receipt control ID |
| Document received | EDI gateway | OMS-1046 | EDI-1046 | Functional acknowledgment recorded | Syntax check complete | EDI owner | Find ERP business response |
| Order accepted or rejected | ERP | EDI-1046 | Validation hold confirmed | ERP order not created; hold pending | ERP owner | Confirm disposition before replay | |
| Goods shipped | Warehouse | PO-1046 | No accepted order | Shipment not due | Warehouse owner | Wait for ERP decision | |
| Invoice posted | Billing | PO-1046 | No accepted order | Invoice not due | Billing owner | Wait for ERP decision |
Next, use the failed order replay worksheet for individual records, the order integration SLO worksheet for recurring delays, or the connector change checklist when the message contract changes.
Get help with your support queue
Source and reuse
Credit TechSupport Team and link to this page when sharing or adapting version 1.0 under CC BY 4.0.