Industry CRM Use Cases

 ·  8 min read

CRM for FMCG: Distributors, Secondary Sales and Trade Promotions

FMCG CRM is a coverage and execution system, not a deal pipeline. A practical model for outlet data, secondary sales, field visits and trade promotions.

Braj Raj Singh Kushwaha

CRM consultant, business analyst and solution architect

Why a standard deal pipeline breaks in FMCG

Most CRM advice assumes a small number of large, slow-moving deals. FMCG works the other way round: thousands of small transactions, a long tail of outlets, and a distributor standing between the company and the shelf. Copy a pipeline from a B2B services template and you get stages nobody trusts, a forecast that ignores sell-out, and a field team that goes back to WhatsApp.

The useful question is not which CRM has the longest feature list. It is which parts of the commercial model the CRM should own, and which belong in the distributor’s system or the ERP. Get that boundary right and the configuration becomes much simpler.

Decide what the CRM owns before you configure anything

Write down the route to market for each channel: general trade, modern trade, e-commerce, and any institutional or horeca business. Then mark each step as owned by the ERP, the distributor’s system, or the CRM.

A workable default:

Business areaPrimary systemCRM’s role
Invoicing, stock, creditERP or distributor systemRead-only reference
Distributor master and commercial termsERP or financeReference and relationship notes
Outlet master, visits, coverageCRMSystem of record
Secondary sales at outlet levelCRM or distributor systemCapture, reconcile, analyse
Trade promotion execution and claimsCRMWorkflow, evidence, approval status
Service requests and complaintsCRMCase management

Two rules prevent most integration pain. First, one system owns each field; do not let the CRM and ERP both edit the same customer name. Second, the CRM should not become a second ERP. If the finance team still needs the ERP for invoicing, the CRM’s job is to make the field work visible and consistent, not to reproduce every financial control.

Build an account model that reflects the route to market

Do not put distributors and outlets into one generic account table with a type field. They behave differently: a distributor has credit terms and a commercial agreement; an outlet has a location, a channel, a visit frequency, and a shelf. Separate objects make reporting and permissions much easier.

A practical minimum model:

  • Distributor — legal entity, territory, commercial terms, primary sales contact.
  • Outlet — name, address and geocode, channel, outlet tier, assigned territory and route, current distributor, status.
  • Contact — the human at the outlet or distributor, with a role and a phone number that is actually used.
  • Territory and route — a hierarchy for reporting and a sequence for the working day.
  • Product or SKU — usually owned by the ERP and referenced in the CRM.
  • Promotion — the commercial offer, participating SKUs and outlets, period, budget, and approver.

On a platform such as Creatio, this maps to separate objects for distributors, outlets and promotions, with the visit flow on the mobile app and promotion approvals handled by a business process. The platform can mirror the route to market; the data model still has to be decided first.

The outlet master is the hardest part. Names repeat and vary: “Sharma Store”, “Sharma General Store”, and “Sharma Kirana” can be the same shop. Use a stable internal outlet code, and where possible a geocode or distributor outlet code, plus phone matching. Define who reviews a probable duplicate; automatic merging without review is how order history ends up attached to the wrong shop.

Capture secondary sales without pretending to replace the distributor system

Be precise about the three flows. Primary sales run from the company to the distributor. Secondary sales run from the distributor to the outlet. Tertiary sales run from the outlet to the consumer. Most FMCG teams have good primary numbers and weak secondary visibility; the CRM should improve the second without inventing the third.

Choose one ingestion pattern per channel and be honest about its latency:

  • Rep-entered order or sell-out at the outlet. Good for direct distribution and high-value outlets. The quality depends on visit discipline.
  • Distributor upload or portal submission. Good for volume, but the data arrives when the distributor chooses to send it. Publish a “data as of” field rather than implying real time.
  • System integration. Best where a distributor management system already holds reliable outlet-level data. Integrate rather than re-key.

