A client’s supervisor said it the way a lot of people say it after a long stocktake.
“We’ve got the spreadsheet. Just overwrite the stock.”
They meant well. The physical counts were done. The differences were circled in red. Someone had already opened Products in wp-admin and was ready to type numbers in, line by line, or paste a CSV over the live catalogue.
That is exactly when an order came in for a SKU they had counted an hour earlier.
Live WooCommerce quantity dropped. The spreadsheet still showed the old expected figure next to the physical count. If they had pasted over the lot, they would have written yesterday’s story on top of a sale that had already happened.
That is why Inventory Check for WooCommerce has a conflict check — and why Update stock refuses to write those lines.
This is not the offline story
If you read The Count That Finished After the Wi-Fi Died, that piece was about keeping the count going when the warehouse signal drops, then syncing when you reconnect.
This piece is different.
Here the connection is fine. The shop is live. Orders, refunds, and the odd manual edit can change WooCommerce quantity while a stock check is still open. The danger is not a missing network. The danger is blindly overwriting a figure that moved under your feet.
Why “just overwrite” is dangerous
A stocktake is a snapshot stretched across time. You start in aisle A at nine. You finish aisle D after lunch. Meanwhile customers buy. Someone processes a refund. A manager corrects a quantity from the desk.
If your reconcile step is “paste the counted column into WooCommerce,” you treat every line as if the live shop froze when you started walking. It didn’t.
Overwrite the wrong SKU and you wipe a real sale. Or you reinstate stock that a refund already put back. Or you write a physical count that was right at ten o’clock onto a product that changed at eleven.
Spreadsheets are fine for capturing numbers. They are a blunt tool for writing those numbers into a live shop.
How the conflict check works
Inventory Check is a stocktaking app on the merchant’s own WordPress site — https://YOUR-SITE/inventory-check/ — not wp-admin and not a neilmatthews.com inventory cloud.
When a product is first counted, the plugin stores WooCommerce’s stock at that moment as the expected quantity. The counter enters the physical count. Saving a count only stores the warehouse figure. It does not change WooCommerce.
Later, on review, the app compares live WooCommerce stock to that expected value.
| Situation | Result |
|---|---|
| Live stock still matches expected | Line is ready. Update stock sets Woo qty to the physical count. |
| An order, refund, or manual edit changed stock during the check | Line is a conflict. It is not written. Recheck it. |
| Product is no longer stock-managed | Line cannot be updated. Recheck or skip. |
Counters can count and review. Only a supervisor, Shop Manager, or Administrator sees Update stock and can confirm the write. Ready lines go through. Conflicts stay for a recheck — then review again.
That is the safe reconcile path. Not paste. Not “trust the spreadsheet column.” Confirm what is still safe to write, and stop on what isn’t.
What “just overwrite” would have done that day
On the client day, the SKU that sold mid-count showed up under Conflicts on review.
Expected (when counted) no longer matched live. The physical count was still useful — it told us what was on the shelf when they walked past — but it was not safe to slam that number into WooCommerce without looking again.
They rechecked the bin. Confirmed the shelf. Reviewed once more. Then Update stock wrote the lines that were still ready and left nothing to chance on the conflicted SKU.
Nobody spent the afternoon untangling “who overwrote the order.”
What this is — and is not
Inventory Check is a stocktake tool, not a warehouse-management system. It does not replace a WMS. It does not change WooCommerce stock until someone with the right role confirms Update stock.
Product and count data stay on your WordPress site. There is no hosted inventory service from me.
And the plugin is fully free. There is no paid edition. Search, barcode scan, offline counting and sync, conflict detection, review, safe update, CSV export, and audit history are all included.
Conflict check is not a premium unlock. It is part of how the free plugin refuses to be reckless with a live shop.
Wrap Up
If an order or refund changes quantity while your stocktake is open, do not “just overwrite the stock.”
Start a check at /inventory-check/. Count what is on the shelf. Review differences. Let a supervisor confirm Update stock. Ready lines write. Conflicts wait for a recheck.
Docs and setup: Inventory Check for WooCommerce. Install from the WordPress.org plugin directory.
Need a hand?
If you want Inventory Check installed and dry-run on your Woo shop — including a quick mid-count conflict walkthrough — hire me. Fixed-price quote, no obligation. Or install the free plugin from WordPress.org and walk it yourself.
Written by Connie, an AI, from Neil Matthews’ notes, archive, and direction. Neil directed and edited this piece. He did not write these words. Augmented publishing by Neil Matthews.