Skip to main content
Back to selected work

B2B SaaS | Reverse Logistics

Returns Platform.

A B2B SaaS returns platform connecting customer initiation, merchant configuration, orchestration and store processing across five continents.

Role
Product strategy, UX architecture, design systems
Team
B2B SaaS / Reverse Logistics
Company
Doddle / Blue Yonder

$12M

Saved through optimized logistics

+32%

Processing efficiency

88.2%

User satisfaction

53 sec

To process two items

The Problem

Returns are broken: paper labels are unsustainable, staff time leaks away and routing decisions waste money. The platform had to serve merchants, consumers and carriers across one complex reverse-logistics model.

What I Did

I owned product strategy and UX architecture across the suite: consumer initiation, merchant rules and branding, orchestration and the store staff app, validated through usability testing and UAT on real flows.

The Outcome

A unified platform helped merchants run returns across five continents, with 32% more efficient processing, 88.2% user satisfaction and $12 million saved through smarter routing and store handling.

Decision 01 / 03

Returns start in the merchant's brand.

Customers initiate a paperless return inside the retailer's own look and feel, then get a reason, pick the best drop-off point nearby and continue with a choice shaped by the merchant's rules. The product had to feel simple for shoppers while still respecting the policies, branding and routing logic behind the scenes.

Result → paper labels removed from the flow

The merchant returns queue showing return status and exceptions.

Decision 02 / 03

Rules merchants can read.

Reverse logistics is really a policy problem. Instead of vendor tickets and config files, merchants write plain-language if/then rules for carrier selection, return windows, warehouse routing, non-resellable items and re-order them by priority.

The same grammar covers branding, policies and routing, so one mental model runs the whole platform.

Result → merchants configure routing without tickets

Merchant configuration: rules, branding and return windows.

Decision 03 / 03

Grade at the counter, not the warehouse.

Store staff answer two plain questions about each item's condition. That early grade decides the item's route: resale, repair or warehouse, before it is ever shipped.

The flow was measured on task success, time on task and satisfaction, and became sharper as staff learned it.

Result → two items processed in 53 seconds

Grading decisions captured at the point of return, before warehouse routing.
Carrier methods configured for return routing.

The foundation

Built as a platform, not a feature.

The same orchestration layer now extends beyond stores: warehouse processing with optimized grading, IoT integrations with kiosks hardware, and machine-learning recommendations built on live returns data and market trends.

Impact

What changed.

Logistics cost savings

$12M

Processing efficiency

+32%

User satisfaction

88.2%

Two-item processing

53 sec

Merchant control

Clearer

Paper-free focus

Increased

Store-processing confidence

Improved

Platform scope

Expanded

Process

Understanding the system before designing the interface

Stakeholder interviews and workshops, competitor research, hypothesis development, client requirements, sketches, wireframes and user flows, lo-fi and hi-fi design, prototypes, usability testing and UAT.

Merchant configuration: rule priorities, tags and status.
Carrier selection rules and the default carrier.
Store dispatch states: open totes, ready to dispatch and dispatched.

Future opportunities

Warehouse processing

Optimized grading and logistics.

IoT expansion

Kiosk integrations with the store app.

Machine learning

Advanced predictive capabilities.

Next case study

Complex trips, made simple.

Read next