Schemes
Submissions waiting for your approval
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.
Claims waiting for your approval
Routing simulation
Re-runs the current approval thresholds over the last 100 decided submissions and shows
how each one would be routed. Read-only — nothing changes.
Sales Dashboard
Net sales (sales − returns) from the uploaded sales reports.
Product Mix
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.
Reports
Sales analysis. Which reports you see depends on your role;
Supervisors and Managers see their own salesman codes and brands only.
Customers With No Purchase
Dormant lists customers who bought nothing at all in the selected
months. Gap lists customers who did buy — but nothing of the principle or brand you
choose, which is where the cross-sell is. Sorted by the customer's net value over the 12
months ending at the To month, so the ones worth chasing are at the top.
កម្មវិធីទិញ ភ្នំពេញ ថ្មី
បំពេញព័ត៌មានកម្មវិធីទិញរបស់អ្នកលក់រាយ។ វានឹងទៅ Sales Supervisor ជាមុនសិន។
Sales-team Incentive Plans
Each plan is a principle group (1–5 principles, summed) + a salesman code set +
a role, with the monthly 80/90/100 amounts, an over-100 bonus cap and a quarterly amount. A Sales Rep
earns on their own code; a Supervisor/Manager earns on the sum of the code set (matched to their assigned
codes — a manager covering two sets earns both). Bonus = over-target amount × 0.35%, capped.
Download the template. Re-importing overwrites the same plan
(principle group + codes + role).
Incentive Run
Choose a month (monthly incentive + bonus) or a quarter (quarterly incentive, no bonus).
The run uses net sales from the uploaded reports against the monthly targets. Mark each person Paid once
the incentive is settled.
Role, Principle Group and Salesman Code filter both the run and the plans list above.
Scheme Setups
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.
New Scheme Setup
Add the tiers, then submit for Director approval.
Brands
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.
Approval Thresholds (Maximum Rewards %)
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. 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.
Scheme limits
Display Allowance limits
— leave blank to always send Display to the Director
Purchase Counting (Sales Report)
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.
Product Groups (Size / Type / Step …)
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.
Dimensions
Groups
New group
Data Quality
Duplicate customers, uncovered salesman codes, unmapped principles and stale
uploads — fix these before trusting reports or connecting the Intelligence Service.
Audit Log
Threshold changes, Director decisions on flagged items, claim decisions and API
token changes — newest first (last 200).
Customers
The customer master list used by New Scheme and Display Allowance forms.
Team Members
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.
Salesman Codes
Add or edit the master Salesman Code list. Use one code per line, format like S017, MM001 or MS001.
Sales Channels
Group salesman codes into channels for the Sales Dashboard header (Total plus one
row per channel). PV is the province channel — its codes are also what the Province Loyalty
System pulls as province sales. A code with no channel shows under Unassigned until you set it.
Monthly Sales Targets
Monthly sales target per Salesman Code + Principle + Year (Jan–Dec). Brand targets are
the sum of the principles mapped to each brand — they drive the Supervisor/Manager achievement header on the
Sales Dashboard and the Sales-team Incentive. Download the template
(Principle, Salesman Code, then Jan…Dec). Re-importing the same code + principle + year overwrites it.
Add User
Telegram Alerts
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.System URL (secure alert links)
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).
Read-only API Tokens (Intelligence Service)
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.Automatic Sales Report Email
Have the Accountant email the ERP report(s) to a mailbox, and the system pulls the
newest attachment automatically and applies it with Only newer invoices (it never clears
existing data). The Daily Sales Detail and the A/R Credit Memo are detected automatically. For
Gmail, turn on 2-step verification and create an App Password
(Google Account → Security → App passwords) — the normal password will not work over IMAP.