| Area |
Purpose |
Key rule |
| Dashboard |
Branch-aware operational and commercial summary |
Totals depend on the user's scope and selected branch |
| Customers |
Customer identity, contact and delivery addresses |
Reuse a customer after lookup; avoid duplicates |
| Quotations |
Price rent, sale, service and transport before commitment |
Acceptance can be recorded and an accepted quote converted to an order |
| Orders |
Commercial record and fulfilment control |
Lock/finalise before relying on totals; dispatch and revert are audited actions |
| Outstanding orders |
Work that still needs payment or fulfilment attention |
Confirm the filter definition before using it for financial reporting |
| Sales agents |
Assign and report ownership |
Agent visibility follows permissions and branch scope |
| Area |
Purpose |
Key rule |
| Trips |
Delivery, pickup/return and lorry-crane work |
A trip is an operational movement, not the order itself |
| Calendar |
Date-based fulfilment view |
Moving a date changes planning; it does not silently complete fulfilment |
| Complaints |
Record and follow up operational issues |
Current routes are authenticated but do not show a dedicated complaint permission gate; review access policy |
| Technicians / operation staff |
Assign workers and maintain operational records |
Keep branch and active status current |
| Vehicles |
OE-facing vehicle data |
Confirm which system is authoritative before editing |
| Area |
Purpose |
Key rule |
| Item master and variants |
Defines rentable/saleable products |
Do not use service items as physical stock |
| Stock items / registration |
Creates identifiable stock and opening/incoming quantities |
Register against the correct warehouse |
| Stock movement |
Stock-in, adjustment, issue, return and transfer history |
Never repair balances by direct database edit |
| Stock approval |
Approves sensitive adjustments and discrepancies |
Approver must review evidence and warehouse |
| Stock checking |
Physical count and reconciliation |
A count difference is an exception requiring traceability |
| Transfer receiving |
Destination acknowledges transferred stock |
Source send alone does not complete receipt |
| Tools and tool checks |
Operational equipment templates/checks |
Some navigation entries are disabled; confirm whether the process is active |
| Area |
Purpose |
Key rule |
| Payments |
Record customer receipts |
Recorded and verified are distinct states |
| Invoices |
View billing records |
Confirm source of invoice numbering and accounting ownership in production |
| Refund |
Request, approve and verify refunds |
Security-deposit refunds depend on completed return fulfilment |
| Deductions |
Charge missing/damaged items or another approved deduction |
The implemented design issues a separate deduction invoice |
| Reports |
Financial/operational summaries |
Validate branch scope, date basis and verification state before export |
¶ Administration and integration
| Area |
Purpose |
Key rule |
| Users, roles and permissions |
Local application access |
Core grant admits the product; local PBAC controls actions |
| Branches |
Operating scope and warehouses |
Store canonical code; display friendly label |
| Companies and quotation terms |
Document identity and commercial wording |
Confirm the correct company before issuing customer documents |
| API tokens |
Machine access |
Rotate and revoke like credentials; never place tokens in this wiki |
| AppSheet sync/outbox |
Exchanges orders, trips, payments and related records |
Retry through the outbox tooling and investigate the last error first |
| OE integration |
Dispatch/board workflows, technicians and vehicles |
Uses machine authentication and commit-style endpoints; monitor job logs |
Follow-up, intercompany and subcontract split pages exist in the frontend tree, while some related navigation entries are disabled or their operating rules are not established in the repository. Treat them as not handover-ready until a product owner confirms scope, permissions and acceptance criteria.
The reviewed repository at commit c0bce14 contains the commercial, operation, inventory, finance, administration and integration route groups summarised above. Production enablement must still be verified against the implementation status.