Catalogue structure
Products, categories, variants, and filters are modelled before anything is styled. How a catalogue is organised decides what can be found, what can be searched for, and what has to be rebuilt the first time the range grows.
Ecommerce
Ecommerce development that starts with the catalogue, not the theme
How products, categories, and variants are structured decides what customers can find and what has to be rebuilt when the range grows. Platform choice, checkout, and search visibility are planned around that, in the order that makes them cheap to get right.
What decides a store
Three things, and only one of them is design.
Most stores that underperform are not ugly. They are hard to search, hard to check out of, or invisible to Google at the category level.
The path to checkout
Every step between a product page and a completed order is a place to lose the sale. Shipping rules, tax, guest checkout, and payment methods are decided deliberately rather than left at whatever the platform installed by default.
Search visibility
Product and category pages are the pages that rank. They get the same treatment as any other page on a Webbify build: unique titles and descriptions, clean URLs, correct canonicals for variants, and Product structured data that matches what is actually on the page.
The approach
Model the catalogue before choosing a theme.
The order matters. Catalogue structure is the decision everything else inherits, and it is the one that is expensive to reverse.
-
Understand what is being sold
Range size, how often it changes, variants, shipping complexity, whether stock is tracked elsewhere, and who updates it week to week. These decide the platform far more than any feature comparison does.
-
Choose the platform on the requirement
WooCommerce, Shopify, or a code-first storefront each fit a different business. The choice is explained in writing with its trade-offs, including what it will cost to change later.
-
Model the catalogue
Categories, attributes, and variants are mapped before build, along with the URL structure they will produce. This is the part that is expensive to redo.
-
Build and connect
Storefront, checkout, payments, shipping, and tax are built and connected to whatever the business already runs, then tested with real orders in a sandbox before anything goes live.
-
Launch, then measure
Analytics and ecommerce tracking are configured so the business can see where orders come from and where checkouts are abandoned. Without that, later decisions are guesses.
Platform
Chosen on the requirement, explained in writing
There is no default platform here. The recommendation comes with its trade-offs and what it would cost to leave, because that is the part nobody mentions until it matters.
- WooCommerce, when the business already runs WordPress and wants full control of the data
- Shopify, when hosted infrastructure and a managed checkout are worth the platform fee
- A code-first storefront, when performance and a custom purchase flow justify the build
- An existing store, audited and improved rather than replaced
What the work includes
The parts of a store that decide whether it works
- Product, category, and variant modelling with the URL structure it produces
- Platform recommendation in writing, with the trade-offs and the exit cost
- Checkout configuration: shipping rules, tax, guest checkout, payment methods
- Product and BreadcrumbList structured data that matches the visible page
- Canonical handling for variants, filters, and paginated category pages
- Migration of an existing catalogue, including redirects for retired products
- Ecommerce analytics and conversion tracking configured at launch
- Handover documentation for adding products and running the store
Honest expectations
What a good store does, and what it cannot do
- Webbify has not yet published an ecommerce case study. The platform, catalogue, and search work described here is the same work done on other builds; the storefront-specific experience is stated plainly rather than dressed up.
- No conversion rate, sales figure, or revenue outcome is promised. A well-built store removes obstacles between a customer and a purchase. It does not create demand that is not already there.
- Payment security is handled by the payment provider, not by the website. Webbify configures the integration correctly and does not describe any store as PCI compliant without a formal assessment by a qualified assessor.
- A store is more ongoing work than a brochure site. Stock, prices, seasonal changes, and platform updates all need an owner, and that should be decided before launch rather than after.
- If the range is small and unlikely to grow, a simpler setup than a full store often serves the business better. That gets said during scoping, even when it means a smaller project.
Where this fits
Store work usually touches development, migration, and technical SEO
Questions
What people ask before building a store.
WooCommerce or Shopify?
It depends on who runs the store and how much control the business wants over its own data. Shopify handles hosting, security, and checkout for a monthly fee and takes less maintenance. WooCommerce gives full ownership of the data and deeper customisation, and in exchange it is a system somebody has to maintain. Neither is the better product in the abstract.
Can I sell a few products without a full ecommerce build?
Often, yes. If the range is small and stable, a simpler setup — a handful of product pages and a hosted payment link — can serve the business well for a long time. That option gets raised during scoping when it fits, because it is cheaper to run as well as cheaper to build.
Will my product pages rank?
They can, and category pages usually matter more than individual products for search. What is controllable is whether each page is unique, crawlable, correctly canonicalised, and marked up with accurate Product data. Whether it ranks depends on competition and demand, and nobody can guarantee a position.
Can you move my existing store to a different platform?
Yes, and it is treated as a migration rather than a rebuild: the catalogue is inventoried, product URLs are mapped one-to-one or deliberately retired, and redirects are in place before launch. Product URLs are frequently the most valuable pages on a store, and they are the easiest to lose in a platform change.
Do you handle payments and PCI compliance?
Payments are handled by an established provider such as Stripe, PayPal, or the platform’s own checkout, which is where card data belongs. Webbify configures that integration correctly and keeps card data off the site entirely. Webbify does not certify any store as PCI compliant; that requires a formal assessment by a qualified assessor.
Selling online, or thinking about it?
Tell Webbify what the range looks like and who maintains it. The first answer is often that a smaller setup fits better, and that gets said before a proposal, not after.