For agencies · Ecommerce delivery

The shop build you had to turn down.

Most agencies can deliver a standard shop. The ones that get turned down are the briefs where pricing, products or checkout work in a way the platform did not anticipate.

Custom checkout Trade pricing Configurators Under your brand
The brief that gets declined

Standard shops are not the problem.

A catalogue, a basket and a card payment is well-trodden ground and most agencies handle it. The briefs that cause trouble are the ones where the business does something specific: prices that differ per customer, products configured rather than picked, ordering against account terms, or a checkout that has to ask something unusual before it can take money.

Those are not bigger versions of a standard shop. They are development projects wearing an ecommerce label, and quoting them as though they were the former is how agencies lose money on the ones they do accept.

We take those on behind you. You keep the client, the design and the relationship; the awkward parts get built properly rather than approximated with plugins that half fit.

What we build

The parts that make a shop complicated.

Customer-specific pricing

Prices following the account or group, including volume breaks and contract terms, rather than one price for everyone.

Account ordering

Ordering against agreed terms with no public checkout, which is how a great many trade businesses actually sell.

Product configurators

Made-to-measure and built-to-order, where the price is calculated from what the customer specifies.

Custom checkout

Extra steps, unusual validation, split delivery, or anything the standard flow cannot express.

Subscriptions

Recurring orders, renewals and the awkward middle cases — pausing, changing tier, failed payments.

Back-office integration

Stock, pricing and orders connected to the accounting or ERP system that already holds them.

Type and spacing honoured

The scale you set, not approximated. If a typeface cannot be licensed for web we tell you before the build rather than substituting it.

Problems raised early

A layout that breaks at 900px, an interaction that will be painful on a phone. You hear about it while it is still cheap to change.

Responsive decisions shared

Designs rarely cover every width. Rather than invent the in-between states we agree them with you.

Built to be edited

So your client can update content without the design falling apart, which is what protects your work after handover.

Nothing branded by us

No credit in the footer, nothing in the code, nothing in the documentation. Your client sees your agency.

Straight answers

Worth agreeing before you quote.

The pricing rules are the project

Not the design. If they are undocumented, writing them down is the first task and it often reveals inconsistencies.

Platform choice matters here

A brief that fights the platform costs more every year. We will tell you when the one specified is the wrong tool.

Scope creeps through edge cases

Not through features. What happens to a part-shipped order, a cancelled subscription, a trade customer over their limit. Worth pinning down early.

When something is very expensive

Some effects cost ten times what they look like they should. We will tell you the price rather than absorb it or drop it silently.

When accessibility is at risk

Contrast below AA, or an interaction that cannot be used by keyboard. We will say so, and propose an alternative that keeps the intent.

Questions

What agencies ask about ecommerce builds.

Can you quote before we go back to the client?
Yes, and we would rather do that than have you guess. Send us the brief and we will give you a range quickly, flagging what would move it. Where the requirement is genuinely unclear we will say what needs establishing first.
Which platform would you use?
Usually WooCommerce for this kind of work, because it is open enough to build unusual rules into. PrestaShop where multi-language and multi-currency selling is central. We would not force a platform that fights the brief.
Do you handle the payment side?
Yes, integrating whichever provider the client uses. Card details never touch the site — that stays with the provider — which is also what keeps the compliance burden where it belongs.
Can you take over a half-built shop?
Often, though it starts with a review rather than a quote. Inherited ecommerce is the one place where a confident fixed price before anybody has read the code should make you nervous.
Next step

Send us the brief you are not sure about.

We will tell you whether it is a standard build or a development project, roughly what it would cost, and what to pin down with the client before you quote.