Setting Up QuantX Ops: The Readiness Checklist and the Org Import

The usual ERP implementation story involves consultants and a quarter. QuantX Ops is built so that a company can set itself up.

What you already have on day one

A new company is not an empty database. It arrives with:

Already configured	Count
Chart of accounts, with posting rules wired up	31 accounts
Document numbering series	20
Approval workflows, ready to use	11
Permission sets (duty roles)	12
Grades and designations	8 and 10
Salary components	6
Leave types, shifts, weekly off	3, 2 and 1
Units of measure	33

What it cannot know is anything specific to you: your people, your customers, your catalogue, your salaries, your tax registration. That is what setup is.

The checklist counts; it does not remember

Every line is recomputed each time the page opens. There is no "setup complete" tick to go stale — delete your last shift and attendance starts telling you it needs one again. Each line says why it matters and what it holds up, and links to the screen that fixes it.

The org import: one row per seat

Building an org chart a person at a time is slow. The import takes the whole thing from one spreadsheet — and it is keyed on seats, not people, which is what lets it express two things a staff list cannot: a vacancy, and a reporting line that survives somebody leaving.

The preview is not an estimate

Upload the file and QuantX Ops performs the real import inside a transaction, then rolls it back and shows you exactly what would happen. Every problem is reported at once, each naming the line number you can see in your own spreadsheet, so one pass through the file is enough. And the whole file is refused if anything is wrong — a half-imported org chart is worse than none, because approvals route into a tree with holes in it.

Related: why the seat holds the org chart.