Skip to content
NEWAI search optimizationSee how

E-commerce & manufacturing

Catalogs are a structure problem, not a design problem

A store with eleven products and a store with eleven thousand need completely different builds. Most of the difficulty in this sector is in how products, variants and specifications are modelled — everything visible follows from that.

Delivered in this sector

Real projects, linked. Nothing on this page is stock sector copy.

The problem

What breaks at catalog scale

These are the issues that turn up once a store grows past a few dozen products.

  1. Variants were modelled as separate products

    Size, material, finish and quantity break each get their own listing. Now you have six near-identical pages competing with each other in search, six sets of inventory to keep straight, and a customer who cannot tell them apart.

  2. Specifications live in a PDF

    Dimensions, materials, compliance data, load ratings — all locked in a datasheet nobody can search and no engine can read. The same data as structured fields on the page makes the product findable and comparable.

  3. Manufacturers are forced into a retail checkout

    Plenty of B2B buyers need a quote, a freight calculation or a trade account, not a Buy button. A site that only offers a cart loses them. One that only offers a form loses the small orders. Both paths have to exist.

  4. Category pages have nothing on them

    A heading and a product grid. No buying guidance, no sizing help, no comparison. These are the pages with the highest search potential in the whole store and they are usually the emptiest.

  5. Checkout is slow where it matters most

    Apps, pixels and review widgets accumulate until the cart takes four seconds to respond. The cost is invisible in a Lighthouse score taken on the homepage and very visible in the revenue report.

2 projects

We have shipped this already

Delivered work in this sector, from storefront to supplier site.

Outcome figures are published only where the client has confirmed them. Where you see none, we did not have a number we could stand behind. See all work · How we approach search

E-commerce & Manufacturing FAQs

What people ask us first

The questions that come up on nearly every call in this sector, answered the way we would answer them on the phone.

Ask us something else

Shopify or WooCommerce?

Shopify when you want the payment, tax and fraud stack handled and your catalog fits its product model. WooCommerce when you need unusual pricing rules, deep WordPress content alongside the store, or ERP integration on your own terms. We will recommend one after seeing your catalog and order volume, and we are happy to say when your current platform is fine and the problem is elsewhere.

Can we take quote requests and card payments on the same site?

Yes, and most manufacturers should. Stock items go through a normal checkout; configured, bulk or freight-sensitive items go to a quote request that captures the specification properly. The same product page can offer both depending on what the buyer selects.

How do you handle product data from our ERP or PIM?

Where your system can export or expose an API, we sync it so the site is never the place product data is typed twice. Where it cannot, we build an import that runs against a spreadsheet your team already maintains. Either way there is one source of truth and it is not the website.

What happens to our rankings if we move platforms?

The migration plan starts with a full URL inventory and a 301 map before any design work begins. Every indexed product, category and content URL gets a destination. We also keep the old structured data and metadata so pages are recognisably the same to a crawler after the move.

Send us your catalog

A spreadsheet export is enough. We can usually tell from the product data alone where the build should go and what it will take.