ERP shipping integration: how it works, who builds it, and what it looks like in production

Your ERP already holds the order data: addresses, weights, delivery requirements and the promised arrival date. An ERP shipping integration sends the shipment data needed for carrier selection, booking, labels and transport documents to a shipping platform, then returns delivery information to the ERP.

What moves between the ERP and the carriers

Across ERP systems, the basic data exchange is the same.

• Order and shipment data goes out. The sales order or delivery document leaves the ERP with everything a carrier booking needs: addresses, weights, service requirements.
• Carrier work happens in the shipping platform. Carrier and service selection, booking against your carrier contracts, and label and document production are handled in multi-carrier shipping software rather than in the ERP itself. The platform maintains rate logic, carrier connections and compliance documents centrally, instead of each being rebuilt inside every ERP.
• Labels and documents return to the packing flow. They print where the parcel is handled, so warehouse teams stay in one physical process.
• Delivery information comes back. Tracking numbers and status updates return to the ERP, and customer service answers delivery questions from the system they already use instead of logging into carrier portals.

Where the connector also returns cost data, finance can reconcile freight charges against the same shipment record used by customer service.

Centralizing the carrier work also changes how maintenance is handled. Carriers change their own requirements on their own schedule: label formats, service codes, customs data fields, API versions. When those connections are maintained in the shipping platform, carrier-side changes are handled there instead of becoming change requests against ERP customizations. The ERP-to-platform interface can remain unchanged as carrier requirements change.

What changes from ERP to ERP

Connector coverage depends on the ERP family, version and delivery model. Dynamics, SAP, NetSuite and Visma each have different version coverage and delivery partners.

Microsoft Dynamics spans Business Central, Finance & Operations, NAV and AX. Certified partner connectors cover all four, providing a connector path across legacy and current Dynamics versions. The Dynamics shipping integration page maps the connectors and partners per version.

SAP integrations are typically delivered by SAP specialists. Gold and Silver certified partners build and maintain the connections, and one certified add-on handles booking and label printing inside SAP screens via the SAP spool. Our SAP shipping integration page includes a 12-minute demo of that flow and the partner directory for SAP ERP, Business One and SAP WMS.

NetSuite keeps orders, inventory and finance in one cloud record, and the shipping connector is co-developed by nShift and a certified partner. Cost and tracking data returns to NetSuite, so finance reconciles freight against the same record customer service reads. Read all about our NetSuite shipping integration.

Visma coverage spans eight systems, including Visma Business, Visma.net and the Swedish small-business lines. Integrations are available across the major Visma lines, delivered by specialist partners, Visma group companies and, for Visma.net, nShift directly. Discover the coverage per system here: Visma shipping integration.

These four are part of a wider ecosystem of 450+ integrations across ecommerce platforms, ERP, WMS and payment providers; the ERP integration directory lists the full ERP list with certification levels and delivering partners.

How cloud ERP changes the carrier integration

In cloud ERP setups, order data passes to the shipping platform for booking and label production, while tracking and cost data are returned to the ERP. Business Central, NetSuite and Visma.net are the cloud examples among the four families above.

Cloud ERP releases are controlled by the vendor, so the connector maintainer has to keep pace. Confirm who owns compatibility with new ERP releases before implementation.

Labels and customs documents still need to print at the packing station. The integration therefore needs to route output from the cloud ERP to the correct local printer without a separate workflow for each carrier.

What happens to shipping when the ERP migrates

With a separate carrier layer, the shipping setup can remain in place while the ERP is replaced. Carrier contracts, shipping rules, label flows and tracking feeds remain configured in the shipping platform, so the ERP-side connection can be repointed without rebuilding the carrier configuration.

SAP has committed to mainstream maintenance for the core applications of SAP Business Suite 7, the ECC generation, until the end of 2027, with optional extended maintenance running to the end of 2030. The pace of the move is public, too: DSAG, the German-speaking SAP user group, surveyed its members for its 2026 investment report, and Constellation Research reports that 37% plan to complete the S/4HANA move by 2027 while 49% plan to extend ECC maintenance and finish by 2030. Dynamics deployments span NAV and AX alongside Business Central and Finance & Operations. And in the Visma family, Visma.net is the cloud option for companies moving from on-premise Visma systems.

