Price Lists and Schemes for FMCG distributors
Apply dated price lists and promotional rules to eligible transactions.
Does this function belong in your operation?
Use when prices vary by customer group, channel, quantity or promotion.
A price or commercial offer changes.
Configure trade pricing by the represented company, product pack and eligible outlet terms. A scheme involving free packs or a slab discount needs its own basis and validity, with the accepted treatment visible to the rep and billing team. Manufacturer claim preparation is a separate reconciliation; applying a retailer offer does not prove the distributor will recover funding from the company. Keep the distributor's selling decision distinct from the manufacturer's settlement rules. A commercial owner may approve an outlet concession that is not recoverable through a company claim. Recording that distinction at the transaction prevents accounts from treating every discount as supplier-funded income when the corresponding reimbursement has not been accepted.
Bring the records the workflow depends on.
- Company and product-pack price records
- Outlet class and applicable margin or discount
- Scheme dates, quantity basis and combination rules
- Company claim conditions recorded by the commercial owner
Outputs to check
- Effective trade-price and scheme register
- Order-level scheme application evidence
- Discount and potential company-claim reconciliation
Follow the price lists and schemes workflow.
Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.
Who uses the module, and who approves?
Keep responsibilities distinct even when one person holds more than one role.
Decide how exceptions are handled.
These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.
Can this work independently?
Pricing can be maintained independently, but quoting or billing must use the approved selection rules for consistent application. Customer groups and item codes provide eligibility. The price module does not establish stock availability, contractual acceptance or whether a promotion is legally permitted.
Systems and records it connects with
- Invoice management: Issued invoice references, line amounts and outstanding balances.
- Point of sale billing: Counter sales, tender records and authorised returns.
- Credit control: Customer limits, current exposure and authorised order releases.
- Dealer portal: Partner identities, submitted orders and permitted account information.
Configure, test and introduce the workflow.
- Hand over price sheets, scheme letters and the discount habits of the counter. A note groups them into lists.
- Decide who sits on which list and how far each role may go. Bills that pick the right rate come back. Try them. Staff raise sample bills from several lists. Corrections return as an adjusted set of lists.
- Billing clerks and sales staff practise approvals. A reference sheet for the counter follows. The next offer is entered with its dates. A review after it ends checks what each party paid.
Check the result before rollout.
Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.
- A billed offer traces to its company, pack basis and valid dates.
- Free quantities are distinguishable from paid quantities on the operating record.
- Claim preparation uses actual qualifying transactions without assuming company acceptance.
How the business operates.
Margins are thin and volume is high. A distributor handling three companies may serve six hundred outlets across a dozen beats, with each company running its own schemes and claim rules.
The records that hold the operation together.
- Outlet, beat, representative and customer ledger
- Order line, batch, price and applicable scheme
- Route loading sheet and delivery acknowledgement
- Collection allocation and representative settlement
Operational bottlenecks to check
Scheme claims are short-paid
Free goods and discounts given to retailers are not tied to the scheme that allowed them, so the claim to the company lacks backing. The credit note comes back reduced.
Retailer dues sit with the route rep
Collections recorded in a pocket diary reach the ledger days later, and some never do. The outstanding report cannot be trusted.
How work flows across this business
This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.
1. Plan the beat and capture orders
Assign outlets and record orders with their applicable rates and schemes. Credit exceptions follow the agreed approval process.
2. Bill and prepare route loads
Allocate available batches to released orders and reconcile the picking and loading quantities.
3. Record the delivery outcome
Capture accepted, short or returned quantities at each outlet. Keep physical returns separate until their condition and ownership are reviewed.
4. Settle collections
Allocate cash, cheque or other recorded collections to the correct bills. The cashier reviews the representative or driver settlement rather than closing it from a verbal total.
5. Reconcile claims and balances
Track approved retailer credits and claims raised with the supplying company. Keep pending claims distinct from credits actually received.
Industry reports to connect with
- Beat coverage and orders awaiting fulfilment
- Batch availability and near-expiry stock
- Route loading, delivery and return differences
- Retailer outstanding, settlement differences and company claims
Questions before implementation.
When should fmcg distributors consider price lists and schemes?
Use when prices vary by customer group, channel, quantity or promotion. A price or commercial offer changes.
What should we bring to the requirements discussion?
Bring anonymised examples of Company and product-pack price records; Outlet class and applicable margin or discount; Scheme dates, quantity basis and combination rules; Company claim conditions recorded by the commercial owner. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.
Does this replace our existing business software?
The starting point is your current system and the gap you need to close. Apply dated price lists and promotional rules to eligible transactions. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.
What is outside this module?
Commercial policy and permitted promotional terms must be approved by your business.
How are scope, price and rollout decided?
The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. A billed offer traces to its company, pack basis and valid dates. Use this check when reviewing the first working version.
Related functions for fmcg distributors.
Discuss price lists and schemes for your business.
Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.
What happens after you share your requirements
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- Review the scope and commercial terms before deciding whether to proceed.
Start with your requirements
Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.
Share your requirements