Scoot Sales

One connected sales journey

Faster Orders, Brighter Business

Record orders during retailer visits, keep them through connection drops, and share them with authorised teams.

Follow the journey

Where this starts

The order used to travel by hand.

Paper moved between people. Now the order travels once.

On paperIn the system
Written twice
Entered once
Carried to the office
Sent from the retailer
Typed again
Reviewed as it is
Chased for detail
Followed up from the record

Retailer score sheets

One master catalogue. A score sheet for each retailer.

Start from the shared product catalogue, then choose and organise the products that matter for each retailer. The salesperson receives that focused list in the field.

Master score sheet → retailer selection
Score Sheet Builder with the retailer list, selected SKU count, visibility toggles and packing size for each product
Score Sheet Settings dialog with retailer-specific visibility, packing, barcode, price and sort-order overrides

Customise where needed

Keep the shared product, then apply retailer-specific visibility and operational overrides.

Mobile product list with search, categories and order selection

The focused list reaches the field

The salesperson works from the configured product selection while retaining search, categories and quantities.

The salesperson’s visit

From arrival to sign-off.

  1. Step 01

    Start the visit

    Open the retailer and begin the guided visit.

    Real guided visit screen with visit stages and order workspace
  2. Step 02

    Build the order

    Find products and enter the requested quantities.

    Real product selection screen with search, categories and add-to-cart actions
  3. Step 03

    Review and sign

    Review the order and capture the signature.

    Real order review screen with quantities, signature and submission actions

Prioritisation and routes

Managers review routes before field work begins.

The system suggests priorities. A manager reviews and approves the route before it is published and assigned.

Exception Control TowerReal capture
Management dashboard showing the Exception Control Tower with route workflow, priority coverage, coverage recovery, commercial risk and data blocker queues

Identify what needs attention

Role-scoped queues surface approved-route work and retailer coverage follow-ups that need a decision.

Priorities and scenariosReal capture
Weekly Route Planner priorities view showing ranked candidate retailers and the route scenario comparison panel

Review the prioritisation

A manager compares ranked candidates and transparent route scenarios before choosing a starting selection.

Visit LogsReal capture
Visit Logs dashboard showing visit totals, tracked retailers, follow-up counts and the latest visit records

Review what happened

Latest visit records and follow-up counts return operational evidence for the next planning cycle.

All interfaces above are real project captures. Visible retailer and activity records are team-entered simulation and testing data, not production validation.

The feedback loop, simplified

Each visit adds better context for the next one.

Everyday field activity becomes useful evidence, while recommendations stay explainable and suggestion-only.

01

Record

Orders, visits and structured outcomes.

02

Understand

Analysis and explainable sales signals.

03

Plan

Priorities, routes and a short visit brief.

04

Visit

The salesperson acts, then records what happened.

Outcomes return as evidence for the next cycle

Benefits by role

One system. A relevant view for each responsibility.

Salesperson

Less paperwork in the aisle.

A guided retailer stop, product search and order entry stay in one continuous workflow, with the order preserved even when connectivity drops.

Simulation data shown
Guided visit screen in the salesperson app, showing the visit stages and order workspace
Salesperson app

Current project position

Built to be evaluated, not overclaimed.

Data context

Records shown are team-entered simulation and testing data associated with real Kuching retailer entities. They are not a complete client production dataset.

Project objective

The proposed approximately 30% reduction in salesperson working time remains a target for controlled user testing, not a measured result.

Responsible interpretation

The current system does not prove productivity gains, lower error rates or sales uplift. Those outcomes require testing and human review.

Location evidence

Location information is supplementary and available only when the user has enabled location sharing.