For shipments starting at a few hundred: ERP integration, checklist, test cases
For most e-commerce merchants, an API-first integration or proven middleware is the most effective way to achieve a functioning ERP shipping integration. Both approaches automate label creation, tracking data feedback, and inventory reconciliation without requiring employees to manually enter shipments into multiple systems. Which option is best depends on IT resources and shipping volume. The next section explains how to make this decision.
In short:
- For small shippers, a plugin is usually sufficient, while larger companies with multiple carriers should rely on middleware or API-first solutions.
- Successful integration depends heavily on a clearly defined project scope, stakeholder coordination, and thorough testing, not just on the technology.
- Incorrect master data such as dimensions, weight, customs tariffs or address formats are the most common causes of faulty labels and delayed customs processing.
- The operational process must ensure the direct creation of labels from the ERP system as well as automatic tracking feedback to avoid media breaks.
- Automated consistency between ERP and shipping data significantly reduces manual effort, error rates, and shipping time.
Table of Contents
- What integration approaches exist for ERP and shipping?
- Project checklist: Scope, stakeholders, schedule, budget, acceptance
- Why do many integrations fail due to master data quality?
- How do carrier workflows work for label printing and tracking?
- How do you test the integration before going live?
- What is the ROI of an ERP shipping integration?
- What data is synchronized between ERP and shipping?
- International Parcel as a practical option for shipping integration
- Sources
What integration approaches exist for ERP and shipping?
Four architectures occur in practice, and each has a clear area of application.
- Plugin or ConnectorA pre-built module connects ERP and parcel service directly, without additional server infrastructure. Solutions like this Shipping module for Sage 100 This approach demonstrates this well. Low implementation effort, but limited adaptability for special processes.
- API-firstDirect interfaces between ERP and shipping platform, usually via REST APIs. High initial development effort, but maximum flexibility for individual workflows.
- File or batch integrationData exchange occurs via CSV or XML files at fixed intervals. This is inexpensive to implement, but unsuitable for companies with high transmission volumes and a need for real-time data.
For smaller shippers with a few hundred shipments per month, a plugin is often sufficient. Growing companies with multiple carriers and international target markets are better off with middleware or an API-first approach because standardized connections To ensure long-term release capability and prevent individual, isolated solutions from failing precisely where carriers change their interfaces.
Project checklist: Scope, stakeholders, schedule, budget, acceptance
Integration projects rarely fail due to technical issues, but rather due to a lack of prior coordination. Five points need to be addressed before the first developer begins work.
- Define scopeWhich ERP modules, which carriers (DHL, UPS, FedEx, DPD, DB Schenker) and which international target markets are affected?
- Identify stakeholdersIT provides the interfaces, logistics defines processes, accounting checks invoice data, and the carrier delivers technical documentation.
- Plan pilot projectA test period of a few weeks with a single carrier and a limited product group will uncover most problems before the full rollout begins.
- Calculate budget: Licensing costs for middleware, development hours for individual mappings and onboarding effort with each new carrier.
- Define KPIsError rate in labels, time-to-ship and WISMO requests (“Where Is My Order”) are the three key performance indicators by which success can be objectively measured.
Pro tip: Define the KPI baseline before the integration goes live. Without a benchmark from the old process environment, the effect of automation will be difficult to demonstrate later.
A realistic timeline typically anticipates several weeks for the pilot phase, while the full rollout depends heavily on the number of carriers and can take several months.
Why do many integrations fail due to master data quality?
The technology often works perfectly. The problems arise from incorrect weights, inaccurate measurements, and address formats that the carrier does not accept.
Four fields cause the most errors in practice:
- measurements and weight: Deviations between system value and actual package lead to recalculations or rejected labels.
- HS codeIf the customs tariff code is missing or incorrectly entered, customs clearance for international shipments is significantly delayed.
- Address formatsPackstations, international postal code schemes and a lack of house number separation are classic sources of error.
- mandatory fieldsEmail address and phone number for tracking notifications are often missing in older ERP records.
Poor master data demonstrably leads to increased error rates in [the process/application]. label printingAnd these errors quickly add up to manual rework, negating the actual automation. Therefore, before going live, define a single source of truth for each data field, usually the ERP system, and specify who is responsible for any discrepancies.
How do carrier workflows work for label printing and tracking?
The operational process determines whether the integration works in everyday life or is circumvented in practice.
- Labels should be triggered directly from the ERP or merchandise management system, without switching to a separate carrier portal.
- Tracking feedback works via webhooks (carrier actively reports) or polling (system queries periodically); webhooks provide faster updates but are technically more demanding to set up.
- Returns and same-day cancellations require a separate process because a printed label cannot simply be deleted.
- Manifest and end-of-day requirements vary by carrier; some require a daily collection manifest before packages are picked up.
These media breaks between label, customs document and tracking data record are eliminated with a functioning ERP connection, because all three data points remain automatically synchronized.
How do you test the integration before going live?
A phased testing plan prevents errors from only being noticed during mass production.
- Sandbox tests: Generate test labels in the carrier test system and compare them with the provider's actual portal.
- Cover critical test casesInternational shipments with customs documents, dangerous goods labeling, parcel locker addresses and returns must be included in the test catalog.
- Implement error handlingRetry logic for failed API calls, a dead-letter queue for permanently unprocessable mailings, and alerting when a threshold is exceeded.
- Step by step to becoming productive: First one carrier and one warehouse, then gradually add more locations and shipping partners.
Pro tip: Set up a dashboard for label error rate and time-to-print, with automatic alerts as soon as a threshold is exceeded. This way, a problem is detected before it affects hundreds of shipments, instead of only afterward.
Sandbox access for label testing is now standard for larger carrier add-ons, making pilot projects significantly less risky.
What is the ROI of an ERP shipping integration?
The economic effect is evident in three areas simultaneously: less manual time per shipment, fewer errors in addresses and customs documents, and a shorter lead time from order receipt to shipping label.
The exact savings amount depends heavily on the starting point. Those who currently manually transfer every shipment to a carrier portal will see the greatest effect immediately after going live. Standardized connections also reduce costs. long-term maintenance costsBecause carrier updates need to be implemented centrally, rather than individually in each isolated system. Therefore, define a baseline before starting the project: current error rate, current time-to-ship, current personnel costs per hundred shipments. Without this initial value, it will be difficult to demonstrate the actual benefits later.
What data is synchronized between ERP and shipping?
Four data categories typically migrate between the ERP system and the shipping platform, and each has its own requirements for being up-to-date.
Orders Data flows from the ERP system to the shipping platform as soon as an order is ready for shipment, including recipient address, item details and desired shipping method. Shipment data They run in the opposite direction: tracking number, carrier, estimated delivery date and status changes automatically update the order status in the ERP. stocks The number of items shipped must be reduced in real time or near real time; otherwise, the online shop will sell items that have already physically left the warehouse. Invoices Customs documents such as pro forma invoices are generated from the ERP master data and must exactly match the items actually packed, otherwise customs clearance will be delayed.
With real-time synchronization, these four data streams run in seconds, usually via webhooks or direct API calls. Interval synchronization, for example every 15 minutes or hourly, is sufficient for companies with lower data volumes and reduces the system load. For ERP integration with automated order, inventory, and invoice synchronization, the manual post-processing effort is significantly reduced because employees no longer need to manually compare status queries between systems. For documents with many attachments, such as consolidated invoices or certificates, structured data extraction from PDF files helps to correctly import even unstructured documents into the system.
International Parcel as a practical option for shipping integration
For those who don't want to build the entire technical implementation themselves, Paket International offers a ready-made alternative to in-house development. The platform connects ERP and online shop systems via API and plugins with common parcel services such as DHL, UPS, FedEx, DPD, and DB Schenker, automatically calculates shipping costs and customs fees, and handles customs clearance without manual paperwork.
This reduces precisely the risks that are most time-consuming in a traditional integration project: incorrect customs documents, inconsistent carrier connections, and manual rework for international shipments. A central dashboard allows shipping managers to monitor all shipments, while proactive customer service provides support for customs inquiries. This is especially beneficial when... International shipping with customs clearanceWherein Bulky goods or when Shipping of machines The difference to self-integration becomes clear because these cases are often inadequately represented in standard connectors.
Anyone who wants to check how their own ERP landscape can be connected will find information on the Integration page of Paket International an overview of available connections, including the Xentral Integration For users of this system. The next step is a non-binding inquiry via the contact page to specifically assess the effort required for your own system landscape.