Web design · Ecommerce
The store is ascoping question first.
Platform, then the collection and the product page, then a checkout that is not carrying twelve extra scripts.
The short answer
What an ecommerce build has to decide.
Shopify, WooCommerce, and BigCommerce are not a taste test at the end of design. They change who can edit the catalog, where checkout lives, and what you will pay a developer to maintain. We settle that in scoping. Then we design the collection, the product page, and the path into checkout. A new theme on the wrong platform is a second project you have already paid for once.
Buying cycle
Collection, product, checkout.
A shopper usually lands on a collection or a product page. The grid needs price, the variant that matters, and a reason to open the product. The product page needs the variant to stick, shipping and returns near the price, and a description in text. The homepage hero is not the page this visit depends on.
Checkout is where theme work goes to die. Guest checkout and a visible total matter more than a custom font in the cart. Every app that injects itself into checkout is a delay. We inventory those apps before we promise a date.
Constraints
Pick the platform before the templates.
Shopify fits a team that wants a maintained checkout and an admin a merchandiser can run. WooCommerce fits when the guides and the catalog live in WordPress with the people who already edit that site, and someone will own hosting and updates. BigCommerce fits when the catalog, B2B price lists, or checkout without a pile of plugins is the actual requirement.
Next.js in front of one of those is a front end, not a default. It is justified when the content model truly needs it. A small catalog does not need a headless rebuild to get a faster product page. Design does not start until the platform is written down. The templates do not move for free.
A store takes longer than a brochure site. Catalog, apps, and checkout rules are why. On a migration the old store stays up until redirects and the catalog check are done.
- Shopify, WooCommerce, or BigCommerce chosen with the people who edit products.
- Collection filters that match how people buy, not every attribute in the database.
- Product pages with variants, shipping, and returns next to the price.
- Guest checkout unless you have a real reason to force an account.
- A written list of apps that are allowed to touch the cart.
Channels and KPIs
Judge the template, not the sale weekend.
A product-page change and a sitewide sale will both move revenue. We separate them. The template is judged on add-to-cart rate, checkout completion, and speed on the collection and the product page. Merchandising and ads stay visible in the same review so a theme launch does not take credit for a promotion.
- Add-to-cart and checkout completion on the new templates, against the prior theme.
- Speed on collection and product templates, on a phone.
- Script count on checkout, before and after.
- Ads landing on a collection URL that exists, not the homepage for every campaign.
Mistakes
A replatform that starts with a theme.
Teams pick a theme, then discover the platform cannot do price lists, or that the content team has no way to edit a guide, or that checkout apps they forgot about break the new cart. The other pattern is a headless project for a catalog that a well-scoped theme would have served.
- No design kickoff before the platform is chosen.
- No shipping cost that appears for the first time on the last step.
- No mega-menu that duplicates every collection with different names.
- No migration that turns the old store off before redirects are checked.
Example engagement
A few hundred SKUs, and a platform question.
A specialty store, a few hundred SKUs. The brief arrived as 'move us to Shopify.' The buying guides already lived in WordPress, next to a WooCommerce catalog. There was no B2B price list coming. The merchandiser and the editor were the same small team.
We wrote the platform choice down and stayed on WooCommerce. Design started after that. Collection filters matched how people bought. The product template put variants, shipping, and returns next to the price. Checkout apps that duplicated the platform came off before launch. The old cart stayed up until redirects were checked.
Woo
Kept after scoping, guides already in WordPress
PDP
Variants, shipping, and returns beside the price
The example uses anonymized results from a Quorum engagement. It is one account, not a benchmark you should budget against.
Questions
Ecommerce questions.
Should we move to Shopify?
Sometimes. If checkout plugins are the outage, and a merchandiser should run the admin, Shopify is the right conversation. If content and catalog are one WordPress site someone can maintain, leaving may cost more than it saves. We answer that before templates.
When is BigCommerce the right call?
When catalog rules or B2B price lists are why you are rebuilding, and you want checkout off a stack of WordPress plugins. It is not a cosmetic upgrade.
Do we need a Next.js front end?
Only when the content model requires it. Many stores need a faster product template and fewer apps. If we recommend Next.js, the proposal says what the platform theme cannot do.
Will you redesign checkout itself?
We design up to the handoff the platform allows: guest checkout, shipping clarity, and scripts that do not need to be there. A fully custom checkout is rare and usually how wallet support gets lost. We will say if that is what you are asking for.
Can the same team edit guides and products?
That is part of the platform question. If the answer is yes, the build has to make both jobs possible without a developer on every price change or every guide. We watch a merchandiser edit a product on staging before launch.
How long is a store build?
Not the brochure timeline. Marketing sites most often ship in 8 to 12 weeks. Catalog, apps, and checkout rules commonly take twelve to twenty weeks, longer when a migration has to run beside the live store.
More in this lane
Other Web Design industries.
Talk through ecommerce.
One conversation. A diagnostic. A plan you can kill if it is not the work.