A requirements-led UK ecommerce technology stack for 2026

This article is MaxInvent's opinionated architecture framework. It is not a ranking, market study or claim that one stack fits every business.

Define systems of record first

For each operational record, name one owner:

• product content;
• operational stock;
• marketplace orders;
• warehouse locations;
• shipments and tracking;
• customer and trade pricing;
• sales invoices, supplier bills and payments; and
• analytics events.

Then document every required data flow, direction, trigger, failure state and reconciliation owner.

Storefront and marketplaces

Choose storefront and marketplace channels from customer and product evidence. Connector scope must be checked per record type; a channel logo does not prove listing, stock, order, return and tracking coverage.

MaxInvent documents live commerce connectors for eBay, Amazon, TikTok Shop, Temu, Groupon, ClearanceFood and Magento. Shopify has connector foundations and limited onboarding, so its scope must be agreed before it is included in a production design.

Inventory, warehouse and dispatch

A focused commerce operations layer can own inventory, orders, purchasing, returns, warehouse locations, barcode pick-pack and dispatch. Test update and retry behaviour for each marketplace API instead of assuming a universal “real-time” latency.

MaxInvent supports multiple warehouses, zones and locations and parcel splitting by quantity, weight and dimensions. It does not claim automatic nearest-warehouse routing or automatic cross-warehouse splitting.

Carrier workflows

Verify every carrier against the account, service and API access you will actually use.

MaxInvent implements Evri, Amazon Shipping where the account and order are eligible, and Temu shipping for eligible connected Temu orders. Other carriers can be assessed and configured subject to account and API availability.

Accounting

Write down required record types, direction, currency, tax mapping, duplicate handling and retry behaviour. MaxInvent's verified Xero scope is optional outbound GBP push for sales invoices, supplier bills and payments. It does not claim two-way, multi-currency, marketplace-fee splitting or credit-note export.

Analytics and privacy

Only enable analytics deliberately. For this website, Plausible remains disabled unless NEXT_PUBLIC_PLAUSIBLE_DOMAIN is set in the deployment environment. Local development should not send production analytics.

For customer systems, document primary hosting, disaster recovery and connected third parties. MaxInvent uses AWS London for the primary app, databases and uploads, with encrypted DR database snapshots in AWS Ireland.

A practical architecture review

For every connection, ask:

1. Which system owns the record?
2. Which fields move and in which direction?
3. What is the trigger?
4. How are retries and duplicates handled?
5. What does an operator see when it fails?
6. How is the result reconciled?
7. Which account, API and regional dependencies apply?

The best stack is the smallest set of systems that satisfies those documented requirements and can be tested with representative data.