This page records approved Encik Beku decisions, newest first. If a newer decision replaces an older one, the older entry is marked as superseded. Shared Sales Module rules still take priority where they apply to every business unit.
For what is not decided, see Open questions.
| Count | What |
|---|---|
| 5 | September rulings — the current word |
| 15 | August decisions — kept with the group's confirmations |
| 7 | August areas since superseded by the master |
| # | Decision | Ruled | By |
|---|---|---|---|
| S1 | Track an itemisation issue on the affected line. Store who raised it, when, the reason and how it was resolved. If the same line is flagged again, keep both issue records. OE works from the flagged-line list. This replaces the earlier decision that there would be no issue record. | 14/09/2026 | Charlie |
| S2 | Cancellation and deletion are different. Cancellation keeps the Order and its history and requires a reason. The system refuses cancellation after work, payment or posting. Deletion is a separate restricted soft-delete action with its own confirmation and reason. | 14/09/2026 | Charlie |
| S3 | The system must enforce a block. A person must not manually decide whether to ignore a blocking rule. Exceptional corrections use a controlled, permission-based process. This decision followed an incorrect cancellation that required manual database restoration. | 14/09/2026 | Charlie |
| S4 | Account is the only mandatory itemisation gate. Remove the old Admin Review and Admin Snapshot steps. OE becomes involved only when Account flags a problem. | 11/09/2026 | Charlie |
| S5 | Materials returned by a technician are stock returns. A refund means money returned to a customer. Do not use the refund process for materials. | 16/09/2026 | Charlie |
These older decisions provide detailed design context. A September ruling above takes priority wherever the two disagree.
Superseded since August by the master (10–14 September): the itemize issue mechanism, the job outcome list, cancel and delete, posting to AutoCount, the lock after posting, the refund types and settings, and the four statuses.
Use Outcome-First, Minimum-Sufficient Design. Start from the business result and a proven user problem. Build the smallest safe and complete workflow. Keep stable IDs, proper permissions, audit history and a clean path to extend later. Do not add a field, status, page, approval or table unless removing it would break a current result or a required control.
The launch-centred workflow is Customer → Order → Itemize → Job Log → Final Invoice → Payment → Completed. Quotation is optional. Service Request is a centralized shared service. Stock and Inventory is a linked module. Complaint Log is implemented for Encik Beku first, with no enable/disable framework for this rollout.
Every important record has two IDs: a staff-facing Reference ID PREFIX-YYMMDD-XXXX (four uppercase hex characters), and a hidden UUID for database relationships.
The customer-facing Order Number lives once, on the Order. Job Logs, Itemize, Payments and Refunds link through the hidden Order UUID, so changing an authorised Order Number does not break those links. Every record keeps created_by, created_at, updated_by, updated_at.
Use policy-based access control. A role may provide a default permission set, but code must not use a role name as the final authority for a sensitive action.
Person-and-scope examples: item master management for a dedicated person; posted-record correction for Charlie, a dedicated Indoor Manager, Account Manager or delegated OE person; branch-scoped technician and subcon access to assigned job logs.
The backend must enforce the permission. Hiding a button is not enough.
Quotation is an optional official price generator. Sales may still quote through WhatsApp and create a direct order. Launch statuses: Draft, Sent, Accepted, Rejected, Converted. Do not add Expired or Superseded as user statuses — keep an updated official quotation as a revision and convert only the accepted revision. Quotation and Order share the Customer base and Item Master. A quotation does not require a Debtor Code.
One order may have several job logs; completing one job log does not complete the order. Job Type, Job Status and Job Outcome are three different fields.
Recheck is a Job Type. Use On Hold, not KIV. Postpone means reschedule and requires the next date when known; when the date is unknown, use On Hold with a reason and a follow-up action.
OE confirmed, 19/08/2026 (Azri Harith, WhatsApp group "Sales Module - Encik Beku", 12:49pm): "Job Outcome / Confirm / Use Completed, Continue Required, Postponed, On Hold, Reassignment Required and Customer Requested Order Cancellation. Recheck remains a Job Type, not a Job Outcome."
OE confirmed, 19/08/2026 (same): "When a job requires continuation, the system should create a new Draft Job Log for the follow-up work. The new Job Log should have an empty Date and Waiting Schedule, so OE can arrange the next appointment before confirming the new schedule."
A Technician or Subcon cannot cancel an order. They select Customer Requested Order Cancellation as the Job Outcome with an optional remark; Indoor or OE then reviews and changes the order status. Cancellation never deletes the order — the cancelled order remains searchable with its history.
OE confirmed, 19/08/2026 (same): "Cancellation / Confirm / Technician or Subcon selects Customer Requested Order Cancellation, with the reason recorded when available. Indoor or OE makes the final decision after checking whether work, payment or AutoCount posting already exists. The Order must remain searchable with Cancelled status and full audit history."
Resolved 14/09/2026 by S2 and S3 above: a system block, with two separate actions.
In-house Technician and Subcon use the same fulfilment steps: open the assigned job, Start Job, update itemize, capture proof, select Job Outcome, submit Job Completion.
Only in-house technicians use Helper and Vehicle. Helper supports multiple selection. Subcon does not need Clock In. For an in-house technician who has not clocked in, use a strong reminder and record the exception — do not hard-block Start Job.
OE confirmed, 19/08/2026 (same): "Clock In / Confirm / Use a strong reminder and record the exception, but do not hard-block Start Job. Attendance issues must be followed up separately and should not delay the customer's scheduled job."
The normal rule is that the customer is on site and signs. For the rare absence case the minimum design is Customer Not On Site: compulsory photos, timestamp, location and remark. Do not offer a general Skip Signature action.
OE confirmed, 19/08/2026 (same): "Timestamp/location photos should be required together with a clear remark explaining the situation. WhatsApp confirmation can be used as supporting evidence. There should be an exception flow for cases where the customer cannot provide a signature, but the reason must be clearly recorded for OE review."
This adds two things not decided before: WhatsApp confirmation may count as supporting evidence, and a no-signature exception flow is required with the reason recorded for OE review.
Every logical itemize line has one stable ITM Reference ID. The same line may appear in the Sales, Technician and Final Invoice snapshots without becoming a different logical line.
One order may receive itemize from several jobs — job 1 adds three lines, job 2 adds four, and the same final invoice may contain all seven verified lines. A later job must not overwrite an earlier job's lines.
A technician may ask OE to key in a line. Record who entered it, who was assisted, and who is credited for fulfilment. Commission uses the finalized sales amount and the final credited fulfiller, not the person who typed the line.
Default Price pre-fills the cart. Floor Price is the lowest normal price a user may enter. There is no normal line-discount field. The order has one Overall Discount. When Floor Price is blank, Default Price is also the floor.
Accounts must still decide how the Overall Discount posts — see Open questions.
An unverified payment log may be edited. Account verification locks normal editing of that payment row. Posting locks the exact posted financial snapshot — entity, Debtor Code, Bill-To snapshot, lines, prices, discount, total, document date and AutoCount reference.
Posting does not lock the whole customer profile or stop later operational job logs. An authorised person may use Controlled Correction with a compulsory reason, keeping the previous posted payload so the system can show what AutoCount currently contains. Audit history alone is not enough to replace the posted snapshot.
One centralized Vehicle Master. Sales may show the BU's vehicle list; the Ops picker reads the same master. Do not create a second Sales-owned Vehicle table. An Other Vehicle entry records plate, description and reason in vehicle history but does not create a Vehicle Master row.
OE confirmed, 19/08/2026 (same): "For in-house technicians, the vehicle list should be based on the technician's allowed branch/vehicle assignment. Vehicles from other branches may be available where applicable. Other Vehicle should only be treated as temporary/history information and should not become a permanent vehicle assignment."
This widens the rule slightly: other-branch vehicles may show for the technician himself where applicable, not only for OE arranging a cross-branch loan.
Backcharge is centralized in UtopiaSpace. Order Details may show a read-only Backcharge Log for linked records. Sales must not create another backcharge ledger.
One BU has one Item Master Listing, managed by a dedicated person through permission, not role name. Normal item adding searches Item Name and Item Description; management may also search Item Code and Sales ACC No.
OTHER is ONE controlled record (confirmed by Charlie, 19/08/2026) — not one per trade, not a new row each time. Each use gets its own itemize line carrying its own description, quantity and price. See Item master.
A cross-functional review assigns who must verify each business area. It does not grant system access by role — system access still follows A3.
| Reviewer | Verifies or decides |
|---|---|
| Indoor / Sales | Item names, descriptions, search words, selling units, displayed prices, whether package names read clearly to a customer-facing user |
| OE | Package components match the real work; Site Visit is usable; missing materials or services are found; the eleven RM50 installation placeholders are confirmed or corrected |
| Account | Overall Discount method; below-Floor-Price treatment; the eight new account names; the 34 unused accounts; Site Visit and contra mapping; package posting; whether missing Cost blocks selling or only margin and commission reporting |
| Dedicated Item Master person | Apply confirmed corrections, keep unfinished rows Draft, record review evidence, control which rows move to Active — a granted capability, not a fixed role |
| Dev | Map the final sheet to the database, preserve package components, apply BU scope, search rules, Draft filtering, Floor Price control, PBAC, audit fields and import tests. Dev does not decide business prices or account meaning. |
| Charlie | Resolve cross-team conflicts and approve the final activation boundary |
The list is not a fixed enum. It is configurable per BU. Full ruling, the eight starting values and the LG correction: Source of Order.
Recorded 24/08/2026 after two wrong attributions in one week: People and channels.
Status: proposed, not locked. Proposed 25/08/2026 and revised the same day: LG order linking.