Trax Retail: Data Collection Configuration Platform

Trax’s field reps work from a mobile app on store visits. What they see in it, which stores, routes and tasks and when, is set up by customer operations teams in a desktop tool. I redesigned that tool’s store and route management.

Support tickets about store and route setup dropped about 30% after launch, as measured in Jira.

As Trax grew, so did the number of stores, routes and visit plans each customer managed. The tool still used a legacy layout with no clear structure for that scale, so setting up and changing field work was slow and hard to keep track of.

I interviewed operations and field-management staff to understand how they think about stores, routes and visit schedules, and where the tool got in their way.

From those interviews, I proposed a master-detail structure: a list of stores and routes on one side, and a detail pane for the selected one, with its schedule, visits, route assignments and tasks. Users scan hundreds or thousands of stores, pick one, and edit everything about it in context, without leaving the list.

The platform’s frame (layout, main navigation, global actions) already existed. Within it, I designed the list and detail panes and the flows behind them: creating, updating and disabling stores and routes, planning visits, and assigning tasks. For scheduling, I added activation windows so planners could switch stores on to match demand. Once a store and route are selected, the relevant tasks (visits, data collection, checks) appear in the detail pane and can be edited there.