Why your bonded warehouse must talk to your own ERP and OMS
A China bonded warehouse holds inventory that is still owned by the overseas brand, yet the daily decisions about that inventory are made inside the brand’s own systems. The sales team watches orders in the OMS, the finance team reconciles stock value in the ERP, and the operations team plans replenishment from the same two platforms. When the bonded 3PL keeps its data inside a standalone WMS that nobody outside the warehouse can see, the brand is flying blind: it does not know the true sellable quantity, it cannot promise accurate delivery dates, and it discovers shortages only after a customer complaint. Bonded warehouse data integration is the discipline of connecting the warehouse’s WMS to the brand’s ERP and OMS so that inventory, orders and exceptions move automatically between the two sides. For cross-border models such as 1210 and 9610, where stock sits in a controlled tax regime before sale, this connection is not a convenience but the foundation of reliable fulfilment.
Three ways to connect: API, EDI and the manual spreadsheet
There are three mainstream ways to link the warehouse to the brand’s systems. The first is a real-time API, where the two systems exchange messages the moment something changes; this is the gold standard for fast-moving consumer goods. The second is EDI, an older but extremely robust message format still demanded by many large retailers and platforms; it batches structured documents such as despatches and invoices. The third is the manual spreadsheet, where a human downloads a report, edits it and uploads it somewhere else; this is cheap to start but slow and error-prone, and it should be treated as a temporary bridge rather than a permanent solution. A capable bonded 3PL supports at least API and EDI, and exposes a clear status page so the brand can see whether the link is healthy. The integration mode you choose should match your order velocity: high-velocity stores need API, steady B2B flows can live on EDI, and the spreadsheet is only for proof of concept.
Real-time inventory sync and how it prevents overselling
The single most valuable outcome of integration is real-time inventory sync. The moment a unit is received, picked, shipped or written off in the WMS, that change is pushed to the OMS so the storefront shows the corrected sellable quantity. Without this sync, the storefront keeps selling stock that the warehouse has already lost to damage, holds, or other channels, and the brand suffers overselling, cancelled orders and platform penalties. Good sync is bidirectional and event-driven: the OMS tells the warehouse what was just ordered, and the warehouse tells the OMS what was just consumed. The brand should insist on a sync latency measured in seconds or minutes, not nightly batches, because every hour of stale data is an hour in which the store can promise goods it no longer has. Real-time inventory sync protects both the customer experience and the brand’s standing with the sales platform.
Order push and status callback: the full round trip
Integration is not complete until orders make a full round trip. The OMS pushes a new order to the WMS, the warehouse picks, packs and hands the parcel to the carrier, and then the WMS sends a status callback back to the OMS with the tracking number, the shipped time and the carrier reference. This order callback is what lets the brand send the customer a real tracking link and what lets finance close the order without manual chasing. A mature integration also handles the partial shipment, the split carton and the exception hold, reporting each state back so the OMS never shows a generic “processing” for days. The round trip must be idempotent: if a message is delivered twice because of a network glitch, the system must not create a duplicate shipment or a duplicate charge. Brands should test the callback path with real samples before going live, not after the first customer complaint.
Inbound appointment and the advance shipping notice
Smooth integration starts before the goods even arrive. The brand sends an advance shipping notice, or ASN, from its ERP to the warehouse WMS before the container lands, telling the warehouse what SKUs, lots and quantities are coming and on which truck. The warehouse uses that notice to reserve put-away locations, stage labour and pre-build receiving inspection checklists. When the truck arrives, the receiving team scans against the ASN, and any discrepancy between expected and actual is flagged immediately rather than discovered during a later count. A clean ASN-to-receipt loop shortens dwell time at the dock, reduces demurrage and gives the brand an early warning when a supplier short-ships. This upstream step is often overlooked, yet it is where most downstream inventory accuracy is won or lost.
Exception handling and reconciliation when the numbers disagree
No integration is trustworthy until it explains its disagreements. When the WMS shows 980 units but the OMS expects 1,000, the system must surface the gap as an exception rather than silently picking the higher or lower number. Good integration produces a daily reconciliation report that lists every variance by SKU, owner and reason code, so a human can investigate theft, miscount, damage or a missed sync. The brand should agree upfront on who owns the truth when systems disagree, and on a time window for resolving exceptions before they harden into permanent inventory errors. Reconciliation is not a one-time setup; it is a running control that keeps the two systems honest as volumes and SKUs grow.
Data security, permissions and the audit trail
Connecting systems also connects risk. The integration must restrict who can read or write which owner’s data, especially in a multi-owner bonded warehouse where one brand must never see another’s stock. Credentials should be scoped per brand, tokens should rotate, and every message should be logged with a timestamp and a sender identity so a missing or wrong update is traceable. Sensitive fields such as cost and customer address should be masked or encrypted in transit, and the warehouse should never expose more than the brand needs to fulfil and reconcile. A clean audit trail is also what regulators and insurers ask for after an incident, so designing it in from day one is cheaper than bolting it on later.
How to evaluate a 3PL’s integration capability before you sign
Before onboarding a bonded partner, the brand should ask concrete integration questions. Can the 3PL show a live API or EDI connection to a brand with a similar SKU count? What is the typical sync latency, and what happens when the link drops? Does it support ASN, order push, status callback and a daily reconciliation feed, or only a static report? What credentials, permissions and audit logs does it provide? Will it map your SKUs to its locations without manual re-keying? A warehouse that answers these questions with specifics and a reference brand is one whose data you can trust; a warehouse that only offers a monthly spreadsheet is a warehouse that will keep you blind. Integration maturity is a leading indicator of overall fulfilment quality.
Hongshengze practice: integration is part of the service, not an add-on
At Hongshengze we treat bonded warehouse data integration as a core deliverable rather than an optional extra. Our WMS connects to the brand’s ERP and OMS through API and EDI, pushes real-time inventory sync in seconds, and returns a complete order callback with tracking and carrier reference on every shipment. We accept ASN before arrival, run a daily reconciliation feed with reason-coded variances, and isolate each brand’s data under scoped credentials with a full audit trail. The goal is simple: the brand always sees the same true inventory that the warehouse holds, the store never oversells, and every order completes its round trip without a human in the middle. For cross-border brands entering China, that visibility is what turns a bonded warehouse from a black box into a controllable node in their own supply chain.