Skip to main content
Orders joins accepted POs with source documents, quantities, transport, functional acknowledgments, and downstream observations. Scope by partner and PO number: business references can repeat. Document presence alone does not establish shipment or payment.

​
Prepare the response

The console supports partial quantities and split cartons. Allocate/download labels, then use those same SSCC-18 identities in the ASN. Allocation consumes serials; downloaded ZPL does not establish physical scanning or retailer acceptance. The server checks product identity, order state, quantities, invoice identity, numeric boundaries, and current policy. The configured outbound compliance mode governs blocking. Review warnings as well as errors.

​
Retain the review

Preview at POST /v1/operations/orders/{partner_id}/{po_number}/preview/{set} sends no EDI. It returns the prepared document, findings, revision, and frozen date overrides. Send via POST /v1/orders/{po_number}/{set}/{partner_id} with the captured overrides and: The CLI retains these in a portable artifact:
Inspect data.passed, data.can_send, and data.send_blockers first. Guarded sends require PostgreSQL; file-backed gateways can preview with can_send:false. A review is operation input with hashes, not a signed authorization grant. Noninteractive order-send executes when invoked, without another prompt.

​
Recover the original document

All direct X12/EDIFACT outbound generation routes accept Idempotency-Key: 1–128 ASCII letters, digits, hyphens, underscores, dots, or colons. Malformed keys or keyed requests without PostgreSQL return 422 before document commitment. Receipts are scoped to tenant, partner, and transaction route. Successful replay returns original wire/control numbers without another document, billing unit, event, acknowledgment tracker, or delivery job. JSON whitespace and object key order do not change identity; changed JSON with that key returns 409. Control-number gaps remain normal. Without a key, each successful call can generate another document. After an uncertain response:
  1. Retain original key, payload/review, revision, wire, and available correlation IDs.
  2. Inspect partner-scoped order, document, and delivery evidence.
  3. Restore access to the same workspace when needed. A later 401/403 does not prove the earlier operation rolled back.
  4. Explicit retries use the original operation. Do not create another key or preview to escape uncertainty. Reconcile first if business intent has changed.
  5. Verify returned original wire, then inspect transport and acknowledgment separately.
Committed receipts remain retrievable after configuration changes or production holds, subject to authorization; retrieval does not initiate delivery. Receipts do not expire automatically. Retention/deletion must account for their document references and define retry windows before removing them. External delivery remains at-least-once.

​
Console recovery boundary

Source 3f6b5c0 preserves pending sends in the current tab’s session storage, scoped to workspace, partner, and PO. Overrides, key, and revision are saved before dispatch; storage failure prevents sending. Reload restores the request. Retry original request recovers it; Refresh order evidence reads state without generating another document. After uncertainty or reload, a later rejection does not discard the original identity. Evidence-refresh failure after successful sending leaves that send accepted. Recovery requires HTTP 200, X12 content type, and an ISA-prefixed body. Redirects, 202, empty bodies, and HTML cannot establish recovery; this check does not qualify business content.
The console fixes in 3f6b5c0 were locally qualified with synthetic identity, real API/PostgreSQL, and response faults. They are newer than the retained production dashboard record. Tab-local session storage is not a server pending-send registry. If the session is lost, inspect recorded evidence before preparing another shipment or invoice. Integrations need durable storage of their own original requests.
Use operations for reprocessing, redelivery, queue recovery, and exception ownership.
Last modified on October 20, 2026