This page compares Encik Beku with the 22 shared Sales Module components.
Read the State column first:
The final column contains detailed rules and implementation gaps. New readers should first read the Overview, then return here for the relevant component.
| Count | State |
|---|---|
| 5 | As written — uses the shared design |
| 15 | Differs — uses an Encik Beku-specific rule |
| 2 | Not used — does not apply to this unit |
| # | Component | State | Encik Beku |
|---|---|---|---|
| 1 | Identity, permission, record scope | differs | The scope axis is the branch — KL, N9, Johor, Penang, Melaka — and every order, job log, technician and address carries one. Subcontractors are outside-company technicians flagged as subcon, and they see only their assigned job logs. Technicians and subcon have no permission template of their own yet and ride the Sale template; that is a gap, not a design. The current-system check found three more problems. Complaints sit behind authentication only. The /oe routes sit outside PBAC (policy-based access control). Role administration has no ceiling on the permissions a grant may give. → PBAC |
| 2 | Settings, numbering, configuration | differs | Order numbers run per trade with a branch variant — AC, ING, JING, PST — and the other twelve trades are not yet set. Company is fixed per branch: five branches map to four companies. Source of Order is a dropdown the unit maintains itself at settings, starting with eight values. The repository seed still contains only Indoor, Telemarketing, LG and Khind; live settings must be checked and completed before rollout. → Order number and identity |
| 3 | Item master | differs | One listing for the unit: 620 items with an id (623 rows), 430 package components, 114 accounts (read 2026-09-15). A package is a parent plus components, and the component total must equal the package price. OTHER is one controlled record with one generic account, never one per trade. Every countable row is buy-to-order except a short keep-stock list only the store team can name. The Sales ACC No. belongs on the item, and must never be shown to Sales, OE or the field. The order-item API still exposes it to anyone who can view the order, which remains a permission gap. → Item master |
| 4 | Chat platform link, lead source | differs | Leads arrive on WhatsApp through ReplyBox and ChatDaddy under trade personas — Amira and the others are not real people. Source of Order is the lead-source field, and two of its values start a next action: SGS starts a commission claim, Intercompany starts a backcharge. → Source of Order |
| # | Component | State | Encik Beku |
|---|---|---|---|
| 5 | Customer record, sales roles, quotation | differs | Quotation is optional — Sales may quote in WhatsApp and create a direct order. Five quotation statuses only: Draft, Sent, Accepted, Rejected, Converted. No debtor code on a quotation. Pricing: the default price pre-fills, the floor price is the lowest a user may enter, there is no line discount, and the order carries one overall discount. Selling roles: Indoor takes the sale, BD visits, QS quotes, BD closes. → Quotation · Pricing |
| 6 | Order and its lifecycle | differs | One order, many job logs; completing a job log does not complete the order. The order number is customer-facing and may be changed by an authorised person; every link uses the hidden record id. Cancel is a status, never a delete. It is blocked once work has started, a job is completed, a payment exists, or a posting has happened. The build does the opposite today: cancel also soft-deletes, and nothing blocks it. The company on the order freezes at fulfilment — the build freezes it at dispatch, which must move. → Order cancellation |
| 7 | Turning a lead into an order | as written | One addition. LG's partner admin keys LG installation orders in through the partner module. Extra work found on an LG job becomes a normal AC order with Source LG. → Order intake |
| 22 | Service request | not used |
Not defined for any unit yet. Encik Beku surfaced it, and holds two cases for it. The first is the on-site upsell, which needs a draft job log under the same order. The second is the own-asset case: a company van's aircond fixed by a technician, with no customer, no order and no invoice. |
| # | Component | State | Encik Beku |
|---|---|---|---|
| 8 | Job and trip record | differs | Called the Job Log. Three fields, never one: Job Type (New, Continue, Recheck), Job Status (Scheduled, In Progress, Completed), Job Outcome (six values, ruled 19 August). A Continue outcome creates a new draft job log with an empty date for OE to schedule. A technician may create a draft job log under the same order. The OE verification gate — a person and a time on the record, not a status value — is not built. Continue currently records the outcome only. Technicians also cannot create that follow-up through the current /ops API. AppSheet brings 11,000 job logs across as imported. → Job outcome |
| 9 | Driver | not used |
There is no driver. The technician drives. The vehicle is chosen at the morning check-in from the central Vehicle Master — in-house technicians only; subcon has no vehicle and no helper. An "Other Vehicle" entry is history, never a new master row. → Helper and vehicle roster |
| 10 | Scheduling and dispatch | differs | Dispatch runs on branch, in a calendar by technician. Cross-branch dispatch is allowed, and the invoice then follows the fulfilling branch's company. Subcon appear in the same picker as technicians. A reusable preferred vehicle and helper pairing exists, but the required daily morning check-in with date, time and Clock In linkage is not built. → Susun trip dispatch |
| # | Component | State | Encik Beku |
|---|---|---|---|
| 11 | Billing, payment, deposit | differs | Payment in stages on one order, never cycles. A checking fee by trade — Aircond RM100, Wiring RM450 — waived on big orders. A technician may take a deposit on site and upload it. A forfeited booking fee is an outcome on the deposit payment, not a refund. One bank account per branch. The on-site invoice is a Sales Module document from the technician snapshot; the e-Invoice is AutoCount's, at posting. → Multi-payment lifecycle |
| 12 | Collecting a payment | as written | Field collection with proof upload. Account verifies the payment independently of the itemize. → Record payment |
| 13 | Payment reconciliation | as written | Nothing Encik Beku-specific recorded. Not built. |
| 14 | Itemize log and statuses | differs | The unit's defining shape: a chain of frozen snapshots, quoted → technician → oe_review (only if a correction happened) → verified, plus imported for AppSheet rows. Each line keeps one stable line id across every snapshot, and lines from several jobs accumulate on one order. The technician keys in on site. OE may key on their behalf, and the record keeps who entered it, who was assisted and who is credited. Every line carries work_done_by — In-House or Sub Con. Build changes owed: retire finalized and amended, add verified and oe_review, add the lineage column. Built since 10 September: a Finance queue now records who verified and when. A reason is required when Account flags an issue, but not for a clean verification. Batch and individual lines are both supported. The old and new routes still coexist, and a later batch can disappear from the queue. → Account verify and flag |
| 15 | Refund | differs | From the build, not from the rule. A refund is money back to the customer, and nothing else. Materials coming back from a technician are a stock return, row 18 (Charlie, 16 September 2026). The four types are deposit, booking fee, overpaid, compensation. The build has Overpaid and Checking Fee — the second is not on the list and the first three of the list are missing. Starting position: approval switch on, threshold zero. AppSheet brings 58 refund rows across. → Refunds |
| 16 | Posting to the accounting system | differs | Four companies, four AutoCount files. Each file has twelve in-house service sheets and one Sub Con sheet. The line's work_done_by picks the sheet, and the item's Sales ACC No. picks the account. Document date is the job date — which visit of a multi-visit job is still open. From 1 August 2026 Penang sales sit under Rev Move Utara. e-Invoice is submitted from AutoCount's own MyInvois link, mandatory since January 2026. Today a read-only feed of verified rows goes to the Account team's AR Portal, which owns the posting. A browser CSV export is still live on two screens. The two gates and revert are not built, and nobody has been named to own them. → Account posting and AutoCount |
| 17 | Sales commission | differs | Commission reads the verified sales amount and the credited fulfiller, not the person who typed the line. SGS — a sale closed on site by a technician or driver — starts a claim; a manager closing a sale is not SGS. The subcon settlement — 70/30 after materials, when HQ bought them — is not commission, and is deferred. The per-line work_done_by it needs is on the line from day one. Not built. |
| # | Component | State | Encik Beku |
|---|---|---|---|
| 18 | Inventory | differs | Goods are bought per job, with a small keep-stock list of fast movers. A zero balance is the normal reading here, and must never show as "out of stock". Stock lives in the linked Stock & Inventory product, not in the order flow. Issue and return: the warehouse issues materials to the technician and takes them back; the technician's app only shows what he holds. A return goes to a to-check zone, then ready or scrap. Locked 14 July 2026 ("Option B"). Built: items, variants, stock in, adjust, transfer, tool checklists. Not built: issue to technician, return from technician. |
| 19 | Procurement | differs | A purchase is raised per order once the customer has said yes; there is no standing purchasing cycle. No Encik Beku rule beyond buy-to-order is written. Not built. |
| # | Component | State | Encik Beku |
|---|---|---|---|
| 20 | Complaint log | as written | Encik Beku is the first unit to run it, with no enable-or-disable framework for this first rollout. Built. Its detailed workflow stays in the separate Complaint Log document and links to the Order and Job Log flow. |
| 21 | Reporting and alerts | as written | One unit ask on top: a technician correction rate, read from the difference between the technician snapshot and the verified one. Dashboard summary, technician performance and order status are built. The correction rate is not complete, because the build does not yet create a verified snapshot. |
Two sections on the Encik Beku business page date from April and describe an Admin Review step and an Admin Snapshot between the technician and Account. The 11 September ruling removed that step: Account is the one hard gate, and OE reviews only when Account flags a problem. Those sections carry a superseded note pointing here.