Routes · Vans · Delivery

ERP for field sales and delivery teams

A field user needs a working day, not an office screen squeezed onto a phone. The office needs to follow the stock and customer activity behind that day.

In short

The van, the visit, and the office share one working day. Can the office account for what left the warehouse, what happened at each customer, and what came back?

Problems it solves

Give field sales and delivery users a structured day, with stock accountability and their commercial work connected to the office.

01

Customer coverage that lives outside the workflow

Use area and route context to organize assignments, planned visits, journey activity, and day-session work.

02

Van stock without an accountable handover

Follow load requests through approvals, dispatch, receipt, and the stock assigned to the route or van.

03

Orders and collections that arrive without context

Capture supported orders, spot bills, collections, and returns with the customer visit and company context. Offline captures remain subject to server validation.

A typical day

A typical day

  1. The user starts the assigned day and checks the route’s stock.

  2. The office and warehouse complete the required loading steps.

  3. The user visits customers and captures the supported commercial activity.

  4. The office reviews synchronized work and the resulting stock and financial outcomes.

Who does what

Who does what

RoleModulesWhat they do
Field supervisorField Sales + Area & RouteSet eligible users, coverage, routes, planned journeys, and field operating rules.
Warehouse/controller teamLogistics + InventoryApprove and complete the relevant load, receipt, and unload handovers.
Field salespersonField SalesWork the customer visits and capture supported orders, spot bills, collections, and returns.
Day-close reviewerField Sales + FinanceReview synchronization/validation and reconcile the counted stock/cash position.

Decisions it supports

Decisions it supports

  • Van sales or pre-sales

    Choose whether the user captures an order for later delivery or sells eligible stock during the visit.

  • Validation responsibility

    Decide which field captures can be validated by the user and which need a supervisor.

  • Day reconciliation

    Compare the route activity and actual count with the expected stock, cash, and recorded transactions.

Exceptions handled

Exceptions handled

SituationWhat happensModules
A load request is approved but not receivedApproval and stock handover are separate steps; review the actual dispatch/receipt state.Controller + field user
A collection is captured offlineSynchronization and the permitted server validation still determine its final business state.Field Sales + Finance
The counted van stock differs from the expected balanceReview unloads, returns, validated transactions, and the day-close exception.Day-close reviewer

What we set up

What we set up

  • Selling channel, field-user eligibility, route coverage, and the permitted day-session flow.

  • Van stock locations, returned-goods locations, warehouse/controllers, and load/unload controls.

  • Price lists, customer credit, spot-billing modes, and create/validate rights.

  • Device allocation, authorized tracking/retention, offline synchronization, and printer formats.

Bring these to the demo

A van load request from approval through receipt. · A customer visit with an order and collection. · Offline capture followed by synchronization, rejection handling, and validation.

Is every field order a spot bill?

No. The supported workflows distinguish an order for later fulfilment from a spot bill and the configured delivery or invoicing process. Choose the flow that reflects how your team actually sells.

Can devices be managed through Prospiro?

Mobile Device Management provides company-scoped Android Enterprise configuration, profiles, enrollment, and device inventory. Availability and remote controls depend on the enabled release and administrative permissions.

What is the difference between field selling and delivery execution?

Field selling covers the salesperson’s visits, orders or spot sales, collections, returns, and day review. Delivery execution covers preparing, checking, loading, dispatching, and proving the customer handover. Prospiro connects these processes while retaining their different ownership.

How does a van-sales day work?

Prepare the eligible user, route, and day session; request and receive the van load; visit customers and capture the permitted sales, collections, and returns; then reconcile the stock/cash position and complete the configured unload and office close.

Does a field order always create an invoice at the customer?

No. The enabled operating model determines whether the user captures an order for later fulfilment or completes an eligible spot-billing flow. Product, package, customer credit, payment, tracking, and validation rules apply to the chosen channel.

What does the office review when a device reconnects?

The server validates queued work against the applicable commercial, stock, user, and session rules. Authorized staff review transaction exceptions and the day’s stock/cash reconciliation. A device queue marked captured is not the same as a final posted transaction.

Book a demo

See Prospiro run your own process.

Tell us what you sell, stock and deliver. We plan the session around the modules you need, in English or Arabic.

  • Built around your products, routes and documents
  • Includes the exceptions, not only the happy path
  • Your request goes straight to our team

Prefer email? info@prospiro.ai

What do you want to see?
We use your details only to reply to your request and follow up on it. Privacy policy
VAT calculator