The migration path differs by ERP. Dynamics connectors cover Business Central, Finance & Operations, NAV and AX, so the carrier configuration can be retained while the ERP-side connector changes. For Business Central, there is also a documented path for moving the shipping platform from on-premises to cloud. Visma integrations cover both on-premise products and Visma.net. The certified SAP integrations documented here are for classic SAP ERP, so migration planning should be agreed with the delivering partner.

Our customer OJ Electronics is a great production example: the Danish manufacturer of HVAC control systems connected nShift to Dynamics AX during its ERP migration and moved freight selection from packer memory to shipping rules that automatically select the lowest-cost or fastest freight option according to defined criteria.

Before an ERP migration, confirm which connector versions are supported today and after go-live. If both are covered, the carrier configuration may not need to be rebuilt.

Who builds the integration, and who maintains it

Buyers often assume one model: the software vendor ships a connector, you install it. In practice, ERP shipping integrations are delivered in several ways, and the model determines who owns support, upgrades and carrier connectivity.

• Partner-built connectors are the most common route. An integration specialist builds and maintains the ERP side under its own product and support terms, and the shipping platform provider maintains the carrier connections centrally. Certification programs exist to validate that split: an nShift Gold or Silver certification, for example, reflects validated integration quality and joint delivery experience, not just a listing.
• Vendor-delivered integrations exist where the ERP maker builds on the shipping platform itself. In the Visma family, several integrations are held by Visma group companies.
• Directly delivered setups are configured by the shipping platform's own consultants. For Visma.net, nShift documents this route end to end: ordered through nShift, configured by an nShift technical consultant, with labels printed from Visma.net and prices and shipment numbers sent back.

With a partner-built connector, connector support goes to the partner and carrier support to the shipping platform provider. The party maintaining the ERP side is also responsible for keeping it compatible with ERP upgrades and migrations.

Get the owner of the ERP connector, the carrier connection and the support boundary between them in writing before the project starts.

What it looks like in production

JYSK, the global home retailer with 3,000+ stores in more than 50 countries, has used nShift Ship since 2010. Sixteen years in production spans several generations of carrier requirements, handled in the platform rather than rebuilt in the ERP. The platform prints labels, transmits EDI and books carriers across its e-commerce shipping operation, and the SAP integration lets JYSK check deliveries against the delivery promise made to customers. The full story covers the warehouse side too.

Unilever Sweden ships around 800 pallets a day to major retailers, inside delivery windows as narrow as 30 minutes. Its transport management system setup automates shipment tracking, and delivery reporting is sent to Unilever's SAP system as a nightly file, letting the team verify timing, status and carrier performance without manual data entry. The Unilever story has the detail.

Motoral, a Finnish auto parts wholesaler, ships roughly 300 parcels a day from Dynamics AX through nShift Ship, 60 of them dangerous goods. The company chose to automate its entire dangerous-goods shipping process through the platform, and its warehouse employees label, document and book shipments in one flow instead of working across separate carrier systems. The Motoral story has the detail on the compliance side.

Solar Screen, a Luxembourg manufacturer shipping around 25,000 orders a year through NetSuite, reports onboarding new carriers about three times quicker than before, with one interface to maintain instead of one per carrier.

Scoping your own evaluation

Ask the integration questions before contracts are signed. In Panorama Consulting's 2026 ERP Report, more than a quarter of organizations exceeded their ERP project budget, and the leading cause was additional technology needs discovered once the project was under way. Use the questions below to define the shipping requirements before implementation.

1. Which ERP and which version? Coverage differs within a family, not just between vendors. Dynamics alone spans four versions with different connectors per version, and Visma is eight systems with different depth per line. Record the exact ERP product and version in scope.
2. Who builds and maintains each side? Get the split in writing: ERP side, shipping side, carrier connections. The certification level tells you how much of that work has been validated in joint deliveries.
3. What comes back into the ERP? Tracking links, status events, costs. The exact set depends on the connector and product, so ask against your workflows, not in general: walk a customer-service delivery question and a freight-cost check through the data the connector returns, and see whether each team gets the data it needs.
4. Which shipping product is behind the connector? Connectors target specific products, and the product determines carrier library, markets and operational fit. Two connectors to the same ERP can connect to different shipping products with different carrier coverage and operational scope.
5. If a migration is on the roadmap, does the coverage span both ends? The version you run today and the version you are moving to. Check support for both the current and target ERP versions.

Browse our ERP integration directory to check ERP coverage and certified partners. For a specific setup, bring the current ERP version and, if a migration is planned, the target version as well.