Province Loyalty Scheme System

Items flagged above the approval thresholds (or without a threshold). Everything within the limits was final-approved by the Sales Manager and never reaches this queue.

Re-runs the current approval thresholds over the last 100 decided submissions and shows how each one would be routed. Read-only — nothing changes.

Net sales (sales − returns) from the uploaded sales reports.

LMM→SD sales by product group — the mix below principle level, month by month. Set the groups up in Setup → Product Groups. Switch to % of brand to read the shift in mix rather than the amounts.

Sales analysis. Which reports you see depends on your role; Supervisors and Managers see their own salesman codes and brands only.

ការទាមទារបញ្ចុះតម្លៃផ្ទាល់លើវិក្កយបត្រ ធៀបនឹង កម្មវិធីលើកទឹកចិត្តពាណិជ្ជកម្ម ដែលបានអនុម័ត។ ដាក់ស្នើដោយអ្នកលក់ ឬអ្នកគ្រប់គ្រង, ផ្ទៀងផ្ទាត់ ដោយ Sales Admin / Manager / Director រួច អនុម័ត ដោយ Manager / Director / Accountant / Finance Manager (មិនមែនអ្នកដែលបានផ្ទៀងផ្ទាត់)។ ចំនួនបញ្ចុះតម្លៃត្រូវបានគណនាដោយស្វ័យប្រវត្តិពីកម្មវិធីដែលបានជ្រើស។

បំពេញព័ត៌មានកម្មវិធីទិញរបស់អ្នកលក់រាយ។ វានឹងទៅ Sales Supervisor ជាមុនសិន។

The SD→retailer sales the team reports — verified scheme purchases and trade-promotion claims, combined — set against what LMM actually sold into that market (LMM order, net of returns). Each pool is a province (its SDs and the retailers they supply) or a single Direct LMM retailer, as marked on the Customers list.
SD invoices carry no reliable number, so one sale may sit in both a scheme and a claim. The combined figure is therefore a range: low = the larger of the two per retailer per month (assumes they overlap), high = both added (assumes they are separate sales).
The check runs cumulatively, month by month: reported sales to date against the order to date (plus the lead months as opening stock and the mark-up allowance). Over even the low figure is above — definite; Pending it would be once pending entries are verified; Check only the high figure is above. Amounts are in $ with no carton data — read flags as signals to check, not exact ties.

Patterns worth a second look over the same month range — each is a reason to ask, not proof of a problem. Click a heading to open it.

Each plan is a principle group (1–5 principles, summed) + a Customer Code (SD) set + a named Username + a role, with the monthly 80/90/100 amounts, an over-100 bonus cap and a quarterly amount. The named user earns on the LMM net sales to their SD(s) for the principle group, against the SD targets. Bonus = over-target amount × 0.35%, capped. Download the template. Re-importing overwrites the same plan (principle group + SD codes + role + username). The Sub-Distributor (SD) incentive itself is automatic per SD — configure its rates in Setup.

Role, Principle Group and Username all filter both the plans list and the run below. (The SD role has no plans — it filters the run only.)

Choose a month (monthly incentive + bonus) or a quarter (quarterly incentive, no bonus). The run uses LMM net sales to each SD against the SD targets. It lists the sales team (Sales Rep / Supervisor / Manager) and each Sub-Distributor (SD), whose own incentive is a % of its net sales by achievement tier (set in Setup). Mark each person Paid once the incentive is settled.

Each setup defines the tiers (Scheme Amount / Month → Scheme Reward + Display Reward) for one Brand and one customer-code prefix, e.g. GT Bippi applies to Bippi schemes for customers whose code starts with GT. Leave the prefix blank to apply a setup to all customer codes for that brand — a specific prefix always wins over a blank one. Setups are submitted by the Sales Manager and approved by the Commercial Director. Each setup takes effect from its Effective Month: a new scheme uses the tiers that were effective in its Start Month, so older setups keep serving older start months until the Director marks them Superseded.

Add the tiers, then submit for Director approval.

The master Brand list used by the New Scheme form, Scheme Setups and the sales report mappings. Renaming a brand updates it everywhere (schemes, tier setups, mappings, rules). Disabling a brand hides it from new submissions only — existing schemes keep working. Other is built-in and always available.

