Tutorial
Set up your organization before the first import
The order of setup that causes the least rework: units agreed, roles at least access, one small file first.
About 10 minutes. Last reviewed against the product on .
Ten minutes of setup decides whether everything after it is comparable. This is the order that causes the least rework.
1. Create the organization before importing anything
Every purchase record is stamped with an organization, and imports land in whichever one you are in. Importing first and organising later means moving data between boundaries, which this site deliberately does not do.
2. Decide your unit conventions now
3. Add people with the least access that works
| Person | Usually needs | Why not more |
|---|---|---|
| Owner | Owner | Someone has to administer it |
| Head chef | Member | Imports and costs, no account administration |
| Accountant | Viewer | Reads everything, changes nothing |
| Supplier rep | No access | They do not need your other suppliers' prices |
Measured from the role checks in src/lib/auth.
4. Import one small file first
Not the biggest one. A twenty-line file tells you whether your column names are understood in under a minute, and fixing a mapping on twenty rows is a different job from fixing it on four thousand.
Check the import contract first if your export has unusual column names.
5. Only then import the backlog
By now your units are agreed, your roles are set and your columns are understood, so the backlog lands once instead of twice.