# Keep another system in sync with orders, products and stock

> Keep another system in sync with orders, products and stock: 2 companies fully do it, 16 with a limit, 20 carry the tag. Every listing in Commerce & checkout with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/commerce.store-sync/
- Markdown: https://www.anchorterminal.com/niches/commerce.store-sync/index.md (~1,600 tokens)
- Slim: https://www.anchorterminal.com/niches/commerce.store-sync/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/commerce.store-sync/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 16 | 20 | 9 | 4 |

## What counts as done

Every order, product or stock change reflected in the second system, with none missed when a webhook is dropped (a reconciliation read finds it).

Measured, for our own tests: in a 24-hour test window, each change is reflected within 5 minutes.

How agents ask for it: sync new orders into our CRM; update stock from the warehouse feed; tell me when an order is refunded; keep our product copy current

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **commercetools (commercetools GmbH)**: create_subscriptions pushes change messages to a queue and read_messages lets a reconciler read missed changes, but no delivery-time bound was read.
- **Spree Commerce (Vendo Connect Inc)**: Webhooks on order, payment, fulfilment, product and stock events retry 5 times over about six minutes with a stable event id, and the docs tell integrations to reconcile from the Admin API.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Adobe Commerce (Magento) (Adobe Inc.)**: No webhook or events page is in the web API docs repository read; events and webhooks live in separate Adobe Commerce extension docs not opened this run.
- **BigCommerce API + MCP (Commerce.com US, Inc.)**: Webhooks cover order created, updated, status, refund and transaction, product, inventory and shipment, with retries; the event page documents no reconciliation query for missed events.
- **Commerce Layer API + MCP (Commerce Layer, Inc.)**: Webhooks fire on orders.place, pay, refund, cancel, fulfill and more, retry up to 10 times and can be retriggered, but no delivery-time bound is stated.
- **Ecwid by Lightspeed (Ecwid, Inc.)**: Webhooks fire for order, product, category, customer and promotion created, updated and deleted, retrying for 24 hours on a widening schedule, so a dropped event can land hours late; updatedFrom search reconciles.
- **Elastic Path API + MCP (Elastic Path Software Inc.)**: Integrations send store events to external systems with job and delivery logs, but the event list and retry rules were not readable.
- **Fabric (Commerce Fabric, Inc.)**: OMS webhooks fire on order created, confirmed, shipped, cancelled and returned, and the API searches event logs and retries deliveries for reconciliation, but no delivery timing or automatic retry schedule is documented.
- **Medusa API + MCP (MedusaJS, Inc.)**: Sync runs on in-process event subscribers such as order.placed rather than hosted webhooks; an open issue shows a subscriber handling order.placed twice and creating duplicates.
- **Saleor API + MCP (Saleor Commerce sp. z o.o.)**: Webhooks cover order created, paid, fulfilled, refunded, cancelled, product and stock updates and voucher events; no reconciliation guidance was read.
- **Shopify API + MCP (Shopify Inc.)**: Order webhooks carry full current state, retry 8 times over 4 hours, and get_order is documented for reconciling missed ones. An account shows a stale updated_at on products/update dropping real changes.
- **Shopware (shopware AG)**: App webhooks subscribe to entity-written events such as order.written and state-machine events, but the guide documents no retry or reconciliation behaviour, and a 6.7 patch release stopped sending some events (per the last assessment).
- **Snipcart API + MCP (Snipcart inc.)**: Webhooks fire on order completed, status, payment status, tracking and refund created, with mode Live or Test; retry and reconciliation behaviour was not read.
- **Square (Block, Inc.)**: webhooksubscriptions and events services exist for notifications and reconciliation, but topics were not read (the webhooks reference is closed by robots.txt), and agent orders carry no distinct source.
- **Swell (Swell Commerce Corp.)**: Webhooks and functions run on store events and GET /events reconciles from the events log, but retry behaviour was not read.
- **Vendure (Elevantiq GmbH)**: No outbound webhook was found in the MCP or tool docs; sync runs on EventBus subscribers in plugin code, with list_orders filtering by updatedAt for reconciliation.
- **Wix Stores and eCommerce API (Wix.com Ltd.)**: Order created, updated and canceled and refund-completed events exist, but no reconciliation guidance was read.
- **WooCommerce API + MCP (WooCommerce, Inc.)**: Webhooks fire on order, product and customer events, but are disabled after 5 failed deliveries by default and no reconciliation pattern is documented.

- not this job: Agentzon (Merit Systems Inc (agentzon.co terms); Merit Systems, Inc. (merit.systems terms)): No webhooks or change feed; the docs say to poll an order only while payment is pending.
- not this job: doola MCP (doola): No webhooks or store data to sync.

## What stops agents finishing

- no webhook for a status change, so the agent must poll
- webhook payload timestamps that break change detection

## Around it

Before: commerce.cart-to-checkout, commerce.catalogue-edit. After: crm.upsert-record, notifications.push.

## Where this comes from

Weight 9 of 100 in Commerce & checkout: 4 of 49 accounts (Shopify forum, ecbot issue, Hacker News); raised slightly because webhooks are a buyer check and back-office use is under-sampled

As data: https://www.anchorterminal.com/api/v1/use-cases/commerce.store-sync.json, or the MCP tool get_use_case with id commerce.store-sync. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
