| Domain | Principal records |
|---|---|
| Access | App user, role, permission, branch and branch permission |
| Customer | Customer, address and sales agent |
| Catalogue | Inventory item, item variant, combo item, company and quotation terms |
| Commercial | Quotation, quotation item, order, order item and transportation charge |
| Fulfilment | Order trip, trip sheet, technician and vehicle |
| Inventory | Stock registration/item, movement event, check, discrepancy and transfer/receipt |
| Finance | Payment, refund, refund deduction, deduction invoice and lines |
| Integration | Debtor/payment/order/trip sheets, sheet-sync outbox and integration job logs |
| Service quality | Complaint, tool/template/check and order audit |
Refer to migrations before relying on a column or status; the model list is not a substitute for the database schema.
The active contract is rooted at /api/v1. The reviewed route file contains public health/version endpoints and authenticated groups for:
The route file is the routing authority. Controller policies and service transactions are the behavioural authority; never infer access or side effects from the HTTP verb alone.
The database and scripts support orders, order items, trips, payments and related sheet records. Changes may be queued in a durable outbox with entity type, entity ID, attempt state and error details.
Recovery order:
OE endpoints sit behind API-token-or-JWT authentication and expose queue/board, draft and commit operations plus technicians, vehicles, provisioning and job logs. Commit endpoints should be treated as state-changing transactions. Capture the request/correlation identifier when investigating a failure.
ShahAlam.