CSV inventory import
Leaving the spreadsheet should not require retyping the spreadsheet.
CSV is a practical bridge between an existing stock sheet and a shared inventory tool. Invumi supports import with a preview and validation step so teams can inspect problems before committing the data.
01
Import the fields that matter
A migration is a good moment to remove columns that nobody trusts. Product name, quantity and the operational context used by the team are more valuable than carrying years of decorative spreadsheet archaeology into a new system.
Invumi's documented template defines the expected columns and lets the import flow surface invalid rows before they become products.
02
Preview before writing
A useful import should separate reading from committing. Previewing the file gives the team a chance to catch formatting errors, missing required values or mappings that would otherwise create a cleanup job after the fact.
This is especially important when a spreadsheet has been edited manually by several people and developed its own local folklore.
03
Migrate in a small slice
There is no requirement to move the entire catalogue on day one. Start with the products that cause the most ordering friction, make the daily movement workflow reliable, then expand the catalogue once the process works.
A small successful migration creates better data than a giant import followed by six months of nobody updating it.
04
History begins after the import
The initial quantity is a starting point. The valuable history grows as the team receives stock, consumes items and performs inventory checks. That history later supports alerts and forecasting.
CSV remains useful in the other direction too: export keeps the data portable for analysis, backup or another migration.