ERP for FMCG Distribution: Van Sales, Expiry, Credit, and Trade Schemes

FMCG distribution combines high transaction volume with thin margins, short customer response times, batch control, expiry risk, promotions, credit, returns, and field execution. A generic sales screen does not prove that an ERP can run this environment.

The implementation must connect demand, warehouse stock, route stock, dealer orders, delivery, settlement, claims, and finance.

Build the operating model

Define:

• Company, region, depot, warehouse, and route
• Dealer and outlet hierarchy
• Salesperson and vehicle
• Item, brand, pack, case, and unit
• Batch and expiry
• Price list and channel
• Credit limit and terms
• Scheme and promotion
• Return reason
• Tender and settlement

Maintain one owner for each master-data domain.

Order to settlement

A complete route flow includes:

1. Capture demand or order.
2. Validate customer, credit, price, and scheme.
3. Allocate stock by batch and FEFO policy.
4. Prepare van load or delivery.
5. Confirm delivered, short, refused, or returned quantity.
6. Collect cash or create receivable.
7. Reconcile route stock and tender.
8. Post accounting and inventory.
9. Route exceptions.

Test partial deliveries, substitutions, damaged goods, customer closure, and route change.

Batch and expiry

Track batch at receipt, transfer, van load, delivery, return, and adjustment.

Use:

• Minimum remaining shelf-life rules
• FEFO allocation
• Customer-specific restrictions
• Near-expiry alerts
• Quarantine
• Recall trace
• Expiry write-off approval

Oyo’s inventory review can compare projected demand with remaining shelf life and recommend transfer or promotion. A planner approves actions that affect price or customer allocation.

Van inventory

Treat each van as a controlled stock location where appropriate.

Reconcile:

• Opening load
• Additional load
• Delivered quantity
• Returns
• Damaged stock
• Closing physical stock
• Cash and digital tender
• Credit sale

Do not close the route while unexplained differences exceed policy.

Credit and collections

Credit rules need:

• Limit
• Terms
• Overdue policy
• Dispute status
• Sales hold
• Approval authority
• Security or guarantee information

Oyo’s receivables review can prepare customer follow-up, identify broken promises, and route credit exceptions. It should not release a blocked order without authority.

Trade schemes

Schemes can create leakage when eligibility and accounting are unclear.

Define:

• Effective dates
• Customer channel
• Product and pack
• Quantity tiers
• Free goods or discount
• Combination rules
• Budget owner
• Return treatment
• Claim and accounting

Simulate representative orders before activation. Keep a versioned scheme record.

Returns

Separate saleable, damaged, expired, quality, and commercial returns. Capture original sale, batch, reason, condition, approval, stock destination, credit treatment, and supplier claim where relevant.

Oyo reviews can classify and prepare routine cases. Physical condition and disputed claims remain human decisions.

Oyo reviews

Useful starting Oyo reviews include:

Replenishment Oyo review: Prepare transfers and purchase requests from projected availability.

Expiry Oyo review: Identify batches at risk and recommend eligible reallocation.

Credit Oyo review: Prioritize overdue accounts and prepare approved follow-up.

Route exception Oyo review: Summarize delivery, stock, cash, return, and scheme differences.

Each Oyo review needs permissions, limits, approval, duplicate prevention, audit, and recovery.

Management control

Monitor:

• Fill rate
• On-time delivery
• Stockout
• Inventory days
• Near-expiry value
• Return rate
• Scheme cost
• Gross margin
• Route productivity
• Cash and stock variance
• Receivable days
• Credit exceptions

Use drill-down from KPI to transaction.

Implementation sequence

1. Clean item, pack, customer, route, price, batch, and credit data.
2. Stabilize warehouse and accounting flows.
3. First release one region and route.
4. Reconcile van stock and tender daily.
5. Add schemes and returns.
6. Run Oyo reviews in observation mode.
7. Enable approval-required execution.
8. Expand by controlled waves.

Demo checklist

Ask the system to process:

• One normal order
• Credit-limit exception
• Scheme
• Batch allocation
• Partial delivery
• Damage return
• Cash and credit settlement
• Van variance
• Near-expiry transfer
• Oyo review approval and audit

