xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField SalesCRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
GLOSSARY

What is Beat Planning?

Beat planning is the practice of grouping retail outlets into named routes ("beats") and assigning each a repeating visit rhythm, so every outlet is called on at a predictable frequency by an accountable salesperson.

Last reviewed

Beat planning is the practice of grouping retail outlets into named routes — called beats — and giving each beat a repeating visit rhythm and an accountable salesperson. A beat is both a geography and a promise: these outlets, this frequency, this person.

Why beat planning matters

In distribution, revenue is a function of coverage. An outlet that is not visited does not order, does not get its shelf corrected, and does not get told about the scheme running this month. Beat planning is how a business converts a vague ambition ("cover the territory") into a schedule that can be staffed, measured and held to account.

It also makes performance legible. When every outlet belongs to exactly one beat with a known frequency, questions like "which outlets did we promise to visit this week, and which did we actually reach?" have an arithmetic answer instead of an anecdote.

How beat planning works

A beat plan is built in four steps, each of which constrains the next:

  • Universe. Establish which outlets exist and which are worth calling on. Outlets are usually classified by value or potential, because frequency should follow contribution.
  • Grouping. Cluster outlets into beats that are geographically coherent — a beat that zigzags across a city wastes the day in transit.
  • Frequency. Assign each beat a cycle: daily, weekly, fortnightly, or a specific week-of-month pattern. High-value outlets get called on more often.
  • Sequence. Decide the order of stops within the beat, which determines how much of the day is selling and how much is driving.

The output is a repeating schedule — often called a permanent journey plan — from which each day's visit list is generated.

An example

A distributor covers 600 outlets with four salespeople and a six-day week. At an achievable 25 to 30 productive calls a day, the team can make roughly 600 to 720 visits a week. If the top 120 outlets are promised a weekly visit and the remaining 480 a fortnightly one, the weekly demand is 120 + 240 = 360 visits — comfortably inside capacity. Promise the whole universe a weekly visit instead and the demand becomes 600, which is only achievable if every call is perfect and nothing goes wrong. Beat planning is largely the discipline of not making that second promise.

Common variations

  • Fixed vs. dynamic beats. Fixed beats repeat unchanged, which aids relationships and accountability. Dynamic beats re-cut the list each cycle based on recent behaviour, which improves efficiency at the cost of predictability for the outlet.
  • Van sales beats. When the vehicle carries sellable stock, the beat is constrained by what fits on the van as well as by time — see van sales.
  • Multi-role coverage. A merchandiser and an order-taking rep may run different beats over the same outlets at different frequencies.

Where beat plans go wrong

The three recurring failures are worth naming. Plans are built once and never revised, so they slowly stop matching the territory. Frequency is set by habit rather than by outlet value, so effort is spread evenly across outlets that contribute very unevenly. And the planned sequence exists only on paper, because nobody compares it to the order the rep actually drove — which is usually different, and often for good reasons the plan should have absorbed.

How xMatix supports beat planning

In xMatix Field Sales, a beat is a visit route: a named, owned collection of outlet stops, each with its own geofence tolerance. Routes carry their own schedule — day of week, week-of-month pattern, or a cron expression — and visit plans are generated from that schedule automatically over a rolling lead-time window, so the day's list exists before the day starts rather than being assembled by hand.

Sequencing is treated as a first-class, versioned property of the route rather than a one-off calculation. A route can hold a planned sequence, an optimized sequence computed over real road distances, and a most-followed sequence learned from the order reps actually drove on previous visits — so the plan can be corrected by evidence. Stops can be transferred between beats as territories change, and reps can discover and onboard nearby outlets that are not yet in the universe.

Execution is offline-first: visits, orders and in-outlet activities are captured on the mobile app with no connectivity and reconciled later through a durable outbox, which matters because coverage is usually worst exactly where the network is.

Related: route optimization · permanent journey plan · FMCG & distribution solution

RELATED TERMS
← All glossary terms
See how xMatix runs this in practice.
Request a demo