{"id":23872,"date":"2026-08-03T05:25:41","date_gmt":"2026-08-03T05:25:41","guid":{"rendered":"https:\/\/engineerbabu.com\/blog\/?p=23872"},"modified":"2026-08-03T12:32:53","modified_gmt":"2026-08-03T12:32:53","slug":"field-force-automation-software-development","status":"publish","type":"post","link":"https:\/\/engineerbabu.com\/blog\/field-force-automation-software-development\/","title":{"rendered":"How to Build a Field Force Automation Platform, Beat Planning, PJP, Order Booking, GPS Tracking, and Merchandising 2026"},"content":{"rendered":"

An FMCG company with 500 field sales representatives who each visit 25 outlets per day generates 12,500 retail touchpoints daily. Without a field force automation platform, the information from those 12,500 visits lives in WhatsApp messages, handwritten notebooks, and the salesperson’s memory.<\/span><\/p>\n

The sales manager knows what last month’s sales were. They have no idea what is happening in the market today.<\/span><\/p>\n

A field force automation platform turns every field visit into structured data, who visited which outlet, what order was placed, what the shelf looked like, what the competitor was doing, what the retailer said, and makes that data available to the entire organisation in real time.<\/span><\/p>\n

For FMCG companies, this is the difference between managing the field and letting the field manage itself.<\/span><\/p>\n

EngineerBabu<\/span><\/a> built field operations intelligence for Simba Beer<\/a> and enterprise operations for Adani Group. CMMI Level 5. Google AI Accelerator 2024 Top 20. Contact: <\/span>mayank@engineerbabu.com<\/span><\/a><\/p>\n

\"field<\/p>\n

What a Field Force Automation Platform Must Handle<\/b><\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Function<\/b><\/td>\nModule<\/b><\/td>\n<\/tr>\n
Beat planning<\/span><\/td>\nOptimal visit routing per salesperson per day<\/span><\/td>\n<\/tr>\n
PJP (Permanent Journey Plan)<\/span><\/td>\nWeekly\/monthly recurring visit schedules<\/span><\/td>\n<\/tr>\n
Outlet management<\/span><\/td>\nComplete outlet profile, segment, contact<\/span><\/td>\n<\/tr>\n
Order booking<\/span><\/td>\nOn-the-spot order capture with product catalogue<\/span><\/td>\n<\/tr>\n
Attendance and location tracking<\/span><\/td>\nGPS-based check-in and out<\/span><\/td>\n<\/tr>\n
Outlet visit documentation<\/span><\/td>\nCall notes, competition data, shelf compliance<\/span><\/td>\n<\/tr>\n
Van sales \/ pre-sales<\/span><\/td>\nStock in van tracking, load and unload<\/span><\/td>\n<\/tr>\n
Merchandising compliance<\/span><\/td>\nShelf photo, planogram check, display verification<\/span><\/td>\n<\/tr>\n
Target vs achievement<\/span><\/td>\nDaily and monthly KPI tracking per rep<\/span><\/td>\n<\/tr>\n
Scheme and promotion communication<\/span><\/td>\nActive scheme details available to field team<\/span><\/td>\n<\/tr>\n
Distributor management<\/span><\/td>\nDistributor stock and order visibility<\/span><\/td>\n<\/tr>\n
Analytics and reporting<\/span><\/td>\nVisit productivity, order conversion, coverage<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Module 1 – Beat Planning and PJP Management<\/b><\/h2>\n

What is a beat?<\/b><\/p>\n

A beat is the defined set of outlets that a salesperson visits in a day. A well-designed beat groups outlets that are geographically proximate, that can be visited in a single shift, and that are classified by visit frequency, some outlets need daily visits, others weekly, others fortnightly.<\/span><\/p>\n

Beat planning inputs:<\/b><\/p>\n\n\n\n\n\n\n\n\n
Input<\/b><\/td>\nDetails<\/b><\/td>\n<\/tr>\n
Outlet universe<\/span><\/td>\nEvery outlet the company services, with GPS coordinates<\/span><\/td>\n<\/tr>\n
Visit frequency<\/span><\/td>\nHow often each outlet category needs a visit<\/span><\/td>\n<\/tr>\n
Salesperson home base<\/span><\/td>\nWhere the salesperson starts and ends their day<\/span><\/td>\n<\/tr>\n
Working hours<\/span><\/td>\nHours available per day<\/span><\/td>\n<\/tr>\n
Historical call rate<\/span><\/td>\nHow many outlets a salesperson typically covers per day<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The beat optimisation engine:<\/b><\/p>\n

Given these inputs, the beat planning engine groups outlets into daily beats that minimise total travel time while ensuring every outlet is visited at its required frequency.<\/span><\/p>\n

The output is a PJP (Permanent Journey Plan), a weekly or monthly schedule showing which salesperson visits which outlets on which day.<\/span><\/p>\n

The optimisation approach:<\/b><\/p>\n

Beats are a variant of the Vehicle Routing Problem with Time Windows, each outlet has a required visit frequency (time window constraint) and a location (routing constraint).<\/span><\/p>\n

The platform uses OR-Tools or a custom VRP solver to generate beats that minimise travel time while satisfying all visit frequency requirements.<\/span><\/p>\n

Dynamic beat adjustment:<\/b><\/p>\n

When a new outlet is added to the company’s distribution network, the beat planning engine re-optimises the affected territory to incorporate the new outlet into the closest beat without significantly increasing any salesperson’s travel burden.<\/span><\/p>\n

When a salesperson leaves, their beat is temporarily redistributed across the team until a replacement is hired and trained.<\/span><\/p>\n

Module 2 – Mobile App for Field Sales Representatives<\/b><\/h2>\n

The <\/span>mobile app<\/span><\/a> is the primary interface for field salespeople. It must work in areas with poor connectivity, load fast, and require minimal data entry, a salesperson who spends 20 minutes per outlet on data entry cannot achieve the call rate the business needs.<\/span><\/p>\n

The daily workflow in the app:<\/b><\/p>\n\n\n\n\n\n\n\n\n\n\n
Time<\/b><\/td>\nAction<\/b><\/td>\nApp Screen<\/b><\/td>\n<\/tr>\n
Morning<\/span><\/td>\nView today’s beat<\/span><\/td>\nToday’s outlets list with sequence and map<\/span><\/td>\n<\/tr>\n
Travel to first outlet<\/span><\/td>\nNavigation<\/span><\/td>\nMap with route to first outlet<\/span><\/td>\n<\/tr>\n
Arrive at outlet<\/span><\/td>\nCheck-in<\/span><\/td>\nGPS-confirmed arrival, outlet card opens<\/span><\/td>\n<\/tr>\n
Conduct the visit<\/span><\/td>\nOrder booking, competition notes, shelf check<\/span><\/td>\nOrder screen, visit form<\/span><\/td>\n<\/tr>\n
Depart the outlet<\/span><\/td>\nCheck-out<\/span><\/td>\nGPS-confirmed departure, next outlet cued<\/span><\/td>\n<\/tr>\n
Repeat for all outlets<\/span><\/td>\n\u2014<\/span><\/td>\n\u2014<\/span><\/td>\n<\/tr>\n
End of day<\/span><\/td>\nSummary view<\/span><\/td>\nOutlets visited, orders placed, targets achieved<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

GPS-based attendance and visit verification:<\/b><\/p>\n

The app records GPS coordinates at check-in and check-out for every outlet visit. The platform validates that check-in GPS coordinates match the outlet’s registered location within a defined radius, typically 100 to 200 metres. Check-ins from outside this radius are flagged as ghost visits requiring explanation.<\/span><\/p>\n

Offline capability:<\/b><\/p>\n

Retail markets in India include areas with poor or no cellular connectivity, industrial estates, rural areas, basements.<\/span><\/p>\n

The field app must function offline, allowing the salesperson to conduct their full workflow, book orders, take photos, and complete call reports without connectivity. All data is cached locally and synchronised to the server when connectivity is restored.<\/span><\/p>\n

\"field<\/p>\n

Module 3 – Order Booking Engine<\/b><\/h2>\n

The product catalogue on device:<\/b><\/p>\n

The salesperson’s device has the full product catalogue, products, SKUs, pack sizes, prices, schemes active for this outlet, cached locally so order booking works offline.<\/span><\/p>\n

The order booking flow:<\/b><\/p>\n

    \n
  1. Salesperson opens the order screen for the outlet<\/span><\/li>\n
  2. Previous order history shown, last 4 orders with quantities as reference<\/span><\/li>\n
  3. Salesperson selects products and enters quantities<\/span><\/li>\n
  4. Scheme applicability calculated in real time, “If you order 5 cases of SKU-X, you qualify for a free case of SKU-Y”<\/span><\/li>\n
  5. Order total shown with scheme benefits applied<\/span><\/li>\n
  6. Order submitted, routed to distributor for fulfillment<\/span><\/li>\n
  7. Order confirmation shown to salesperson<\/span><\/li>\n<\/ol>\n

    Van sales \/ pre-sales mode:<\/b><\/p>\n

    For van sales operations, where the salesperson carries stock in their van and sells directly, the app supports two modes:<\/span><\/p>\n

    Pre-sales mode:<\/b> Order is booked during the visit, fulfilled from the distributor later. Van sales mode: Order is fulfilled from stock in the van immediately. Van inventory decrements in real time as each sale is made.<\/span><\/p>\n

    Van load and unload are recorded, opening stock confirmed at day start, closing stock counted at day end. Any variance between calculated closing stock and actual count triggers an investigation.<\/span><\/p>\n

    Module 4 – Outlet Visit Documentation<\/b><\/h2>\n

    The structured call report:<\/b><\/p>\n

    Every outlet visit generates a structured call report, not a free-text note, but a form that captures specific data points that feed into analytics.<\/span><\/p>\n\n\n\n\n\n\n\n\n\n
    Field<\/b><\/td>\nInput Type<\/b><\/td>\nAnalytics Use<\/b><\/td>\n<\/tr>\n
    Outlet availability check<\/span><\/td>\nChecklist, which of our SKUs are currently stocked<\/span><\/td>\nCoverage rate per SKU<\/span><\/td>\n<\/tr>\n
    Competitor stock check<\/span><\/td>\nWhich competitor brands are stocked<\/span><\/td>\nCompetitive intelligence<\/span><\/td>\n<\/tr>\n
    Shelf share estimate<\/span><\/td>\nOur products vs total shelf space %<\/span><\/td>\nShare of shelf tracking<\/span><\/td>\n<\/tr>\n
    Display compliance<\/span><\/td>\nIs our display\/POSM correctly placed?<\/span><\/td>\nExecution compliance<\/span><\/td>\n<\/tr>\n
    Retailer feedback<\/span><\/td>\nStructured categories, pricing issue, quality complaint, competitor offer<\/span><\/td>\nRetailer intelligence aggregation<\/span><\/td>\n<\/tr>\n
    Reason for no order<\/span><\/td>\nIf no order placed, why<\/span><\/td>\nNon-ordering reason analysis<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Merchandising photo compliance:<\/b><\/p>\n

    For key accounts and high-visibility outlets, the platform requires a photo of the shelf or display, captured live from the camera, GPS-tagged, timestamped. The photo is uploaded to the outlet’s record and available for review by the area manager.<\/span><\/p>\n

    Phase 2 can add AI-powered image analysis, automatically detecting whether the planogram is correct, whether our products occupy the correct shelf position, and whether competitor products have expanded their shelf space.<\/span><\/p>\n

    \"\"<\/p>\n

    Module 5 – Target Setting and Performance Management<\/b><\/h2>\n

    Hierarchy of targets:<\/b><\/p>\n\n\n\n\n\n\n\n\n
    Level<\/b><\/td>\nTarget Type<\/b><\/td>\nExample<\/b><\/td>\n<\/tr>\n
    National<\/span><\/td>\nMonthly sales volume by category<\/span><\/td>\n10,000 cases of premium spirits<\/span><\/td>\n<\/tr>\n
    Regional<\/span><\/td>\nRegional allocation of national target<\/span><\/td>\nSouth region: 3,200 cases<\/span><\/td>\n<\/tr>\n
    Area<\/span><\/td>\nArea manager allocation<\/span><\/td>\nBangalore area: 800 cases<\/span><\/td>\n<\/tr>\n
    Territory<\/span><\/td>\nSalesperson allocation<\/span><\/td>\nSR-045: 120 cases<\/span><\/td>\n<\/tr>\n
    Outlet<\/span><\/td>\nOutlet-level target<\/span><\/td>\nOutlet X: 12 cases<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    The live scorecard per salesperson:<\/b><\/p>\n\n\n\n\n\n\n\n\n
    Metric<\/b><\/td>\nTarget<\/b><\/td>\nAchievement<\/b><\/td>\n%<\/b><\/td>\n<\/tr>\n
    Outlets visited today<\/span><\/td>\n25<\/span><\/td>\n22<\/span><\/td>\n88%<\/span><\/td>\n<\/tr>\n
    Orders placed<\/span><\/td>\n18<\/span><\/td>\n15<\/span><\/td>\n83%<\/span><\/td>\n<\/tr>\n
    Order value<\/span><\/td>\n\u20b945,000<\/span><\/td>\n\u20b938,400<\/span><\/td>\n85%<\/span><\/td>\n<\/tr>\n
    SKU productivity (SKUs per order)<\/span><\/td>\n3.5<\/span><\/td>\n3.1<\/span><\/td>\n89%<\/span><\/td>\n<\/tr>\n
    Monthly volume target<\/span><\/td>\n120 cases<\/span><\/td>\n84 cases (22 days)<\/span><\/td>\n70%<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Manager visibility:<\/b><\/p>\n

    The area manager sees every salesperson’s real-time scorecard, who is behind target, who is not achieving their visit plan, who is consistently under-ordering.<\/span><\/p>\n

    Alerts fire when a salesperson falls more than 15% behind their daily visit plan by midday, the manager can call and course-correct in time to recover the day.<\/span><\/p>\n

    Module 6 – Distributor Integration and Stock Visibility<\/b><\/h2>\n

    The field force app is most powerful when the salesperson can see distributor stock levels during the outlet visit.<\/span><\/p>\n

    A salesperson who books an order for 10 cases of SKU-X when the distributor has only 3 in stock is creating a fulfillment problem that reflects on the field team even though it is a supply problem.<\/span><\/p>\n

    Distributor stock visibility in the app:<\/b><\/p>\n

    The app shows, for the outlets in the salesperson’s beat, which SKUs are available at their serving distributor.<\/span><\/p>\n

    When booking an order, if a requested quantity exceeds available distributor stock, the android or <\/span>iOS app<\/span><\/a> warns the salesperson immediately, they can book the available quantity and flag the shortage, or reduce the order to match availability.<\/span><\/p>\n

    Secondary sales reporting:<\/b><\/p>\n

    The platform pulls secondary sales data, what distributors sold to retailers, from the distributor DMS or from the structured data feed described in the <\/span>liquor distribution platform<\/span><\/a> blog.<\/span><\/p>\n

    This secondary sales data is overlaid with field-reported orders to identify discrepancies, orders the field team reported that do not appear in distributor sell-out data, which signals potential order fabrication.<\/span><\/p>\n

    Build Cost: Field Force Automation Software Development<\/b><\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    Module<\/b><\/td>\nCost Range (USD)<\/b><\/td>\nNotes<\/b><\/td>\n<\/tr>\n
    Beat planning + PJP optimisation engine<\/span><\/td>\n$8K \u2013 $15K<\/span><\/td>\nOR-Tools VRP solver<\/span><\/td>\n<\/tr>\n
    Mobile app (<\/span>Flutter<\/span><\/a>, iOS + Android, offline)<\/span><\/td>\n$12K \u2013 $22K<\/span><\/td>\nOffline-first architecture critical<\/span><\/td>\n<\/tr>\n
    GPS attendance + visit verification<\/span><\/td>\n$5K \u2013 $10K<\/span><\/td>\nGeofencing, ghost visit detection<\/span><\/td>\n<\/tr>\n
    Order booking engine + catalogue<\/span><\/td>\n$8K \u2013 $15K<\/span><\/td>\nOffline catalogue, scheme calculation<\/span><\/td>\n<\/tr>\n
    Van sales \/ pre-sales mode<\/span><\/td>\n$5K \u2013 $10K<\/span><\/td>\nVan inventory, load\/unload<\/span><\/td>\n<\/tr>\n
    Structured call report + competition tracking<\/span><\/td>\n$5K \u2013 $10K<\/span><\/td>\n<\/td>\n<\/tr>\n
    Merchandising photo compliance<\/span><\/td>\n$4K \u2013 $8K<\/span><\/td>\nGPS-tagged, timestamped live capture<\/span><\/td>\n<\/tr>\n
    Target setting + live scorecard<\/span><\/td>\n$5K \u2013 $10K<\/span><\/td>\nHierarchy cascade<\/span><\/td>\n<\/tr>\n
    Distributor stock integration<\/span><\/td>\n$5K \u2013 $10K<\/span><\/td>\nReal-time stock visibility in app<\/span><\/td>\n<\/tr>\n
    Manager dashboard + team analytics<\/span><\/td>\n$6K \u2013 $12K<\/span><\/td>\nReal-time field intelligence<\/span><\/td>\n<\/tr>\n
    Analytics + coverage + productivity reports<\/span><\/td>\n$5K \u2013 $10K<\/span><\/td>\n<\/td>\n<\/tr>\n
    AWS + VAPT + Year 1 ops<\/span><\/td>\n$5K \u2013 $10K<\/span><\/td>\n<\/td>\n<\/tr>\n
    Total<\/b><\/td>\n$73K \u2013 $142K<\/b><\/td>\nFull field force platform<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    EngineerBabu built field operations intelligence for Simba Beer and enterprise operations for Adani Group. CMMI Level 5. Google AI Accelerator 2024 Top 20. Contact: <\/span><\/i>mayank@engineerbabu.com<\/span><\/i><\/a><\/p>\n

    FAQs about Field Force Automation Software Development<\/b><\/h2>\n
      \n
    • \n

      What is a Permanent Journey Plan (PJP) in FMCG field sales and how is it optimised?<\/b><\/h3>\n<\/li>\n<\/ul>\n

      A Permanent Journey Plan (PJP) is a recurring weekly or monthly schedule that defines which salesperson visits which outlets on which day. It is “permanent” in the sense that it repeats every cycle, the same salesperson visits the same outlets on the same days every week, building retailer relationships and creating predictable order patterns. PJP optimisation uses route planning algorithms to group outlets into daily beats that minimise total travel time while ensuring every outlet is visited at its required frequency. Fast-moving outlets in high-priority segments require daily or twice-weekly visits. Standard outlets are visited weekly. Low-priority outlets may be visited fortnightly. The optimisation balances visit frequency requirements, geographic proximity, and the salesperson’s achievable call rate per day.<\/span><\/p>\n

        \n
      • \n

        How does the field force app work in areas with no cellular connectivity?<\/b><\/h3>\n<\/li>\n<\/ul>\n

        A field force app designed for FMCG field sales must operate fully offline because a significant portion of retail coverage, rural markets, industrial areas, building interiors, has poor or no cellular data coverage. The offline architecture works as follows: the app caches all required data locally on the device before the salesperson leaves for their beat, outlet list, product catalogue with prices and schemes, current stock levels, previous order history. During the visit, all interactions, GPS check-in, order booking, call report, photos, are written to local device storage. When cellular connectivity is restored, typically when the salesperson reaches an area with coverage or returns to base, the app synchronises all cached data to the cloud server automatically. The critical design requirement is that the salesperson cannot tell the difference between connected and offline operation, the app behaves identically in both modes.<\/span><\/p>\n

          \n
        • \n

          What is the difference between pre-sales and van sales in field force automation?<\/b><\/h3>\n<\/li>\n<\/ul>\n

          Pre-sales is the model where the salesperson visits the outlet, books an order, and the order is subsequently fulfilled from the distributor, typically the next day or later that week. The salesperson carries no stock. Van sales is the model where the salesperson carries inventory in their vehicle and fulfils orders immediately from van stock, the retailer pays and receives goods in the same visit. Van sales is common in beverages, dairy, and bakery distribution where retailers prefer immediate availability. Field force automation handles both models: in pre-sales mode, the order is routed to the distributor system for fulfillment; in van sales mode, the app manages the van’s inventory in real time, decrementing stock with each sale, tracking van load and unload at day start and end, and reconciling van inventory against orders placed at day close.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

          An FMCG company with 500 field sales representatives who each visit 25 outlets per day generates 12,500 retail touchpoints daily. Without a field force automation platform, the information from those 12,500 visits lives in WhatsApp messages, handwritten notebooks, and the salesperson’s memory. The sales manager knows what last month’s sales were. They have no idea […]<\/p>\n","protected":false},"author":1,"featured_media":23873,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1271],"tags":[],"class_list":["post-23872","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-software-development"],"_links":{"self":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/23872","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/comments?post=23872"}],"version-history":[{"count":3,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/23872\/revisions"}],"predecessor-version":[{"id":23891,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/posts\/23872\/revisions\/23891"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/media\/23873"}],"wp:attachment":[{"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/media?parent=23872"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/categories?post=23872"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/engineerbabu.com\/blog\/wp-json\/wp\/v2\/tags?post=23872"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}