Authenticate
Provision credentials and scopes without exposing secrets in normal operator or client surfaces.
Integrations
Connect systems without surrendering operational truth.
Normalize external orders, products, inventory, rates, labels, milestones, invoices, and machine reports into governed XMS Cloud contracts with replay and recovery.
Integration readiness
Match the connector to your exact environment.
Readiness depends on credentials, vendor edition, region, API entitlement, data scope, rate limits, and validation against representative exchanges.
AvailableAvailable with configurationAvailable through API or EDIIn qualificationPartner-deliveredPlanned
Compatibility guides
Match each interface to your systems and data flow.
Each guide names direction, protocol, prerequisites, current status, limits, security, ownership, and the validation steps used before go-live.
IN QUALIFICATION
Shopify
Orders, inventory, prices, catalog actions, OAuth, webhooks, API-version limits, and location/SKU mapping.
Review Shopify →IN QUALIFICATIONAmazon and FBA
Selling Partner orders and feeds plus the separate catalog and inbound-preparation workflow.
Review Amazon →IN QUALIFICATIONSAP S/4HANA
OData sales-order read scope, paging, watermark, mapping, auth, ship-to, and release-specific limits.
Review SAP →CONFIGURATION REQUIREDMulti-carrier labels
Rate, label, void, tracking, exact-charge commerce, account qualification, and local printing.
Review carriers →API / EDI3PL X12 EDI
X12 940, 945, 856, 214, and 997 direction, mapping, transport, acknowledgement, and replay.
Review EDI →CONFIGURATION REQUIREDAGV and AMR
Vendor fleets, VDA 5050, mission authority, reservations, acknowledgements, capability, and safety.
Review mobile robots →CONFIGURATION REQUIREDWCS and PLC
Sortation, conveyors, pick cells, packaging, Modbus, permissives, handshakes, and commissioning.
Review fixed automation →CONFIGURATION REQUIREDAccounting and billing
Invoice APIs, file rails, external identity, idempotency, correction, status, and scope boundaries.
Review accounting →Connector lifecycle
Recovery is part of every data flow.
Each integration defines authority, identity, idempotency, observability, recovery, and tenant boundaries alongside its primary exchange.
Normalize
Map external identifiers and payloads into canonical product, order, shipment, event, and finance contracts.
Execute
Submit idempotent work, record acknowledgements, and retain source and correlation evidence.
Recover
Quarantine failures, replay safely, reconcile state, rotate credentials, and audit changes.
Versioned readiness
Connector scope stays tied to version and test depth.
XMS records the adapter class, protocol, vendor version range, build, owner, lifecycle, limitations, validated scenarios, and uncovered scope.
Catalog entries map to implementations.
Each named integration links to a versioned adapter type and supported protocol.
Validation depth is explicit.
Contract conformance, emulator failure scenarios, and recorded-exchange replay are tracked as separate levels.
Uncovered scope stays visible.
Skipped scenarios, uncovered capability, artifacts, adapter build, product build, and later version drift remain visible.
Commerce and marketplaces
Bring demand in; send inventory and fulfilment back.
Merchant SKU and barcode mappings stay explicit before inbound, inventory, labels, and fulfilment depend on them. Invalid orders enter visible quarantine and correction.
Shopify and Amazon Selling Partner
Substantial order and write-back adapters exist, but the current Shopify API version and Amazon regional/feed-result behavior require upgrade or live-account qualification.
WooCommerce, PrestaShop, Magento, and eBay
Storefront API adapters for order, inventory, price, fulfilment, and status exchange. Exact scope varies by vendor version, contract, account, and recorded scenarios.
Cdiscount, Mirakl, Fnac-Darty, ManoMano, Temu, Back Market
Adapter code is cataloged, but live write paths or vendor-instance behavior still require recorded-exchange qualification before production commitment.
Custom storefront and channel API
Typed API, scoped key, webhook, polling, mapping, idempotency, quarantine, and replay pattern for channels outside the named catalog.
ERP and accounting
Connect operational evidence to financial systems.
Direction and object coverage differ by connector. Sales-invoice exchange, master data, and warehouse synchronization are scoped independently.
Microsoft Dynamics 365 Business Central and Odoo
ERP client implementations for sales-order and operational exchange through vendor APIs.
Pennylane, Cegid Loop, Sage X3, Sage Intacct, MyUnisoft
Accounting and invoice paths with vendor-specific authentication, payload, status, and retry behavior.
Qonto, Sellsy, Axonaut, Holded
Invoice and accounting integrations; exact object and write coverage is confirmed during configuration.
SAP S/4HANA
OData client implementation is present; live-tenant behavior and deployed object scope require qualification.
EDI, carriers, and transport data
Keep documents, labels, tracking, and tenders on the shipment.
EDI and carrier interfaces share the same shipment, handling-unit, milestone, proof, and financial context used by transport control.
- Available through EDI X12 940, 945, 856, 214, and 997 payload flows.
- Available with configuration Carrier rates, labels, manifests, tracking, voids, invoices, and returns.
- Available through API Telematics, webhooks, position feeds, milestone normalization, and confidence.
Automation and edge
Integrate at the correct authority boundary.
Mission APIs, fleet adapters, WCS gateways, PLC protocols, station bridges, and device-side print/scanner paths stay separate from business APIs.
FMS and vendor APIs
Canonical mission intent with vendor capability, mapping, health, and acknowledgement.
WCS and PLC gateways
Conveyors, sorters, AS/RS, doors, lifts, and machine cells through controlled OT boundaries.
Local hardware bridge
Scanners, printers, cameras, and other bench devices remain connected to warehouse stations, not the backend.
Typed API and webhook
Scoped keys, signed webhooks, idempotency, correlation, replay, and explicit support classification.
Review one interface
Bring the source payload and the operational outcome.
Map authority, identifiers, tenancy, retries, reconciliation, observability, and credential lifecycle.