Order status and ERP status can differ because an order's commercial commitment is distinct from downstream execution and financial settlement. The Admin Panel presents these states as separate diagnostic dimensions for investigating an order.

The orders list has separate ORDER STATUS and ERP STATUS columns. The Status filter contains exactly All, Pending, Declined, Waiting for approval, and Complete. The Erp status filter contains exactly All, Pending, Complete, Failure, and Sent. Keeping the filters separate helps preserve the distinction between commercial state and downstream execution. A single status should not combine commercial, fulfillment, invoice, payment, and return state.

Publishing an order for downstream processing does not by itself mean that the order was accepted, created in an ERP, fulfilled, or invoiced. An external order mapping connects canonical transaction references with scoped external records, but it does not prove that the external record accepted or completed the order. Transport or synchronization acknowledgement does not transfer authority or prove acceptance. ERP, OMS, finance, WMS, and other assigned specialist systems remain authoritative for the post-sale facts within their respective boundaries.

When the external outcome is unknown, reconcile the difference and establish idempotency before retrying. An Order Reconciliation Record compares canonical and external representations, records the relevant authority and severity, and preserves remediation and closure evidence. A blind retry can create another external record or leave the original mismatch unresolved.

An order detail view can expose ADD PRODUCT, CONFIRM, DECLINE, and RESTORE actions, depending on the order state. The order line table uses SKU, PRODUCT, BASE PRICE, DISCOUNT, ITEM PRICE, QUANTITY, and SUBTOTAL columns. An Order Line represents an independently governable committed product, service, fee, or entitlement whose quantities can be reconciled across order changes and downstream references. The Admin Panel provides an operational control surface and does not own source-system records or runtime execution. Direct production ERP mutation from the Admin Panel is prohibited.