HyperBridge Platformhyperbridge.digital ↗
QuantumOS
Book a demo
QuantumOS Route · Field

Beat plans, outlet visits and an offline operation queue

Beat plans, outlet visits and an offline queue that turns field orders into Channel invoices. No field mobile app yet.

6 visit outcomes
recorded per visit
6 kinds of record sync offline
each with its own conflict rule
One invoice per field order
converting the same order twice returns the same invoice
About

What QuantumOS Field is

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.

At a glance

What is available and what is not

6 capabilities: 2 available, 1 built and tested, 3 on the roadmap.

  • Available

    In production and usable in the QuantumOS admin workspace by customers who have the module.

  • Built and tested

    Built and tested, but not yet a finished feature. It may not be in production on its own, or may have no workspace screen yet. The description says which.

  • Roadmap

    Planned only. Nothing runs yet.

Capabilities

What Field actually does

Each entry says where to find it in the product. Where a capability stops short of what its name suggests, the detail says so.

01

Offline queue

Available

Devices 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

Available

Publish 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 tested

An 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

Roadmap

A 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

Roadmap

Van 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.

  • Planned only
06

Merchandising audits and shelf evidence

Roadmap

Shelf 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
Workflows

How the work moves

From beat plan to Channel invoice

The back-end path, end to end. The offline-queue step needs a field app, and none exists yet.

  1. 01Create a beat plan for a rep and publish it
  2. 02Record a visit to an outlet with an outcome
  3. 03An order draft arrives through the offline queue and is accepted (or held as a conflict)
  4. 04A reviewer settles any conflict, keeping the rep's entry or the system's
  5. 05Convert the accepted draft into a Channel sales invoice
Connections

How it connects to the other modules

These are the hand-offs that work today. They are optional, so you can use one module without the others.

Field writes to Channel

Converted orders land in the Channel secondary-sales ledger through one defined hand-off. Field does not write to Channel anywhere else.

Channel reads Field

Day End warns when accepted order drafts have not been converted into invoices.

Outlets are shared

Visits are recorded against Channel outlets.

Boundaries

What is not built, and where it stops

Roadmap

Not built yet

  • Re-pricing of captured orders against your catalogue
  • Workflows that apply collection, return-request and stock-take records
  • A rep picker and a stop picker in the beat-plan form
Limits

Worth knowing

  • There is no field app for the offline queue yet.
  • Beat plans and visits are recorded in the admin workspace; there is no rep-facing screen.