A search for ecommerce web design near me ends with a list of studios and a pile of attractive portfolios, with very little to tell them apart. This guide gives you a yardstick: what design work for an online shop should include, how a good designer runs the process, and how to test their past shops yourself in fifteen minutes.

Design here means the look and the flow of the store: page layouts, the product page, cart and checkout screens, and the rules behind fonts, colours and buttons. Writing the code is a separate job, and the guide to finding the right ecommerce developer covers who does that.

What should an ecommerce designer deliver?

Ask for this list in the quote, item by item. A designer who cannot name each output has not thought through the job.

  • A research summary: who buys from you, which competitor shops they compare you with, and what your current analytics say about where people leave.
  • Wireframes for each template. A shop with 400 products still has only six or seven templates: home, category, product, cart, checkout, account and content page.
  • A clickable prototype you can tap through on your own phone before any code exists.
  • A design system: colours with their contrast values, a type scale, buttons and form fields in every state (normal, hover, keyboard focus, error, disabled).
  • A handoff package for the developer, with measurements, exported images and icons, and written notes on how each part behaves.
  • Accessibility notes that list which WCAG 2.2 criteria the design was checked against.

Which design process should the quote describe?

A sound process has gates. You approve each stage before the next starts, because every later stage builds on the one before, and a change after a gate costs more than the same change before it.

Example: a 60-hour design project for an invented gift shop with one physical store (hours for illustration only):

StageWhat you seeWhat you approveExample hours
ResearchA two-page summary and three competitor screenshots with notesThe problems the design must solve8
WireframesGrey boxes for each template, desktop and phoneLayout and the order of content12
PrototypeClickable screens in full colourLook, wording on buttons, the buying flow14
Design systemColours, fonts, components and their statesThe rules the developer will follow10
HandoffSpecs, assets, notesThat the developer has what they need6
Revision roundsChanges from your feedbackTwo rounds per stage, as agreed in the quote10

Total: 8 + 12 + 14 + 10 + 6 + 10 = 60 hours. If a quote shows one line called “design” with a single price, ask for this split. It tells you where the time goes and what happens when you want a third round.

Customised theme or custom design: which fits your shop?

Most small shops start from a theme, the ready-made design that a platform or an outside studio sells. The real question is how far the designer moves away from it.

Customised themeCustom design
Starting pointAn existing theme and its demo storeA blank page and your research
What the designer changesColours, fonts, images, section order, a few new sectionsEvery template, drawn for your products
Design hoursA fraction of a custom jobAll six stages in full
Theme updatesEasier to apply when edits stay inside the theme settingsYour developer maintains the code
Who helps when it breaksThe theme maker, for its own codeYour designer and developer

On Shopify, Shopify’s store setup guide explains that free themes are built by Shopify, which also supports customising them, while paid themes come from outside designers who handle customisation help themselves. Paid themes are non-refundable, and Shopify lets you try one in your own store before buying, so ask the designer to test the shortlisted theme with your real product photos first.

Decision rule: open the theme demo on your phone. If it already shows about 80% of what you want, customise it. If your products need a layout no theme offers (made-to-measure options, a configurator, a booking calendar), budget for custom templates on those pages only.

What matters most on a product page?

The product page is where the sale is won or lost, so ask the designer to draw it at phone width first and to defend the order of what appears. A useful order to start from:

  1. Photos that show size, texture and the item in use, with zoom.
  2. Price, and next to it the delivery cost or the free-delivery threshold, so the total is never a surprise at checkout.
  3. Options such as size or colour, with stock shown per option and sold-out choices marked in words as well as colour.
  4. The add-to-cart button, visible without scrolling on a phone.
  5. Local details: collect from the shop today, delivery days in your area, the address of the pickup counter.
  6. Returns in one sentence, linked to the full policy.
  7. Reviews and specifications, lower down for those who want them.

For the pickup wording and the “ready to collect” messages behind point 5, see the guide to buy online, pick up in store.

Which cart and checkout details belong to the designer?

Some platforms limit how far the checkout page can be changed, so ask early which parts of the checkout the designer can touch on your platform. Whatever they can change, these points come straight from the WCAG 2.2 success criteria and are easy to check in a prototype:

  • Errors in words. When a field is wrong, the field is identified and the problem is described in text (criterion 3.3.1). A red border alone fails.
  • No retyping. Information the customer already entered in the same process is filled in or offered for selection (3.3.7, Redundant Entry). A “billing address same as delivery” box does this job.
  • Logins without memory tests. Customers must be able to sign in without solving or recalling something, unless help is available, such as support for password managers and pasting (3.3.8).
  • Buttons big enough to hit. Targets are at least 24 by 24 CSS pixels, or spaced so they do not crowd each other (2.5.8).
  • Nothing covering the focus. A sticky cookie bar or chat bubble must not completely hide the field a keyboard user has moved to (2.4.11).

What does WCAG 2.2 ask of a shop design?

