Fewer support requests
Designing the states people actually hit — empty, loading, error, permission denied — removes the questions your team answers by hand later.
Design the full shopping interaction, including the difficult states.
We design ecommerce interfaces around browsing, selection and the next supported purchase step. Filters, variant choices, cart updates and recovery behaviour are specified so the store is usable beyond a perfect sample order.
A few clients we’ve worked with
What we do
UX/UI design for ecommerce businesses: shopping flow, selection and cart states, prototype and specification.
What UX/UI design needs to account for.
A product option can become unavailable after a shopper selects it.
Cart changes need visible confirmation and recovery when they fail.
Account requirements should be clear before shoppers reach a blocked step.
What interface decisions cost when nobody makes them.
Interfaces are not decorated; they are decided. When the tasks, roles and states are never agreed, they get invented during development — one screen at a time.
Development stops guessing
An agreed screen inventory and behaviour means engineers implement decisions instead of making product decisions in code review.
The product survives its next feature
Patterns designed once hold when the roadmap adds a role, a plan tier or a new workflow.
UX/UI design scope.
Plan shopping flow, selection and cart states and prototype and specification as connected parts of the engagement.
Shopping flow
Map the tasks shoppers perform to find and compare items. Define where product guidance, account access or an appointment is needed.
Selection and cart states
Design variant availability, quantity limits and basket changes. Include invalid combinations, stock changes and failed updates.
Prototype and specification
Build a reviewable Figma flow using representative products. Document platform constraints and business decisions for engineering.
Selected website projects across our wider practice
All case studies
“What I appreciate most is that the team always communicates openly and stays honest throughout.”
“They delivered what they said they would, on time.”
“They met all our expectations by providing great strategies based on our needs.”
UX/UI design deliverables.
The agreed UX/UI design scope is documented in the following work products.
- 01
Role and user-flow diagrams
- 02
Figma screens with interaction states
- 03
Clickable prototype and behaviour specifications
Our process
How we approach UX/UI design.
Map shopping rules
Define product choices, stock behaviour and permitted cart actions with the business owner.
[ 01 ]
Prototype difficult states
Design unavailable variants, failed updates and recovery alongside the ordinary buying path.
[ 02 ]
Review platform behaviour
Confirm the flow fits supported commerce controls and document unresolved rules before development.
[ 03 ]The people who do this work.
No account layer between you and them. These are the Norml specialists this work runs through.
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get startedUX/UI design for ecommerce businesses: questions.
Can you improve one journey without redesigning the whole store?
Yes. Product selection, filtering or cart behaviour can be scoped as a bounded interface change.
Will you decide return or stock reservation policies?
No. Your team supplies those rules; we identify missing decisions and express the approved behaviour in the interface.