Mobile app (PWA)
Used by Sales Ambassadors and managers for route planning, GPS check-in, forms, camera photos, issues, visit history and notifications. It installs from the browser—no app store required.
Learn how to plan routes, check in, complete visit reports, work offline and manage field operations in the bolttech Store Visit Tool.
An offline-first field operations platform with a mobile app for visits and a web portal for management.
Used by Sales Ambassadors and managers for route planning, GPS check-in, forms, camera photos, issues, visit history and notifications. It installs from the browser—no app store required.
Used by managers and administrators for approvals, tracking, visits, stores, forms, users, roles, issue configuration, maps, reporting and master data.
Permission-aware: the pages and actions you see depend on your assigned role, permissions, team and country. A missing menu item usually means it is not enabled for your account.
Complete your first sign-in while connected, then prepare the phone for field work.
Use the mobile app URL for field work or the web portal URL for management. Your administrator supplies both URLs.
Enter the email address and password supplied for your account. Your initial sign-in requires an internet connection. Follow any password-change prompt shown by the system.
On mobile, allow precise location while using the app and allow camera access. Location supports check-in/check-out; camera access is required for visit evidence.
iPhone / Safari: Share → Add to Home Screen. Android / Chrome: menu (⋮) → Install app or Add to Home Screen.
Open Profile to check your name, role, team and country. Select your preferred language where available.
Security: never share credentials. Sign out on shared devices. If your account is locked, password is forgotten, or access is denied, contact your administrator.
Start with the section that matches your work. Custom permissions can change the exact options available.
Plan and conduct visits from the mobile app, submit forms and photos, flag issues and review personal activity.
Use the SA mobile flow, plus the web portal to assign and approve routes, monitor the team and resolve issues.
Manage country-level stores, users, roles, forms, issue configuration and reporting from the web portal.
Manage country context and global master data with the broadest system permissions.
| Scope | Typical role | What it means |
|---|---|---|
| Own | SA | Your routes, visits, responses and activity only. |
| Team | ASM | Data belonging to members of your assigned team. |
| All | Admin / SuperAdmin | All permitted data in the active country context, or global master data where enabled. |
Your mobile navigation keeps daily work, history and account settings close at hand.
See approved, pending and rejected plans; today's stores; weekly progress; sync status; visit actions; and future weeks.
Review your own visit activity and history. Open completed records to view previously submitted reports.
Build and submit a seven-day store visit plan with visit days and optional objectives.
Start an unplanned visit at a store that is not on the approved route.
Review alerts and updates relevant to your plans and work.
Check account information and role context, change language where enabled, or sign out.
Prepare the week, understand every route state and keep the plan current.
Choose the start date for the seven-day period.
Search by store name or use available team, region and channel filters.
Select a day and store, then add optional visit objectives. Repeat for each planned stop. The tool warns about duplicate same-store, same-day entries.
The proposal appears under Pending until a manager approves or rejects it.
| State | Meaning | Available actions |
|---|---|---|
| Approved | Ready for field execution. | Check in, manual check-in where available, skip an eligible current-week visit, fill details, view report, check out. |
| Pending | Waiting for manager decision. | Review the proposal. If a check-in action is presented, you can begin that visit. |
| Rejected | The manager returned the plan with a reason. | Read the reason, Re-propose with changes, or dismiss the rejected plan. |
| Skipped | An approved visit will not be completed. | View the reason/note; use Undo while the route week remains active. |
On an eligible current-week route, tap Skip, choose an administrator-defined reason and enter a note if required. The change is saved offline and syncs later.
Use Cancel Week only when the whole approved weekly plan should be withdrawn. Confirm carefully—the action affects the week's route plan.
Check in at the correct store, record the result and finish with a complete report.
Open the route card and confirm the store name, visit day and objectives. Review available store context such as location, grade, channel and previous information.
Tap Check In. The app records time and location. Normal geofence check-in expects you to be within approximately 300 metres of the store.
If GPS is unavailable or you are outside the normal range, use the presented manual/override option and choose an accurate reason, such as GPS issue, relocated store or manager-approved override. Overrides are auditable.
Select a form if more than one applies. Answer the fields shown for your team, country, role and store grade. Questions may appear or disappear based on earlier answers.
Open Photos and use the in-app camera. At least one camera photo is required before continuing. Remove and retake an image if it is unclear.
Choose a severity and category, write a factual description, then tap Add Issue. You can add multiple issues or continue without one.
Check the selected form, answers, photos and issues. Use Back to correct anything before submission.
Tap Check Out. The app completes the visit and queues the form, photos, issues and checkout for synchronization. Approved visits may also auto-check out when you leave the geofence; manual checkout is available as a fallback.
Ad-hoc visit: open Ad-Hoc Check-In, find the store and tap Check In Now. An ad-hoc visit is fully recorded but is not tied to a pre-approved route. Finish any active visit before starting another.
Do not close or refresh with unsaved work. The app warns before a page close when form answers, photos or issues have not yet been submitted.
Continue field work through poor connectivity and let the queue deliver records when service returns.
Previously synchronized approved routes, published form templates and skip reasons are cached on the device.
Form responses, camera photos, issues, checkout and skip/undo changes are stored locally until they can be sent.
Sync checks periodically and when the browser comes online. Retry delays increase after failures; the pending count remains visible.
ASMs use the same mobile visit functions as SAs, plus team-level controls and reporting on the web.
DashboardMonitor visit completion and operational indicators for your permitted team.
RoutesAssign stores and visit days, add objectives, and review route plans.
Approve or reject proposalsApprove to make a plan actionable, or reject with a clear reason so the SA can re-propose.
VisitsOpen submitted visits and inspect timings, form responses and photos.
IssuesFilter escalations, review details and progress them from open to acknowledged to resolved.
Visit MapReview where visits occurred and investigate location overrides where visible.
Tracking ReportCompare assigned, pending and completed work by representative and date.
Additional reportsUse Form Coverage and Partner Report when granted by your permissions.
Write useful rejection reasons. The reason appears to the SA and should say exactly what must change—store, day, workload or objective.
Admins maintain the data, access and workflows used by the field in their permitted country.
Add and edit stores individually or import data from CSV/Excel. Maintain store name and code, GPS coordinates, grade, channel, region and available performance data. Accurate coordinates directly affect geofence check-in.
Create and maintain accounts, assign country, team and roles, activate/deactivate access where supported, and reset passwords. Verify the user's scope before saving.
Use base or custom roles. Permissions are granular by module and action—view, create, edit or delete—and by data scope—own, team or all. Apply least privilege and test custom roles before broad assignment.
Create versioned visit forms with text, number, choice, checkbox, radio, photo, rating and date fields. Add conditional branching, preview the form, define targeting by team/country/role/store grade as available, and publish the correct version. Historical responses retain their submitted version.
Maintain the categories and severity options shown to field users. Keep labels clear and non-overlapping so issues can be reported and filtered consistently.
Oversee plans and visits within your scope. Visit deletion is permission-restricted and should only be used according to local data-governance rules.
Recommended setup order: master/reference data → stores → teams and users → roles → forms → issue configuration → route assignment. This reduces missing options and targeting errors.
Use the view that matches the operational question, then filter to the correct country, team and date range.
High-level completion and issue indicators for the current permitted scope.
Detailed visit records with submitted form responses and photos.
Geographic view of visit activity and location evidence.
Route execution and completion by user and time period.
Visibility into form submission coverage across the permitted operation.
Partner-oriented reporting view where enabled for the account.
Exports: where an export control is available, CSV data can support Power BI or offline analysis. Exported content is permission- and scope-restricted; handle it according to company data policies.
SuperAdmins have broad capability but still operate in an explicit country context for scoped pages.
After sign-in, choose Select Country to Manage. The gate cannot be dismissed without a selection because portal data must be scoped.
Manage stores, users, forms, issues, routes and reports for the active country using the same workflows as an Admin.
Open Master Data to maintain available Country, Team, Region and Channel records. This page is restricted to SuperAdmin.
Confirm the active country before bulk operations or configuration changes. Broad permissions increase the impact of mistakes.
A consolidated inventory of the user-facing pages and capabilities available in the current tool.
| Area / function | SA | ASM | Admin | SuperAdmin |
|---|---|---|---|---|
| Mobile: My Routes, weekly progress, route statuses | Own | Own | If enabled | If enabled |
| Mobile: Propose Plan, re-propose, dismiss, cancel week | Yes | Yes | If enabled | If enabled |
| Mobile: Planned and ad-hoc check-in | Yes | Yes | If enabled | If enabled |
| Mobile: GPS geofence, override, manual/auto checkout | Yes | Yes | If enabled | If enabled |
| Mobile: Dynamic form, camera photo, issues, review | Yes | Yes | If enabled | If enabled |
| Mobile: Skip visit / undo skip | Eligible routes | Eligible routes | If enabled | If enabled |
| Mobile: Activity, visit report, notifications, profile/language | Own | Own | If enabled | If enabled |
| Mobile: Offline cache, pending queue, automatic sync | Yes | Yes | If using mobile | If using mobile |
| Web: Dashboard | No portal access | Team | Country | Selected country |
| Web: Issues and status workflow | No portal access | Team | Country | Selected country |
| Web: Visits and submitted photos/forms | No portal access | Team | Country | Selected country |
| Web: Routes, assignment and proposal decisions | No portal access | Team | Country | Selected country |
| Web: Stores and CSV/Excel import | No | By permission | Yes | Yes |
| Web: Forms and publishing | No | By permission | Yes | Yes |
| Web: Users and password reset | No | By permission | Yes | Yes |
| Web: Roles and granular permissions | No | By permission | Yes | Yes |
| Web: Visit Map and Tracking Report | No portal access | Team | Country | Selected country |
| Web: Form Coverage and Partner Report | No portal access | By permission | Yes | Yes |
| Web: Issue Configuration | No | By permission | Yes | Yes |
| Web: Country selection and Master Data | No | No | No | Yes |
“If enabled” and “By permission” reflect role customization. Your administrator can grant a different combination of module, action and data-scope permissions.
Resolve common field and portal issues without risking unsynchronized data.
Your role or data scope probably does not grant it. Portal access is restricted to ASM, Admin and SuperAdmin roles. Ask an administrator to review your permissions rather than sharing another user's account.
Select a country and tap Continue. Country-scoped pages remain gated until a country is selected.
Complete or manually check out the active visit before starting another. If the tool offers to close a previous open visit, verify the store before confirming. Very old open visits may be automatically closed by the system.
Open the Rejected tab, read the manager's reason, choose Re-propose, update the plan and resubmit it.
Use these short exercises in a training environment before working with live data.
Need more help? Capture the page name, time, store/user involved and visible error. Send these details through your organisation's approved IT or SVT support channel. Do not include passwords.