Most Dynamics AX and Dynamics 365 integrations with a carrier, a web shop or a payment platform need only a handful of flows: the order in, the shipment and tracking number out, the payment or settlement in, and stock levels out. UPS, Hermes (Evri), Volusion, JustGiving and the rest all follow that same shape. The work is in deciding which system owns each piece of data and what happens when a message fails, not in the connector.
What does a carrier integration actually move?
A carrier integration such as UPS, Hermes, DPD or FedEx with Dynamics 365 Finance & Operations (or AX 2012) does three things. It sends the shipment (addresses, parcels, weights, service level) and gets a label and a tracking number back. It writes that tracking number on the sales order and packing slip so customer service can answer “where is my order” without opening the carrier portal. And it brings back delivery status and, if you negotiate it, the invoice lines for reconciliation against what you were quoted.
Everything else, such as rate shopping, address validation and pickup booking, is optional and usually better left in the carrier’s own tool until the three basics are stable.
What does a web shop integration move?
A web shop such as Volusion, Shopify, Magento or WooCommerce sends orders and customers into the ERP and reads products, prices, stock and order status out of it. The mistake is to let both systems own the same thing. The table below is the ownership we recommend for most companies.
| Data | Owned by | Direction and trigger |
|---|---|---|
| Product catalogue, descriptions, images | Web shop | Stays in the shop; the ERP holds the item number and price only |
| Item numbers, cost, list prices | Dynamics 365 | To the shop on a schedule, read-only there |
| Available stock | Dynamics 365 | To the shop every few minutes, or on each stock movement for fast movers |
| Web orders and the customer on them | Web shop at checkout | To Dynamics 365 at payment confirmation, as a sales order with a shared web order number |
| Order status, shipment, tracking number | Dynamics 365 | Back to the shop when the packing slip is posted |
| Payments and refunds | Payment provider | Settlement file into Dynamics 365 daily; refunds raised in the ERP, executed by the provider |
The same pattern holds for a donation platform like JustGiving: the platform owns the donor and the gift, the ERP receives a daily settlement with fees, and nobody re-keys anything.
Which identifier links the two systems?
Every integration that went wrong in our experience had this in common: there was no single identifier that both systems kept. Decide it on day one. The web order number lives on the sales order in Dynamics 365; the Dynamics 365 sales order number is written back to the shop; the tracking number is written to both. Customers are matched by email first and then by a stored external ID, never by name alone.
AX 2012 or Dynamics 365: does the design change?
The design does not change; the plumbing does. On AX 2012 the integration runs through AIF services or custom X++ services and a middleware layer that polls. On Dynamics 365 Finance & Operations the same flows use data entities through OData or recurring integrations, with business events raising “packing slip posted” to a Logic App or a Power Automate flow. A company moving from AX 2012 to Dynamics 365 should carry over the field-ownership decisions and the reconciliation report, and rebuild the plumbing on supported patterns rather than porting the old code.
What should happen when a message fails?
A web order that never reached the ERP is lost revenue and an angry customer two days later. A tracking number that never reached the shop is a “where is my order” email. The integration needs four things before it goes live:
- A queue, so a message that fails is retried, not dropped
- A named person who is told when a message has failed three times
- A daily reconciliation: orders placed in the shop yesterday, sales orders created in Dynamics 365 yesterday, shipments posted, tracking numbers sent, with the differences listed
- A way to replay one message by hand without touching code
The reconciliation report is the most valuable part of the whole project and takes an afternoon to build. Companies that have it stop discovering integration faults from customers.
A worked design for a company shipping web orders
Orders are paid in the web shop. Every five minutes a flow reads paid orders since the last run, creates a sales order per web order in Dynamics 365 with the web order number in the customer reference, and writes the Dynamics 365 order number back to the shop. The warehouse picks and packs in Dynamics 365. On packing slip posting, a business event sends the shipment to UPS or Hermes, the label prints in the warehouse, and the tracking number is stored on the packing slip and sent to the shop, which emails the customer. Each night the payment provider’s settlement file is imported and matched to the sales orders by web order number, with fees posted to the right ledger account. Each morning a report lists any web order without a sales order, any sales order without a tracking number after 24 hours, and any settlement line without a matching order.
Decisions to make before the first line of code
- Which identifier links an order, a customer and a shipment across all three systems
- What creates a new customer in Dynamics 365, and what happens if the email already exists
- How partial shipments and back orders are shown in the shop
- Whether stock in the shop is physical, available or available minus a safety margin
- Who owns a cancelled web order after the sales order has been picked
- How carrier surcharges and fuel adjustments are reconciled against the carrier invoice
Signs an existing integration needs attention
Orders typed into the ERP by hand “because the sync missed one”. A spreadsheet of tracking numbers. Stock showing in the shop that was sold yesterday. A carrier invoice that nobody checks against shipments. An integration user whose password expired on a Friday. Each of these is a design gap, not a tool failure, and each is fixed by deciding ownership, adding a queue and building the morning report.
Re-keying web orders or chasing tracking numbers by email? See how we design integrations or book a consultation.
Frequently asked
Do we need middleware, or can Dynamics 365 talk to the carrier directly?
Dynamics 365 Finance & Operations can call a carrier API from a business event through Logic Apps or Power Automate without a separate middleware product. Middleware earns its place when there are several shops, several carriers or high volumes that need queuing and replay in one place.
How long does a web shop or carrier integration take?
With ownership decided and a standard platform on both sides, the first order-to-tracking flow is usually live in four to eight weeks, including the reconciliation report. Custom catalogue logic, bundles and multi-warehouse stock add time; the connector itself rarely does.
We are still on AX 2012. Is it worth integrating now or should we wait for the upgrade?
Decide the design now, because it carries over. Whether to build on AX 2012 depends on how far away the upgrade is: within a year, build the flows so that the business rules and reconciliation are ready and only the plumbing changes; further out, build on AX 2012 and plan the rebuild into the upgrade scope.
