Catalogue and site architecture
How the range is grouped, what a category page has to prove, and the route from a browse to a checkout. Built around how people shop the catalogue, not how the warehouse files it.
Ecommerce web design that survives the second year.
Norml designs and builds stores for brands that already sell — the catalogue structure, the design system, the storefront, and the fulfilment and marketing plumbing behind it. Rebuilt in slices, so traffic and revenue never stop while the new store goes live.
A few clients we’ve worked with
A store that works at 200 orders a month starts failing at 2 000.
The theme was chosen when the catalogue had 40 products, and every new category now fights the template.
Fulfilment, review requests and customer questions are still done by hand, so growth costs staff hours rather than earning margin.
Ad spend rises and return on it falls, because nothing on the site tells you which product or campaign actually paid.
The brand looks one way on Instagram and another on the product page, and the gap is doing quiet damage to conversion.
A redesign has been postponed for two years, because nobody can promise the rankings and the revenue will survive it.
What our ecommerce web design services include.
Seven things, in the order we do them. Web design for ecommerce starts with the catalogue you actually have and the orders you actually get, so custom ecommerce web design begins with your range rather than a theme; Norml can take the whole scope or work beside your in-house team.
Product and collection pages
The page that closes the sale. For Vona Bride we built a directory organised by designer, with a page per gown carrying its own photography, pricing and detail — because brides browse and come back before they ever book.
Design system in Figma
Components, states and responsive rules, so the fortieth product page looks like the first and a seasonal launch does not need a designer.
Storefront build
WordPress with WooCommerce, or a headless front end — on the stack your team can actually run. Including replacing a page-builder store that has become too slow to fix.
Migration without a revenue gap
We rebuild in slices and ship them one at a time, watching traffic and tracking at each step. That is how we moved Polaclub onto a new store with no disruption, and how we migrated Diet vs Disease off Elementor while its SEO and paid traffic kept running.
Order and support automation
The manual work that scaling makes unbearable. For Polaclub that meant review collection over email and SMS, warehouse fulfilment wired into the carrier, and an AI support assistant answering from the real product catalogue.
Analytics and acquisition
Conversion tracked per product so campaigns have something real to optimise against, plus the SEO and paid work to bring people in. Configured at launch, not bolted on after.
Ecommerce web design deliverables.
The exact scope depends on the catalogue and the stack. A typical ecommerce engagement hands over the following:
- 01
A catalogue and URL map you can hand to anyone — every page, its job, and what links to it.
- 02
A Figma design system with components, states and responsive rules.
- 03
Product and collection page templates written against the real range.
- 04
A built storefront on WooCommerce or a headless front end — your team runs it.
- 05
A staged migration plan with redirects, so rankings and paid traffic hold.
- 06
The order, review and support automations wired to your real tools.
- 07
Analytics and Search Console configured on day one, conversion tracked per product.
- 08
A handoff session and the files, so nothing about the store depends on us staying.
Our process
How our ecommerce web design process works.
Discovery
We read the catalogue, the analytics and the support inbox. Not a questionnaire. You get the diagnosis — where shoppers drop out and which manual step is costing the most.
[ 01 ]
Architecture
Category structure, URL map and what each page has to prove. A map you can argue with before anything is designed.
[ 02 ]
Design
Wireframes first, then the system in Figma. Product and collection templates, not a stack of static screens.
[ 03 ]
Build
The storefront, then the automations behind it. A store your team can edit without a developer.
[ 04 ]
Launch in slices
Section by section, each one checked against the old version before the next ships. Redirects, analytics and Search Console through the whole transition.
[ 05 ]Ecommerce web design questions.
What does an ecommerce web design agency actually do?
It designs and builds the store: how the catalogue is organised, what a product page has to prove, the design system that keeps the whole thing consistent, and the build itself. A good one also takes on the work around the order — fulfilment, review requests, support, tracking — because that is where growth gets expensive. Whether a firm calls itself an ecommerce web design company or an agency, the job on the storefront is the same.
Which platform should our store run on?
Usually WordPress with WooCommerce, because it keeps the content and the catalogue in one place and your team can run it without a developer. A headless front end is the right answer when the catalogue is large or the storefront has to be very fast. Drag-and-drop page builders are the wrong answer for a growing store: they get slow, and eventually nobody can maintain them — replacing one is a job we do often.
Can you redesign our store without losing rankings or sales?
Yes, and it is planned work rather than a hope. We rebuild in slices and ship them one at a time, checking traffic and tracking against the old version at each step before the next goes live. That is how Polaclub moved to a new store without disruption, and how we took Diet vs Disease off Elementor onto a custom theme while its SEO and paid traffic kept running.
How much does ecommerce web design cost?
Norml publishes its rates on Clutch — $50–$99 per hour with a $5,000 project minimum. Full ecommerce web design services, meaning architecture, design system, storefront and the automation behind the order, sit well above that minimum. We scope after discovery, not before.
Do you sell an ecommerce web design package?
No, and the reason is the catalogue. A store with 40 products and one fulfilment route is a different piece of work from a store with 4 000 and three, and a fixed package prices one of them wrong. We scope after discovery, when the catalogue, the stack and the manual steps are on the table.
Can you automate fulfilment and customer support too?
Yes — that is usually where the return is. For Polaclub we integrated warehouse fulfilment with the carrier, moved review collection onto automatic email and SMS, and added an AI support assistant that answers from the live FAQ and product catalogue. Which of those is worth doing depends on where your team is currently spending its hours.
Our catalogue is small and the store is mostly about booking a visit. Does that count?
Yes, and it is a common shape. Vona Bride is a bridal boutique in Kitchener: the site has to let brides explore designer collections and individual gowns before they drive to the store, then turn that browsing into a booked fitting, with confirmations and reminders handled automatically. The catalogue work is the same discipline whether the page ends in a cart or an appointment.
We have not launched yet. Should we wait?
Not necessarily. GoPetZen came to us before their app existed, needing to prove demand to investors — we built the brand, the landing page, and a multi-step registration and survey system that collected real data from pet owners through the fundraising period. If the product is not ready, the site can still be doing the work that makes the next step possible.
What happens after launch?
You can run it yourself — the handoff includes the files, the design system, and a session with your team. When a team would rather not, Norml Care covers updates, monitoring and small changes on a monthly plan.
Website 2.0 combines strategy, design, development and launch in one engagement — the same process behind Polaclub, Vona Bride and GoPetZen.