Retail store visit plan: call frequency, schedule and route

What a store visit plan is made of

Field work in distribution breaks down neatly into four levels. Each has its own planning horizon and its own cost of getting it wrong.

• Territory and outlet base. The list of active and prospective outlets assigned to a rep, with coordinates, format, opening hours and a contact person. It's reviewed whenever the customer base changes.
• Call frequency. How many times per cycle each outlet needs a visit. It's set by segmentation rules, not by the rep's preferences.
• Store visit schedule. How calls are spread across the days of the cycle: which weekday the rep comes to a given store.
• Daily route. The order in which today's outlets are covered, taking opening hours and travel time into account.

The classic mistake is to start with the route. A rep plots a convenient path through familiar addresses; the path is short, but outlets that are awkward to reach systematically fall out of it. A short drive through the wrong set of addresses doesn't make a territory covered.

The right order is the reverse: first the outlet base and frequency, then a check that the workload fits into working hours, then weekdays, and only after that the stop sequence. Each level constrains the next. If frequency is inflated, no day-by-day layout will save you, and if days are assigned without regard to geography, the route within a day will zigzag across the whole city.

It's just as important to agree on who owns each level. The outlet base and frequency are signed off by the channel manager or supervisor: this is a decision about where the company invests its field team's time. The weekly layout is best built together with the rep, who knows the quirks of each neighborhood and store. The stop sequence within a day is better calculated automatically, leaving the rep the right to flag a deviation rather than reshuffle addresses at will.

Call frequency: segmenting outlets by value

Giving every outlet the same frequency is the most expensive version of a plan. A large store with a wide shelf and a small kiosk need very different levels of attention, and if the rep calls on both every week, their time goes where it doesn't pay off.

The core tool is customer base segmentation. Most teams run an ABC analysis on several months of shipments and add qualitative criteria on top:

• Volume and potential. Current shipments plus an estimate of how much the outlet could take with good assortment coverage.
• Format and channel. Chain store, independent retail, HoReCa, pharmacy — each has its own ordering cycle and its own merchandising requirements.
• Strategic importance. An outlet in a new area, a store where a competitor is merchandising aggressively, a customer that's still being onboarded.
• Delivery cycle. If a store orders every two weeks, it doesn't need a weekly visit just to place an order.

Segments feed into a frequency matrix: for each category, the number of calls per cycle and a standard call duration. For example, category A might get a full weekly visit, B one every two weeks, and C a monthly call with a quick shelf check. The actual numbers depend on the product category and your agreements with customers, so derive them from your own data rather than copying someone else's playbook.

Review the segmentation regularly — say, once a quarter. An outlet whose shipments have grown moves up a category and gets more attention, while one that has stopped ordering frees up the rep's time for promising addresses.

Prospects need a rule of their own. If they don't get a slot in the plan, reps will only work the existing base and the territory will stop growing. A common approach is to reserve a limited number of calls per cycle for acquisition and record the outcome of every contact: interest, a refusal or an agreed follow-up meeting.

Workload: how many outlets fit into a working day

Once frequency is set, the plan has to be tested for feasibility. It's easiest to count in minutes per cycle: for each outlet, multiply the number of calls by the call duration, add up the results and then add travel time between addresses.

Compare that demand with the rep's available time. From the working day, subtract:

• Travel to the first outlet and back. On large territories this is a sizable chunk of the day, and it's often forgotten.
• Driving between outlets. It depends on how dense the area is, on traffic and on how well each day is grouped by district.
• Waiting in the store. The buyer is busy, a delivery is being received, the right person is at lunch — this time is unavoidable and has to be built into the plan.
• Admin work. Reports, order approvals, team meetings and check-ins with the supervisor.

If demand exceeds available time, you have three options: reduce frequency for the lower categories, shorten the standard call by standardizing what happens in store, or split the territory. This has to be settled at the planning stage. Otherwise the problem will surface on its own: the rep will start choosing which calls to skip, and the choice will almost always favor convenient addresses.

It also pays to balance workload across territories. If one rep's plan fills the day to the last minute while their neighbor has time to spare, moving outlets along the territory border achieves more than trying to speed up the overloaded person.

