Sales Returns and Credit Notes for FMCG distributors
Record customer returns and link their financial and stock effects.
Does this function belong in your operation?
Use when supplied goods or billed amounts can require returns or credit adjustments.
A customer requests a return or credit.
Market returns need the retailer, original supply and physical condition behind the credit decision. Configure expired, leaking and damaged packs separately, capturing batch information where it is available. Goods returned from the beat should enter the appropriate held location before any resale decision, and a retailer credit must remain distinct from the distributor's recovery claim against the supplying company. A collection note can include goods from different batches or companies, so the inspection record should separate them before any claim is prepared. The same retailer may receive one approved credit while other lines remain disputed. Retain that line-level decision rather than accepting or rejecting the whole collection as an unexplained total.
Bring the records the workflow depends on.
- Retailer and original bill or approved return reference
- Item pack, batch and returned quantity
- Return reason and condition evidence
- Company claim and customer-credit approval rules
Outputs to check
- Inspected market-return register
- Held-stock and authorised credit record
- Company-recovery claim support
Follow the sales returns and credit notes 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?
Returns need the original sale or an approved exception reference. Inventory records accepted quantities and condition; accounting issues credits and manages refunds. A return request does not prove goods arrived, and receiving goods does not automatically authorise a full financial refund.
Systems and records it connects with
- Invoice management: Issued invoice references, line amounts and outstanding balances.
- Stock: Item-location quantities and authorised stock movements.
- Credit control: Customer limits, current exposure and authorised order releases.
- Quality control: Inspection results and authorised hold or release decisions.
Configure, test and introduce the workflow.
- We trace a return from gate to ledger. You show recent cases, and a written flow is sent back.
- Reasons and time limits are agreed. You approve the list used in the screens. The note is matched to your invoice series and tax details. Accounts proof a sample.
- Saleable and damaged bins are set up. The storekeeper tries both paths. Returns start here on an agreed day. The owner receives a monthly count.
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 return can be traced from outlet collection through inspection and disposition.
- Expired or damaged packs do not enter saleable stock automatically.
- Retailer credits and company claims reconcile independently.
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 sales returns and credit notes?
Use when supplied goods or billed amounts can require returns or credit adjustments. A customer requests a return or credit.
What should we bring to the requirements discussion?
Bring anonymised examples of Retailer and original bill or approved return reference; Item pack, batch and returned quantity; Return reason and condition evidence; Company claim and customer-credit approval rules. 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. Record customer returns and link their financial and stock effects. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.
What is outside this module?
Consumer obligations, tax treatment and refund policy require your adviser-approved rules.
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 return can be traced from outlet collection through inspection and disposition. Use this check when reviewing the first working version.
Related functions for fmcg distributors.
Discuss sales returns and credit notes 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