Ask five agencies what your ecommerce "tech stack" should be and you'll get five different answers — each suspiciously aligned with what they sell. The truth is less exciting: an ecommerce tech stack is just the set of systems that take a customer from "I want that" to "it's at my door", plus everything that has to work behind the scenes to make that happen reliably. Here's the full anatomy, what each layer does, and how to choose without getting sold.
The layers, bottom to top
1. The commerce platform (the foundation)
Shopify, WooCommerce, Magento/Adobe Commerce, or custom-built. This is the system that holds your products, takes orders and processes checkout. For most UK SMEs, the mainstream hosted platforms or WooCommerce cover it — the former if you want simplicity and reliability, the latter if you want control and already live in WordPress. Enterprise complexity (multi-brand, heavy B2B, exotic fulfilment) pushes towards Adobe Commerce or custom. Our Shopify vs Shopify Plus guide covers the upgrade decision within Shopify's world.
Choose the platform for where you'll be in three years, not where you are today. Replatforming mid-growth is one of the most expensive disruptions in ecommerce.
2. Payments (the money layer)
Stripe, PayPal, Klarna/Clearpay (buy-now-pay-later is near-mandatory for UK fashion and lifestyle), Apple Pay and Google Pay for mobile. The rules: offer the methods your customers actually use (check your analytics, not your preferences), keep checkout to as few steps as possible, and make sure failed payments recover gracefully — a surprising share of "abandoned" checkouts are payment failures, not changed minds.
3. Product information (the often-missing layer)
PIM — Product Information Management. Unsexy, critical. As catalogues grow past a few hundred SKUs across multiple channels (your site, Amazon, eBay, Google Shopping), product data chaos follows: inconsistent titles, wrong images, pricing mismatches. A PIM (or at minimum, disciplined product data processes) keeps every channel selling from the same truth. Businesses skip this layer and pay for it in manual effort forever.
4. Inventory and order management
Where stock lives, what's available to promise, and how orders flow to fulfilment. Small operations manage this inside the commerce platform. Growing ones need a dedicated OMS or ERP integration — especially with multiple warehouses, click-and-collect, or marketplace orders mixed with direct ones. The classic failure: selling stock you don't have (overselling) or hiding stock you do (underselling). Both are systems problems with systems solutions.
5. Fulfilment and logistics
Warehouse management, carrier integration (Royal Mail, DPD, Evri — UK customers have strong delivery preferences and stronger opinions), tracking, returns. Returns deserve emphasis: UK fashion ecommerce sees return rates that would horrify other sectors, and a smooth returns process is a conversion factor, not just a cost centre. Integrate tracking and returns into the post-purchase experience, not as an afterthought.
6. Marketing technology
Email/SMS (Klaviyo dominates this space for good reason), loyalty and reviews (Judge.me, LoyaltyLion), paid media feeds (Google Shopping, Meta catalogues), and analytics. The principle: every marketing tool should read from and write to the same customer truth — which usually means your CRM or customer data platform sits at the centre, not a dozen disconnected apps.
7. Analytics and attribution
GA4 properly configured, server-side tracking (increasingly necessary as cookies die), and honest attribution that looks beyond last-click. If you can't connect marketing spend to revenue by channel, you're flying the business on instruments that don't work.
How to choose: principles over products
- Integration beats features. The best individual app that doesn't talk to your stack is a data silo with a subscription fee. Prioritise systems with robust APIs and proven integrations with your platform.
- Fewer, better tools. Every app is a subscription, a failure point, a page-speed tax and a security surface. Audit annually: if a tool's value can't be articulated in one sentence, cancel it.
- Own your customer data. Whatever you choose, customer records, order history and consent data must live in systems you control and can export. Platforms come and go; your customer list is the business.
- Plan for the unglamorous. Data migration, staff training, process redesign — the "boring" 60% of any stack project determines whether the exciting 40% delivers. Budget for it.
The mistakes to avoid
App sprawl: twenty apps each adding 200ms of load time and £30/month. Audit ruthlessly. Building custom what you should buy: payments, tax calculation, email delivery — solved problems; don't rebuild them. Buying enterprise what should be simple: a £50k ERP for a 500-order-a-month business is a very expensive way to feel professional. Ignoring mobile: most UK ecommerce traffic is mobile; if any layer of your stack treats mobile as an afterthought, customers feel it.
A worked example: the £2m fashion retailer
Principles are nice; here's what a sensible stack looks like for a concrete business — a UK fashion retailer doing £2m online, 800 SKUs, selling direct and through two marketplaces:
- Platform: a standard hosted plan — Plus not yet justified at this volume. Theme customised, not custom-built.
- Payments: Shopify Payments + PayPal + Klarna. Mobile wallets enabled. One-page checkout.
- Product data: disciplined PIM-lite process inside Shopify with structured metafields; full PIM deferred until the catalogue or channel count forces it.
- Inventory: Native inventory plus a stock-sync app covering the marketplaces — overselling protection as the priority.
- Fulfilment: 3PL warehouse with carrier integration (Royal Mail + DPD), branded tracking page, self-service returns portal.
- Marketing: Klaviyo for email/SMS, Judge.me for reviews, Google Shopping + Meta catalogues fed from the product data.
- Analytics: GA4 with server-side tagging, the attribution setup from our guide, and a monthly revenue-by-channel review.
Total app count: under ten. Nothing exotic, everything integrated, every layer earning its place. That's what a good stack looks like — boring in the best way.
Revisit the stack annually: kill the apps nobody can justify, renegotiate the contracts that crept up, and check every integration still earns its subscription. Stacks rot by accumulation; the audit is the antidote.
We design and build ecommerce systems for UK retailers — platform selection, Shopify builds, integrations, and the analytics to prove it's working. If your stack grew by accident and now needs architecture, get a free consultation.