Repeat the workload check after every significant change: a new retail chain coming on board, a wider assortment, seasonal growth in traffic. A plan that was feasible in spring may no longer fit into a day by autumn without a single change to the outlet base.

Store visit schedule: laying out calls across the cycle

The schedule answers the question of which day the rep comes to a given outlet. A good schedule is stable: the store knows the rep drops by on Tuesdays and prepares its order for that day, and the rep doesn't waste time arranging every call.

Build the layout step by step:

• Choose the cycle length. If the matrix includes calls every two weeks or once a month, the cycle has to accommodate them — for example, four weeks built on a repeating weekly framework.
• Split the territory into daily zones. Give each weekday a compact area so that driving within the day stays short.
• Place outlets with hard constraints first. Stores with fixed order-taking days, narrow opening hours or a contractually agreed call day go in before anything else.
• Spread frequent calls evenly. An outlet with two calls a week should get them at a sensible interval, not on back-to-back days.
• Distribute infrequent calls. Category C outlets are spread across the weeks of the cycle so that no single week gets overloaded.
• Leave a buffer. Keep part of the day free for new outlets, unplanned stops and a second attempt if a store was closed.

Once the layout is done, check the workload for each day separately. The weekly average can look fine while Monday turns out to be impossible. Public holidays, vacations and outlets closing for refurbishment also need rules written in advance: which calls move to the next day and which are skipped until the next cycle.

Sales rep route planning within the day

A sales rep's route is the order in which the outlets assigned to that day are covered. With only a few addresses the task looks simple: connect them on a map and go. The complexity comes from the constraints.

Opening hours and receiving windows. Some stores only see reps in the morning, others close for lunch, and at others there's no point approaching the buyer while a delivery is being unloaded. Priorities. Category A outlets and calls tied to an order deadline must make it into the day even when things go wrong. Call duration. A quick drop-in and a full visit with merchandising push the rest of the day back by very different amounts. Start and finish. A route may begin at home, at the office or at the warehouse, and that changes the optimal sequence.

With just a dozen addresses and a few time windows, the number of possible sequences becomes far too large to work through in your head. The rep picks a familiar order, and the route works, but with needless backtracking and waiting outside closed doors. In essence this is the same vehicle routing problem (VRP) as in courier delivery, and it's solved with optimization algorithms, not a map on the wall.

Think through what happens when the day deviates from the plan. If an outlet is closed or a call runs long, the rest of the route has to be rebuilt, and the missed call either rescheduled for another attempt or logged with a reason. Otherwise, by the end of the week the plan quietly fills up with misses nobody ever saw.

A useful habit is to compare the planned route with the actual one. The gaps show where the plan has lost touch with reality: a store consistently opens later than listed, a call at a particular outlet always runs over the standard, crossing downtown at rush hour takes noticeably longer than estimated. Each of these observations feeds back into the plan: the opening hours in the outlet record, the standard call duration or the boundaries of the daily zone get corrected.

Tracking execution and automating the plan

A visit plan only makes sense if you can see how it's being executed. The minimum set of metrics:

• Visit plan completion — actual calls as a share of planned ones, by rep and by outlet category.
• Base coverage — how many active outlets were visited at least once during the cycle.
• Repeat misses — outlets that drop out of the schedule two cycles in a row.
• Unplanned calls — stops at outlets that weren't on the schedule for that day.
• Reasons for misses — store closed, nobody in charge on site, ran out of time.

When the plan lives in a spreadsheet, these metrics are compiled by hand and late, and confirmation of each call rests on the rep's word. In itlogist, plan and actuals sit in one system: visit tasks are assigned to reps, routes are visible on a live map, and the stop sequence is calculated by an OR-Tools-based optimization engine that accounts for time windows and other constraints. Reps work in a mobile app with photo reports and checklists, or in a mobile web interface with no install required, and each call is confirmed right on site. You can see how this works for field teams on the Distribution management page.

You won't have to move your outlet base over by hand: there are integrations with 1C, AmoCRM, Bitrix24 and Excel. Rollout takes 7 days with no long-term contracts, and the solution is designed for teams of 5 to 100 field workers. A sensible path is to record your current plan completion figures, run a pilot on one territory and compare the results after one or two cycles.