Zalando
Zalando
Zalando
Zalando’s partners around the world send their product orders through one internal system, the Z Retail Center. Pommer Design led UX for its new dashboard, which the order teams now use every day.
Zalando’s partners around the world send their product orders through one internal system, the Z Retail Center. Pommer Design led UX for its new dashboard, which the order teams now use every day.
Zalando’s partners around the world send their product orders through one internal system, the Z Retail Center. Pommer Design led UX for its new dashboard, which the order teams now use every day.


Year
2022
Client
Zalando
Category
Fashion
Duration
7 months
Objective
Objective
Behind Zalando’s online store is software that manages product orders from partners worldwide. The brief: a dashboard for the Z Retail Center that makes order management measurably faster for the teams who use it.
Role
Role
The scope: analysis of the existing flows, interviews with operations staff, information architecture, concepts, prototypes and final visual design in Zalando’s design framework. Pommer Design also took on smaller design work elsewhere on the platform.

Approach
Approach
The dashboard has five modules, one per workflow: order intake, returns, inventory reconciliation, performance tracking and exceptions. Each one started as rough flows, went through quick wireframe rounds and ended as high-fidelity prototypes in Zalando’s design system, with the same patterns throughout.

Outcome
Outcome
The first dashboard widgets are in production, together with reworked follow-up flows. Pommer Design validated the concepts with working prototypes, in close collaboration with product management, engineering and data analytics. New rounds of user testing are shaping the next expansion of the system.

Illustrative views. Client work is confidential.
More work More work
03
//FAQ
Questions
ANSWERS
01
How does a project start?
With a short discovery phase. We agree on goals, constraints and success criteria and put them in writing first.
02
What kinds of organizations do you work with?
Organizations that run on information: banks and insurers, airlines and rail operators, energy, pharma and software companies. Size matters less than what’s at stake in the decisions the product supports. The common thread is complexity: regulation, several product teams, or expert users with no time to spare. Early-stage companies with a hard problem are welcome too.
03
How do you approach complex digital platforms?
We map the work before we design for it: who decides what, under which business rules, and how the systems depend on each other. That map becomes the frame for every feature and team that follows.
04
How do you keep a large product portfolio consistent?
With a design system that engineering owns as much as design does: shared components, documented decisions and a review process for changes. New teams start from it instead of from scratch, and the portfolio still feels like one product as it grows.
05
How do you measure success?
We test the new product against the old one on the same tasks and compare time, errors and ratings. A project succeeds when the new version wins on all three.
06
What’s different about working with Pommer Design?
Senior people run every project, from the first interview to launch. We measure the product again after release. The work counts as done when the numbers hold in daily use.
03
//FAQ
Questions
ANSWERS
01
How does a project start?
With a short discovery phase. We agree on goals, constraints and success criteria and put them in writing first.
02
What kinds of organizations do you work with?
Organizations that run on information: banks and insurers, airlines and rail operators, energy, pharma and software companies. Size matters less than what’s at stake in the decisions the product supports. The common thread is complexity: regulation, several product teams, or expert users with no time to spare. Early-stage companies with a hard problem are welcome too.
03
How do you approach complex digital platforms?
We map the work before we design for it: who decides what, under which business rules, and how the systems depend on each other. That map becomes the frame for every feature and team that follows.
04
How do you keep a large product portfolio consistent?
With a design system that engineering owns as much as design does: shared components, documented decisions and a review process for changes. New teams start from it instead of from scratch, and the portfolio still feels like one product as it grows.
05
How do you measure success?
We test the new product against the old one on the same tasks and compare time, errors and ratings. A project succeeds when the new version wins on all three.
06
What’s different about working with Pommer Design?
Senior people run every project, from the first interview to launch. We measure the product again after release. The work counts as done when the numbers hold in daily use.
//FAQ
Questions
ANSWERS
How does a project start?
With a short discovery phase. We agree on goals, constraints and success criteria and put them in writing first.
What kinds of organizations do you work with?
Organizations that run on information: banks and insurers, airlines and rail operators, energy, pharma and software companies. Size matters less than what’s at stake in the decisions the product supports. The common thread is complexity: regulation, several product teams, or expert users with no time to spare. Early-stage companies with a hard problem are welcome too.
How do you approach complex digital platforms?
We map the work before we design for it: who decides what, under which business rules, and how the systems depend on each other. That map becomes the frame for every feature and team that follows.
How do you keep a large product portfolio consistent?
With a design system that engineering owns as much as design does: shared components, documented decisions and a review process for changes. New teams start from it instead of from scratch, and the portfolio still feels like one product as it grows.
How do you measure success?
We test the new product against the old one on the same tasks and compare time, errors and ratings. A project succeeds when the new version wins on all three.
What’s different about working with Pommer Design?
Senior people run every project, from the first interview to launch. We measure the product again after release. The work counts as done when the numbers hold in daily use.
03
//FAQ
Questions
ANSWERS
01
How does a project start?
With a short discovery phase. We agree on goals, constraints and success criteria and put them in writing first.
02
What kinds of organizations do you work with?
Organizations that run on information: banks and insurers, airlines and rail operators, energy, pharma and software companies. Size matters less than what’s at stake in the decisions the product supports. The common thread is complexity: regulation, several product teams, or expert users with no time to spare. Early-stage companies with a hard problem are welcome too.
03
How do you approach complex digital platforms?
We map the work before we design for it: who decides what, under which business rules, and how the systems depend on each other. That map becomes the frame for every feature and team that follows.
04
How do you keep a large product portfolio consistent?
With a design system that engineering owns as much as design does: shared components, documented decisions and a review process for changes. New teams start from it instead of from scratch, and the portfolio still feels like one product as it grows.
05
How do you measure success?
We test the new product against the old one on the same tasks and compare time, errors and ratings. A project succeeds when the new version wins on all three.
06
What’s different about working with Pommer Design?
Senior people run every project, from the first interview to launch. We measure the product again after release. The work counts as done when the numbers hold in daily use.
Project inquiries
Frankfurt and London. Operating worldwide

Interaction design since 2010
Interaction design for enterprise platforms and operational tools. Tell us about your project.
Project inquiries
Frankfurt and London. Operating worldwide

Interaction design since 2010
Interaction design for enterprise platforms and operational tools. Tell us about your project.
Project inquiries

Interaction design for enterprise platforms and operational tools. Tell us about your project.
Project inquiries
Frankfurt and London. Operating worldwide

Interaction design since 2010

