Ecommerce and ERP stock sync: what to require
To sync inventory between an ecommerce platform and an ERP, first define who calculates sellable stock, when a unit is reserved and how a failed update is recovered. Then compare an existing connector with a custom integration. Copying quantities between two screens is not enough: the scope must cover your inventory rules and operational exceptions.
The decision is how to maintain availability, not publish products
This guide is for operations and IT teams selling through an online store and other channels while an existing ERP manages inventory. The problem is not writing descriptions or creating a catalog: it is preventing reserved, returned or transferred units from being offered as available by mistake.
If you need to create and publish product listings, that is a different scope: our ecommerce product onboarding guide covers that workflow. You do not need AI to copy a number. Inventory synchronization needs explicit rules, stable identifiers and concurrency controls; a language model should not decide how many units to sell.
Buy a verifiable workflow: from a real inventory movement to the published available quantity, with evidence of what was applied and what remains pending. Do not accept a promise of real-time updates without a definition of latency, channels and behavior when a system stops responding.
Define what stock means for each channel
Physical stock is not always sellable stock. Separate units on hand, committed to orders, temporarily reserved, held for inspection and in transit. Decide which locations each channel can draw from and who can release a reservation. If you sell kits, define how their components are deducted.
For example, Tiendanube's inventory guide covers inventory locations and levels. That does not mean your ERP uses the same rules: the supplier needs to provide a mapping of variants, locations and availability before writing quantities. A single total can hide a mismatch between warehouses.
Assign one authority per data item. The ERP may own physical quantities while the store owns an order's status, but do not let both overwrite the same availability independently. The design must also account for reservations that have not reached the ERP yet: a correct value read a few minutes ago may put a newly committed unit back on sale.
Existing connector or custom integration
Start with a connector already offered for your ERP or ecommerce platform if it supports your variants, locations, reservations and order states. Ask for a demonstration of those rules, not just a list of compatible logos. A quantity-sync connector may be sufficient for a simple operation but not cover kits, multiple warehouses or orders awaiting approval.
Custom integration makes sense when a specific exception remains unsolved: stock allocation by channel, movements originating outside the store, an ERP with a particular interface or an operational recovery workflow missing from the connector. Separate what the products already do from what must be built and maintained.
Do not budget only for the first connection. Check API access, usage limits, required plans, version changes, monitoring and error ownership. The automation budgeting guide distinguishes implementation from ongoing operation; pricing this workflow requires verifying its systems and rules.
What happens when an event arrives twice or arrives late
An event notification is not a transaction spanning all your systems. Shopify documents that webhook ordering is not guaranteed, and its delivery guidance covers duplicate events. An integration must recognize processed events, avoid deducting twice and detect stale updates before replacing a newer state.
A retry after an unavailable system must retain the operation's identity. This is idempotency: repeating the same operation should not deduct stock again. You also need periodic reconciliation against the destination, with differences recorded in a visible queue. Receiving a webhook is not proof that the ERP applied its change.
As an example of concurrency protection, Shopify's quantity-setting API warns about concurrent writes and supports comparison with the previous quantity. This is not a universal recipe or permission to overwrite inventory: the implementer must use each system's current mechanism and test simultaneous updates. Sources checked on November 16, 2026.
The last-unit test
Hypothetical example: two channels display one available unit and receive orders almost simultaneously. If both accept before coordinating a reservation, later synchronization cannot undo the promise to the customer. Ask the supplier to demonstrate what prevents, detects or contains this situation and how an exception is handled if it still occurs.
Options depend on the platforms: reserve centrally before confirmation, allocate separate channel quotas or keep a safety buffer. Each option has an operational cost. A quota may reduce overselling risk while leaving units unavailable on the channel with demand. No responsible zero-overselling guarantee can omit how every order gets confirmed.
Agree explicitly on whether selling without stock is allowed. Do not confuse an authorized preorder with a synchronization error. When a connection fails, decide whether the channel keeps the last quantity, limits availability or requires review. Do not leave that decision until an incident.
Acceptance tests to include in the proposal
These are suggested tests, not results from a client project. Run them in a test environment or with controlled, authorized transactions, recording origin, destination, time and expected result. The business owner must approve the rules alongside technical validation.
| Test | Scenario | Expected result |
|---|---|---|
| Duplicate event | The same reservation arrives twice | It is applied once, with a trace of the duplicate. |
| Simultaneous orders | Two channels attempt to take the last unit | The agreed reservation, quota or exception policy is visible; conflicts are not hidden. |
| Late notification | An old quantity arrives after a new one | Stale stock is not restored without detecting and resolving the conflict. |
| Cancellation and return | An order is cancelled or an item is returned | Stock is released or held according to state and physical condition, without adding twice. |
| ERP outage | The store takes orders while the ERP is unavailable | Pending work is visible, selling policy is defined and recovery is reconciled. |
| Unknown variant or location | An SKU arrives without a mapping | It is not assigned to a different product; an owned exception is recorded. |
What to bring to a supplier conversation
List your systems and versions, channels, locations, variants and reservation rules. Include anonymized examples of a sale, cancellation, return and manual adjustment, identifying who determines availability at each step. You do not need to send credentials or complete databases for an initial conversation.
Ask the proposal to identify the authority for each data item, included and excluded flows, latency targets and measurement, duplicate protection, reconciliation, alerts, support ownership and acceptance criteria. Distinguish deployment from validated operation: one successful API response is not completion.
Duotach offers automation and system integration. If you need to evaluate a connection between your ecommerce platform and ERP, tell us which systems you use and where inventory falls out of sync today. The inquiry starts a scope conversation; it does not imply universal connector availability or a diagnostic deliverable before an agreement.
Frequently asked questions
Does syncing more frequently eliminate overselling?+
Do I need to replace my ERP?+
Does this require artificial intelligence?+
Discuss your integration
Tell us which systems you use and which inventory rule needs to be addressed.
