Product variant inventory is reconciled when the physical count and the store's recorded quantity agree for the same variant, location, and inventory state. A product-level total can look correct while individual sizes, colors, or packs are wrong, so reconcile the exact sellable variant rather than the parent product.
Freeze the comparison point
Choose a low-activity window and record the count start time. Pause avoidable receiving, transfers, bulk imports, and manual adjustments while the count is open. If sales must continue, keep the transaction timestamps so movements during the count can be separated from the physical quantity. Export the current inventory before editing anything. That preserves the original system count and gives you a rollback and audit reference.
Match the same variant, location, and state
Build the count sheet from stable identifiers such as SKU, barcode, or platform variant ID. Include product name, option values, location, system quantity, physical quantity, and variance. Do not combine two sizes because they share a product page. Shopify displays inventory states for each product or variant and distinguishes quantities such as on hand, available, committed, unavailable, and incoming. Compare like with like: a physical shelf count should not be matched blindly to an available quantity that already subtracts committed units.
Count and recount exceptions
Have the counter enter the observed quantity without seeing the expected number when practical. Calculate the variance after the first pass. Recount material differences with a second person or a fresh scan, checking nearby bins, returns, damaged goods, open orders, receiving areas, and transfers. Confirm that the barcode resolves to the intended variant and location.
Square's variance reporting compares counted inventory with recorded inventory and can export both item-level variance data and a count summary containing counters, reviewers, and timestamps. Whether or not your system has that report, preserve the same evidence: who counted, who reviewed, when the session began and ended, and which variants changed.
Explain the variance before adjusting
Classify each confirmed mismatch with a reason such as unrecorded receiving, damage, return, transfer, fulfillment error, wrong variant scan, or unexplained shrinkage. Review adjustment history and orders near the count time. A reason should describe the event, not merely say correction. If the cause is unresolved, label it unresolved and assign follow-up rather than inventing certainty.
Post a controlled correction
Only an authorized inventory user should post the physical count or adjustment. Apply it at the variant and location level, use the platform's adjustment reason, and retain the before quantity, counted quantity, change, reviewer, and supporting note. Square documents that physical counts represent verified quantities for an item variation at a location, while computed counts reflect adjustments since the prior physical count. The distinction is useful: the physical count resets the known point, but the history still matters for preventing recurrence.
Verify every selling surface
After the correction, reopen the inventory view and confirm the saved quantity and state. Test the storefront or point of sale for one corrected in-stock variant and one sold-out variant. Check that reservations, open orders, bundles, and connected sales channels did not immediately recreate the mismatch. Save the final variance report and schedule a shorter follow-up count for high-risk variants.
A complete reconciliation ends with matching counts, documented reasons, an approved adjustment trail, and a verification that customers see the intended availability.
Sources: Shopify inventory states, Square inventory variance reports, and Square inventory model.
Sources
- Understanding inventory states — Shopify Help Center
- View and export inventory variance report — Square Support Center
- Inventory API — Square Developer Documentation