Authorize
Configure shop URL, supported API version, app credentials, access token, scopes, and secret rotation.
Commerce integration
The connector implements order pull, inventory and price write-back, catalog actions, OAuth onboarding, and HMAC webhook verification. Its coded Admin API version is 2024-01, so a supported-version upgrade and live-store qualification are required before production commitment.
Data contract
The supported exchange covers the objects and behavior below; additional store features and API surfaces are configured separately.
| Direction | Data | Implemented behavior |
|---|---|---|
| Shopify → XMS | Orders, customer reference, shipping address, line SKU, quantity, price, currency | Incremental REST pull using creation time, status-any scope, bounded payload reading, and per-order parse errors |
| XMS → Shopify | Inventory availability | Resolve an active Shopify location and inventory item, then set inventory by location |
| XMS → Shopify | Price and catalog changes | Variant/SKU resolution plus catalog write-back interfaces; exact store behavior requires scope qualification |
| Shopify → XMS | Webhook events | Inbound webhook contract with Shopify HMAC-SHA256 verification and event idempotency at the platform boundary |
Implementation path
Configure shop URL, supported API version, app credentials, access token, scopes, and secret rotation.
Bind Shopify variant and SKU identity to canonical product, packaging, warehouse, client, and channel records.
Replay representative orders, cancellations, partial fulfilment, location inventory, price changes, duplicates, and throttling.
Approve covered scope, monitoring, quarantine, retry, credential ownership, and rollback before enabling production write-back.
Limits and security
The current implementation names Admin API 2024-01. A supported Shopify API version and regression run are prerequisites.
Variant, inventory-item, location, canonical SKU, barcode, packaging, and client ownership must resolve without ambiguity.
Access tokens and app secrets belong in the deployment secret store; webhook signatures are verified before event processing.
Parsing, mapping, rate-limit, authorization, and external-request failures remain reviewable instead of silently dropping demand.
Compatibility review
Define read/write objects, cadence, identity, exception ownership, security, and upgrade acceptance before connection.