Field is the back-end half of field-sales execution. Admins with the right permissions publish beat plans and record outlet visits in a workspace with four tabs: Overview, Visit queue, Beat plans and Sync status. Underneath is an offline queue that a device can send changes to and fetch updates from. It ignores repeated sends, rejects out-of-order ones, and gives each type of record its own rule for settling conflicts. The field-sales mobile app that would use that queue is not built, so nothing calls the queue yet.
01
Offline queue
AvailableDevices register, send changes and fetch updates. Repeats, ordering and conflicts are handled by the system.
Each change carries an ID from the device, a sequence number and a timestamp. A repeated ID is treated as a duplicate, a sequence that goes backwards is rejected, and device clocks are never used to order or settle anything. Each record type has its own conflict rule. Fetching uses stable, bounded batches, so a long catch-up does not shift while new changes arrive. This is the back-end half only: no field app calls it yet.
- Record types: visit, order draft, collection, return request, stock take, merchandising observation
- Conflict rules: visits, stock takes and merchandising observations keep the newest entry (by system-adjusted time); order drafts need manual resolution; collections and return requests keep the system's version
- A device cannot be taken over by another user
- Only order drafts have a downstream use today; the other record types are stored with their conflict outcome
Where to find it: Field workspace, Sync status tab
02
Beat plans, visits and conflict review
AvailablePublish beat plans, record outlet visits with an outcome, and settle sync conflicts by hand.
A beat plan has a code, a name, a rep, an optional day of the week and stops, and moves from draft to published to retired. A visit is recorded against an active outlet with a rep, an optional beat plan, an outcome and notes. The system stamps the times: recording a visit without an outcome opens it, and recording one with an outcome closes it. An order-taken outcome must point to its order draft. Recording the same visit twice is safe. The Sync status tab lists devices and the conflicts that need review, where a reviewer keeps either the rep's entry or the system's. The first decision wins; reopening means a new conflict, not a silent change.
- Visit outcomes: order taken, no order, no response, closed, payment collected, return recorded
- Beat plan states: draft, published, retired
- Keeping the rep's entry on an order draft makes it convertible to a Channel order
- The Overview shows published beats, open visits, 7-day visits and orders, and active devices
Where to find it: Field workspace, Overview, Visit queue, Beat plans and Sync status tabs
03
Order capture with Channel conversion
Built and testedAn accepted order draft converts into a Channel sales invoice, once.
The visit drawer offers Convert to Channel order for an accepted draft. Conversion writes a sales invoice into Channel through the same document writer Relay uses, so converting twice returns the same document. Re-pricing against your catalogue is not built: conversion trusts the prices captured on the draft.
- Needs an accepted order draft with a seller and at least one line
- The invoice number comes from the original order, so a retry does not create a new one
- Prices come from the draft and are not re-checked against your catalogue
Where to find it: Field workspace, Visit queue, visit drawer
04
Field-sales mobile application
RoadmapA dedicated app for reps to work a beat offline is planned, not built.
Nothing runs yet. The offline queue above is the foundation it would use.
- Planned only
- No app calls the offline queue yet
05
Van sales
RoadmapVan inventory, on-the-spot billing and delivery confirmation are not built.
Van sales is planned as a way of working inside Field rather than a separate product. Nothing is built yet.
06
Merchandising audits and shelf evidence
RoadmapShelf evidence, audits and competitor observations are not built.
The offline queue has a record type for merchandising observations, but no workflow or screen uses it. The capability is planned only.
- Planned only
- The record type exists in the queue; nothing applies it