Target has upgraded the app its store employees use to run daily work, turning the handheld from a lookup device into a routing system for tasks. Retail Dive reported the change in mid-October, framing it as an operations upgrade rather than a customer-facing feature. That framing understates the impact. When task assignment moves into software, the store stops being managed by shift meetings and starts being managed by a queue, and the quality of that queue determines whether labour hours land on the shelf or disappear into coordination.
Key Conclusions
The core shift is from batch to flow. In a batch model, a team leader walks the floor in the morning, lists what needs doing, and assigns it verbally. In a flow model, the system holds the list, ranks it by urgency and location, and pushes the next task to whoever is closest. The second model reduces walking and waiting, but it also removes the informal judgement that experienced associates apply when they reorder work.Target upgraded the app employees use for store operations（Retail Dive）
The second shift is measurement. Once tasks are routed through software, completion becomes observable at the individual level: how long a task took, how often it was deferred, which aisles generate repeat work. That data is valuable for planning, and it is also the raw material for performance management. Retailers that adopt routing without agreeing on how the data will be used tend to see associate trust decline within two quarters.
What routing changes on the floor
The most visible change is the reduction of dead time between tasks. In stores with long aisles and multiple back rooms, associates can spend a meaningful share of a shift walking. Routing that sequences tasks by physical proximity cuts that share, and the recovered minutes can be redirected to shelf work or customer assistance.
The second change is the visibility of exceptions. When a task cannot be completed, the system records why: product not in back stock, fixture blocked, label missing. Aggregated over weeks, those reasons point to root causes that a shift meeting would never surface. Stores that review exception data weekly tend to fix recurring blockers rather than repeatedly reassigning the same task.
The training burden
Routing systems fail when associates do not trust the queue. If the sequence sends someone to an aisle and the item is not there, the associate learns to ignore the next instruction. Building trust requires that the first weeks of data be cleaned, that wrong assignments be corrected quickly, and that associates be able to flag errors without penalty. That is a management task, not a software feature.
Why shelf availability improves first
Shelf availability is usually the first metric to move, because replenishment tasks are easy to define and easy to sequence. Customer assistance is harder, since it interrupts the queue and cannot be scheduled. Retailers that measure only task completion tend to see availability improve while service perception stays flat, because associates are being pulled away from the aisle conversation.
Best Practices
Start with a narrow task set. Replenishment, price change, and return-to-shelf are the three categories with the clearest definitions and the most reliable data. Routing those first produces visible results within a month and gives the team confidence before more ambiguous work is added. Attempting to route everything at once usually produces a queue nobody follows.
Define the exception path before launch. Every task needs an escape hatch: what the associate does when the item is missing, the fixture is blocked, or the label is wrong. If the escape path is unclear, associates improvise, and the data collected afterwards is unreliable. A one-page exception guide is more useful than a long training module.
Aligning labour hours with the queue
A routing system can only route work that labour hours allow. If the queue contains four hours of tasks and the shift has three, the system will report persistent backlog that no associate can clear. Labour planning and task planning need to be reviewed together, otherwise the tool becomes a record of failure rather than a coordination mechanism.
Common Mistakes
The first mistake is treating routing as a cost-cutting tool. If the primary goal is to reduce hours, associates detect it quickly and the data they produce becomes defensive. The same system that improves coordination can destroy trust when it is framed as surveillance, and recovery takes far longer than the initial rollout.
The second mistake is measuring task volume instead of task value. A store can complete two hundred low-value tasks and still fail on the ten that matter, such as an out-of-stock on a promoted item. Prioritisation rules must reflect commercial weight, not just proximity and age of the task.
The data governance question
Routing generates individual-level performance data, which raises questions that most retailers have not answered in policy. Who can see how long a task took? Is the data used in scheduling decisions? Can an associate contest a record? Answering these before rollout is cheaper than answering them after a dispute.
A workable approach is to separate operational data from personnel data. Operational views aggregate by task type and aisle, which is enough to fix blockers. Personnel views are restricted, time-limited, and used for coaching rather than discipline. The separation protects both the associate and the reliability of the data.
What good looks like after six months
Six months in, a well-run deployment shows three things: a falling share of deferred tasks, a stable or improving service score, and a shorter list of recurring exceptions. If completion rises while service falls, the queue is crowding out customer work. If exceptions do not shrink, the system is recording problems rather than solving them.
Summary
Moving task assignment into a handheld changes how a store is managed: from shift meetings to a queue, from batch to flow. The operational gains are real, but they depend on a clean first data set, a clear exception path, and labour hours that match the queue.
The governance question matters as much as the technology, and it is the part most rollouts skip. Separating operational data from personnel data, publishing a short policy on who can see what, and framing routing as coordination rather than surveillance all determine whether associates trust the queue enough to follow it when the store gets busy.
Data Sources
1. Retail Dive: Target upgrades store operations app
2. Retail Dive: seasonal store openings
3. CNBC: retailers trim assortments
FAQ
What does task routing actually change?
A: It replaces verbal assignment at shift start with a ranked queue pushed to a handheld. Work is sequenced by urgency and location, which reduces walking and waiting between tasks.
Why does shelf availability improve first?
A: Because replenishment tasks are easy to define and sequence. Customer assistance is harder to schedule and often interrupts the queue, so service metrics lag behind availability.
How should a rollout be scoped?
A: Start with replenishment, price change, and return-to-shelf. Those three have clear definitions and reliable data, and they produce visible results within a month.
What is the main trust risk?
A: Framing the tool as surveillance. If associates believe the data will be used to cut hours, they produce defensive records and the queue loses credibility.
What should be reviewed after six months?
A: The share of deferred tasks, the service score, and the list of recurring exceptions. Rising completion with falling service means the queue is crowding out customer work.
References
1. Retail Dive: store operations upgrade
