These rules apply across customers, quotations, orders, trips, stock, payments, refunds and integrations.
¶ Identity and access
- Core establishes identity and the Scaffolding product grant; local roles, permissions and branch access still apply.
- The backend must enforce permission and branch scope. A hidden frontend control is not security.
- Machine integrations must use approved API-token or JWT middleware.
¶ Branches and audit
- Store canonical branch codes and display friendly labels:
ShahAlam → Shah Alam.
- Every branch-scoped read and change must use the user's allowed branches.
- Commercial, stock, approval and integration changes must remain traceable.
- Use stable record IDs for relationships and reconciliation, never names alone.
- Use supported revert, approval and retry flows instead of direct database edits.
- Use the backend's exact rounding rules, never floating-point approximations.
- Keep recorded payments separate from verified payments.
- Keep the original order invoice unchanged when issuing a separate deduction invoice.
- A security-deposit refund cannot bypass its required pickup/return state.
- Do not claim monthly billing or accounting posting is automatic without production evidence.
¶ Inventory and fulfilment
- Only physical items affect stock; pure services do not.
- Stock follows reservation → issue → on-rent/sold → return → reconciliation.
- A transfer is incomplete until the destination receives it.
- Stock discrepancies require evidence and authorised approval.
- Delivery and pickup are separate events; a scheduled trip is not a completed trip.
- Order, trip and stock states must agree before a return-dependent refund proceeds.
- The application database remains authoritative for locally owned records unless an approved contract says otherwise.
- AppSheet/sheet changes use the outbox and supported retry process.
- OE draft and commit calls must be logged and reconciled.
- Credentials and environment identifiers belong in approved configuration/secret storage, not this wiki.
¶ Privacy, time and environments
- Customer contacts, addresses, payment and refund evidence are sensitive.
- Never place secrets, raw customer exports or unredacted financial evidence in documentation or tickets.
- Validate uploads and revoke leaver/exposed-machine access promptly.
- Display business time in
Asia/Kuala_Lumpur; store timestamps consistently with the database contract.
- A Git branch, merge or migration is not proof that behaviour is live in production.