No pre-approval API keys
Registration creates a login, not a merchant account. Approval creates and activates the merchant account before sandbox or production keys can be managed.
WOOCOMMERCE · SHOPIFY PILOT · MERCHANT API · OPTIONAL MCP
Every channel enters the same merchant workflow.
Whichever route you pick, orders land in the same merchant-scoped record: supplier parcels are received and forwarded, stocked lines reserve merchant-owned inventory, and mixed orders wait for a recorded decision. The WooCommerce plugin is free on WordPress.org. The separate Shopify app remains in approved development-store validation and is not generally available. Custom systems use Merchant API V1.
V1 / EARLY ACCESSapproval-gated merchant access
PICK AN ENTRY POINT
Start where your stack already is.
WooliiPorter Fulfillment for WooCommerce
A free WooCommerce connector to Woolii-operated fulfillment in China, listed on WordPress.org. Smart routing sends stocked lines to warehouse dispatch, supplier-direct lines to parcel forwarding, and mixed orders to a recorded merchant decision, version 0.5.1.
WooCommerce fulfillment from ChinaMerchant API V1
For custom storefronts, ERPs and internal tools. Idempotent orders, structured value-added services, packed quotes, line-item settlement and HMAC-signed webhooks.
Read the API documentationShopify fulfillment-service pilot
An embedded fulfillment-service app using assigned fulfillment orders, Shopify-managed installation, session tokens and GraphQL Admin API. Currently limited to approved development-store validation.
Review the pilot scopeStandalone MCP server
Optional. Exposes the supported Merchant API subset to an external agent you deliberately connect with a merchant API key. Not required by, and not part of, the WooCommerce plugin.
Review the agent surfaceCONTRACT PRINCIPLES
Idempotent orders, signed events, hard isolation.
V1 is built for teams — and agents — that automate carefully: a safe retry returns the original response instead of a duplicate order, and a resource ID alone is never enough to read data.
Stored-response replay on operations explicitly marked idempotent
Signed webhooks (HMAC over the raw body) with immutable event IDs
At-least-once delivery your receiver can deduplicate
Per-merchant keys, explicit scopes and visible sandbox/production execution mode
Estimates always distinguished from final packed quotes
V1 SURFACE
The complete merchant operation surface, route by route.
The documented V1 covers Store connection and WooCommerce fulfillment intents, pre-order estimates, direct forwarding, value-added services, packed quotes, line-item settlement, pay-per-shipment, tracking and signed events — plus optional SKU registration, typed inbound workflows, ledger-computed inventory, fulfillment orders, warehouse transfers and monthly statements. The standalone MCP server exposes the supported agent subset.
connectionv1storev1fulfillment_intentv1supplier_parcelv1estimatev1order_prealertv1vas_requestv1packed_quotev1settlementv1trackingv1timelinev1webhook_eventv1skuv1inbound_shipmentv1inventoryv1fulfillment_orderv1transfer_orderv1statementv1HONEST BOUNDARIES
What we do not claim
No procurement
The API never buys from suppliers or handles the purchase payment — you own the supplier relationship.
No public Shopify listing yet
The Shopify fulfillment-service app is not represented as App Store approved. The separate Shopify app remains in approved development-store validation and is not generally available.
No forced stocking
Stocking and dropship fulfillment exist in V1 — but as an option. Pass-through forwarding never requires inventory, and stocked goods remain merchant-owned with ledger-based storage billing.
INTEGRATION QUALIFICATION
Start with data ownership and the merchant use case.
We review the systems, technical owner, webhook owner, proposed data flows and sandbox readiness before enabling early-access integration tools.