← All workBACKBAR / Hospitality · SaaS Product Design

Stock decisions.
With context.

An inventory dashboard designed for the daily work behind stock management. Overview, product and reporting screens connect visibility with the next operational action.

01 / Project at a Glance

The business context.
The design scope.

Who the experience serves, the environment it operates in and the design work included.

Industry
Hospitality & inventory
Platform
Desktop web app
Primary Users
Bar managers & stock teams
Project Scope
Stock checks & replenishment
Services
SaaS product UX/UI
Deliverables
Inventory screens & UI components
02 / The Problem Worth Solving

Where the journey
needed attention.

Keep products, stock quantities and replenishment needs easy to compare.

Product recognition

Recognise similar bottleswith clear visual stock cues.

Separated stock context

Keep quantity and pricingclose to each product.

Ambiguous replenishment

Separate planned top-upsfrom orders sent to suppliers.

Design ObjectiveConnect product recognition, stock comparison and replenishment context in one operational workspace.

03 / The Experience We Designed

The key moments.
Designed together.

Clearer journeys bring useful information and important actions into focus.

Move from the shelf to the next stock decision

Stock overview

See stock summaries beside product cards. Keep low-stock context close at hand.

Design note

The supplied workspace view combines summary information, recognisable product cards and low-stock context. It gives the team one starting point for reviewing the shift.

What To Notice
  • Stock overview
  • Bottle recognition
  • Replenishment context
See where the stock value sits.

Inventory reports

Connect stock value and bottle counts. Compare categories from one overview.

Design note

The reporting view connects stock value, bottle counts and category comparisons in one overview.

What To Notice
  • Stock value
  • Category comparison
  • Inventory reporting
Identify the products that need attention.

Low-stock signals

Review stock and expected deliveries. Plan the remaining need before ordering.

Design note

Low-stock planning brings on-hand quantities, expected deliveries and existing drafts into the same comparison.

What To Notice
  • On hand / target
  • Expected deliveries
  • Existing drafts
Keep replenishment context close.

Plan replenishment

Keep draft actions beside each product. See the remaining need in context.

Design note

The supplied replenishment view keeps the remaining need and the draft action beside each product.

What To Notice
  • Still-needed quantities
  • Covered-by-order status
  • Create-a-draft action
Keep every bottle in view.

Browse inventory

Browse bottles, stock and categories. Keep inventory details easy to recognise.

Design note

The inventory page combines recognisable bottles, stock details and category controls in a product-led overview.

What To Notice
  • Bottle recognition
  • Category navigation
  • Stock details
Keep the workspace connected

A shared workspace

Connect stock, overview and replenishment. Use familiar navigation throughout.

Design note

A shared navigation and visual system connect the daily overview, stock catalogue and replenishment views.

04 / Decisions Behind the Design

Choices that serve
the task.

These are design intentions. The benefits below are not presented as measured outcomes.

Information hierarchy

Find the right bottle

Use category names, subtype chips and bottle photography together. Recognise the product before reading the details.

Navigation

Compare the operational essentials

Keep quantity, location, purchase price and selling price on the product card. Compare key stock details in one familiar place.

Interaction design

Understand incoming stock

Distinguish on-hand stock from quantities already covered by expected deliveries. See outstanding needs beside incoming stock.

Visual consistency

Keep planning distinct from purchasing

Label the intermediate action as Create Draft and explain what it does. Keep stock planning distinct from sending a supplier order.

05 / Built for Consistency

Built to repeat.
Ready to extend.

Shared components, type and interaction patterns keep the product consistent.

Reusable components

Related actions and interface elements follow a familiar structure.

Type and spacing

Consistent hierarchy gives dense and quiet screens a shared rhythm.

Interaction states

Clear selections and feedback support predictable next steps.

06 / What the Project Delivered

What the design
engagement produced.

Explore the design deliverables. Intended benefits are not measured results.

Clearer user journeys

Stock insights and reporting.

View screens
07 / Have a Similar Challenge?

Facing this kind
of challenge?

Tell us what your users are struggling with, and we’ll help you explore a practical way forward.

Discuss a Similar Project
A FRESH PAIR OF EYES

Get a Free UX Audit

Share your website or app and the experience you’d like us to review.

YOUR NEXT MOVE

Let’s shape your project.

Share your starting point. We’ll help you find the next step.

Your details are only used to respond to your enquiry.