/

Order management

Concept

Order and fulfillment platform for
growing online stores

Order and fulfillment platform for growing online stores

A concept for one place to manage orders — from the moment they come in to the moment they ship.

A concept for one place to manage orders - from the moment they come in to the moment they ship.

A concept for one place to manage orders - from the moment they come in to the moment they ship.

E-commerce · SMB/DTC

E-commerce · SMB/DTC

E-commerce · SMB/DTC

Industry

Product, IA, UI, design system

Product, IA, UI, design system

Role

Web · Mobile

Web · Mobile

Web · Mobile

Platform

2024

2024

2024

Timeline

Self-initiated concept

Self-initiated concept

Type

E-commerce, B2B, orders view
E-commerce, B2B, orders view

Orders dashboard - The screen the team keeps open all day: health metrics on top, a dense, sortable table below.

Order side panel - Any order opens in a side panel, so an operator can review it without

losing their place in the list.

Order side panel - Any order opens in a side panel, so an operator can review it without losing their place in the list.

Command menu (⌘K) - Jump to any order, customer, or report, or trigger an action, from anywhere in the app.

01 / Overview

Overivew

A mobile app shaped by the warehouse, not the desk (iOS)

Overivew

In the products I've worked on, the hard part of orders is rarely the sale itself — it's managing everything that comes after it. Picking, checking, provisioning stock, arranging shipment, handling the orders that don't go out cleanly on the first try.

In the products I've worked on, the hard part of orders is rarely the sale itself — it's managing everything that comes after it. Picking, checking, provisioning stock, arranging shipment, handling the orders that don't go out cleanly on the first try.

Context and challenge

I created this concept for small and mid-sized online stores with complex fulfillment needs. The goal was to design a simple daily tool that captures orders requiring extra steps before shipping, without making it feel like a spreadsheet or requiring separate tools.

Role and scope

I owned every part of the product-design work: defining the workflow model, structuring the information architecture, designing the interaction states, producing the high-fidelity UI, and building the design system that keeps web and mobile consistent.

02 / Discovery

Key design decisions

A mobile app shaped by the warehouse, not the desk (iOS)

Key design
decisions

Three decisions shaped the product. Each one answers a specific tension

in fulfillment operations.

Three decisions shaped the product. Each one answers a specific tension

in fulfillment operations.

01 / Order status as explicit stages

Extra fulfillment steps don't fit a "paid → shipped" model, so status is modeled as ordered stages — the longer steps live inside the order, not the daily list.

One model, simple orders to multi-step — no separate mode.

02 / Narrowed the scope to one job

A full commerce admin does far more than fulfillment, so I used Shopify's admin as a density benchmark rather than a template, then cut scope to fulfillment only.

Proven dense-data patterns, one focused workflow.

03 / A dark, system-first interface

Operators live in the tool for hours, so it's dark and dense for reading speed — and built system-first, from shared tokens and states, so web and mobile stay one product.

Legible dense UI with reusable patterns across platforms.

03 / Web

The command center for
fulfillment, in one view

The command center for fulfillment, in one view

A single workspace for seeing the full picture and acting on it — built for operators

who make hundreds of decisions a day and need each one to be informed.

A single workspace for seeing the full picture and acting on it — built for operators who make hundreds of decisions a day and need each one to be informed.

Order details - Items, customer, totals, and a full timeline in one place: change status, add tracking, and leave notes without leaving the order.

Every order state, one component - The same progress bar covers every state an order can be in — payment failed, ready to ship, delivery rescheduled — each with its own next action, so edge cases are handled by design rather than bolted on.

Customers - Every customer with their orders, payments, and invoices in one place.

Locations - Inventory by location, as cards or a table, edited in place, no separate tool to open.

Modals - Purpose-built modals for the three most frequent fulfillment actions: marking shipments, provisioning stock, and onboarding customers.

04 / Mobile

A mobile app shaped by the
warehouse, not the desk (iOS)

A mobile app shaped by the warehouse, not the desk (iOS)

Designed for packing, checking, and shipping — not spreadsheets. The mobile app is deliberately focused: fewer features, faster actions, and built to be used one-handed while moving.

Find an order fast - Search and filters shaped for a thumb, so the right order is a few taps away.

Status down to each item - Every line item carries its own state, so it's clear exactly what's holding an order up.

Status down to each item - Every line item carries its own state - you see exactly what's holding an order up.

Mark as shipped flow - Carrier, tracking number, confirm — the one job the floor needs, in three steps.

05 / Outcome & reflection

In a fulfillment tool, the interface
earns its keep in how it handles
the exceptions — not the happy path.

Where I would

take it next

Status visibility

Does a visible order status measurably cut the time spent checking on orders?

Web / mobile split

Does the split match how teams actually divide the work between desk and floor?

Progressive detail

Where the dashboard should hide detail for newer users.

No usage numbers yet — the work produced a coherent product model and a design system

shared across web and mobile.

No usage numbers yet — the work produced a coherent product model and a design system shared across web and mobile.

Got a project in mind

or need a design partner?

©Designed and Developed by Konrad Księżopolski 2026. All rights reserved.

Got a project in mind

or need a design partner?

©Designed and Developed by Konrad Księżopolski 2026. All rights reserved.

Got a project in mind or need a design partner?

©Designed and Developed by Konrad Księżopolski 2026. All rights reserved.