The Web Content Accessibility Guidelines (WCAG) are the W3C standard for making web pages usable by people with disabilities. According to the W3C’s summary of what is new in WCAG 2.2, version 2.2 became a W3C Recommendation on 5 October 2023 and adds nine success criteria to WCAG 2.1. Each criterion has a level: A, AA or AAA. Put level AA in the design contract and ask for a written list of the criteria checked.

CriterionLevelWhat it means on a shop page
1.4.3 Contrast (Minimum)AABody text at least 4.5:1 against its background, large text at least 3:1. Pale grey prices on white fail fast.
1.4.11 Non-text ContrastAAField borders, icons and button edges at least 3:1 against what surrounds them
2.4.11 Focus Not Obscured (Minimum)AA, new in 2.2Sticky headers and banners never fully hide the focused item
2.5.7 Dragging MovementsAA, new in 2.2A price slider also works with taps or typed values
2.5.8 Target Size (Minimum)AA, new in 2.2Quantity buttons and filter checkboxes at least 24 by 24 CSS pixels, with listed exceptions
3.2.6 Consistent HelpA, new in 2.2The help link or contact form sits in the same place on every page
3.3.7 Redundant EntryA, new in 2.2The checkout never asks for the same details twice
3.3.8 Accessible Authentication (Minimum)AA, new in 2.2Account login allows paste and password managers, or offers another method

The full text of each criterion, with its exceptions, is in the WCAG 2.2 standard. Whether a law in your country requires conformance is a legal question for an adviser; the design checks above are worth doing either way, because every one of them also helps customers on a small phone screen.

How do you review a designer’s portfolio in fifteen minutes?

Screenshots flatter everyone. Live shops tell the truth, so run this test on two or three of the designer’s past stores:

  1. Ask for live URLs of shops they designed, then check each one still runs their design.
  2. Buy on your phone. Find a product, choose an option, add it to the cart and go as far as the payment step. Count the moments where you hesitated.
  3. Press Tab on a laptop and move through a product page. You should see where you are at every step, and no sticky bar should hide the focused item.
  4. Test the pale text. Run the lightest grey on the page through any free contrast checker and compare it with 4.5:1.
  5. Trigger an error in the newsletter or checkout form and read whether the message says what went wrong.
  6. Ask what they designed and what came with the theme. A clear answer, with the theme’s name, is a good sign.
  7. Request one wireframe and one design system file from a past project, with the client’s name removed if needed.

Score what you find with the discovery call scorecard, so the designers you meet are compared on the same lines.

How do you give design feedback without paying for extra rounds?

Revision rounds are where design budgets leak. Three habits keep them in check:

  • One person collects all feedback and sends it in one message per round. Five people sending notes at different times create five rounds.
  • Describe problems and leave the solutions to the designer. “Customers will not see the delivery cost” gives them something to solve; “make it bigger and red” gives them an order that may break the design system.
  • Number every comment and ask for a numbered reply, so nothing is lost between rounds.

Example arithmetic (invented rates): if one extra round takes 5 hours at 70 an hour, it costs 5 × 70 = 350. Three unplanned rounds across the project add 1,050, which is more than the whole handoff stage in the 60-hour example above. Agree in the quote how many rounds are included and what an extra one costs.

Does a designer near you make a difference?

A local designer can walk round your shop, see how customers handle the products, and photograph the counter, the pickup shelf and the stock in real light. Workshops in the same room tend to be shorter and clearer. Those are real gains for a business whose customers also visit in person.

Distance does not change the test, though. Run the same portfolio check on a studio down the road as on one across the country, and judge them on the outputs listed at the top of this page. If you are weighing a studio against a single freelance designer, the comparison of an ecommerce agency vs a freelancer covers the trade-offs.

FAQ

How long does ecommerce web design take?

The hours and the calendar differ. A 60-hour project like the example above can stretch over four to six weeks, because each stage waits for your approval. Give the designer a date for every gate, and keep one for yourself too.

Can I keep my existing logo and brand colours?

Yes. Ask the designer to test each brand colour for contrast first. A colour that fails 4.5:1 against white can still work for large headings or decoration, while body text and prices move to a darker shade.

Does a small shop need a custom design?

In most cases a customised theme covers it. Custom templates make sense for the pages where your products need a layout no theme offers, such as a product configurator or a booking calendar.

What files should the designer hand over at the end?

The source design file with editing rights, the design system with every component state, exported images and icons, and written notes on behaviour. Make sure the files sit in an account you own, so a future designer can pick them up.

That depends on where you trade and which laws apply there, so ask a legal adviser. WCAG 2.2 itself is a W3C standard, and designing to level AA is a clear brief you can put in any contract.

Should the designer write my product descriptions too?

Copywriting is a separate skill and a separate line in the quote. The designer should plan space for real text, so ask for the wireframes to use your actual product names and description lengths.

How many design directions should I ask for?

One direction developed properly beats three rough ones for a small shop. If you want options, ask for two variations of the product page only, since that page carries the most weight.

What should you do before contacting designers?

Write down the templates you need, the problems you want solved and the WCAG level you expect, then send the same short brief to every designer you contact. The ecommerce brief template gives you the structure.

If you would like help preparing that brief or reading the replies, write to MarketPulse through the contact form.