Integration should preserve the order's meaning

Connecting a China parcel warehouse to Shopify, eBay or WooCommerce is more than importing addresses and exporting tracking numbers. The connection must preserve which items are authorized for release, which quantities went in each parcel and which fulfillment record belongs to that parcel. A successful API response is useful evidence of a system update; it is not proof of physical dispatch.

Begin with an order-state map agreed by the merchant and warehouse. Identify paid, held, canceled, partially fulfilled, released and dispatched states. Define who can change each state and how a change received after packing is handled. Avoid treating every newly visible order as permission to ship.

Keep platform identifiers beside warehouse identifiers

Store the platform order and line-item IDs, the warehouse order, SKU mapping and the parcel identity. Display names alone are weak keys: a merchant can edit a product name without changing the underlying variant. Preserve quantities and any bundle-component mapping so a partial shipment cannot accidentally close an entire order.

Validate destination fields, phone requirements and service eligibility before label purchase. Keep customs descriptions, material data and values in controlled product or shipment fields. Do not scrape a promotional product title into a customs description without checking that it identifies the goods accurately.

Shopify: fulfill the intended location and items

Shopify's fulfillmentCreate documentation describes creating a fulfillment from fulfillment orders, with item selection, tracking information and notification preferences. The documented operation groups fulfillment orders associated with the same order and assigned location. Your integration must respect that assignment rather than assuming every order belongs to the China warehouse.

Be explicit about line items. The documentation notes that omitting item selection can fulfill all items in the fulfillment order. A split parcel or backorder therefore needs a deliberate quantity map. Read returned user errors and retain the resulting fulfillment identifier before considering the platform update complete.

Keep notification control with the merchant's approved workflow. A warehouse test should not send a real customer a dispatch email. Verify both the stored tracking information and the intended customer view in a safe test order before live activation.

eBay: map the contents of each package

The eBay order-management guide explains shipping fulfillments for packages, including tracking when labels are not purchased through eBay. Associate the correct line items and quantities with each package and retain the fulfillment record returned by the platform.

Do not send one carton number as though it covers every item in a multi-parcel order. Check supported carrier identifiers and tracking format. When an update fails, retrieve the current package records before retrying; otherwise an uncertain network response can lead to duplicate updates or contradictory tracking.

WooCommerce: verify the actual extension and version

WooCommerce installations can differ by extensions and custom code. Its Shipment Tracking documentation describes adding provider, tracking number, link and shipped date, and displaying those details to customers. That capability belongs to the documented extension and configuration, not every possible store installation.

Agree which fields or supported interface the connector uses. Test the order screen, account page and email behavior in the installed version. A tracking value stored in an unrelated custom field may look successful to middleware while remaining invisible to the buyer.

Test failures before the first real release

Run a paid order, a held order, cancellation before packing, cancellation after label creation, partial shipment, multi-parcel order and corrected tracking number through the whole flow. Test repeated notifications and delayed updates. Each case should produce one explainable inventory and shipment result.

Use stable event identities or equivalent deduplication controls in the implementation. If a request times out, reconcile platform state before resubmitting an operation whose result is uncertain. Keep a failed-update queue with an owner; a hidden retry loop is not an exception process.

Finally reconcile three counts: released order quantities, physically accepted parcels and platform fulfillment quantities. Differences should be visible and actionable. A good integration lets support trace a buyer's item from authorization to a specific package without guessing which system's status is the truth.

Sources and verification links

Operational rules can change. Check the linked primary sources and confirm shipment-specific requirements before booking.