Skip to main content

Decoded Commerce · live infrastructure

A storefront that fits how you actually sell.

Three tiers, priced on what you need rather than how many days it takes. Where a client wants more than a tier covers, that’s scoped and costed separately.

It’s built on the Medusa B2B starter: company accounts, spend limits, approval workflows, quote negotiation, order editing, and a full storefront and checkout, all on an open-source core. Real foundations, not a from-scratch build. That’s why it comes in well under the £8,000–£20,000 bespoke range you’ll be quoted elsewhere for the same thing.

A B2B trade storefront product listing page: decorated garments in a filtered grid with trade pricing shown per account, size and colour facets down the left, and a quote-request action alongside add to basket.decoded commerce · trade storefront

Trade pricing per account, quote requests alongside the basket, and a catalogue that reads from the same data as the warehouse.

What each tier is

Priced on functionality, not on days.

You pick the tier by what the business needs to do, not by how long I think it’ll take me. The scope is written down before anything starts.

Core

Single storefront

Product catalogue, customer accounts and logins, manual pricing tiers. No approval workflow. If nobody in your customers’ businesses needs to sign off an order, you don’t need to pay for the machinery that makes them.

Standard

The B2B trade portal shape

Adds company accounts with multi-user roles, per-employee spending limits, approval workflows, and quote negotiation. This is what most trade businesses in this sector actually mean when they say they want a trade portal.

Extended

More than one of everything

Multi-site storefronts, ERP integration (Khaos Control sync and similar), and bespoke checkout and pricing logic where the standard rules genuinely don’t describe how you price.

Product page with trade pricing and decoration optionsdecoded commerce · product page

Capability · DO-ART-103

Core to Extended, by capability.

Each tier adds what the one below doesn’t have.

Core to Extended, by capabilityEach tier adds what the one below doesn't haveDO-ART-103 · REV 01DECODED OPS · ISSUEDCoreCatalogue · customer accounts · manual pricingSINGLE STOREFRONTStandard+ company accounts · spend limits · approvals · quote negotiationTHE B2B TRADE PORTAL SHAPEExtended+ multi-site · ERP integration · bespoke checkout & pricingMORE THAN ONE OF EVERYTHINGTITLECORE TO EXTENDED, BY CAPABILITYDRAWING NO.DO-ART-103REV01

Off the tier list

When it’s a full rebuild, not a tier.

The worked example

A full migration off WooCommerce, a new storefront, and reintegration back into Khaos Control. That’s scoped and quoted like any other full custom build, not read off a tier list.

How it starts

With a Clarity Audit, the same as any rung 3 conversation. Everything on the market goes on the table first, priced, including the options I’d expect you to reject. And the decision stays yours.

How I decide what to build →

What each tier covers

Three tiers. Pick by what the business needs to do.

Which tier fits depends on your setup. What you sell, who buys it, and how they’re allowed to buy it. That gets settled in conversation before the build is quoted.
Decoded Commerce
TierScope
CoreSingle storefront, catalogue, accounts, manual pricing
Standard Most take thisCompany accounts, spend limits, approval workflows, quote negotiation
ExtendedMulti-site, ERP integration, bespoke checkout and pricing

A full rebuild, like a migration off an existing platform, isn’t on this table on purpose. That’s scoped separately.

What this costs depends on scope, so it’s quoted once I know what your setup needs rather than read off a list. I’m not VAT registered, so there’s no VAT to add. How I price everything else is on the pricing page.

Founding-client terms

No client has taken first delivery of the packaged product yet.

Real work has been scoped and quoted, but nobody has yet bought Decoded Commerce as a tiered product. Until that happens it sells at the rates above with the first six months of support waived, in exchange for accepting that some features arrive during the engagement and agreeing to be a named reference.

Stated plainly, because you’d find out anyway. And you should be able to price it in before you decide, not after.

Talk about your storefront.

An hour on what you sell and who buys it. If a tier fits, I’ll name it. If what you actually need is a migration, I’ll say that instead of selling you a tier.