One complete route tells more than a feature list.

Dealer and outlet governance

Separate the party that pays from the outlet that receives stock. A dealer may serve many outlets, while pricing, credit, delivery, and scheme eligibility apply at different levels.

Maintain legal account, delivery location, route, channel, territory, sales ownership, credit ownership, price list, tax status, and active dates. Control duplicates and territory changes. Historical orders should retain the structure used when they were created.

Oyo preparing collection or allocation must know whether to act at account, route, or outlet level. It should not merge balances merely because names look similar.

Secondary sales and demand

Primary dispatch from a distributor does not always equal consumer demand. Where secondary-sales or outlet data is available, keep its source, period, completeness, and lag visible.

Use confirmed orders, route history, outlet sell-through, promotion plans, seasonality, stock at depot and van, return trends, and market events. Do not present a forecast as a confirmed order. A proposal should show facts and estimates separately.

Review forecast error by item, route, and horizon. Large error may require a planner rather than Oyo broader review authority.

Route planning and dispatch

Build a route load from approved orders and available stock. Validate vehicle capacity, delivery window, customer status, batch rule, and document readiness.

The dispatch pack contains route manifest, customer sequence, item and batch, loaded quantity, tender expectation, return containers, and exceptions. Record departure, delivery, refusal, short delivery, return, and arrival. Oyo’s route review compares plan with actual.

Physical loading and count need accountable warehouse confirmation. Oyo should not confirm stock it cannot observe.

Scheme accounting and claims

Free goods and discounts change revenue, margin, inventory, and sometimes supplier claims. Define the accounting outcome before activation.

Reconcile eligible sales, applied benefit, budget, free-goods issue, customer return, supplier-funded claim, accrual, and settlement. Oyo can detect missing claims or overspend. Commercial and finance owners approve adjustments.

Reverse logistics

Create a disposition matrix:

Capture transporter, route, salesperson, original invoice, batch, and evidence.

Settlement controls

At route close, compare cash, digital receipt, credit sale, discount, free goods, delivered stock, return, damage, and closing van stock.

Do not clear an unexplained difference through a generic adjustment. Route it by reason and authority. Monitor aged unsettled routes.

Implementation data pack

Prepare item and pack hierarchy, batch policy, customer and outlet hierarchy, routes, price lists, credit limits, schemes, supplier lead times, opening depot and van stock, orders, and balances.

Validate sample transactions before bulk migration.

Acceptance scenarios

Test an order above credit limit, stock at another depot, a batch below shelf-life policy, overlapping schemes, partial delivery, damaged return, customer refusal, cash difference, lost response, duplicate settlement, and route reassignment.

Inspect inventory, finance, customer balance, scheme, audit, and Oyo review behavior in every case.

Governance after launch

Review route exceptions daily and master data weekly. Review forecast, scheme, credit, expiry, and Oyo review policy monthly.

Assign named owners for items, customers, routes, pricing, schemes, credit, inventory, finance, Oyo reviews, and integrations. Expansion to another region repeats migration, training, reconciliation, and acceptance.

Design the operating day before the screens

An FMCG rollout works better when the team first defines the operating clock. Write down when orders close, when credit is checked, when stock is allocated, when routes are loaded, when vehicles leave, when collections are counted, and when settlement is approved.

That clock exposes dependencies. A route cannot be released if a price or scheme dispute is unresolved. A warehouse should not pick an order that credit has blocked. A van cannot settle while an undelivered invoice or physical return remains unclassified.

Use three practical horizons:

• Today: fulfilment, collections, route exceptions, and stock at risk
• This week: replenishment, expiry transfers, dealer credit, and scheme usage
• This month: forecast accuracy, route economics, claims, write-offs, and policy changes

Oyo should operate inside these cutoffs. A proposal created after load closure belongs to the next approved cycle unless a supervisor authorizes an exception.

Capture orders with evidence

Field orders often arrive through a salesperson, call desk, dealer portal, message, or route visit. The ERP needs one controlled order record regardless of channel. Keep the original source, capture time, outlet, requested delivery date, salesperson, route, price basis, scheme basis, and any promised exception.

