Skip to content

Store audits

One store audit, from the plan to the client's file.

Follow one visit through Orbitus. First the visits are planned. Then the auditor records the shelf in the store. A supervisor checks the work, and the client gets the file.

01

Plan the visits

Add your list of stores from an Excel or CSV file, with your own store codes, addresses and map coordinates. Add your people the same way. Then you can give each auditor their visits as tasks. Or the auditor picks stores from a list that shows how far away each one is.

  • You keep the store codes you already use
  • You can import several files at once
  • Tasks and routes for each auditor, if you turn them on
  • Auditors can add a new store they find. You can choose to approve it first.

02

In the store

The auditor opens the store on the phone. If the phone is far from the store, your organisation's rule decides what happens. Then the questions come one per screen: is the product on the shelf, what does it cost, and a photo of the shelf. No internet is needed. The visit is saved on the phone until it can be sent.

  • The same questions repeat for every product on the list
  • A number keypad for prices, and a button for when a price does not apply
  • Photos stay on the phone until they can be sent
  • From the phone, an auditor can suggest a new location for a store

03

Check in the back office

The back office is the website your office team uses. Every visit arrives in its review list, and visits with warnings come first. The supervisor sees the answers, the photos, how long the visit took and where it was sent from. Then they approve it or reject it. They can also reject it and ask for the visit to be done again before the collection period ends. The auditor sees this request the next time the phone connects.

  • Warnings for visits sent far from the store, or done too fast
  • Approve all visits without warnings in one step
  • You can correct an answer while you check it. The change is recorded.
  • The auditor's phone shows which visits were rejected

04

Deliver

Approved visits go out as an export: a spreadsheet file in Excel or CSV. An export template is a saved layout. It sets the file your client gets: which sheets, which columns and what they are called. You can email these files at set times with a download link, or show them in the client portal. Reporting software can also read the data with a private key.

  • A template can be copied to another questionnaire
  • Files can go out every day, every week or every month
  • A JSON data link for reporting software. It needs a key and can only read.
  • In the client portal, your client sees progress and downloads the files

Also in Orbitus

The same system runs surveys

Surveys of households, shoppers or staff run in the same app, on the same phones, with the same team. They use the same review list, the same files and the same client portal. A survey can also go out as a web link.

See surveys

Tell us about your field work

Tell us what your team collects today, and how. We will reply with how it would work in Orbitus and what it would cost.

  • Store audits
  • Field surveys
  • Web surveys
Talk to us