Post-Holiday Shopify Stocktake Across Several Stores
After the rush, stock counts, old promo codes and rushed listings need a cleanup. A stocktake routine for several Shopify stores where every change is checked.
January is when the holiday rush leaves its marks on a catalog: hurried counts, December promo codes still active, listings written at speed. With several stores, all of that is multiplied by the number of admins.
The goal of a post-holiday cleanup is not only to fix the numbers. It is to end up with stock and catalog data you can trust again, and to know that every change you made actually landed.
Know which stock number you are comparing
Shopify tracks several inventory states for each item at each location (Shopify Help Center):
- On hand: every unit at the location.
- Committed: set aside for unfulfilled orders, draft order reservations and transfers ready to ship.
- Unavailable: for example damaged stock, a quality-control hold or safety stock.
- Incoming: on its way, not received yet.
- Available: what you can actually sell.
After the holidays, on hand and available can be far apart, because committed units for unfulfilled orders and unavailable units sit between them. When you compare the same product across stores, compare available stock, not on hand.
Find out who changed what
When a count looks wrong, the first question is who changed it. Shopify records inventory changes automatically: each product or variant has an adjustment history with the date, the activity and who made the change, whether a staff member, an app or a sales channel. It covers the last 180 days, and for older changes you use the Inventory adjustment changes report (Shopify Help Center).
With several stores, that is one history per store.
A stocktake routine for several stores
1. Count, then submit, not type straight into the live store
Counts typed into a live store go live at once, typos included. Have staff submit counts as proposed changes for review.
2. Review before and after
For each store, look at the current value next to the new one, and at how many items a change touches. A count that drops a best-seller to zero should stand out before it reaches customers.
3. Check that each change landed
“Approved” is not the same as “done”. After a change is written, check the store again and confirm it shows the new value. Anything that did not land should show as failed, with a reason.
4. Compare stores side by side
Put each SKU’s available stock in every store side by side and look for mismatches, missing SKUs and duplicates.
5. Fix differences on purpose
Some merchants have learned the hard way that a change that fans out to every store silently is the riskiest kind. If a store needs to match another, make that one change, check it and approve it, rather than letting a tool copy numbers on its own.
Tidy the catalog while you are at it
Two more holiday leftovers:
- Old promo codes. Codes from December may still be active in several stores, and nobody remembers which ones still matter. Look for active codes with almost no use and turn them off.
- Rushed listings. Products added during the rush often have weak titles or descriptions. Draft better ones and review them before they go live.
How Storefleet helps
In the Storefleet web dashboard, Inventory & Products > Stock by SKU puts each SKU’s available stock in every store side by side, read live, with Mismatch, Missing and Duplicate badges and a filter for only mismatched or missing SKUs. Nothing changes on its own: Storefleet has no automatic cross-store sync, and every cross-store change is chosen and approved by a person. To fix a mismatch, Match another shop sets one store’s available quantity to match another’s, and that change goes through approval like any other stock edit.
Stock edits are sent for approval (“Sent for approval. Stock hasn’t changed yet.”), with a Before and After, the number of objects affected, and a badge for changes that can’t be undone. After an approved change is written, Storefleet reads the store back from Shopify and only marks an item applied when Shopify shows the new value. Approved changes go into the Ledger, with who asked, who approved and the before and after, filterable across your stores.
If a stock change was wrong, it can be rolled back where Shopify allows it. Stock set and discount create, update, activate and deactivate can be rolled back; refunds, cancels, captures, discount deletes and bulk codes cannot.
With StoreFleet Agent (Mac preview / early access), the AI Store Ops agents can take on part of this routine: a low stock check that proposes adjustments, a discount check that proposes turning off codes with almost no use, and a catalog check that drafts SEO fixes. Each one asks before anything changes. For the wider question of shared products across stores, see how to keep inventory in step across multiple Shopify stores.
Summary
Compare available stock, not on hand. Submit counts instead of typing them into live stores, check that each change landed, and fix differences one deliberate change at a time.
Install Storefleet Store Ops on Shopify and start the year with stock you can trust.