3PL Runtime Admin
Admin guide for provider accounts, provider configs, runtime settings, warehouse handoff, alert routing, and scheduler ownership
Use the 3PL Management app and Settings app in QA:
https://exodus--vesper.sandbox.lightning.force.com/lightning/app/ThreePL_Management
https://exodus--vesper.sandbox.lightning.force.com/lightning/n/ThreePL_Runtime_Settings
Runtime Ownership
3PL work is business-critical because failed fulfillment can block orders from leaving the warehouse. Treat provider config, warehouse handoff, and scheduler state as operational controls.
Callouts run as the current or scheduled user. Do not describe the runtime as impersonating Warehouse__c.Integration_User__c unless the implementation changes.
Core Records
| Record | Purpose |
|---|---|
ThreePL_Provider_Account__c | Reusable provider account identity and credential/account grouping. |
ThreePL_Provider_Config__c | Warehouse/provider runtime config, endpoints, sync toggles, windows, and lookbacks. |
ThreePL_Provider_Transition__c | Successor-backed provider/warehouse handoff evidence. |
ThreePL_Record_Sync_State__c | Per-record provider sync state and source reference. |
ThreePL_Runtime_Request__c | Queued/runtime work item. |
ThreePL_Transaction__c | API transaction and telemetry evidence. |
Fulfillment_Sync_History__c | Fulfillment sync and provider writeback history. |
Fulfillment_Operation__c | Operational fulfillment state. |
Provider Config Checklist
For each provider warehouse/config:
- Confirm provider system and tenant/account key.
- Confirm active warehouse and source warehouse mapping.
- Confirm sales order, purchase order, and inventory sync toggles.
- Confirm order, shipment, inventory, and purchase order endpoint extensions.
- Confirm lookback windows and poll frequency minutes.
- Confirm runtime window start/end, operating days, and time zone.
- Confirm connection status and last connection error fields.
- Confirm primary/secondary provider account references.
Key config fields include Provider_System__c, Provider_Tenant_Key__c, Warehouse__c, Primary_Provider_Account__c, Enable_Sales_Order_Sync__c, Enable_Purchase_Order_Sync__c, Enable_Inventory_Sync__c, Runtime_Window_Start__c, Runtime_Window_End__c, and Runtime_Window_Time_Zone__c.
Runtime Settings
ThreePL_Runtime_Settings__c records scheduler/runtime ownership and alert behavior.
| Field | Admin meaning |
|---|---|
Scheduler_Status__c | Current scheduler state shown to admins. |
Scheduler_Owner_User_Id__c and Scheduler_Owner_Username__c | User that owns installed scheduled work. |
Runtime_User_Id__c and Runtime_User_Username__c | Runtime user context stored by the settings surface. |
Last_Setup_Checked_At__c | Last setup/status check. |
Last_Request_Processed_At__c | Last runtime work processed. |
Notify_On_Fulfillment_Failure__c | Enables fulfillment failure alerting. |
Fulfillment_Failure_Cooldown_Minutes__c | Prevents repeat alert storms. |
After scheduler changes, confirm CronTrigger state and the settings page. A class existing in metadata does not prove the schedule is installed or active.
Warehouse Handoff
Configured 3PL provider warehouses require successor-backed handoff. Do not deactivate or replace a provider warehouse through a generic warehouse edit if it has active provider config, provider inventory, open orders, or external references.
Safe handoff flow:
- Identify the source warehouse and provider config.
- Identify successor warehouse/config.
- Review inventory blockers and open order blockers.
- Record transition reason.
- Execute through the 3PL warehouse/provider takeover path.
- Confirm provider configs and future routing point to the successor.
- Keep the transition record for audit.
Alert Routing
Fulfillment failure alerts should be managed through 3PL runtime settings and notification profiles. Alert routing should include the operational people who can diagnose provider failures, not only the Salesforce admin.
Validate alerts by forcing a safe QA failure or using existing test data. Confirm alert cooldown prevents repeated noise.
Troubleshooting
| Symptom | Check first |
|---|---|
| Orders are not syncing | Scheduler state, runtime settings, provider config toggles, runtime window, sync state. |
| Provider returns auth failure | Provider account, Named Credential, External Credential, credential status. |
| Inventory looks stale | Inventory sync toggle, poll frequency, last success/error, provider-owned mirror rows. |
| Tracking is missing | Shipment endpoint, provider writeback, sync history, sales order tracking records. |
| Handoff is blocked | Active inventory, open orders, configured provider warehouse, missing successor. |
Last updated on