The guardrail for delegated approvals, per Brand + Customer Code Prefix. A scheme submission that complies with its tier, stays at or under the tier total, or whose Total Rewards % is within the Maximum Total Rewards % is final-approved by the Sales Manager; above the maximum it is flagged for the Director. Display Allowances use the customer's prior 3 months of net purchases as the base. Claims within the Maximum Total Final Rewards % (Final Rewards ÷ Total Purchase) can be approved by the Finance Manager; above it, by the Director. A trade-promotion claim is routed the same way against the Max Trade-Promotion Claim % — the claim's discount ÷ its purchase amount; blank = every promotion claim for that brand + prefix goes to the Director. Leave the Customer Code Prefix blank to cover every customer of that brand; when a blank row and a specific-prefix row both exist, the longest matching prefix wins. A brand with no matching row here always goes to the Director. Every change is recorded in the audit log.

Direct on-invoice discount promotions that Claims are checked against, per Brand + Customer Prefix. The type sets what the tier threshold is measured in — carton (buy X cartons) or amount (buy $X). Each tier can give a discount % of the purchase, a $ per carton, and/or a flat $ — any combination is added together; the highest tier the purchase reaches is applied. A promotion is used by Claims only once the Director approves it; the Finance Manager or Director can edit it afterwards.

Group a brand's SKUs along a dimension you define — Size (NB, S, M, L, XL, 2XL/XXL, 3XL/XXXL), Type (Pants, Tape), Step (1, 2, 3, 4), or anything else. A SKU can sit in one group per dimension, so the same diaper is Size 2XL / XXL and Type Pants at once. These groups drive Sales → Product Mix, the Reconciliation report, and the Trade Promotion scope. SKUs appear after a 🔄 Sync from PP (the SKU detail arrives with the sync). Packaging Type and Category are used by Trade Promotions and can be renamed but not deleted.

Controls how uploaded sales invoices fill in scheme purchase amounts. Each mapping says: invoices with this Principle count toward this Brand, for invoice months inside the effective range. Unmapped principles are never counted — they appear in the Unmatched report instead.

Duplicate customers, uncovered salesman codes, unmapped principles and stale uploads — fix these before trusting reports or connecting the Intelligence Service.

Threshold changes, Director decisions on flagged items, claim decisions and API token changes — newest first (last 200).

The customer master list used by New Scheme and Display Allowance forms.

Each SD (Customer Code) earns a % of its own LMM net sales when its total order achievement (net ÷ target, all principles) reaches a tier. Set the achievement thresholds and the reward rates below. Shown for every SD in the Incentive Run (Incentives tab).

Add accounts, assign a Salesman Code to each Sales Rep, and assign the codes covered by each Supervisor, Manager, Accountant and Sales Admin (they only see schemes under their assigned codes; a Sales Admin with no codes assigned sees everything). Visible Brands limits which brands a Supervisor or Manager sees on the Sales Dashboard, and which brands a Sales Admin sees in the Scheme & Display lists (no brands set = all).

Add or edit the master Salesman Code list. Use one code per line, format like S017, MM001 or MS001.

Monthly LMM → SD order target per Customer Code (SD) + Principle + Year (Jan–Dec). These SD targets drive the Sales-team Incentive and the Sub-Distributor (SD) incentive. Download the template (Principle, Salesman Code, Customer Code, Province, then Jan…Dec — matching is on Customer Code; Salesman Code and Province are informational). Re-importing the same customer code + principle + year overwrites it.

Connect a Telegram bot so the team gets instant alerts for rejections and comments. Create a bot with @BotFather in Telegram (send /newbot), then paste the token here.

With a System URL set, Telegram messages contain only the alert type, the submission ID and a link to open the system — never customer names or amounts. Leave empty to keep sending the full alert text (e.g. for LAN-only use).

Tokens give the future LMM Intelligence Service read-only access to schemes, tiers, approval history, thresholds and the data-quality report under /api/v1/… (send Authorization: Bearer <token>). Bank details, phone numbers and photos are never exposed. A token is shown only once at creation.