eCommerce Software Development Company in London, built to ship.

Selling into the EU is now cross-border trade

Before 2021 a UK storefront selling to a customer in Germany was a domestic sale inside a single market. It is now an export, and the checkout has to say so. The practical consequences are a customs declaration, VAT owed in the destination country rather than the origin, and a decision about whether to register for Import One Stop Shop so that VAT is collected at checkout instead of demanded from the customer by a courier at the door. That last outcome is the one that generates support tickets and refunds, because a customer who paid at checkout does not expect a second bill. The build consequence is that landed cost has to be computed live, per destination, before payment, which means the tax engine is an integration rather than a lookup table.

Next-day is the floor, not the premium

UK consumers have been trained by two decades of national carrier density to treat next-day delivery as ordinary. That pushes the engineering constraint out of the storefront and into the warehouse cutoff. The site has to know, per SKU and per postcode, whether an order placed at this moment still makes today's despatch, and it has to stop promising once the cutoff passes. Getting that wrong is worse than being slow, because a missed promise costs the reorder. Click-and-collect adds a second inventory pool with its own truth, and a shopper who reserves in store expects the stock to actually be there.

Payments: cards, wallets and an open banking option that actually works

Card remains dominant, but the UK has the most mature open banking infrastructure of any market we serve, which makes pay-by-bank a genuine alternative rather than a demo. It settles faster and costs less than card interchange, and for high-value baskets the saving is material. Buy-now-pay-later is regulated more tightly here than in Australia and the rules continue to move, so a BNPL integration needs its affordability and disclosure behaviour checked against current guidance rather than copied from another market. Card surcharging on consumer transactions is restricted, so the price shown must be the price paid.

Accessibility and consumer law are enforceable, not aspirational

UK consumer regulations give a distance-selling right to cancel that is broader than a typical returns policy, and the storefront has to present it correctly rather than bury it. Accessibility expectations follow WCAG and are a real procurement question for anything B2B. Cookie consent under UK GDPR and PECR has to be genuine consent, which means analytics and marketing tags do not fire before a choice is made, and that has an engineering consequence for how tag management is wired.

What we would check first on a UK build

Whether the tax engine computes destination VAT live or guesses. Whether the despatch cutoff is modelled per SKU or hardcoded. Whether consent gating actually blocks tags rather than merely recording a preference. Whether returns create a real inventory event or an email to a person. Those four account for most of the operational pain we see in UK stores, and all four are cheap to design in and expensive to retrofit.

Marketplace pressure sets the reference price

A UK shopper checks the marketplace before buying direct, so the storefront is competing on a price they can verify in seconds. That pushes the commercial case away from price and toward the things a marketplace cannot do: bundles, configuration, subscription, and owning the customer relationship after the sale. The build consequence is that the product model needs to express things a marketplace listing cannot, otherwise the direct store is a worse version of a channel the customer already trusts.

Peak is Black Friday into January, and it is brutal

The UK peak is a six-week continuous load rather than a single day, running from late November through the January sales, with returns arriving on top of ongoing trade. Capacity has to survive concurrent traffic, order volume and a returns queue at once, which is a harder profile than a single-day spike because nothing gets a chance to drain. Load testing against a one-hour peak will miss the failure mode entirely.

Returns are a legal right with an operational cost

Distance selling rules give a cancellation window that is wider than most published policies, and clothing categories in this market run return rates that make reverse logistics a primary flow rather than an exception. Restocking condition, refund timing and whether the item returns to sale need modelling as first-class states, because the finance reconciliation depends on them and support spends its day inside them.

Search and structured data decide discovery

Product schema, availability, price and review markup are what put a listing into the rich result, and in a market this competitive the rich result is a meaningful share of the click. Faceted navigation also has to be crawl-controlled, because an unconstrained filter set generates a combinatorial explosion of URLs that consumes crawl budget and produces near-duplicate pages, which is the most common technical SEO failure we find on UK stores.

Stock is the hardest number on the site

Available means on hand, minus what is in unexpired carts, minus what is picked but not despatched, plus what is inbound and confirmed. Get the definition wrong and you oversell, which costs refunds and reviews, or you phantom-hold stock and lose sales quietly, which is worse because nobody reports it.

Checkout is where every architectural shortcut surfaces

Address validation, tax by jurisdiction, shipping rules, promotion stacking, payment retry and a network drop between authorisation and order creation. Each is small on its own and together they are most of the risk, so checkout gets designed as a state machine rather than a form.

Peak is a different system

A storefront that is comfortable at ordinary traffic can fall over at a sale launch, because everyone arrives at once and they all want the same three products. Cache strategy, database contention on hot rows and queue depth all have to be planned for the peak, and the peak has to be load-tested rather than estimated.

Returns are half the operation and get a tenth of the design

The return flow touches inventory, refunds, restocking condition, and the customer's belief about whether to order again. It is usually bolted on after launch and it is usually the thing support spends its day on.

Working overlap

3.5 hours a day

Five and a half hours behind Surat in winter, four and a half in summer. The overlap is our afternoon and their morning, roughly 14:00 to 17:30 IST. That is enough for a daily call and not enough for continuous pairing, so the working agreement has to be written down rather than assumed.

Payments

Open Banking is further along here than almost anywhere, so account-to-account payment initiation is a realistic option rather than a novelty, and Faster Payments settles in seconds. Bacs Direct Debit still carries most recurring billing and its three-day cycle has to be modelled in the subscription state machine.

Sectors that dominate

Financial services and the fintech layer around it dominate, with insurance and the Lloyd's market, legal technology, and media close behind. A striking share of software buying here is by a regulated entity even when the product itself is not regulated.

The mistake we see most

The supplier assurance process is routinely longer than the build. A security questionnaire, evidence of insurance and often a penetration test report arrive before contract, and teams that scheduled the project from the kick-off date rather than from the assurance start date are late before they write a line. Ask for the questionnaire in week one.

Working week

Monday to Friday. The overlap is our afternoon and their morning, roughly 14:00 to 17:30 IST, which is one good call a day and not continuous pairing.