📦 Material management

material management in mantsu defines how materials are organized, tracked, and linked within the system it is structured around four main objects material class → material → batch → sub batch 🔹 material class identified by a unique id supports multi language descriptions (english is mandatory) shows all linked materials can be archived and restored (not deleted) includes audit trail creator, last update, timestamp 🔹 material identified by a unique id linked to one or more material classes has a base unit of measurement (uom) supports uom conversion tables (defined in settings) always start from base uom build a conversion table (e g , kg → g, kg → lbs) supports multi language descriptions (english mandatory) shows linked batches in the material screen archivable with audit trail 🔹 batch identified by a unique id linked to one specific material (mandatory) contains a quantity (mandatory) and a uom (from material) has a status (e g , blocked, unblocked → defined in settings) can be linked to a location (from location management) can contain multiple sub batches archivable with audit trail 🔹 sub batch identified by a unique id linked to a batch (mandatory) contains a quantity , uom , and status includes a type (defined in settings, e g , bag , box ) uom could still be kg , while type specifies bag of 25kg can be linked to a location archivable with audit trail 💡 key principles archive only no deletion, everything can be archived/restored auditability each object tracks creator, editor, and timestamps consistency english descriptions mandatory; uom and types managed via settings traceability batches and sub batches link back to materials and locations