ERP & Online store
ERP and online store show different stock levels
Different numbers do not automatically mean that a connection has failed. “Stock on hand”, “available” and “reserved” may refer to different values. First, agree which quantity the store should display and sell.
- SourceAuthoritative stock
- Check the connectionRules & Mapping
- DestinationAvailable in the store
How this appears in daily operation
The ERP still shows five units. The store shows zero, or keeps selling even though the last units are already reserved. The first useful comparison considers the same product, variant and point in time.
Distinguish typical causes
Inconsistent stock definitions
Physically present goods and goods available for sale may differ. Reservations, multiple warehouses or safety stock must be clarified in the process.
Incorrect product or variant mapping
If an identifier in the store does not map unambiguously to the ERP, a plausible value can end up on the wrong product.
Transfer interrupted by timing or business rules
A run may be delayed, miss a change or stop on an error. Simply saying “the interface is running” does not explain the specific product.
What you can check first
Select a concrete example
Record the product and variant, along with the values in both systems at the same comparison time.
Identify the authoritative value
Clarify with the business whether available stock, physical stock or another approved quantity is transferred.
Review existing transfer logs
When was this specific product last processed? Compare the feedback and destination. Do not trigger a test order in the production store.
When the problem runs deeper
Reliable synchronization needs more than a regular export. We agree which system is authoritative, how reservations are handled and what happens when mappings are missing. Event-driven transfers must also handle retries; Shopify, for example, notes that webhook deliveries may be duplicated.
A concrete example instead of an indiscriminate full synchronization
One product with one variant is often enough to reveal the existing path. Further cases, such as multiple warehouses or reversals, can then be added. The necessary cases depend on your sales process.
How this becomes a reliable process
Source, field mapping, destination and feedback are connected transparently. When an error occurs, it remains clear which value was not transferred. New synchronization is planned only after business rules are established; “real-time” is not a blanket promise.
When support makes sense
If overselling, manual corrections or recurring discrepancies cost time, reviewing the entire stock data path is worthwhile. The names of both systems and an anonymized product example are enough for an initial consultation.
The right solution pathSynchronize stock between systemsSources for technical assessment
Technical content reviewed on 7 October 2026. Vendor statements refer to the products named; they do not replace checking your specific configuration.
Clarify the next step together.
Your application names and a brief description of the problem are enough to start.
