Fulfillment and 3PL
Sales Order sync, provider routing, packed lines, tracking, runtime requests, and warehouse handoff
Provider Flow
What Sync Owns
The 3PL runtime owns provider order creation/refresh, provider sync state, fulfillment history, shipped-line evidence, tracking records, runtime request status, provider sync tags, and sync issue messages.
Nonphysical order lines such as shipping, tax, credits, labor, service, and other accounting lines should stay on Salesforce financial records and should not be sent as provider fulfillment rows.
Operational Checks
| Check | Where |
|---|---|
| Provider health and runtime queue | 3PL Dashboard and reports. |
| Provider account/config | 3PL Provider Account and 3PL Provider Config tabs. |
| Fulfillment state | Sales Order page, Shipped Lines, Tracking, Sync State. |
| Runtime errors | 3PL Runtime Request, Fulfillment Sync History, dashboards. |
| Warehouse replacement | 3PL Warehouse Manager and provider transition records. |
Missing Tracking
Provider tracking can be absent while shipment identity and packed-line evidence are present. Do not assume missing tracking means no fulfillment. Check packed lines, external shipment or fulfillment IDs, picked dates, source line references, provider status, and current Sales Order fulfillment quantities.
Missing Tracking Decision Flow
Warehouse Handoff
Configured provider warehouses require successor-backed deactivation. Inventory balances and active provider configs are blockers until a safe transition is planned.
Last updated on
Payment Lifecycle
End-to-end payment object lifecycle from order intent through checkout, tokenization, transaction execution, receipt, allocation, settlement, refunds, voids, and disputes
Fulfillment Runtime Lifecycle
End-to-end 3PL lifecycle from sales order eligibility through runtime requests, provider sync, fulfillment operations, inventory mirror, tracking, and recovery