China–UK & UK domestic logisticsGuangzhou · Hong Kong · Edinburgh
RoyalMailParcelBY JETON EXPRESS
ENESعربي
Shipment trackingChat on WhatsApp
E-commerce logistics

Custom logistics API & system integration

Connect commerce, warehouse and transport workflows across China–UK trade and UK domestic fulfilment. Design the order, inventory and shipment data handovers around the agreed operation.

Discuss your requirements
China–UK & UK 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.

Information to provide

Share the systems, API documentation, required fields, update frequency and intended workflow, with anonymised sample records that omit customer secrets. Include linked examples for the same order and order line, available identifiers for message delivery and events, the source trigger time and the local receipt time. Confirm what each field means and which identifiers and timestamps the actual interface supplies; a trigger time may differ from the physical event time. Identify which team owns orders, stock, labels and transport status.

Service arrangements

Agree the actual endpoints, permissions, data processing scope, authentication, mapping, retries, test environment and go-live checks. Before integration, define the expected result for four test cases: duplicate arrival, reversed arrival order, a missing notification, and checking the final source state after recovery. Agree who reviews mismatches and whether any follow-up action needs authorisation. Confirm the working connection and supported events before relying on automatic updates; these are proposed acceptance checks for the agreed integration.

How does this differ from Royal Mail API support?

Royal Mail 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 services

Shopify shipping integration

WooCommerce shipping integration

Merchant shipping support

Preparation tools
Weight & volume calculatorShipping document preparationCustoms preparation checklistImport duty & VAT plannerShipment tracking

Discuss your requirements

Speak to our team about your goods, route and operating requirements.

WhatsApp

How your service is quoted

Transport and handling, storage and fulfilment, packaging and returns are itemised for the services you choose. Recurring operations can be scoped together; API implementation and ongoing support have their own agreed deliverables. Your quotation sets out charging units, included work, additional charges and payment terms.

Start with the service your business needs

Share your products, shipping direction and order or stock volumes. Our team will put together the relevant service scope, quotation and handover arrangements.

Discuss this service

Connect the next step

Combine the services your goods need. Handling instructions and the scope of each step are agreed with our team.

Order fulfilment

Include warehouse order references and stock allocation in the agreed integration scope.

Returns & aftercare

Agree how return references connect with the original sale and handling records.

Related resources

Use these guides to prepare your service brief and agree the next steps.

These articles are available in English.

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.