Stock imports need verified codes, locations and count units
Move a photographed count sheet into a CSV that you can review and map to an inventory import. Preserve item and location identifiers as text, and resolve count-unit differences before any file is used to update stock.
Preparing a cycle-count import
Recover sheet entries, verify the bin and SKU mapping, and adapt the reviewed columns to the inventory system’s import template.
Combining counts from separate locations
Add verified location context to reviewed files before combining them, keeping identical SKUs from different bins distinguishable.
Prepare count-sheet rows for your system’s template
- Capture the whole count table with its location and unit labels.
- Correct codes, handwritten counts and any rows affected by strike-through marks.
- Export CSV, match the target template and review the proposed stock changes separately.
Leading-zero SKUs, mixed units and crossed-out stock counts
- Does inventory sheet to CSV overwrite stock quantities?
- No. It produces a downloadable file. Updating inventory is a separate operation in your own system after validation.
- How do I preserve SKUs with leading zeros in CSV?
- Review the extracted characters and configure the destination importer to treat SKU fields as text rather than numbers.
- Can case counts and individual units share one quantity column?
- Only if their meaning remains explicit. Keep a unit column or normalize quantities yourself using verified pack sizes before an inventory import.
- Will crossed-out counts be interpreted as the corrected value?
- Recognition may read either mark or both. Check each correction against the original sheet and confirm the intended quantity manually.
