FAB Field · Mobile

Field Sales Tracking

Complete visits, orders and collections in the field—even offline.

A field sales app that works out of coverage, queueing visits, orders, collections and returns locally and syncing them without conflicts.

  • Orders can be taken out of coverage
  • Visits recorded against events
  • Instant collection receipts
Product tour

FAB Field, screen by screen.

FAB Field · Route

Today’s route in your pocket.

Planned, completed and unplanned visits on one list.

  • Route planningComparison of the planned visit list with actual visits.
  • Visit recordsLocation captured on visit start/end events and shown on a map.
FAB Field · Customer

Know the balance before you walk in.

Balance, amounts due, credit limit, risk status and active campaign.

  • Location at visit start and end only; no continuous tracking
  • Reorder from history
FAB Field · Order

Orders work even out of coverage.

Van-stock sales, campaigns and discount limits; records queue on the device.

  • Offline operationOrders, collections and returns stored locally and synced when connectivity returns.
  • Van stockVan inventory and end-of-day count tracked for van sales.
FAB Field · Collection

Receipt instantly, account update on sync.

Cash and cheque collection, receipt number and end-of-day hand-over.

  • Collections and receiptsCash and cheque collection with receipt numbering and account posting.
FAB Field · Manager

The desktop view is for managers only.

Plan vs actual, offline queue, van stock and collections on one screen.

  • Unvisited customer report
FAB Field manager screen: route, visits and offline queue
How it works

In the field offline, in the centre once connected.

HQ wins on price and stock; field records win on visits and collections.

01

Route loads

Portfolio customers, prices and stock download to the device.

02

Visit

Location at start and end; visits are event-based.

03

Order

From van stock with campaigns, minimum order and discount limits.

04

Collection

Cash or cheque; receipt number instantly.

05

Device queue

Each record carries device ID + sequence number.

06

Sync

A resent order is never booked twice.

ERP

ERP

Orders, collections and returns post to accounts and stock.

Who uses it?

Every role sees its own screen.

  • Field rep

    Route, orders, collections and returns — on the phone.

    Mobile app
  • Sales manager

    Plan vs actual and unvisited customers.

    Manager view
  • Warehouse

    Van loading, end-of-day count and returns.

    Van stock
  • Finance

    Receipts, hand-over and account posting.

    Collections
In a day

A field rep’s day

  1. FAB Field mobile route screen

    Route ready

    Six stops, ordered, on the device.

  2. FAB Field mobile customer and balance screen

    Visit started

    Balance and amount due on screen.

  3. FAB Field mobile order screen

    Offline order

    No coverage; record queued on device.

  4. FAB Field mobile collection and receipt screen

    Collection receipt

    Cheque taken, receipt number issued.

Integration surface

The product is not an isolated island.

Data ownership, error handling, security and audit trails are designed as part of the implementation.

  • ERP and accounting
  • Banking and payment services
  • Devices, terminals and sensors
  • Cargo and logistics
  • BI and reporting
  • REST API · Webhook

What is field sales tracking?

The field sales app is where a rep records orders, collections, returns and visits at the customer site. The critical requirement is that all of it completes even out of network coverage.

Which problem does it solve?

  • Orders are entered at the office in the evening, so stock and dispatch planning always run a day behind.
  • Visit data is self-reported and cannot be verified.
  • Receipts are written by hand, so posting to the customer account is delayed.

How it works

The app keeps the rep's portfolio — customers, prices and stock — on the device. When an order is entered it is written to a local queue and uploaded when connectivity returns. Every record carries a unique device id plus sequence number, so a resent order is not processed twice.

Location capture is event-based rather than continuous: a position is taken at visit start and end. That reduces both battery drain and unnecessary personal data collection.

Conflict resolution is explicit: prices and stock win from the centre, while visit and collection records created in the field are preserved.

Modules

  • Customers and portfolio: visit frequency, address, balance, risk status.
  • Orders: campaigns, discount limits, minimum orders, reorder from history.
  • Collections: cash, cheques, receipt numbering, end-of-day handover.
  • Returns: reason, product condition, return to van stock.
  • Routes: planned visits, actual visits, unvisited customer reports.

Integrations

ERP for customers, prices, stock, orders and accounts, the dealer portal, CRM, bank integration for collections, e-document systems, and the offline architecture covered under mobile app development.

Usage scenarios

  • Pre-sales: orders collected in the field, shipped from the warehouse.
  • Van sales: selling from van stock with immediate delivery.
  • Collection-led field work: collecting due receivables during visits.
  • Merchandising: shelf checks, competitor price and stock observations.

Roll-out

  1. Portfolio and routes: customer assignments, visit frequency, route plans.
  2. Order rules: pricing, discount limits, credit limit behaviour.
  3. Collections: receipt series and end-of-day handover flow.
  4. Measurement: visit completion, orders per visit, collection performance.

Frequently asked questions

Is location tracked continuously?

No. Location is captured at visit start and end events. Continuous tracking drains the battery and collects more personal data than needed; employees must be informed and the scope defined in writing.

Can collections be taken without internet?

Yes. Receipt numbers are issued from a range pre-allocated to the device and uploaded during sync. Each device gets its own range to avoid collisions.

How do we limit the discounts a rep can give?

Discount limits are defined on the server and pushed to the device as a rule. Exceeding the limit is either blocked or routed to approval; no person-by-person exceptions.

See the product with your process

Let’s plan a demo around your workflow—not a generic presentation.

See the field app →
Call me back