Information to provide
Share the systems, API documentation, required fields, sample records without customer secrets, update frequency and intended workflow. Identify which team owns orders, stock, labels and transport status.
Custom logistics API & system integration
Connect commerce, warehouse and transport workflows across China–US trade and US domestic fulfilment. Design the order, inventory and shipment data handovers around the agreed operation.
China–US & US domestic logistics
Service scope
01
Map SKU, order, purchase order, parcel and stock references between your shop, ERP, OMS or WMS and the agreed logistics workflow.
02
Define inbound and dispatch messages, inventory updates, assigned tracking references, delivery events and exception notifications.
03
Coordinate customs-document data and agreed billing or payment-status messages where the authorised systems support them.
Service arrangements
Agree the actual endpoints, permissions, data processing scope, authentication, mapping, retries, test environment and go-live checks. Confirm the working connection and supported events before relying on automatic updates.
How does this differ from USPS API support?
USPS merchant integration focuses on the selected carrier’s label and dispatch workflow. A custom logistics integration can connect the wider order, stock and transport process, with the actual systems and permissions agreed separately.
Related services
All logistics servicesPreparation tools
Discuss your requirements
Speak to our team about your goods, route and operating requirements.
Order-system connection preparation
Do I need a file transfer or a platform connection?
Share a sample order file or your platform requirements. We will agree the fields, order references, update process and dispatch feedback; any platform or API connection needs an agreed implementation.
What should a trial check before live orders are connected?
Use an agreed sample of products and orders. Check normal and changed orders, SKU mapping, stock differences and dispatch feedback on both sides, then confirm the working process.
What should I retain when an order does not import?
Keep the source order reference, expected fields, time of the attempt, last successful transfer and relevant logs. Use the agreed support route to identify the stage that needs attention.
Stock that is available to dispatch
Does stock at a location always mean it can fulfil an order?
Confirm which location may dispatch each order. Physical stock, reserved items and stock approved for release need separate records, together with any transfer or handling instructions.
Can several channels use the same stock?
Start with a consistent SKU map and agreed inventory ownership. Confirm allocation, order handover and update responsibilities before using the stock across channels.
Is receiving the same as making stock available?
Receiving and quantity reconciliation come first. Review any differences and required checks, then approve the stock for its agreed next use.
Kits, components and packing versions
What should a kitting instruction include?
List the kit SKU, component SKUs, quantities per kit, materials, packing version and requested checks. Confirm the batch and release instructions before assembly.
How should shared components be allocated?
Identify the stock available for single items and each kit or batch. Agree the reservation and update process with the stock owner before releasing components.
Can a production batch retain each customer order?
Keep the batch summary linked to the original order references. Confirm how received units will be allocated, packed and released for each customer order.