Minimum access
The pilot requests only what the workflow needs: fulfillment write, assigned fulfillment orders, location read, and product read for linking store products to warehouse SKUs. Customer delivery data is processed only for fulfillment.
SHOPIFY FULFILLMENT SERVICE · DEVELOPMENT PILOT
The embedded app connects fulfillment orders assigned to Woolii with the existing China receiving, inventory routing, supplier forwarding, packing, dispatch and tracking operation. It is being validated on approved development stores and is not yet publicly listed.
CHANNEL BOUNDARY
Shopify owns installation, merchant requests and the fulfillment-order view. Woolii owns the operational record and physical handoffs. The adapter normalizes one channel contract into the same backend used by WooCommerce, Merchant API and manual merchant orders.
Shopify-managed installation with session-token authentication
GraphQL Admin API only; no legacy REST order workflow
Only fulfillment orders assigned to the Woolii location
Live SKU, route and account checks before acceptance
Tracking returned to Shopify after real warehouse dispatch
The pilot requests only what the workflow needs: fulfillment write, assigned fulfillment orders, location read, and product read for linking store products to warehouse SKUs. Customer delivery data is processed only for fulfillment.
Stocked lines, supplier-forwarded lines and mixed orders use the same fail-closed Woolii routing rules instead of a Shopify-specific inventory cache.
Installation remains limited to approved test merchants until protected-customer-data review, callback reliability and real production fulfillment evidence are complete.
PILOT QUALIFICATION
Development-store access is limited to existing Woolii merchant accounts with mapped SKUs, an active operations route and a named technical owner.
PILOT OPERATIONS
Approved pilot merchants can follow the connection checklist and diagnose a failed pipeline station without bypassing queue idempotency or operator audit.