Enterprise

EPICO FFA

Field Force Automation Platform

Industry: Distribution & FMCG
Duration: 7 months
Delivered: 2024
Client: EPICO (demo)

ReactTypeScriptNode.jsPostgreSQL

EPICO FFA covers the daily loop of a field sales organisation: plan the route, check in at the outlet, capture orders and report back before the next visit. The mobile app keeps working without a signal and reconciles through a delta sync layer when connectivity returns, so no visit is lost. Dispatchers manage schedules, territories and targets from a web console, and reporting rolls up from individual representatives to regions. This demo shows how offline-first design turns scattered field activity into same-day operational data.

The challenge

What the business was up against

Field teams were operating with almost no reliable data. Representatives planned routes from memory, logged visits in notebooks and sent orders by messaging app at the end of the day, so the office learned about a lost sale long after the buyer had gone elsewhere. Coverage in rural territories was impossible to verify, targets were set without a clear picture of historical performance, and reporting depended on someone retyping spreadsheets. Patchy connectivity made any online-only tool risky, because a failed sync mid-route could erase an hour of work. Managers had activity happening in the field but no dependable way to see it.

At a glance

Industry: Distribution & FMCG
Duration: 7 months
Delivered: 2024
Engagement: Discovery → delivery → support

The solution

What we designed and shipped

We delivered an offline-first representative app and a dispatch console over a shared sync layer. Visits, orders and reports are written to a local queue on the device and pushed as deltas when a connection is available, with conflict rules that keep the field record authoritative. Check-ins capture location and time, territories are drawn and assigned as geofences, and targets roll up automatically from representative to region. Dispatchers adjust schedules and reassign work without waiting for the next sync cycle. Device trust and role checks gate access, so a lost handset cannot expose the territory book.

At a glance

Primary category: Enterprise
Services: Enterprise · Web · Mobile
Team: Product, design, engineering, QA
Delivery: Two-week increments

Key features

What the platform actually does

Operations Dashboard

Live view of visits, orders and coverage across active territories.

Sales Representative App

Offline-first mobile workspace for routes, visits and order capture.

Visit Scheduling & Check-ins

Geofenced check-ins and planned routes for each working day.

Order Capture

Structured product orders taken at the outlet with pricing rules.

Field Reports

Structured forms for competitor, stock and shelf observations.

Territory Maps

Assigned geofences with coverage and overlap shown at a glance.

Targets & Goals

Quota tracking rolled up from representative to region.

Architecture

How the system is put together

Each tier can be scaled, replaced or taken offline independently. Data flows left to right; failure in a downstream tier never blocks the primary transaction path.

Mobile & Web clients

Primary interfaces run offline-first and reconcile through the sync layer.

Offline-first appLocal queue keeps visits and orders usable without signal.
Dispatch consoleScheduling, territory and target management for managers.

API & Sync layer

Sync, queueing and device identity sit between clients and domain services.

Delta syncExchange only changed records since the last acknowledged sync.
Offline queueOrdered change log replayed safely after reconnection.
Auth & device trustPer-device sessions with revocation for lost handsets.

Domain services

Business rules for field activity, sales and performance measurement.

VisitsCheck-in, check-out and visit outcome rules.
OrdersPricing, catalogue and order validation at capture time.
TargetsQuota assignment and performance roll-up logic.
ReportingAggregation of visits, orders and coverage metrics.

Data

Persistence for operational records, hot cache and analytics.

PostgreSQLSystem of record for visits, orders and master data.
Redis cacheSession and hot-path cache for fast mobile responses.
Analytics warehouseHistorical facts for territory and performance analysis.

Technology stack

Chosen for the decade, not the demo

Every dependency here has a long support horizon, an active community and a large hiring pool. That keeps total cost of ownership predictable long after launch.

Demo project

ReactTypeScriptNode.jsPostgreSQL