3PL and Fulfillment Object Fields
Field guide for provider configs, runtime requests, transactions, sync state, tracking, shipped lines, and fulfillment operations
3PL and fulfillment reporting should separate setup/configuration, queued work, provider call evidence, sync state, shipment/tracking evidence, and shipped-line detail.
Fulfillment Object Map
3PL Provider Config
Provider Config records define runtime behavior for a warehouse/provider route.
| Field family | Important fields | How to use in reports |
|---|---|---|
| Identity and provider | Config Label, Warehouse, Provider System, Provider Tenant Key, Connection Key, primary/secondary provider account fields. | Use for provider setup inventory. |
| Credentials/routes | Named Credential, secondary named credential, endpoint extension fields. | Use for admin review; do not expose secrets. |
| Sync toggles | Enable Sales Order Sync, Enable Purchase Order Sync, Enable Inventory Sync. | Use to understand why records do or do not sync. |
| Runtime windows | Runtime Window Start, Runtime Window End, Runtime Window Time Zone, Operating Days. | Use for scheduler/runtime availability reporting. |
| Polling/lookback | sales order, purchase order, inventory poll frequency and lookback fields. | Use for stale data and runtime cadence review. |
| Provider-specific fields | Katana, Packiyo, OrderDesk source/location/customer fields. | Use for provider-specific operational reports. |
| Lifecycle | Status, Retired At, Retired By, Retired Reason, Superseded By, Rate Limited Until. | Use for active/inactive provider review and migration safety. |
Best practice: a provider config can be present but disabled. Always include status and sync toggles in config reports.
3PL Provider Account
Provider Accounts represent reusable provider identity and credential grouping.
| Field family | Use |
|---|---|
| Provider/account identity | Which provider account this config/runtime uses. |
| Credential grouping | How runtime resolves credentials without hardcoding them on every config. |
| Lifecycle/status fields | Whether the provider account is active, replaced, or needs migration. |
Best practice: use Provider Account reports for credential/account governance. Use Provider Config reports for warehouse-specific runtime behavior.
3PL Runtime Request
Runtime Requests are queued work items.
| Field family | Important fields | How to use in reports |
|---|---|---|
| Work identity | Work Type, Source Object Type, Source Record Id, Warehouse, Provider Config, Request Key. | Use for queue inspection and dedupe. |
| Queue state | Status, Requested At, Requested By, Next Attempt At, Attempts, Force Run, Send Summary. | Use for backlog, retry, and scheduled-work reports. |
| Processing evidence | Processed At, Processed By, Last Transaction, Last Error. | Use for exception queues and runtime troubleshooting. |
Best practice: Runtime Request reports show what Salesforce is trying to do. Use Transactions to see what happened during the provider call.
3PL Transaction
3PL Transactions are request/response evidence for provider calls.
| Field family | Important fields | How to use in reports |
|---|---|---|
| Operation | Work Type, Operation, Direction, Provider System, Warehouse, Provider Config, Provider Account. | Group provider calls by purpose and route. |
| Timing | Started At, Completed At, Duration Ms, Attempt Number. | Use for latency and retry reports. |
| Request/response | HTTP Method, Endpoint, HTTP Status Code, Status, Status Family, request/response summary/hash/size fields. | Use for provider health and failure analysis. |
| Related records | Sales Order, Sales Order Tracking, Purchase Order, Runtime Request, Source Object Type, Source Record Id, related record refs. | Drill back to the affected record. |
| Error handling | Error Category, Error Severity, Error Message, Error Details, Failure Fingerprint, Is Replayable, Replay Status. | Use for exception dashboards and replay triage. |
| Provider references | External Transaction ID, External Reference, Provider Request ID, Correlation ID, Idempotency Key. | Use for provider support and reconciliation. |
| Volume | Items Processed, Items Succeeded, Items Failed. | Use for throughput and partial-failure reports. |
Best practice: avoid using raw payload fields in user reports unless the audience can interpret JSON. Use summaries, statuses, errors, and related record links.
3PL Record Sync State
Record Sync State tracks the mapping between Salesforce records and external provider records.
| Field family | Use |
|---|---|
| Source record and provider record mapping | Shows which Salesforce record maps to which external record. |
| Last hash/status/error fields | Explains whether the latest sync succeeded, failed, or did not need changes. |
| Provider/system references | Helps reconcile with external systems. |
Best practice: use Sync State reports when records repeatedly resync or fail because Salesforce and provider state disagree.
Fulfillment Operation
Fulfillment Operations describe operational progress for fulfillment work.
| Field family | Use |
|---|---|
| Sales Order and provider references | Tie fulfillment work back to orders and providers. |
| Status/progress fields | Show current fulfillment lifecycle state. |
| Quantity and validation fields | Explain partial fulfillment or validation failures. |
| User-friendly error fields | Show fixable errors to operators. |
Best practice: use Fulfillment Operation reports for warehouse/operator queues, not low-level provider debugging.
Sales Order Tracking
Tracking records represent shipments and carrier/tracking status.
| Field family | Important fields | How to use in reports |
|---|---|---|
| Order and provider | Sales Order, Sales Order Link, Fulfillment Provider, Warehouse, External Shipment ID, External Tracking ID, External Tracking Provider, Last 3PL Transaction. | Use for order-to-shipment traceability. |
| Tracking identity | Tracking Number, Tracking URL, Carrier. | Use in customer-service detail reports. |
| Shipment state | Shipment Status, Ship Date, Delivered Date, estimated delivery fields, On-Time Status, Transit Time Days, Return to Sender, failed delivery attempts. | Use for shipping performance and exception reports. |
| Checkpoints | Last Checkpoint Time, Last Checkpoint Location, Last Checkpoint Message, checkpoint history. | Use for exception/detail reports. |
| Packed/unpacked detail | Packed Line Items, Unpacked Line Items, Total Items Packed, Total Quantity Packed, split shipment fields. | Use for shipment completeness review. |
| Email evidence | Tracking Email Status, Tracking Email Sent, Tracking Email Sent Count, last tracking email fields. | Use for customer notification coverage. |
| Refresh timestamps | AfterShip Last Refresh At, Tracking Last Updated, Tracking Created Date. | Use for stale tracking reports. |
Best practice: Sales Order Has Tracking is an order-level shortcut. Use Sales Order Tracking reports when you need carrier, delivery, checkpoint, or notification detail.
Shipped Line
Shipped Lines connect shipped quantity to Sales Order Lines and Items.
| Field family | Important fields | How to use in reports |
|---|---|---|
| Item/order | Sales Order, Sales Order Line, Item, warehouse fields. | Use for exact item fulfillment detail. |
| Quantity and shipment | Quantity Shipped, Shipping Date, Shipped Time, Unit of Measure, serial numbers. | Use for shipped quantity, partial fulfillment, and serial tracking. |
| Price/discount | Price, Discount. | Use for shipped-line audit when needed. |
| Migration lineage | migrated link fields. | Use only for legacy reconciliation. |
Best practice: use Shipped Lines when you need item-level fulfillment proof. Use Tracking records when you need carrier/package proof.
Last updated on