Designing a clearer delivery experience across 12 markets

When users redeemed points for physical rewards, the experience didn’t make the delivery process clear enough – where the order would go, what would happen next, or when it was likely to arrive.

I redesigned the shipment flow to make delivery more transparent while supporting different address requirements across 12 markets.

Selected project details and visuals have been anonymised for confidentiality.

Role

Product Designer

Scope

UX, UI, Prototyping, Multi-market flows, Design handoff

Year

2026

Platform

iOS · Android

Context

From points to physical rewards

The product is a loyalty and parenting app where users can scan purchases, earn points and redeem them for rewards.

Some rewards are digital, while others are physical products delivered to the user’s address. That meant redemption wasn’t the end of the journey – users also needed to understand where their order was going, when to expect it and what was happening after checkout.

Digital rewards end at redemption. Physical ones are where the flow had to keep going

The problem

The delivery journey left too much unclear

Recurring user complaints about the shipment experience were raised to me by the project manager.

Once I reviewed the existing screens, the reasons were easy to see. Delivery information was fragmented across the flow, address handling varied between markets, and users had little visibility into what happened after placing an order.

The existing UI also had accessibility issues: some colour combinations did not provide sufficient contrast, so the redesign included updating key interface colours alongside the delivery experience.

The challenge wasn’t only to improve one checkout screen. The whole journey needed to explain:

Where is my order going?
When should I expect it?
What is happening to it now?

The flow as it was: the address disappears after checkout, the confirmation provides no delivery details, and the order detail screen ends after just four lines

Designing for different markets

One form couldn’t work everywhere

Address structures differed significantly between markets.

In Germany, users entered a street and house number followed by postal code and city. In the UK, the form used house number and street, town or city, and postcode. Spain required additional fields such as province and tax identification.

Japan was even more structurally different: the journey began with postal code and prefecture, followed by municipality, street address and building details, with the recipient’s name appearing later in the form.

Instead of maintaining a completely separate form for every market, I created a master address template containing all supported fields. Each market configuration could then enable, disable and reorder the fields it required.

This gave the product a shared structure while preserving local address conventions.

One template, reconfigured per market. Fields switch off, switch on, and change position according to each market’s postal format

Making delivery visible

Showing what happens after redemption

The redesigned journey made shipment information visible beyond the checkout itself.

I introduced clearer delivery information and a dedicated tracking experience that showed both an estimated delivery range and the current order state.

The tracking model covered Processing, Shipped and Delivered, while also accounting for Cancelled orders.

The goal was to give users a clear answer to the question the previous experience left unresolved: what happens now?

Several existing colour combinations didn’t meet WCAG AA contrast requirements. I updated key interface colours as part of the redesign, improving contrast alongside the changes to the delivery experience.

No screen ends without saying what happens next

Order tracking shows what happened, what’s happening now, and what comes next – with delivery estimates updated only when confirmed

Prototyping & validation

Testing the journey before implementation

I built an interactive prototype in Figma Make so the complete journey could be experienced rather than reviewed as a series of static screens.

The prototype was used during remote usability sessions with users in the US. I joined the sessions while the research team walked participants through the experience and checked whether they could complete the flow, understood what would happen next and could interpret the delivery information.

The same prototype also became a communication tool for development. It helped demonstrate navigation, interactions and details such as the tracking progress animation – areas that were difficult to communicate through static handoff alone.

From design to implementation

Making the behaviour explicit

Alongside the final screens, I documented the market-specific address configurations, tracking states and interaction behaviour so development could implement the flow consistently.

Rather than creating twelve independent experiences, the design used a shared structure with market-specific configuration where necessary.

The implementation details behind the final UI: edge cases, spacing rules and both brand themes from one source

Outcome & learnings

One delivery journey, adapted to local requirements

The final solution made delivery information part of the product journey instead of leaving it implicit, while giving each market enough flexibility to support its local address requirements. It also gave design and development a shared reference for how the complete shipment flow should behave.

The flow shipped, market by market. No measure was agreed before launch and none was taken after, so what I can show is the change in the screens, not a number – next time I’d settle on one measure first, even something as plain as how many support messages mention delivery.


Next project

Bringing order to a fragmented multi-market product

Next project

Bringing order to a fragmented multi-market product

If you have an interesting project, want to collaborate, or just want to say hi:

Warsaw, Poland · OPEN TO work

Warsaw, Poland · OPEN TO work

Volya Darashkevich | 2026

Volya Darashkevich | 2026