Bidirectional sync
Push and pull in both directions between stores, or run one-way from a master store, chosen per connection rather than as a global setting.
One pool of stock, several places selling from it. Stock Sync Bridge keeps quantities aligned across Shopify stores, locations, your ERP and supplier feeds, with rules for who wins a conflict.
Stock Sync Bridge connects a source of truth for inventory to every place that sells from it. That source can be one Shopify store, a specific location, an ERP, or a supplier CSV dropped on an FTP server. When a quantity changes, the app pushes the new number to the connected destinations according to the rules you set, including a safety buffer so you never sell the last unit twice. Every change is written to a log with the before and after values.
Push and pull in both directions between stores, or run one-way from a master store, chosen per connection rather than as a global setting.
Match products by SKU, barcode or a manual mapping table when the same item is listed under different codes in different systems.
Hold back a fixed quantity or a percentage per SKU or per channel, so a busy sale on one store does not oversell your wholesale commitments.
React to Shopify inventory webhooks for near-real-time updates, and run scheduled full reconciliations to catch anything the event stream missed.
Define which system wins when two sources disagree, whether that is the master store, the lowest quantity, or the most recent timestamp.
Ingest CSV files over FTP, SFTP or a URL, map the columns once, and turn a supplier's stock file into live availability on your storefront.
Connect your stores, locations and external sources, and nominate which one is the master.
Map SKUs across systems, resolving mismatches with barcode matching or a manual mapping table.
Set buffer quantities, sync direction and conflict rules per connection, then run a dry-run sync.
Enable live syncing and monitor the log for mapping gaps, feed failures or rejected updates.
Cancelling an order because the item was already sold elsewhere costs a customer, not just a sale. Shared stock levels remove that failure mode.
Nobody spends the morning copying quantities between spreadsheets and admin screens, which is where most inventory errors originate anyway.
Launching a second storefront for a different market or currency stops being an inventory problem, so the decision is purely commercial.
List items you do not physically hold, backed by a supplier feed and a safety buffer, and widen the catalog without buying inventory upfront.
[PRICE] per month. Two connected stores or locations, SKU-based mapping and scheduled syncs on a capped SKU count.
[PRICE] per month. More connections and SKUs, webhook-triggered syncs, buffer rules, conflict handling and supplier CSV feeds.
[PRICE] per month. Large catalogs, ERP connections, custom mapping logic, extended log retention and priority support.
Webhook-triggered updates typically propagate within seconds, subject to Shopify API rate limits on large catalogs. Scheduled reconciliations run on the interval you choose and are there as a safety net rather than the primary mechanism, so the two work together.
Barcode matching catches most of it. Anything left over goes into an unmapped list where you can pair items manually or upload a mapping CSV. The app will not guess at a match, because a wrong mapping silently corrupts stock across every connected system.
If your ERP exposes an API or can produce a scheduled file export, yes. We have connected inventory to accounting and ERP systems as part of our ERP work. Send us the system name and available integration options and we will scope it.
Failures are logged with the SKU, the source, the destination and the error, and retried on a backoff schedule. You can set alerts so a feed that stops arriving, or a run with an unusual number of rejections, reaches your team the same day.
We will map your SKUs, set the sync rules and run a dry-run before anything goes live.