Administration
Categories, tags, units & fields
The controlled vocabularies: category tree, tags with merging, units and conversions, conditions, reason codes, and custom fields.
Why curated vocabularies
Lists everyone picks from — categories, tags, units, conditions, reasons — only stay useful while someone curates them. All of them live under Settings, need the settings-edit permission, and share the same philosophy: reuse a value instead of creating a near-duplicate, and check usage before merging or retiring anything.
Categories
A hierarchical tree for the catalog. Categories can be reparented as the structure evolves and restored if archived by mistake — the tree drives filters, reports by category, and alert scoping.
Tags
Free-form labels for everything cross-cutting. The cure for tag sprawl is merge: consolidate synonyms into one canonical tag and every tagged record follows.
Units
The units stock is controlled in, plus conversions between them (purchase in boxes, control in pieces). Get conversions right here rather than working around them per movement — items reference these units everywhere.
Conditions and reason codes
Conditions describe stock state (new, used, damaged, refurbished…) on records and receipts. Reason codes are the mandatory explanations on adjustments, quarantines, and variances — per movement kind, in both languages. Curate reasons to what you'd actually act on in a report: "damaged in transit" is a decision input, "miscellaneous" is not.
Custom fields
Custom fields extend records with your business's attributes — typed (text, number, date, choice…), validated, searchable, and available to imports, exports, and the API. Archive fields that outlive their use; their historical values remain readable.