Create codes

Paste a line, or drop an invoice. Nothing is written until you submit.

⌘

Resolution results appear here Each line runs three phases: does the code exist → does the taxonomy exist → what are the specifications.

Item master

The working master. Edits here change fields, never codes.

All items

Every head

	Code	Item / group path	UoM	Status	ERP ready	Actions

0 selected

Item Group Edit

Heads, sub-heads and groups — the 7-letter identity behind every code, and the spec slots each group carries.

All groups

Every head

Approvals

Push / deactivate / group-change requests waiting on a manager or admin decision, and what happened to every request that has already been decided.

	Kind	Payload	Requested by	When	Status

0 selected

Admin

Usage, flagged codes, pending approvals and failed pushes at a glance; system toggles, manual backup and the ERPNext health check.

Codes per person (last 8 weeks)

Flagged codes per person

Failed pushes (30d)

Users

System toggles

Anomalies

Everything the master currently disagrees with itself — or with ERPNext — about. Nothing here changes on its own; each finding names the rows and the decision someone has to make.

◷

Scanning the ledger… Every head, sub-head, group, item and ERPNext code is compared.

Activity

Field-level before and after for every save, filterable by person, item and date — with Revert on each entry. Which codes were re-issued and which numbers come next follow below.

When	Who	Item	What changed	Matched by

Re-issued codes

Old	New	Reason	By

Next free group number

Next	Sub-head	Freed by	When

Next free item position

Next	Group	Freed by	When