Tenants (every organization on the platform)
| Name | Slug | Tier | Active | Users | Est. MRR | Trial | Created |
|---|
Users (every tenant, every role)
| Name | Role | Tenant | Active | Created |
|---|
FieldOps Cloud
Today's Work
Performance this month
Total Sales:
Total Discount:
Total Collection:
Sales Orders
| Date | Customer code | Name | Order no | Order amount | Discount |
|---|
Cash Collected
| Date | Customer code | Name | Receipt no | Amount |
|---|
Tap a customer to start a sales order for them.
My Customers
Every customer from any of your route plans, not just today's — tap one to start a sales order for them.
Movements
New load / unload request
Items
Offload everything from this van
This creates an unload request for all stock currently on the van, exactly as recorded — not what's typed here. Once approved, the van's stock for these items drops to zero.
| Item No | Description | UOM | Qty | Value |
|---|
All movements
| Code | Type | Sales Rep | Van | Warehouse | Movement date | Value | Status |
|---|
Movements by Sales Rep
Pick a sales rep to see everything they’ve submitted — Load, Unload, Offload, and Sales Order — newest first.
| Code | Description | Van | Warehouse | Qty | UOM | Movement date | Value | Status |
|---|
Movement Detail by Sales Rep by Item
Pick a sales rep, then an item, to see every line they’ve moved — Load, Unload, Offload, and Sales Order — in order, with a running cumulative quantity in the item’s base UOM.
| Date | Voucher | Item code | Description | UOM | Qty | Qty (base UOM) | Cumulative qty |
|---|
Sales Rep Statement of Account
Pick a sales rep to see their running value balance — Load (+), Unload (−), Offload (−), Receipt (−) for cash collected, and Promotion (−) for discounts given — in date order.
| Date | Voucher | Type | Amount | Cumulative amount |
|---|
Sales Order
| Item code & description | UOM | Available | Price | Qty | Line total |
|---|
Order value: 0.00
Tax: 0.00
Total: 0.00
Preview Order
| Item code & description | UOM | Qty | Price | Promo | Discount | Line total |
|---|
Order Value:
Tax Amount:
Discount Value (incl. order promo ):
Invoice Price:
Signatures
Collect Payment
No outstanding invoices for this customer.
| Invoice Number | Invoice Type | Amount (USD) | Settled Amount |
|---|
Total settled: 0.00
Recent sales orders
| Code | Customer | Date | Lines | Total |
|---|
Pending approvals
For unload/offload: approving books the quantity, but doesn't drop van stock yet — that happens when the ERP integration events poll below confirms it.
Van Stock
| Vehicle | Sales Rep | Item No | Description | Base UOM | Qty (QOH) | Booked | Available | Value |
|---|
Collections
Record a payment
| Invoice | Outstanding | Settle amount | |
|---|---|---|---|
| Select a customer first\u2026 | |||
All collections
| Receipt | Amount | Status |
|---|
Stock audits
Submit an audit
Items
All audits
| Code | Mode | Status |
|---|
Approving an unload or offload only books the quantity — van stock's Qty and Booked columns don't actually change until you run this poll, which stands in for JDE's batch job confirming the record.
| Event | Status | Retries | Last error |
|---|
Master data
System Maintenance
Jump to any master data setup screen below.
Company Information
Printed on every invoice and sales order: your logo, name, address, and contact details.
No logo
![]()
User Access Rights
Control which screens each role can open in the Hub. A function row toggles all of its screens for that role at once. Tenant Admin always has full access and is not listed here. Changes take effect when a user next signs in or reloads.
Warehouses
Used as the starting point for a route's "Suggest order (by location)" button, via whichever warehouse a route's user has as their loading warehouse.
| Code | Name |
|---|
Business Units
| Code | Name | Description |
|---|
Channels
| Name | Description |
|---|
Suppliers
| Code | Name |
|---|
Brands
| Name |
|---|
Customers
| Code | Name | Channel | Tel | Type | Credit Limit | Status |
|---|
Customer Branches
| Customer | Branch code | Name | Address |
|---|
Items
| Code | Description | UOM | Price | Taxable | Category | Supplier | Brand | CBM | Weight | Shelf life | Status |
|---|
Alternate units of measure —
Each alternate UOM has its own price and a conversion factor back to this item's base UOM ().
| UOM | Price | Conversion to base |
|---|
Item Categories
| Name | Description |
|---|
Vehicles
Driver assignment is set from the Users form below, not here.
| Code | Plate | CBM | Max kg | Cold | Next service | Assigned to |
|---|
Users
| Code | Name | Role | Balance | Active | Created |
|---|
User Customers
Link customers to a specific sales rep. If a rep has no linked customers, they can serve any customer.
Roles
The 8 built-in roles can be relabeled or deactivated but not renamed or deleted — the app has logic tied to those exact names. A custom role you add here is fully usable for assigning to a user and as an approval chain level, but doesn't gain access to anything else in the app beyond that.
| Name | Label | Description | Active |
|---|
Add a custom role
User Items
Restrict a user to a specific set of items for every load/unload/offload they submit. A user with nothing checked here is unrestricted — can use any item, same as before this existed. Checking even one item switches them to "only these."
ERP Integration
Every movement, payment, and stock audit staged for delivery to the ERP, with its current status. Submitted means our side wrote the record successfully — Confirmed means the ERP’s own batch job has picked it up. Poll simulates that batch job running now; Retry resubmits a failed event using the same idempotency key, so it can never be double-posted.
| Event | Source | Delivery mode | Status | Retries | Last error | Updated |
|---|
Document Numbering Setup
Configure the prefix and starting number for each document type, per sales rep. Each rep has their own sequential counter per document type.
| Doc type | Prefix | Next number | Pad length |
|---|
Archive Transactional Data
Moves all of a sales rep's movements, payments, sales orders, route plans, targets, and van stock to permanent archive tables and removes them from live tables. This is irreversible. The rep's balance is reset to 0.
Day Close Management
Every day a sales rep has closed. Reopening is permanent and full — the rep regains normal access to submit sales orders and payments for that date again, and the original close record (including its totals) is removed. A log of who reopened what, and when, is kept separately for audit purposes.
| Sales rep | Date closed | Closed at | Total sales | Total discount | Total collection |
|---|
Distribution List
Which items a customer can be sold — the same opt-in shape as User Items above: a customer with nothing checked is unrestricted. Use the bulk-add controls to check everything from a supplier, category, or brand in one click, then fine-tune individual items below before saving.
Approval Chains
For each voucher type, who has to approve it, in order, before it's fully approved. Editing this only affects vouchers submitted afterward — anything already pending keeps the chain it was created with.
Promotions
| Code | Description | Discount | Scope | Apply at | Active | Expiry |
|---|
Targets
| User | Year | Month | Amount |
|---|
Route Plans
Route number is assigned automatically — the next one for this user, regardless of date.
| User | Route | Date | Stops |
|---|
Clone routes
Clones every existing route in the route no range below (for the user selected above) into a matching set of new, consecutively-numbered routes — e.g. with routes 1, 2, 3, 5, 6, 7 on file (4 missing, say from a deleted route) and a range of 1 through 7, this creates 6 new routes, 8 through 13, each carrying its corresponding source's own stops: 8 from 1, 9 from 2, 10 from 3, 11 from 5, 12 from 6, 13 from 7. A gap in the range is skipped, not an error. Dates step one day at a time from the starting date; check off whichever days count as a holiday below and a date landing on one moves to the next day instead of scheduling a route there.
Defaults to the day after this user's most recently dated route plan.
Check the customers on this route. Visit order is the order they're listed in below — drag a row to move it, or use the arrows (more reliable on a phone or tablet). Customers with coordinates on file start ordered by nearest-neighbor distance; anyone without coordinates is listed after, in no particular order, since there's nothing to place them by.