Keeping Square POS and Shopify Inventory in Sync
Short answer: Pick one system as the master for stock counts, usually the tool where most of your physical sales happen, and let the other system follow it. Match products by SKU or barcode, never by name. Expect a short delay between a sale in one channel and the count changing in the other, and plan for it with a small reserved buffer on fast sellers. Run a weekly drift check on your best sellers, because even a good sync can leave a few counts wrong after a refund, a return or a manual adjustment.
Choose the master first
Two systems that both change stock will eventually disagree. The fix is to decide which one holds the truth. For most shops with a counter, the point-of-sale system is the better master, because most sales and receipts pass through it, and staff adjust counts there when a box is damaged or a sample leaves the shop.
Write the decision down. Under that rule, every sale, return, transfer and adjustment is recorded in the master first. The second system only receives updates. Staff should never edit the online count directly, because that edit will be overwritten or will create a conflict the next time the sync runs.
Native connection or an app?
You have two broad ways to connect the systems. The first is a connection built by a platform or a partner app, which pushes counts through an API. The second is a middle-layer app that reads from both systems and writes updates in both directions. Check the current documentation on each platform's developer and help pages, because which integrations are supported, and on which plan, changes over time.
When you compare options, ask four questions:
- Does it sync in one direction only, or both? Two-way sync is more useful, but it is also where conflicts happen.
- How does it match products? Look for SKU and barcode matching.
- What happens to variants, such as size and colour? Confirm that each variant is matched separately.
- What is the stated delay between systems? Get the number in writing from the provider, not from a sales page.
Matching products and variants
Most drift starts with matching. A product named "Linen Shirt" in Square and "Linen Shirt - Blue / M" in Shopify looks like the same item to a person, but to a sync tool it may be two products. Set up a single identifier before you connect anything. The SKU is best, because it is unique and can print on a label. Use the barcode for items that already carry one.
For variants, check that every size and colour has its own SKU in both systems. A shirt in four sizes and three colours should be twelve matched lines, not one parent product with an unmatched child. Export both catalogues to a spreadsheet and check that the SKU columns match before you turn on sync.
The sync delay and overselling
Sync is rarely instant. A sale in the shop may reach the online count after a few seconds or a few minutes, depending on the connector and how busy the systems are. During that gap, an online customer can buy the last unit that has already sold in store.
Here is a simple example. A candle shop has one jar of its best-selling scent left. A customer buys it in the shop at 14:02. The online count still shows one for two minutes. Someone orders the same jar at 14:03. The shop now owes an apology and a refund.
The usual protection is a buffer. For fast sellers, reserve a unit or two online, so the website shows zero when the true stock is one or two. For example, if the candle shop keeps one jar in reserve, the website shows the product as sold out with a single unit left in the shop. Buffers cost a little revenue on slow days, but they remove most of the cost of an oversell.
A weekly drift check
Even a healthy sync drifts. A refund processed in one system but not the other, a manual edit made under pressure, or a failed update during an outage can leave counts wrong. A weekly check on your top sellers catches drift before it causes a cancellation.
- Export the stock counts from both systems for your top 20 SKUs.
- Compare the two columns in a spreadsheet and mark any difference.
- Count the real stock on the shelf for each mismatch.
- Correct the master count first, then let the sync push the fix to the second system.
- Note the cause of each mismatch: a refund, a return, a damaged item, or an unknown reason.
If the same SKU shows drift two weeks running, check its matching, its variant mapping, and whether a staff member edits it by hand.
Handling returns and transfers
Returns are where drift starts most often. A customer brings back an online order to the shop, and the staff member records a refund in the till but never marks the item as returned in the stock system. Write a simple rule: returns always go through the master system, even when the original sale came from the website. Transfers between shops, if you run more than one, follow the same rule.
A short staff routine
Staff need only three habits. Sell and adjust stock in the master system. Never edit the online count by hand. Report any sold-out item that still shows as available online. Put these rules on the back-office wall, because they are easier to follow than a long policy document.
FAQ
Which system should be the master?
Usually the point-of-sale system, because most physical sales and adjustments happen there. If most of your revenue is online, reverse that choice, but keep the rule consistent.
Do we need a paid app to sync?
Not always. Native connections can be enough for a simple catalogue. Check which plan each option requires, and whether it supports your variants and your number of locations, before you assume an app is necessary.
How big should the buffer be?
Start with one unit on any product that sells more than a few times a week, then adjust after a month of sales data. Buffers should be small and reviewed often, not a permanent hiding place for stock you cannot find.
What if the counts disagree again next week?
Work back through the drift check: confirm the SKU matching, check the variant mapping, and look at the refund and return routine. Repeated drift on the same product usually points to one of those three causes.
If you would like us to set up the matching, the buffer rules and the weekly check for your shop, tell us which tools you use and how many locations you run, and we will take it from there: reach out.