Delivery Management Systems
Acumatica Delivery Management System
ACUMATICA + SUITEFLEET

Acumatica Delivery Management with SuiteFleet

ERP

Plan Acumatica delivery integration around SO302000 shipment records. Review field mapping, dispatch, exceptions, and completion.

Free Trial
Big & bulky last mile delivery — oversized goods and furniture delivery
Order release
Release approved shipment quantities with a stable source link, a verified destination, and clear delivery instructions.
Dispatch visibility
Review tasks, drivers, hubs, and operational states while preserving the relationship to each originating transaction.
Exception control
Retain failed attempts and partial outcomes so redelivery does not duplicate shipment posting or hide outstanding quantities.
Source reconciliation
Return delivery details to the correct execution record and verify the remaining work across all shipments.

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.

Acumatica starting order SO 004812 with SuiteFleet extension
Start with the Acumatica order and review the SuiteFleet delivery fields before releasing the shipment.

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:

Tenant/company → Order Type + Order Nbr. → Shipment Nbr. → shipment line/split → SuiteFleet task
Acumatica to SuiteFleet field mapping and return mapping
Acumatica–SuiteFleet field mapping. Confirm source fields, destination fields, and transformation rules during configuration.
Acumatica sourceSuiteFleet destinationRule
Order Type + Order Nbr.Order reference / correlationKeep both values.
Shipment Nbr.Reference numberOne task-to-shipment relationship.
Shipment lines / splitsItems / source line keysPreserve lot, serial, and UOM context.
Customer / shipping contactConsigneeUse shipment contact.
Shipment addressShip ToValidate pin after edits.
Warehouse IDBranch / hubExplicit lookup.
Requested OnDelivery Date (configured)Confirm requested receiving date.
Ship OnDispatch dateSeparate from delivery window.
SuiteFleet resultAcumatica destinationWriteback rule
Task ID / AWBShipment custom delivery fieldsConfirm field access during configuration.
Delivered / FailedCustom delivery statusConfirm field access during configuration.
Recipient / completion timeShipment delivery informationConfirm field access during configuration.
Photos / signatureShipment evidence referenceConfirm 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.

SuiteFleet Shipment Details with order reference and delivery window
SuiteFleet task 824516: order ORD-55055, AWB SF7104046580, and the receiving window in America/Chicago (CDT).

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.

SuiteFleet task list with operational statuses
Review task status, assigned driver, and the receiving window before dispatch.

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.

SuiteFleet driver panel beside the operations map
Review available drivers and task capacity alongside the Dallas–Fort Worth service area.

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.

SuiteFleet proof of delivery with recipient photos and signature
Delivery evidence example: Jessica Miller, October 15, 2026 at 12:36 PM CDT. Reconcile accepted quantities against the shipment lines.

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.

Acumatica completed delivery example linked to SO 004812
Review delivery status and evidence on the linked Acumatica shipment record. Reconcile any outstanding quantities separately.
Completion example

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.

SuiteFleet dashboard
Review the source records, field mapping, delivery workflow, and return updates for your Acumatica implementation.
Acumatica + SuiteFleet

Connect Acumatica delivery operations with SuiteFleet

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.
Multi-stop sequencing
Capacity-based planning
Traffic-aware routing

Acumatica ERP + SuiteFleet Delivery Scaling

As Your Business Grows

Starting Out

20/day

Manual dispatch
Paper manifests

Barely manageable
→
→

Scaled

500/day

Full automation
Fleet analytics

Review staffing needs

Confirm Your Acumatica Workflow

Distribution

Wholesale delivery

Commerce

E-commerce orders

Manufacturing

Direct-to-customer

Retail

Store delivery

Workflow illustration. Any quantities, timings, costs, or routes shown here are sample values separate from the article’s order. Billing and inventory updates follow the configured source-system rules.

Other Solutions

All Solutions