Check expected stock before a proposed overwrite
Compare proposed inventory changes with a fresh CSV snapshot by exact SKU and location. Flag missing baselines and stale starting quantities.
How can I check whether a stock update uses a stale quantity?
Compare the quantity the update expects with a freshly exported quantity for the same SKU and location. Stock Guard blocks its comparison when the baseline is blank, the SKU/location is absent from the snapshot, or expected and fresh quantities differ.
Input requirements and report limits ↓Inputs
Copy a table from Excel or Google Sheets, including its header row, and paste it below. CSV/TSV files also work. Use “Map your columns” for different headers. IDs stay as text.
Free: UTF-8 CSV/TSV · 200 KB / 500 rows per input · 5 successful reviews per browser per day. CSV calculations run locally.
Need larger files or repeat batches? View editions →
Reuse a column profile
A profile stores column names only. It does not store your file contents.
Review report
Before you use this review
| Bring | Proposed sku, location, expected_current, proposed_new; fresh sku, location, on_hand snapshot. |
|---|---|
| Match | Unique SKU + location in each table; compare expected_current with the fresh on_hand value. |
| Read the result | Missing baselines and stale quantities block the comparison. Delta is proposed_new minus fresh on_hand. |
| Cannot establish | Live stock after the snapshot, physical counts or a safe platform-specific inventory import. |
Required inputs
Proposed changes need sku, location, expected_current, proposed_new. The fresh snapshot needs sku, location, on_hand. Each SKU + location key must be unique. Quantities must be supported whole numbers; negative quantities are permitted within the tool's numeric limits.
Interpret the report
In a synthetic example, an update expecting 10 units against a fresh count of 8 receives a stale-snapshot block. The displayed delta is proposed new quantity minus fresh on-hand quantity, not an instruction to apply that difference.
A matched snapshot only means the two provided quantities agree. Orders after the export can make it stale again. The tool does not fetch live stock, create locations, write inventory or produce a Shopify import. Review SKU mappings separately when supplier and store identifiers differ.
Should a blank stock baseline be treated as zero?
No. Enter 0 only when your source confirms zero units. A blank expected_current value has no baseline and is blocked; a SKU/location absent from the fresh file is also blocked. Do not fill either gap with zero just to make the comparison pass.
Is proposed_new an adjustment or a replacement quantity?
It is the proposed final quantity, not an amount to add. For example, expected stock 10, fresh stock 10 and proposed_new 12 produce a delta of 2. The report does not apply that adjustment. Export a fresh snapshot again if stock may have changed before your actual update.
Prepared by Supplier Desk Team · Updated . Examples are synthetic.
Who this is for
Small retail and wholesale operations teams reviewing supplier exports before changing catalog, stock or purchasing records. This is a focused review worksheet; it does not connect to your store or post transactions.
Related background
Read the source discussion or documentation. This describes the broader workflow. Use the input requirements and calculation rules above to decide whether this particular check fits your task.
Free tools with optional offline batch editions. Higher file limits, saved batch configurations and grouped report exports. No automatic store changes.