CSV import guide
What it's for
CSV import is the fastest way to load or change many units at once — hundreds of plots at launch, or price and stage changes across a whole phase. You prepare a spreadsheet, check it with a dry run that changes nothing, and then commit. Rows whose unit already exists update that unit; new rows create units.
Before you start
- You need permission to manage inventory on the project.
- Create everything the file refers to, on the project, before importing: custom Inventory stages, Unit type / Zones, Ownership companies and, on multi-map projects, the Multi map structure sections. Unknown names fail the dry run.
- Check your plan's inventory limit; the page shows Inventory usage.
- Limits per file: 5,000 data rows and 10 MB, as
.csv.
The Upload inventory page
Open the project's Inventory tab and choose upload. The page has four tabs:
| Tab | Use it for |
| How it works | Links to the project's stages, zones, ownership companies and sections; the allowed unit_type values; the column reference |
| Upload CSV | Template download, export of current inventory, dry run and commit |
| Bulk update | Change stage, section, pricing, facing and more for a list of unit numbers. See Bulk update units |
| Remove units | Delete a list of units by number |
Import step by step
- Get a file. On Upload CSV, download the template, or Download your current inventory in import format to edit existing units.
- Fill it in following Prepare your CSV. Save as CSV (UTF-8) from Excel or Google Sheets.
- Choose the file under CSV file.
- Press Dry run. Nothing is saved. You see how many units would be updated and created, sample rows under Will be updated and Will be created, inventory usage after import, and any Import errors by row.
- Fix every error in the spreadsheet and run the dry run again until it is clean. See Dry run and commit.
- Press Commit import. A result banner shows what was created and updated, with links to the inventory list and sales layout.
How rows are matched
- A row updates the existing unit with the same
unit_number and unique_identifier (empty counts as a value). Otherwise it creates a new unit.
- Survey numbers and external IDs are never used to match rows.
- Empty cells do not clear existing values; they are left as they are.
What happens automatically
- New and updated units link to existing map shapes with the same labels — no need to republish maps.
- Stage colours on the public map and sales layout change on their next load.
- The inventory usage meter goes up by the number of units created.
- If the commit fails part way, nothing is saved; fix the file and try again.
Export
The export uses the same columns as the import, so a round trip is easy: export, edit in a spreadsheet, dry run, commit. From the inventory list, the export follows the filters you have applied. Columns for internal price and customer details are only included for users allowed to see them.
Tips and common questions
- Always run the dry run, even for small files — it catches stage-name typos before they reach live data.
- "Import affects live inventory" — committing changes real units, including prices, stages and internal notes.
- Keep
unit_number identical to the map labels, without &. Wrap values that contain commas in quotes (spreadsheets do this for you).
- Multi-map projects: read Section paths before your first import.
Related: Prepare your CSV · Dry run and commit · Inventory basics