Skip to content
E-commerce

EightBlocks Pull out the wrong one, and the whole shop comes down

What this work is

Ecommerce that is useful for customers, easy for staff, and reliable to run without costing the earth.

Four things, and most shops are only sold the first two. Useful: a customer finds the right product, understands it, and knows what delivery costs before they commit. Easy for staff: because a shop is also where somebody spends their working day, and most platforms treat that as another department’s problem. Reliable: the checkout takes money, the stock figure is true, and the site stays up on the day a campaign lands.

Then the fourth, which rarely appears on a quote. A shop held together by nine paid extensions costs more every year whether or not it sells more, and that bill is far easier to argue with before anything is built than after. Part of this work is saying which of them you actually need.

Underneath all of it sit product data, categories, shipping rules, payment flows, stock logic, search and support, every one of which has to agree with the others. The visible store is the small part. We work on Magento, WooCommerce and Shopify, and on the problems that are none of their fault.

No sound. It plays out in pictures. Eight labelled blocks stacked into a tower: product data, storefront, checkout, delivery, payment, pricing, stock, catalogue. Then one gets pulled and the lot comes down. Then the same pieces, laid as foundations.
How the parts connect

Catalogue, checkout, stock and delivery, all holding each other up.

The labels on the blocks in the film are not decoration. They are the parts of a shop that depend on one another: product data feeds the catalogue, the catalogue feeds search, stock decides what checkout may sell, and delivery rules decide what the customer is actually quoted. Pull any one of them out and the tower leans. Built as foundations rather than stacked, the same pieces carry a shop that holds up under real use.

Product data Categories Shipping rules Payment flows Stock logic Search SEO Performance E-commerce holds together under real use
A practical process

How an ecommerce project actually runs.

The build follows the operation, not the homepage. The catalogue, the fulfilment and the support load set the constraints, and the storefront is fitted inside them. It is the reverse of how most shops get quoted.

  1. Product and catalogue structure

    Product data comes first: names, attributes, options, descriptions, categories. Most of the pain further downstream starts here rather than at the till.

  2. Platform and technical fit

    The platform is matched to the operation, not the marketing. A small catalogue with simple fulfilment does not need an enterprise stack; a complex B2B operation should not be wedged into a beginner SaaS.

  3. Checkout, shipping and payment logic

    The visible checkout is the easy part. The real work is shipping rules, taxes, payment options, refunds, exceptions and the edge cases that decide whether a customer trusts you.

  4. Performance, search and SEO

    Category and product pages have to be fast, scannable and findable. If search is bad, the catalogue is invisible to the customer who knew what they wanted.

  5. Monitoring, support and improvement

    An online shop is operational software, not a launch project. Stock issues, payment failures, plugin updates and broken funnels all need somewhere to land after go-live.

Decision guide

Shopify, WooCommerce, Magento or something bespoke?

The platform should fit the operation behind it: the catalogue, the fulfilment, the support load, and how much of it your own staff have to touch each day. The fashionable choice this quarter is rarely the same answer twice running.

  • Hosted shop platform

    Best for Small to medium catalogues, simple fulfilment, low admin overhead.

    Faster to launch. Custom flows and unusual rules can start fighting the platform once the business outgrows defaults.

  • Self-hosted commerce CMS

    Best for Content-heavy stores, editorial control, custom marketing flows.

    Flexible and familiar. Needs care around hosting, performance and plugin discipline so it does not bloat over time.

  • Enterprise commerce platform

    Best for Large catalogues, complex pricing, multi-store, B2B operations.

    Powerful and complex. The operational and technical cost is real, and so are the savings on edge cases at scale.

  • Custom or headless setup

    Best for Configured products, integrated workflows, decoupled storefronts.

    Highest control, highest investment. Choose when the platform is the bottleneck, not the comfort zone.

Next step

Got an online shop that needs a careful look?

Bring the platform, the catalogue and the jobs your staff dread. Start with the operation and the product data rather than the homepage. The storefront is rarely where the real work hides.

Not sure where the actual problem is? Start with a Digital Health Check