Mobile or disconnected capture needs a clear synchronization policy. The device should retain a local reference and submission time. When connection returns, the server must identify duplicates before creating a second order. A changed price, blocked outlet, expired promotion, or depleted batch should return as an exception rather than silently altering the request.

Treat suggestions separately from commitments. Oyo’s order review may recommend quantities from prior sales and current stock, but the salesperson or customer confirms the order. The audit record should show which lines were suggested, edited, accepted, or removed.

Control picking and vehicle loading

Allocation is an accounting promise. Loading is a physical confirmation. Keep the two distinct.

The allocation step selects depot, item, pack, batch, and quantity according to availability, shelf-life policy, customer requirements, and route priority. The warehouse then picks and scans or counts the actual stock. Differences return to allocation for a controlled substitute, short shipment, or route change.

A useful loading control compares:

• Approved route manifest
• Picked item, pack, batch, and quantity
• Physically loaded quantity
• Vehicle or compartment limits
• Required documents and return containers
• Unresolved order or credit exceptions

Release should identify the checker and time. Oyo can highlight missing scans, unexpected batches, capacity conflicts, and orders that changed after the pick began. A responsible warehouse user confirms the final load.

Make credit and collection policy explicit

Customer balances alone do not explain collection risk. Keep credit limit, overdue threshold, grace period, disputed invoice, promised payment, security, route ownership, and exception authority as separate facts.

Before release, Oyo’s credit review can assemble current exposure, open orders, aged invoices, recent receipts, returned payments, disputes, and approved temporary limits. It can recommend release, partial release, cash conversion, or credit review. It should not hide an overdue balance inside a single risk score.

For collections, record the invoices covered, tender, collector, receipt reference, collection time, deposit status, and any difference. Unallocated cash requires a queue with a named finance owner. Sales staff can add context, but finance controls allocation and write-off. This preserves commercial relationships without weakening the ledger.

Read route economics carefully

Revenue by route is not enough. Managers also need delivered value, gross margin, discount, scheme cost, free goods, returns, failed stops, collection effort, distance or time where captured, and unresolved settlement.

Use these measures to investigate route design, not to score individuals without individual review. A rural route, a new territory, and a dense urban route have different service conditions. Poor margin may come from the assortment, promotion, delivery frequency, or customer mix rather than the salesperson.

An operations review should pair the numbers with exception reasons. Oyo can identify routes with falling delivered value, rising returns, or repeated stockouts. A manager decides whether to change visit frequency, load mix, credit policy, or territory.

Define an approval ladder for every Oyo review

Oyo authority should be specific to action, amount, party, location, and risk. For example:

Each approval should expire if the underlying quantities, price, batch, or balance changes. Execution then creates a receipt with the action, record identifiers, actor, approver, time, and outcome. Failures remain visible until resolved or cancelled.

Walk through one representative route

Use one realistic scenario to test the whole design. A dealer places orders for several outlets. One item qualifies for a scheme, one requested batch fails the minimum shelf-life rule, and the account is near its credit limit. The system proposes a different batch and a partial release. The credit manager approves it.

The warehouse loads the confirmed quantities. During delivery, one outlet refuses a damaged carton and another pays two old invoices. The driver returns with saleable stock, damaged stock, cash, and a digital receipt. Each item receives a disposition and each payment is allocated.

At settlement, the route Oyo review compares the manifest with deliveries, returns, tenders, and closing van stock. It finds one unexplained pack difference and assigns it for physical recount. The route remains conditionally closed until finance resolves the difference.

This scenario tests real operating control. It also gives the demo team a repeatable script with visible evidence, approval, execution, audit, and recovery.

Related Oyo guides

• Inventory control in ERP
• FBR POS integration in Pakistan

Sources and further reading

• GS1 standards overview
• GS1 traceability standard
• FBR digital-invoicing FAQ
• Odoo inventory documentation

Run your route scenario

Bring one item family, route, price list, scheme, credit rule, and settlement report to an industry demonstration.

Book an FMCG demo