Twenty-six modules. One database.
Grouped into fourteen areas of the admin panel. A garment booked at the counter is the same record the plant sorts, the customer tracks, the report counts and the audit log remembers — entered once, never re-typed.
Learn one screen and you have learnt twenty.
Every list works the same way.
This is the part most software gets wrong. Rather than twenty screens each with their own logic, every record list in the platform shares one grammar — the same tabs, the same actions, the same log. Training a new cashier takes an afternoon.
Submenu counts
All, Active, Inactive — or the status set for that module — each showing a live record count before you click.
Ten standard actions
List, add, edit, view, activate, duplicate, delete, activity log, import, export. On every module.
Activity log everywhere
Field-level change history with actor, IP address and timestamp, readable from the record itself.
Branch scoping
One switcher in the header re-scopes every list, chart and report to the outlet you are looking at.
Role gating
If a role has no permission for a module, its menu is absent and its routes refuse the request.
Excel in and out
Downloadable templates for import, formatted workbooks for export, on every list in the system.
Fourteen groups as they appear in the sidebar of the admin panel.
Modules with a deep-dive page are linked.
The sidebar, top to bottom.
The offline build covers the store. The web platform covers the chain.
Not every store needs all of it.
Open all of it and click around.
The sandbox has a year of orders, a full catalog, four branches, eight employees and a loaded expense register. It resets nightly.