The product
Twelve modules that behave like one system
Each module ships with the documents, registers and reports a plant actually uses. They all post into the same stock ledger and the same books, so switching one on does not create another island of data.
Commercial
Buying and selling
2 modules
Sales & Order Book
Quotation to invoice with a live order book, delivery tracking and customer ledgers.
Purchase & Suppliers
Requisition to payment, with GRN, incoming QC, supplier bills and payables in one chain.
Operations
The shop floor
3 modules
Inventory & Stores
One stock ledger for every store, batch and rack — no negative stock, no parallel spreadsheets.
Production & Planning
Route every order through the plant — weaving, dyeing, finishing, stitching, packing — with real output per shift and machine.
Quality Control
Incoming, in-process and final inspections with defect capture and a 4-point score.
Finance
Money and cost
3 modules
Product Costing
Cost per piece and per kilo built from actual material, wages, utilities and overheads.
Finance & Accounts
Double-entry accounting that posts itself from operations — trial balance, P&L and balance sheet always tie.
Reports & Exports
Twenty-five plant and finance reports, filterable and exportable, with no report-writer licence to buy.
Control
Control and visibility
4 modules
Dynamic Approvals
Decide which documents need approval, at how many levels, by which role and above which amount.
Business Control Centre
One screen for the whole business — money, orders, plant, quality, people and pending approvals.
Activity Tracking & Session Replay
Know who logged in, from where, on what device, what they did and how long they spent on each screen.
Roles, Users & Audit
Department-level roles with per-module view, create, edit and delete rights — enforced in the API, not just the menu.
Underneath
The engine that makes the modules agree
Four services every module is built on. This is why the trial balance ties and why the store balance can be trusted.
Document engine
Draft → posted → completed or cancelled, with numbering per document type and a full audit stamp. Cancelling reverses effects instead of deleting history.
Single stock ledger
Every movement in any module writes one line, valued at moving average. There is no second place where stock lives.
Double-entry journal
Postings are generated by the module that owns the event, against a real chart of accounts.
Permission layer
Role rights are checked on the server for every request, with branch and store scoping for groups.