Agree the granularity before build: daily or weekly, SKU level or category level, invoice-level or aggregated. Then reconcile. A gap between distributor-reported secondary sales and the sum of outlet records usually means missing outlets or timing differences, not fraud. Reconcile on a fixed cadence and record the explanation.

Design field execution around the visit

The field app is where an FMCG CRM succeeds or fails. A rep has minutes between stops, often with poor connectivity. Design for that reality.

A useful visit flow is short: check in, review the outlet’s must-stock list, capture the order, record visibility or merchandising compliance, note a competitor price if relevant, and check in on any outstanding collection or complaint. Every field should drive an action. If a question never changes what anyone does, remove it.

Journey plans and visit frequency should follow outlet tier and channel, not a single blanket rule. GPS check-in can provide coverage evidence and route adherence, but publish a clear policy: it supports planning and fair coverage, not surveillance. Offline capture matters more than a polished animation.

Treat trade promotions as a workflow, not a spreadsheet

A promotion needs a record before it needs a dashboard: mechanic, period, participating SKUs and outlets, budget, approver, and the evidence required for a claim. In the CRM, that becomes a workflow with states — proposed, approved, active, claim submitted, verified, settled.

Two controls are worth building early. First, a unique key for promotion, outlet and claim period prevents duplicate claims. Second, separate execution evidence from financial approval: the sales team records what happened at the outlet, finance confirms the claim against the agreed terms.

Report on execution quality, not just volume

A sales manager does not need twenty charts. Three views cover most of the job:

  • Daily execution: planned versus actual visits, outlets not visited, visits completed without an order.
  • Weekly coverage and quality: unique outlets covered, new outlets opened, must-stock compliance, lines per order, data freshness.
  • Monthly promotion view: outlets enrolled, execution evidence complete, claims by status, and spend against budget.

Avoid borrowing benchmark percentages from the internet. Coverage and strike-rate targets depend on channel, outlet tier, and route to market. Set thresholds from your own baseline, then improve them.

Roll out in slices

Start with one channel and one territory. Clean the outlet master for that slice, configure the visit flow, agree the secondary-sales method, and build the three reports. Run a full sales cycle before extending. This exposes the arguments about outlet ownership, visit frequency, and promotion eligibility while the scope is still small.

Train by role, not by feature. Reps need the visit flow; supervisors need coverage and route planning; distributors need the submission process; finance needs the claim states. Adoption is visible when data is entered during the visit rather than reconstructed at month end, and when managers use the coverage view in their regular reviews.

Put one person in charge of the outlet master

An FMCG CRM decays through its outlet data faster than through its workflows. Outlets open and close, change hands, move, and get reclassified. Name an owner for the outlet master, define a change process, and review duplicates and stale records on a fixed cadence. Territory reassignment and rep changes should be handled as governed events, not bulk edits.

Track a small set of data-quality measures: completeness of mandatory fields, duplicate rate, percentage of outlets visited as planned, and the lag on secondary-sales submission. Review them monthly with the commercial owner. A CRM with clean coverage data and a modest feature set beats a feature-rich system nobody trusts.

A first-release checklist

  • One channel, one territory, and a named business owner.
  • Separate objects for distributor, outlet, contact, territory, route, and promotion.
  • A defined minimum outlet record, with duplicate review.
  • A visit flow a rep can finish in minutes, including offline capture.
  • One agreed method for secondary sales, with a published data-as-of field.
  • A promotion workflow and a duplicate-claim control, if promotions are in scope.
  • Three reports: daily execution, weekly coverage, monthly promotion spend.
  • Clear integration boundaries with the ERP and any distributor system.
  • Acceptance tests written against real outlets and a real visit week.

The measure of an FMCG CRM is not how many features it has. It is whether a sales manager can trust coverage, a rep can finish a visit before the next stop, and finance can trace a promotion claim to evidence. Get those three right and the platform decision becomes much less risky.

Scoping an FMCG CRM rollout?

Bring the channel and territory you want to start with. We will look at the outlet data, the visit flow and the reports before deciding anything about the platform.

Start a conversation Creatio CRM for FMCG