Grocery Retail Web & E-commerce

Catering support, in one place.

Catering brings Whole Foods Market $306 million a year in the first 150 stores alone, and its customer support was spread across disconnected tools, so agents often had to hunt for an order and kitchen teams didn’t always receive the full request. I brought that work into the Amazon Customer Care Console (AC3) so agents could handle catering orders in the console they already used.

My goal was to give agents the order details, customer context and handoff tools they need in one place.

Following an order through the existing process

Before I designed anything, I traced a catering order from the customer to support and then to the kitchen. I used workshops, journey maps, interviews and a tool audit to see where the process broke down.

01Discover

Getting both teams in the room.

I coordinated an interactive catering ecosystem workshop with the Amazon and Whole Foods Catering teams. We listed the questions people ran into during a catering order, grouped them by theme, and used those questions to guide the research.

Workshop session at the parking lot wall
Surfacing open questions with the Catering on Amazon (WFMOA) and Whole Foods Catering teams.
Close up of the parking lot post-it wall
Open questions, grouped by theme before triage.

01Discover

Mapping the work before the software.

I mapped the order journey first, without tying it to any tool, and then added the systems people used at each step. That separated a broken process, like changes reaching the kitchen after prep started, from a tool getting in the way, like agents searching several systems for one order.

Stakeholders at the tool-agnostic journey wall
The journey on the wall, and the tools mapped under every step of it.
Current tooling mapped by channel
Current tooling by channel. Blanks and question marks mark the unknowns.

01Discover

Listening to the people doing the work.

Support agents and kitchen teams, on opposite ends of the same handoff, described the same problems: missing order details, last-minute changes and too much time spent piecing together what had happened. That gave me three things to solve for. Order details had to be right the first time, changes had to reach the kitchen before prep started, and agents needed one place to understand and resolve an issue.

It is such a waste of time to have to switch between tools or screens to find orders.
Support agent
I just want all the actions I need in one place.
Support agent
We often receive incomplete or unclear requests, because agents don’t have the right information upfront.
Kitchen team member
I always have to search using an email or phone number, and sometimes that isn’t enough to locate the order.
Support agent
We don’t always know which orders are urgent or require immediate attention.
Kitchen team member
It takes too long to find the right order when a customer isn’t authenticated.
Support agent

02Define

Affinity mapping the interviews.

I sorted the interview notes by theme with affinity mapping. Agents typed unique identifiers by hand, repeated steps and escalated simple issues because the order card lacked context, and newer agents learned by trial and error. The kitchen’s side, summarized here, came down to hearing about problems late, working around the system and having no central way to track an escalation.

We relied on back-and-forth calls with customer service just to work out what went wrong. It felt like we were constantly playing catch-up instead of focusing on the food.

Catering team member Whole Foods Market

This representative quote combines themes raised across the interviews.

What the kitchen needs
  • Order details that are right the first time
  • Changes that reach the kitchen before prep starts
  • One place to check, not four
What gets in the way
  • Orders arriving incomplete or late
  • Last-minute changes heard about second-hand
  • Systems that do not talk to each other
  • Peak catering season, when none of it can wait

02Define

Seeing the whole tool landscape.

I mapped the tools around the catering journey with developers, project managers and end users. Each touchpoint is the tool used for one step in one sales channel, and across six channels and seventeen steps I found 102 touchpoints: 15 repeated the same information, 18 were unclear or missing, and only 6 worked cleanly from end to end. The direction was clear: stop making agents move between tools to get the full picture.

Less ownership and control More ownership and control
Global support activities
In-store back of house
In-store front of house
Journey
Assortment & recipe
Data
Production planning
Execution
Staging & stocking
Handoff & reconciliation
Problem
What do we want to sell?
Is the item set up everywhere?
How do we make it?
What does it cost us?
Where do we buy it from?
What does the customer pay?
When can they buy it?
How much will we need?
Do we have it in the store?
How much can I sell today?
What do I need to make?
Is it safe to sell?
How much does it weigh?
Where do I put this?
How do I close the order?
What needs refilling?
Is the count still right?
Step
Planning
Item setup
Recipe setup
Cost setup
Sourcing
Price setup
Availability
Forecasting
Ordering
Allocation
Prep
Temp check
Labeling
Staging
Payment
Replenishment
Counting
Process
Assortment plan
Catalog entry
Recipe build
Cost load
Purchase order
Price publish
Window publish
Demand plan
PO creation
Inventory allocation
Production run
Safety check
Label print
Order staging
Reconciliation
Restock
Cycle count
Current tooling by channel 102 touchpoints across 6 channels
Setup happens three different ways
No shared view of what is actually available
This part already works
Owned storefront
Marketplace
Third-party delivery
Phone & walk-in
Corporate catering
Subscription & pre-order

Duplicated 15 Gap or unknown 18 In place 53 Works well 6 Not applicable 10

Scroll the map sideways to read it.

The map is a table of six sales channels against seventeen journey steps. Each cell names the kind of tool used and its state: in place, works well, duplicated, a gap or unknown, or not applicable. Totals for each state are given in the key below the map.

02Define

Following the handoffs.

