The Acumatica–SuiteFleet integration links SO302000 shipment records to delivery tasks. Dispatchers review destinations, assign drivers, and follow delivery attempts in SuiteFleet. Each result returns through the configured connection to the matching source record, preserving shipment lines and lot or serial splits and any outstanding quantities.
Connector availability: SuiteFleet plans to publish its Acumatica connector on Acumatica Marketplace, subject to the marketplace review and release process.
1. Start with the Acumatica order
Open the source order SO 004812 for Summit Industrial Supply and inspect its delivery destination, line quantities, and configured SuiteFleet relationship. The example contains two lines with quantities 4 and 6 in the units shown.

Use an SO order with shipment processing enabled. Confirm its approval, credit, stock, and shipping rules before creating the shipment. Keep Order Type with Order Nbr.; the visible number alone is not the complete business key.
Sales Orders is SO301000 and Shipments is SO302000. One shipment may include multiple orders for the same customer, so the correlation must preserve every participating order line. Lot or serial splits and warehouse details must survive any aggregation into one delivery stop. Acumatica Sales Orders reference.
2. Configure the field mapping
Preserve this relationship before exporting delivery work:

| Acumatica source | SuiteFleet destination | Rule |
|---|---|---|
| Order Type + Order Nbr. | Order reference / correlation | Keep both values. |
| Shipment Nbr. | Reference number | One task-to-shipment relationship. |
| Shipment lines / splits | Items / source line keys | Preserve lot, serial, and UOM context. |
| Customer / shipping contact | Consignee | Use shipment contact. |
| Shipment address | Ship To | Validate pin after edits. |
| Warehouse ID | Branch / hub | Explicit lookup. |
| Requested On | Delivery Date (configured) | Confirm requested receiving date. |
| Ship On | Dispatch date | Separate from delivery window. |
| SuiteFleet result | Acumatica destination | Writeback rule |
|---|---|---|
| Task ID / AWB | Shipment custom delivery fields | Confirm field access during configuration. |
| Delivered / Failed | Custom delivery status | Confirm field access during configuration. |
| Recipient / completion time | Shipment delivery information | Confirm field access during configuration. |
| Photos / signature | Shipment evidence reference | Confirm field access during configuration. |
Validate the contract-based REST endpoint, version, entities, actions, and custom fields in the actual tenant. The form labels in this guide are logical mappings, not unverified REST property names. Confirm which supported action owns shipment confirmation and inventory posting. Acumatica Shipments reference.
3. Create and verify the SuiteFleet task
Send only the released shipment allocation through the configured interface. Store the returned task ID before reporting successful export. If the request times out, check for an existing task under the persistent shipment key before retrying creation.

Compare Ship To, Items, delivery date, receiving window, and instructions with Shipment 006245. Preserve item units independently from package count. A package quantity of one can contain several product units; neither value should silently replace the other.
Treat unmapped origins, missing contacts, and invalid addresses as actionable exceptions. Record the failing record key and field so the responsible user can correct the source and retry without re-entering the entire order.
4. Dispatch and manage exceptions
Use Tasks to filter operational work and open Dispatch & Operations to review Company, Driver, and Hub. Agree whether the connector or dispatcher owns each field; order updates should not silently overwrite an active driver assignment.

Workbench adds a geographic view of tasks and drivers. Inspect unresolved locations before dispatch and confirm that the driver can meet the receiving window. Keep route planning subordinate to actual release eligibility and warehouse readiness.

A confirmed shipment of selected quantities can leave other order lines outstanding under the configured shipping rules. Do not use Complete Order merely to remove a delivery exception from the queue.
For a failed or rescheduled stop, retain the attempt, reason, and original shipment relationship. Decide whether the next action is redelivery, return handling, address correction, or customer contact before creating more work.
5. Review delivery before writeback
On completion, match the result to the stored task and shipment identifiers. Review recipient and required proof, then reconcile accepted quantities at source-line level. Route missing or contradictory evidence for review instead of deriving acceptance from Delivered alone.

Deduplicate repeated completion messages and preserve event order. Store actual completion time separately from sync time; a later retry must not make an old delivery look newly completed. Keep delivery success and writeback success as distinct audit outcomes.
6. Verify the result in Acumatica
Attach delivery details to the shipment or a related customization. Confirm Shipment and sales-order completion belong to Acumatica’s shipment workflow; a shipment’s Completed status can involve invoice release. Do not force native statuses from a Delivered task. Acumatica Sales Orders reference.

Shipment 006245; task SF-DEMO-7104; recipient Michael Reed; actual handover October 15, 2026 · 1:35 PM MDT (America/Denver). First line: 4 shipped and 4 accepted. Second line: 6 shipped and 6 accepted.
Read back the linked record and review every outstanding allocation before marking the full order delivered. Test partial shipment, partial acceptance, failed delivery, duplicate completion, and delayed writeback. Keep inventory posting, receipt evidence, and payment reconciliation under their respective configured rules.
Frequently asked questions
Which Acumatica records should link to SuiteFleet?
Sales Orders is SO301000 and Shipments is SO302000. One shipment may include multiple orders for the same customer, so the correlation must preserve every participating order line. Lot or serial splits and warehouse details must survive any aggregation into one delivery stop.
How should delivery completion update Acumatica?
Attach delivery details to the shipment or a related customization. Confirm Shipment and sales-order completion belong to Acumatica’s shipment workflow; a shipment’s Completed status can involve invoice release. Do not force native statuses from a Delivered task.

.webp)

