CASE STUDY 03 / B2B ORDERING

Leier

Preparing complex B2B orders in a constrained workspace

Read the case study

CENTRAL DESIGN QUESTION

How can buyers prepare an order while handling product and logistics rules?

Leier’s B2B order-preparation interface brought together product selection, specialist calculators, quotation building and logistics. I designed the workflows and detailed screens around the information buyers needed to keep in view. A central decision was to fit ten product rows, logistics controls and the order summary into a 1440 × 900 workspace. I also reviewed an implementation against the agreed requirements and documented 13 discrepancies for follow-up.

MY ROLE

Product designer responsible for detailed UX and UI across the order-preparation flows, with implementation review.

SCOPE

Four-level product browsing, a roof-tile calculator, a chimney configurator, quotation building, load grouping and order summaries.

DELIVERY

More than 16 artboards, adapted components, defined interface states and an annotated review of an implementation.

An order depended on more than product selection

A buyer could not complete this workflow by choosing products and quantities alone. The interface also needed to accommodate product-family rules, calculated quantities, minimum ordering units, pallet norms, framework-contract controls and logistics. These details affected whether the proposed order made sense as a whole.

The main design challenge was keeping those dependencies understandable while users moved between selection and preparation. A product could come from a browsing hierarchy or from a calculation. Its quantity could be calculated or manually adjusted. Its price could still need approval. The order summary needed to preserve the relevant grouping by vehicle load.

I treated these as connected parts of the task. That led to detailed work on how information was grouped, how states were labelled and which controls needed to remain visible together.

FIG 1 · ALTERNATIVE AND CHOICE

The compact layout keeps ten product rows, logistics controls and the summary within the same 1440 × 900 workspace.

Matching the interaction to the product family

I designed four levels of product browsing and distinct configuration flows for different types of building product. The roof-tile calculator used three steps, with between three and eight API-driven fields depending on the product family. The chimney configurator was planned as six steps and later had to be simplified to two: the flues first, then options and quantity.

Those differences mattered. A single generic configuration form would have hidden the fact that different products required different inputs and sequences. I kept the interaction specific to the task while using shared visual patterns to make the overall experience coherent.

The building-system selection used 80 × 80 icon selectors, with recognisable categories presented within the shared component approach.

Product browsing

Four levels of navigation

Organising a product hierarchy without treating every item as equivalent

Roof-tile calculation

Three steps with three to eight product-family fields

Adapting data entry to the selected family

Chimney configuration

Six steps, simplified to two

Keeping dependent choices clear in fewer steps

Quotation building

Ten rows with commercial and logistics controls

Preserving the information needed to assess the proposed order

Order summary

Grouping by vehicle load

Carrying the logistics structure into the review stage

FIG 2 · CHIMNEY CONFIGURATOR

Choosing density through a concrete comparison

The quotation screen had to keep ten product rows, load controls, logistics information and the summary within a 1440 × 900 artboard. I compared compact and more spacious treatments, then measured the remaining vertical space after the ten rows.

The more spacious version did not leave enough room for the full set of controls and summary information. I selected the compact direction and used grouping to preserve readability. The deciding factor was the space required by the complete task, rather than the appearance of an isolated row.

This choice involved a real cost. Compact rows leave less room for each item to breathe, particularly when names or identifiers become long. The benefit was that buyers could retain more of the order context on one screen. I used the layout comparison to make that trade-off explicit.

The measurement established what would fit. It did not establish how quickly people could complete an order or how comfortable the density would be in extended use. Those questions remained appropriate subjects for testing with realistic product data and representative tasks.

FIG 3 · LOAD GROUPING

Each truckload groups one delivery address, one plant and one delivery method, and shows how close the load is to the vehicle limit.

Making exceptional states part of the normal workflow

Several decisions concerned situations that a visually tidy happy path would omit. I distinguished calculated quantities from manually entered quantities with an icon and text. This made the origin of a value visible without requiring users to infer it from the number itself.

I also used written status labels alongside visual treatments. A state needed an explicit meaning in the interface, especially when different rows could require different kinds of attention. Colour supported that meaning rather than carrying it alone.

Missing prices required a particularly careful distinction. I designed a pending-approval state for the affected row while allowing the quotation to be submitted. The commercial uncertainty remained visible, but it did not block the entire preparation task.

The implication was specific: submission could move the quotation forward while the unresolved price remained identifiable. It did not mean the price was confirmed or that the order had received final approval. Keeping those meanings separate was important to the integrity of the workflow.

I separated internal notes from messages sent to Leier, making the destination of the content explicit in the interface.

Using a component foundation with deliberate exceptions

I worked from an existing component and token foundation, importing 2,926 tokens and the associated icon system. I rebuilt the Button, Badge, Link and Form components for the product’s needs and used a deliberate Leier brand-dark exception of #002958.

I applied the shared conventions to the quotation builder, configuration steps and order summary, adapting their hierarchy to each task. My responsibility was the product-level adaptation; the original token architecture already existed.

Reviewing the implementation against the agreement

I compared the implemented product list with the client meeting notes and produced an annotated review containing 13 points. Four were structural discrepancies; the remaining points concerned details. I weighted the findings so the follow-up could distinguish changes affecting the structure from smaller adjustments.

Each observation was connected to a documented requirement, giving the developer discussion a concrete basis for deciding what needed attention.

I also identified a limit in the design material: the product data was still placeholder content. I requested a real export so that long product names, identifiers and other edge cases could be checked. The final data replacement remained unresolved in the work covered by this case.

07 · WHAT THE WORK ACHIEVED

How can buyers prepare an order while handling product and logistics rules?

08 · TAKEAWAY

Leier strengthened my ability to translate domain rules into visible interaction. The decisive work often happened at the boundaries: whether a missing price should block progress, how users recognise the source of a quantity, and how much context must remain visible while they prepare an order.

NEXT CASE STUDY · 04 / 06

Szimpatika

Making pharmacy selection part of the shopping journey

horvath.bertalan.andras@gmail.com · +36 30 311 8560