The journey map showed the customer’s path, and a service blueprint showed what happened behind the scenes. Two handoffs kept causing trouble, agent to lead and agent to the next team, and those became the basis for the ask-a-lead and warm transfer flows.

02Define

Finding the two paths to the order card.

Agents reach an order card in one of two ways. A signed-in customer selects Need Help on Amazon.com and reaches an agent who can already see the order. Everyone else has to be found through Research and Resolve by order ID, email address, phone number or name, so that unauthenticated path is where I focused.

Usability testing on the existing Research call to action showed agents were unsure how to reach the order card, repeated steps and typed unique identifiers by hand. Only 12 agents had access to it, so the path also had to work for a much larger group.

02Define

Writing the requirements as user stories.

The project goal set what agents had to do for a Catering on Amazon order: create or cancel it, add or remove items, change a quantity, switch between pickup and delivery, change the pickup location, date or time, revise or reprocess a payment and process a refund.

I wrote those needs as user stories from the agent’s side. Every change or cancellation sends the customer an email specifying it and alerts the in-store Team Members. The stories also set every order detail an agent needs, from the customer’s contact details and pickup time to each item’s price look-up (PLU) code or Amazon Standard Identification Number (ASIN), the quantity ordered against the quantity filled, and the full payment breakdown.

03Develop

Reusing what already works.

Before making new components, I reviewed Amazon’s existing support patterns against the catering tasks, and most of the flow could use what agents already knew. That kept the experience consistent between Whole Foods and Amazon, let engineering build on proven components and saved new design for the real gaps.

The catering design system: color, the two icon sets and the heading scale.
Four console states left to right, from an incoming call through customer issue context and suggested replies to a resolved conversation, with the path between them drawn
Existing Amazon console patterns, from an incoming call to a resolved conversation.

Scroll sideways to follow the flow.

03Develop

Adding a Catering Card to the existing workflow.

The AC3 workflow already ran in four steps: open Research, select the Research call to action, enter a unique identifier and land on the order card. A separate catering workspace would have meant rebuilding components that don’t carry over, so I added a Catering Card to the existing workflow instead.

I started from the existing order card, took out what catering didn’t need and added back what it did. The unique identifier inputs became one search field that accepts an email address, phone number or customer name. I also asked engineering to build on the AC3 functional workflow, whose back button keeps agents from losing unsaved actions.

03Develop

Filling the gaps in the existing console.

Catering needed a few things the console didn’t already have, including pickup details and a clearer order history view. I designed those pieces to fit the existing Customer Care experience, used Amazon Ember, checked contrast, and made sure status was never communicated by color alone.

Four console states left to right, from an incoming call through a catering order's pickup details to its full order history with each stage marked

Scroll sideways to follow the flow.

03Develop

Ordering the solve card around customer questions.

Feedback on the low fidelity solve card mockups set three rules for the next revision. Every piece of information had to answer a common customer question, the expanders were ordered by how often customers ask each question, and acronyms were written out or explained.

03Develop

Ranking the action stripe by usage.

Review feedback on the action stripe set four rules. Actions are ranked by usage, which leaves room to add more later. Buttons stay visible instead of being disabled, and selecting an inactive one explains why, so the agent can help the customer fix the issue. Actions that can’t apply to an order’s status, like changes to a cancelled order, are hidden.

03Develop

Scoping order edits for the next milestone.

The next milestone added order edits: adding an item, changing a quantity, removing an item and updating the pickup slot. I raised the open questions with the product team, including whether an agent could add several items at once and whether the quantity dropdown should cap at what’s in stock. If only 4 trays of meatballs are left, 5 and up would be greyed out or hidden. Pickup slot changes are only allowed until 48 hours before pickup.

03Develop

Adding to the system with care.

When a component could be useful beyond catering, I added it to the shared system and documented how to use it, and catering-only pieces stayed with the feature. That gave the Amazon team a clear handoff without turning a focused project into a parallel design system.

REPLACE-WITH-PROCESS-SYSTEM.png A documentation page with its usage guidance, or the release notes for a version. Anything that shows the system being run rather than designed.
A component with its usage guidance, and the release it shipped in.

04Deliver

Testing the work with the people who’d use it.

I took the core flows through visual design and usability testing with agents and kitchen teams, then piloted the updated Research and Resolve workflow with the 12 agents who already had access. Their feedback stayed tied to finding an order, making a change and handing work to the right person, and the final refinement added tooltips and visual aids for new agents.

REPLACE-WITH-PROCESS-09.png A testing session, a task board, or the annotated screens that came back from it. Anything that shows the design being checked rather than presented.
Visual design and usability testing, through to launch.

One console, built for the way agents work

Catering support now sits inside Amazon Customer Care, with the order, the customer’s context and the next actions in one workspace. It soft launched to 150 stores in 2023 and reached every store by the end of 2024. Each flow below is paired with the interview finding it answers.

Keeping the work in one place

Agents can find the order, understand what the customer needs and take action without bouncing between systems.

Building on patterns agents already know

The catering experience uses familiar Amazon components wherever possible, and new user interface (UI) was saved for the work that didn’t fit an existing pattern.

Carrying context through a handoff

Ask a lead and warm transfer send the issue type, the order details and a short summary with the request, so the next person has what they need to help without asking the agent or customer to repeat the story.