Inventory mismatches between your ERP and Shopify are not just an inconvenience. They are a direct threat to revenue, customer trust, and marketplace standing. When your Shopify storefront shows a product as available but your warehouse is empty, you oversell. When your ERP has stock but Shopify shows zero, you lose sales. Both scenarios erode the reliability that customers and marketplace platforms expect.

This guide breaks down the practical architecture of real-time inventory sync, covering the states that cause confusion, the sync patterns that prevent drift, and the operational monitoring that catches problems before customers do.

The Five Inventory States That Get Mixed Up

Most sync failures trace back to a fundamental misunderstanding: inventory is not a single number. Your ERP tracks multiple states, and each one means something different.

On-hand quantity is the total physical stock in your warehouse. Available quantity is what can actually be sold right now. Reserved quantity is stock allocated to existing orders that have not shipped yet. Incoming quantity represents purchase orders or transfers that have not arrived. Safety stock is a buffer you maintain to absorb demand spikes or supply delays.

The number Shopify cares about is "available," and it is calculated: on-hand minus reserved minus safety stock. If your integration blindly pushes on-hand to Shopify, you will oversell because that number includes stock already promised to other orders. If you subtract too aggressively, you will show items as out of stock when they are actually available.

Getting this calculation right, and keeping it right across every sync cycle, is the core challenge of inventory integration.

Shopify Inventory Fundamentals

Shopify tracks inventory at the intersection of two dimensions: inventory item and location. Every variant in your catalog has an associated inventory item, and each inventory item has a quantity at each location where you sell or fulfill.

This means a single SKU can have different available quantities at different warehouses, stores, or fulfillment centers. Your integration must account for this: pushing a single aggregate number when Shopify expects per-location data will break multi-location fulfillment and confuse your operations team.

The Shopify inventory API allows you to set or adjust quantities per item per location. The "set" approach overwrites the current value. The "adjust" approach increments or decrements. Choose wisely: "set" is safer for full reconciliation syncs, while "adjust" works for real-time event-driven updates where you know exactly what changed.

Recommended Sync Patterns

The right pattern depends on which system is your source of truth for inventory.

In the ERP-as-source-of-truth model, the ERP owns all inventory data. Changes flow one direction: from ERP to Shopify. This is the simplest and most reliable pattern. Your integration reads inventory states from the ERP, calculates the available quantity using the formula above, and pushes updates to Shopify. Shopify never writes back.

In the Shopify-as-source-of-truth model, Shopify owns inventory because it handles POS transactions or direct fulfillment. The ERP receives updates from Shopify. This is less common but necessary for some retail businesses.

The hybrid model is the most complex but also the most realistic for omnichannel merchants. Both systems can modify inventory (ERP from warehouse operations, Shopify from POS sales), and a reconciliation layer ensures they stay aligned. This requires conflict resolution rules and regular full syncs to catch drift.

Galantis Connect supports all three patterns through configurable rules. You define which system is authoritative per location or per product category, and the platform enforces those rules automatically.

Handling Multi-Location, Bundles, and Kits

Multi-location inventory adds a dimension of complexity. Each Shopify location needs its own inventory level, and your ERP may organize warehouses differently. The mapping between ERP warehouse codes and Shopify location IDs must be explicit and maintained as either system adds or removes locations.

Bundles and kits present a different challenge. A bundle product in Shopify may not exist as a single item in your ERP. Instead, it represents a collection of component SKUs. The available quantity of the bundle is limited by the least-available component. Your integration must calculate this dynamically and update the bundle's Shopify inventory whenever any component changes.

Galantis Connect handles bundle inventory through its rules engine. You define bundle composition, and the platform automatically calculates availability from component inventory levels, updating Shopify in real time.

Preventing Race Conditions

Race conditions are the silent killer of inventory accuracy. They occur when two systems try to update the same inventory record simultaneously, and the final state depends on which update lands last.

Common scenarios include an ERP batch update running at the same time as Shopify processes a sale, or two marketplace channels both decrementing the same SKU within milliseconds. Without proper safeguards, one update overwrites the other, and inventory drifts.

Prevention strategies include using Shopify's inventory "adjust" endpoint instead of "set" for real-time decrements, implementing optimistic locking where updates include the expected current value, processing inventory updates through a single serialized queue per SKU, and using idempotency keys to ensure retried operations do not double-count.

Rate limits add another constraint. Shopify's API has call limits, and aggressive sync patterns can exhaust them. Design your sync to batch updates efficiently and use bulk endpoints where available.

Operational Monitoring

Even a perfectly designed sync will drift over time. APIs fail, webhooks get dropped, network partitions happen. The question is not whether drift will occur but how quickly you detect and correct it.

Set up automated alerts when inventory deviation between ERP and Shopify exceeds a threshold per SKU. Run a full reconciliation at least daily, comparing total quantities across all locations. Monitor sync latency: if updates are taking longer than expected, investigate before the backlog becomes a problem.

Track your retry success rate. If retries are consistently failing, the underlying issue is systemic, not transient. Log every sync operation with enough detail to diagnose problems after the fact: timestamps, quantities before and after, source system, and any transformation rules that were applied.

Galantis Connect provides all of this through its built-in monitoring dashboard. You see real-time sync status per flow, drill into individual records, and configure alerts on deviation thresholds, all without building custom monitoring infrastructure.

Ready to stop overselling? See a sample inventory mapping template or book a call with our integration team to review your current sync architecture.