Work

Home

1KOMMA5 OS
Warehouse Solution Redesign

Re building the tools for 1K5's core warehouse and logistic operations ground up,
to answer growing business need and seamless product experience.

Building solutions for 1K5’s core warehouse and material logistic operations.
Goal to

75 %

Integrations of 1K5 warehouse

workflows

90 %

Stock traceability through Inbound

process for Auditing

New flows standartises the process for all users across Germany

MY ROLE

Lead Product Designer

TIMELINE

May 2026- Present

TEAM

6 Engineers

Product Manager

Product Lead

PROCESS

Stakeholder mapping

Service blueprint

Discovery, Design flows

DELIVERABLES

Discovery interviews

Service blueprint mapping

Design flow high fidelity

The Challenge

The OS tracked stock levels, but not the story behind them — how an article entered the warehouse, what it cost, where it moved, or why. Inbound bookings weren't validated against any proof of purchase: no delivery note, no invoice, no price check, no unit-of-measure guardrail.

Undefined processes

Stock numbers in the OS was difficult to explain due fragmented and unclear process and responsibilities.

Warehouse employees track order through excel sheets that are not updated well

Cost efficeny

Uncertain processes led to the problem of not making sure business runs in most efficent way or how processes can be optimised

Contextual observations

Panel 1 of 2

Financial workflow

Finance and central controlling needed something stronger: every movement tied to a proof document, so the OS itself could stand as an audit trail.

Warehouse workflow

Warehouse managers (e.g. branch-level teams in Bremen) needed to record purchases fast and find discrepancies faster. Anything that slowed inbound down without visibly helping them would be worked around, not adopted.

Insights from discovery

Downstream, the picture didn't improve: movements, picks, corrections, and returns existed in the system but without the context — project, order, person, reason — that made them legible. Reconstructing a discrepancy meant Excel exports and manual cross-referencing across tools, every time.

Panel 1 of 2

Financial workflow

Finance and central controlling needed something stronger: every movement tied to a proof document, so the OS itself could stand as an audit trail.

Warehouse workflow

Shared problem definition

"The deeper problem wasn't simply that users were missing an article history view. The system didn't give them enough confidence that the information entering the system was correct in the first place."

The tools in use weren't chosen, they were defaulted to. Excel exports and Artikeljournal weren't tedious workflows — they were what existed in the absence of anything better.

Solution Definition

After discovery it became clear that that improving visibility after the fact wasn't enough. We also needed to improve the quality of the information at the point where an article entered the system.

Controlled entry and tracable movement

Lorem ipsum dolor set

Capture the right information

Use our intuitive drag-and-drop editor, smart tools stunning designs.

Preserve the right context

Easily integrate with your favorite tools to launch your project effortlessly.

Design Desicions

Foundation for the design direction was to treat warehouse movements as isolated transactions, as we wanted the OS to represent the article's lifecycle and make the important checkpoints explicit.

Navigation architecture

The navigation makes the fix structural: inbound is no longer one action but three trackable stages, each with its own state. That's what turns "proof of purchase" from a policy into something the interface actually enforces.

One undifferentiated step with no check points.

Streamlined status

A status taxonomy that mirrors the lifecycle, not the database. Draft → Confirmed → Part. delivered → Delivered isn't a technical status field, it's the answer to "what happened to this article" rendered as four honest states.

Key screens