Orders and channel updates
Pull orders and lines, resolve participating marketplaces, then publish inventory, pricing, and fulfilment feeds.
Marketplace and fulfilment integration
Connect Amazon demand without confusing marketplace and FBA scope.
In qualification
XMS Cloud implements Amazon Selling Partner API order pull plus inventory, price, and fulfilment feeds. Its current connector defaults to the North America endpoint, so regional endpoint, authorization, marketplace, feed-result, and live-account qualification are required for European production.
Two connected scopes
Marketplace synchronization and FBA preparation are not the same interface.
Product and inbound readiness
Map merchant and canonical SKUs, packaging, lot/serial/expiry rules, cartons, pallets, labels, booking, documents, and discrepancies.
No unsupported Seller Central promise
FBA shipment-plan, placement, appointment, compliance, and Amazon-native label APIs require explicit contract evidence before being claimed.
Implemented exchange
Keep feeds and physical work on one order context.
| Direction | Data | Current implementation |
|---|---|---|
| Amazon → XMS | Marketplace participation, orders, buyer reference, shipping address, items, quantity, price, currency | CreatedAfter order pull with separate order-item retrieval and bounded parsing |
| XMS → Amazon | Inventory availability | Feeds API document creation, pre-signed upload, and inventory-availability feed submission |
| XMS → Amazon | Product pricing | Pricing XML feed through feed-document upload and POST_PRODUCT_PRICING_DATA submission |
| XMS → Amazon | Fulfilment status | Order-fulfilment XML feed with carrier/tracking context from the canonical shipment |
Prerequisites and limits
Qualify region, authorization, and feed outcome.
Endpoint must match marketplaces
The coded default is the North America Selling Partner endpoint. EU and other regions require explicit endpoint configuration and regression.
Seller and SP-API access
Seller identity, app registration, access token, marketplace participation, roles, scopes, rotation, and revocation must be configured.
Submission is not acceptance
A successful feed POST is not proof that Amazon processed every record; processing reports and reconciliation must close the loop.
SKU and packaging governance
Amazon SKU, merchant SKU, ASIN/FNSKU where used, barcode, canonical product, packaging, and prep rules need an approved crosswalk.
Client-owned preparation
Prepare stock before it reaches the warehouse.
The merchant workspace lets clients maintain catalog mappings and versioned inbound plans while warehouse receipt, quality, location, and discrepancy truth remain operator-owned.
- Canonical and merchant identity before label or receipt.
- Versioned cartons, pallets, documents, and expected arrival.
- Visible mapping issues, receiving state, and discrepancies.
Compatibility review
Bring the seller region, marketplaces, authorization, product identity, and FBA workflow.
Separate covered SP-API objects from FBA preparation and define feed-result reconciliation before production.