Tell Us What You’re Connecting
Provide the systems, workflow and business requirements.
Shipping execution · Operations
Connect Acumatica + ShipHawk
Automate shipment release, ship-to, weights and dimensions, tracking and shipment confirmation, shipment confirmation posting, shipping charge reference between Acumatica and ShipHawk — with monitoring and managed support from APIWORX.
APIWORX connects the systems your business already uses and takes responsibility for the agreed integration workflows after go-live. The exact objects, direction and cadence are fixed in writing during scoping.
ERP + eCommerce Specialists
Managed & Monitored Integrations
Expert Integration Team
APIWORX Provides the Service
Yes. APIWORX connects Acumatica and ShipHawk.
But connecting the applications is only the beginning. The work that costs you time sits in the process running between them.
APIWORX automates that process end to end — the objects moving between Acumatica and ShipHawk, the ownership rules that decide which system wins, the exceptions when a record will not post, and the monitoring that tells someone before your team finds out from a customer.
How it works
From requirements to a managed integration
We Design the Integration
APIWORX recommends the integration architecture, mappings and implementation approach.
We Build, Monitor & Support It
APIWORX implements the integration and provides ongoing monitoring and support as applicable.
Who this is for
This page is for operations teams running Acumatica as the ERP of record with ShipHawk executing parcel and freight shipping.
What needs to be in place
- Acumatica with API access and a service account permitted to read shipments and post confirmations.
- A ShipHawk account with carriers, services and origins already configured.
- An agreed release point between Acumatica shipments and shipping execution.
- A named operations contact for hold, split and freight decisions.
When you may not need this
One origin and parcel-only shipping can often run without managed integration. It earns its place when mixed modes, multiple origins or exception volume make manual handling a standing cost.
What is out of scope
- Carrier accounts, negotiated rates and service availability remain yours; we move data, we do not resell shipping.
- Which charge values reach the ERP — and whether they come from the shipping platform or the carrier invoice — is confirmed in scoping.
- Rating, packing and label logic stay in the shipping platform unless a specific rule set is agreed as integration scope.
- Customs, duty and international documentation requirements are assessed per lane before any commitment.
What actually moves, and who owns it
A representative scope. Exact records and charge handling are confirmed before build.
AcumaticaAPIWORX (mapping, retries, exception queue)ShipHawk
| Object | From | To | System of record | Trigger | If it fails | Owner |
|---|---|---|---|---|---|---|
| Shipment release | Acumatica | ShipHawk | Acumatica | Shipment reaches the agreed release state | Held in exception queue with the validation error | APIWORX |
| Ship-to, weights and dimensions | Acumatica | ShipHawk | Acumatica | With the release | Shipment held; missing detail flagged | APIWORX |
| Tracking and shipment confirmation | ShipHawk | Acumatica | ShipHawk | Shipment confirmed | Retried, then queued for review | APIWORX |
| Shipment confirmation posting | ShipHawk event | Acumatica | Acumatica | Confirmation received | Queued with the shipment reference | APIWORX |
| Shipping charge reference | ShipHawk | Acumatica | Agreed in scoping | Agreed cadence | Held for finance review | APIWORX with your finance team |
Three decisions that make or break this integration
A shipment is split across parcels or trailers
Splits are recorded against the lines they cover, so Acumatica reflects what actually left the building rather than a single summary event.
- Line-level quantities recorded per shipment.
- Remaining quantities stay open where the rule allows.
- Confirmation posting follows your agreed completion rule.
Shipping data fails validation
Missing weights, dimensions or address detail hold the shipment with the specific reason, so the fix happens once in Acumatica.
- Required fields validated before release.
- APIWORX reprocesses the original shipment after correction.
- Recurring gaps raised as a master-data change.
A new origin location opens
Origins, carriers and service mappings are configuration maintained inside the engagement, so a new location is a change request rather than a rebuild.
- Origin and carrier mappings maintained by APIWORX.
- Per-origin rules kept separate.
- Exceptions labelled with the origin they came from.
Reliability and ownership
The operating rules that apply to this workflow after go-live.
- Every shipment message is logged with the source order reference so a parcel can be traced back to its order.
- Failed writebacks are retried on a defined schedule; anything still failing is held in an exception queue rather than silently dropped.
- Duplicate prevention keys on the order number and shipment identifier so a replay does not create a second fulfilment.
- Exceptions are worked by the APIWORX team and escalated to your named contacts when a business decision is needed.
- New warehouses, carriers, service levels and store mappings are handled as configuration work inside the ongoing engagement.
- Support windows and response commitments live in your agreement; this page does not state an SLA.
How a shipment is traced
Illustrative — not customer data
An illustrative reference trace from Acumatica shipment to ShipHawk execution.
| Acumatica shipment number | ShipHawk shipment reference |
|---|---|
| Acumatica warehouse | ShipHawk origin location |
| ShipHawk tracking number | Acumatica shipment confirmation |
| Charge batch period | Acumatica posting period |
Scope and questions
- Do you set rating rules in ShipHawk?
- No. Rating stays in ShipHawk; we confirm the scope in place and deliver the data it needs.
- Are charges posted to Acumatica?
- Only where the charge data is available and the accounts are agreed in scoping.
- Can multiple origins be supported?
- Yes — origin and carrier mappings are configuration maintained inside the engagement.
- Who owns exceptions?
- APIWORX works the queue and escalates to your named contacts when a business decision is required.
Your integration plan
Get My Integration Plan
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Ready to map your integration?
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Next step
Scope your ShipHawk + Acumatica integration
Tell us your systems and documents. A specialist confirms scope by email.