How to replace inventory spreadsheets with a multi-warehouse stock system (without losing a unit)

"The spreadsheet says we have twelve, the shelf says three, and the customer has already paid." Most trading and distribution businesses reach this point sooner or later. Stock lives in a shared workbook, each warehouse keeps its own tab, the shop updates it at the end of the day (when it remembers), and reordering depends on whoever happens to notice an empty bin.

This guide is for owners and operations managers who want to move off spreadsheets and onto one stock system, and for agencies doing that move for a client. It uses Inventra, our self-hosted inventory and ERP platform, but the checklist works whatever you choose.

Why spreadsheets stop working

Spreadsheets are fine for one location and a few dozen products. They break down when:

• More than one person sells the same stock. The shop, a field rep and a wholesale order can all promise the last unit, because nobody sees the others' sales in time.
• Stock moves between locations. Goods on a truck are in neither warehouse, so they quietly disappear from the count.
• Cost matters. A quantity column says nothing about what the stock cost you, which batch expires first, or what you made on each sale.
• Nobody can say why a number changed. A cell gets overwritten and the history is gone.

What good looks like

Whatever system you pick, check it for these five things:

1. Every change is recorded. You can see why on-hand went from 12 to 3, who did it and against which document.
2. Available stock is honest. What a channel can promise is on-hand minus what is already allocated, minus a safety buffer.
3. Locations are first-class. Warehouses, shops and 3PLs each have their own stock, bins and rules, and in-transit stock is tracked.
4. Reordering is automatic. The system drafts a purchase order when stock falls to the reorder point.
5. The money follows the stock. Receipts, dispatches and invoices post to the books without re-keying.

Inventra is built on these ideas. Every stock change writes a movement to an append-only ledger with its value change, reference document, bin, batch and serials, and stock updates run inside database transactions so two orders cannot take the same unit.

Step-by-step: moving off the spreadsheet

1. Map your locations first

Before importing a single product, set up your network on the Facilities & bins page. Each facility has a type (central warehouse, fulfilment centre, retail shop or 3PL), a tax jurisdiction, a local currency, opening hours and fulfilment rules: whether it ships, offers store pickup or accepts transfers, and its routing priority. Add bins where you use them. Stock that arrives without a bin waits in an UNBINNED staging area until someone puts it away, so nothing gets lost during the switch.

2. Import products and opening stock

You do not have to retype the workbook. Every main module header (Products, Sales orders, Vendors, Customers, Staff & attendance and Shipments) has Download sample and AI Import buttons.

1. Click Download sample to get the CSV or XLSX layout, or open the Guide for the file rules.
2. Upload your spreadsheet, or a PDF, a photo of a stock sheet or pasted text.
3. Review the staged rows in the grid. Each row shows a confidence badge (green at 90% or more, amber at 70–89%, red below 70%), and you can edit cells inline, filter to rows that need fixing and set a whole column at once.
4. Commit. The commit is all-or-nothing: if any row fails, nothing is written.

Spreadsheets are mapped by their column headers and need no AI at all. Photos, scans and messy text need an optional AI API key. If a batch turns out to be wrong, Roll back batch on the AI import page under Administration reverses it, as long as the data is not already in use.

Inventory imports match products by SKU and set stock to the counted quantity in a bin, so do a physical count the day you switch and import that count rather than the spreadsheet's number.

3. Bring in vendors and customers

Use the same import on Vendors (matched by tax ID or name) and Customers (duplicates by code, email, tax ID or name are flagged for merging). Vendor imports can also draft a purchase order per vendor, which is useful if you have open orders on the day you switch.

4. Set reorder points and safety buffers

Per product and facility you can set a safety buffer, a reorder point, a maximum stock level and a local price override. From then on:

• channels only promise Available = On-hand − Allocated − Safety buffer;
• auto-reorder drafts a PO when stock falls to the reorder point;
• an optional nightly job recalculates a dynamic reorder point from average daily sales and each vendor's measured lead time, and can suggest rebalancing transfers between facilities based on days of stock.

Start with simple fixed reorder points. Switch on the dynamic calculation once you have a few months of sales and receipts in the system.

5. Move stock with transfers, not edits

When stock goes from the warehouse to a shop, raise an internal transfer request. It is approved (the requester cannot approve their own, except an admin), dispatched with a goods transfer note, and received at the other end, partially if needed. While it is on the road it shows as in-transit, and lots, costs and serials travel with the goods.

6. Sell from the same stock

Once stock is in, every channel draws on the same numbers: sales orders with pick, pack and ship, the POS till with barcode scanning and register shifts, field reps' orders and the B2B portal for wholesale buyers (who never see cost prices). The till keeps selling through a network outage and syncs when the connection returns.

Tips and pitfalls

• Freeze the spreadsheet. Pick a cut-over day, count, import and make the old file read-only. Two sources of truth are worse than one bad one.
• Clean SKUs before importing. Matching is by SKU, so duplicates and typos in the workbook become duplicates in the system.
• Use roles from day one. Warehouse managers can be limited to their assigned warehouses and field reps to their own customers. It is easier to start strict than to tighten later.
• Use a replica set. Inventra needs MongoDB running as a replica set, because stock and ledger postings use transactions. MongoDB Atlas works out of the box.
• Try the demo first. The seeded demo business has a five-facility network, consignment and drop-ship vendors, and logins for every role.

Who it's for

Inventra suits trading, wholesale and distribution businesses with more than one location, a counter or shop, and some mix of B2B, field sales and export, plus the agencies that implement systems for them. One deployment can host many businesses, each in its own workspace. Read the Inventra case study for how the stock ledger and the books stay in agreement, or ask our web development team to set it up for you.

Next step

If your stock still lives in a spreadsheet, the move is mostly a counting and importing job, and Inventra's import review grid and rollback make it safe to try. Explore the live demo, then get the full source on the Inventra marketplace page.