Adapt the operating model, not the database.
Modules shape behavior while products, requests, orders, receipts, and sales remain unified, filterable workspaces.
Connect requests, approvals, purchasing, receiving, stock, sales, and manufacturing through one controlled, auditable flow.
Pointer response reduced · select a stage to open the system
One purchase order moves through the same controlled chain. The module decides what the receipt means—without creating a custom database or a hidden workflow.
The receipt posts an immutable purchase-receipt movement at the validated line destination.
Current quantity comes from movement history. Reservations reduce what operators can use without rewriting the stock ledger.
Reservations stay explicit.Stock-consuming operations check available quantity so work already promised elsewhere remains protected.
Permission-scoped signals bring approvals, purchasing, receiving, sales, and manufacturing into one ranked operating view.
Route decisions, control stock, shape each module, and design the outputs your team needs. Every layer stays visible, permission-aware, and connected to the same ERP kernel.
Approval rules match module and purchase-request cost total, then resolve deterministically by priority. The matched chain advances one required step at a time, while the Approval Inbox shows only the current actionable decision.
Transfers preserve a balanced movement trail, counts post only real variances, and the location matrix derives its position from stock, reservations, and active storage assignments.
Posting writes TRANSFER_OUT and TRANSFER_IN exactly once after rechecking available stock.
Only the variance becomes a movement. A zero variance writes nothing.
Each module declares its capabilities and product-field profile. When selected, module context travels through the workflow, while purchase requests, orders, receipts, products, and sales remain unified pages.
One request queue, with module context on every row.
Build saved operational reports from a controlled receipt-line dataset, then shape module-aware templates for the documents your team previews, prints, or saves as PDF.
| Module | Receipt Reference | Receipt Date | Purchase Order Reference | Vendor | Product Code | Product Name | Quantity Received | Cost price | Line cost | External Reference | Received By | Line Destination |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Inventory | GRN-6032 | 10 Jul 2026 | PO-2081 | Axis Components | DRV-400 | Drive Assembly | 18 | 280 | 5,040 | AX-8841 | Nandi M. | Main Location / Main Stores |
| Non-Inventory | GRN-6031 | 09 Jul 2026 | PO-2080 | Kalahari Cooling | SVC-COOL | Cooling Service | 1 | 2,450 | 2,450 | JOB-119 | Amara K. | — |
| Programmes | GRN-6030 | 08 Jul 2026 | PO-2078 | Northstar Supply | KIT-NORTH | Northstar Field Kit | 25 | 95 | 2,375 | NS-772 | Nandi M. | — |
Modules shape behavior while products, requests, orders, receipts, and sales remain unified, filterable workspaces.
Controlled mappings and durable links prevent duplicate Xero or QuickBooks Online draft exports.
One controlled system for the work between request, receipt, movement, and fulfilment.