Enter your username and password to open the app.
Routes Analysis and Visits Planner.
Upload the Customer List (QuickBooks export). Weekly sales are built automatically from the Sales by User report below, and last no-sale dates from the Non-Service Report. Just select the Customer List and the Sales by User report — the data merges and loads by itself.
You can still upload an old “Weekly Sales Report” here instead; it will be used as-is.
Upload the non-service report (visits with NO sales). Each upload adds new rows to the record kept in the cloud — you can upload just the latest weeks and history is preserved (duplicates are ignored). Visits WITH sales come from the Sales by User report below.
Upload the "Sales by User" transaction report. Each upload adds new transactions to the record kept in the cloud (duplicates are ignored), so you only need to upload the latest weeks — the full history builds up over time. This feeds the weekly sales, classes and every report.
Upload the Inventory List (.xlsx / .xls). The file is stored in the cloud and reloads automatically after a refresh.
Add, edit, or delete the users who are allowed to log in to the app.
| Username | Role | Tabs | Actions |
|---|
Add, edit, or delete the routes and their salesman contact information. Changes are shared across all devices.
| Route No | Salesman | DBA | QBs ID | LaceUp ID | Price Level % | Phone | Actions |
|---|
Pick a route and get the next available customer ID. The ID is region letters + 4-digit number (e.g. NC0422); the route only decides the letters and the number range. Uniqueness is checked by letters + number across the loaded Customer List (active + inactive), Sales, and Non-Service reports, so it never repeats.
| Route | Letters | Range | Used | Free | Next free |
|---|
| Metric | Route Customers | Customers Visited | Total Visits | Visits with sales | Visits with no-sales | Credit only | Total Sales | Total Credits | Grand Total |
|---|---|---|---|---|---|---|---|---|---|
| Load a file to see results. | |||||||||
| Customer | Route | Setup Date | Active Weeks | Weeks Analyzed | Weeks With Sales | Last non sales date | Reason | Date of Sales | Last Visit Sales | Total weeks since last visit | Average / Week | Real Sales / Week | Class | Preferred Day | Preferred Week | Fixed Service | Notes | Recommendation | Total Sales |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Load a file to see results. | |||||||||||||||||||
The year is split into 4 quarters. Enter the weekly goal for each period, then Save. Goals are stored per route so they reload when you open that route again.
Select one or more quarters to list their weeks with sales vs weekly goal.
| Period | Week (Sun – Sat) | Sales | Goal | vs Goal | % of Goal |
|---|---|---|---|---|---|
| Choose a route and at least one period to analyze. | |||||
| Metric | Actual Data | Reclassified Class | Difference | % Change |
|---|---|---|---|---|
| Planned Stops | 0 | 0 | 0 | 0% |
| Route Customers | 0 | 0 | 0 | 0% |
| Driving Time | 0 hrs | 0 hrs | 0 hrs | 0% |
| Service Hours | 0 hrs | 0 hrs | 0 hrs | 0% |
| Total Hours | 0 hrs | 0 hrs | 0 hrs | 0% |
| Route Capacity Used | 0% | 0% | 0% | 0% |
| Estimated Miles | 0 mi | 0 mi | 0 mi | 0% |
| Unscheduled | 0 | 0 | 0 | 0% |
| Planned Sales | $0 | $0 | $0 | 0% |
| Week | Day | Seq | Customer | Address | City | State | Zip | Route | Class | Visit Rule | Preferred Day | Preferred Week | Fixed Service | Notes | Expected Sales / Visit | Real Sales / Selling Week | Real Sales / Visit | Gap / Visit | Avg / Week | Total Sales | ETA / Miles From Prev |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Build planner to see results. | |||||||||||||||||||||
This section is not just a description of the customer classes. It is a complete action plan for how to protect sales, grow the right stores, reduce wasted time, and improve route profitability. The purpose of the class system is to help the team spend more time where the return is highest and less time where service is not paying back enough.
| Class | Business meaning | Default service rule | Main objective | Main risk |
|---|---|---|---|---|
| Class A | Power accounts that carry major weekly volume and heavily influence route performance. | 3 visits every week | Protect volume, availability, and shelf dominance. | Stockouts, poor execution, competitor gain. |
| Class B | Strong accounts with real growth potential and the ability to become future A stores. | 2 visits every week | Grow basket size and upgrade into A. | Underdevelopment and inconsistent follow-up. |
| Class C | Solid middle accounts that can either grow or become time-consuming average performers. | 1 visit every week | Separate growers from non-growers. | Too much time with too little return. |
| Class D | Lower-value accounts that may still be worth keeping, but only under controlled service. | 1 visit every other week | Serve efficiently and test upgrade potential. | Low profitability and route drag. |
| Class E | Very small accounts that often consume more time than they generate in contribution. | 1 visit every 4 weeks | Minimize service cost and keep only core value. | High cost-to-serve ratio. |
| Class F | Weak accounts that should stay only if there is a strategic reason, special territory value, or clear recovery plan. | 1 visit every 4 weeks / subject to removal | Review aggressively and eliminate waste. | Pure route loss. |
These customers carry the route. In many territories, a relatively small number of A accounts produce a huge share of weekly sales. A stores should be treated as protected assets.
B accounts are where disciplined route management creates future A stores. These customers already matter, but they still have room to climb with the right execution.
C customers should be managed with discipline. This class usually contains both hidden opportunities and hidden inefficiencies.
D customers are not automatically bad accounts, but they require control. If they are visited too often, they quietly destroy productivity.
E customers must be handled with discipline. This class often creates hidden cost because the rep gives more time than the account can justify.
F customers should not remain in normal service by default. They need a clear business reason to stay active in the plan.
| KPI | Why it matters | Best use |
|---|---|---|
| Sales by class | Shows where the route truly earns money. | Protect high-value classes and spot weak mix. |
| Stops by class | Shows time allocation. | Check whether low classes are absorbing too many visits. |
| Average sales per visit | Measures service efficiency. | Reduce low-return activity. |
| Weeks since last sale | Detects dormant accounts. | Target D/E/F reviews fast. |
| Growth trend by account | Separates winners from stagnant stores. | Promote or downgrade based on evidence. |
| Miles per sales dollar | Measures route efficiency. | Find remote low-value problems. |
| Order compliance / fill rate | Protects A and B accounts. | Fix service failures before they hurt volume. |
For FG items only (Item type = FG), shows which ones each route buys and which ones it has never bought. Purchases come from the SalesItemDetail sheet; each route is matched by its QBs ID (Setup → Routes) against the Name column. Pick a date range to limit the results, or select a single route to see its full never-bought list.