The storefront is where it starts, not where it ends
Websites, ecommerce and D2C platforms, built with the part most people leave out. Inventory truth across channels, order flow into finance, and the returns reconciliation nobody scopes until the margin has gone.

Adding a channel adds a version of the truth
A storefront can be launched in weeks, and that is where most of the market stops. We build them too. The difference is what we do about everything downstream, which is where the eighteen month problems live.
The storefront reserves stock at checkout. The marketplace panel holds its own buffer and updates on its own schedule. The warehouse knows what has been picked but not what has been promised. The store knows what is on the shelf and tells nobody. None of them is wrong. They are answering different questions, and no system was ever given the job of deciding.
The damage lands twice. At the front, in oversells and cancellations that cost a customer rather than a sale. At the back, in returns reconciliation, where a return not matched to its original order is stock you have paid for twice and can no longer sell at full price.
Quick commerce made this sharper. Replenishment windows that used to be weekly are now measured in hours, running against planning logic built on the older assumption. A model that was merely inaccurate becomes expensive.
What the work covers
Website and storefront build
Design and build for the customer-facing side, from a marketing site through to a full transactional storefront. Built so the catalogue, customer records and order data behind it are usable by everything downstream rather than trapped in the front end.
Platform selection and replatforming
Which commerce platform fits your channel mix, order volumes and fulfilment model. Scored against your requirements, with the scoring handed over. Replatforming plans that account for catalogue, customer accounts and SEO continuity.
Inventory and order management
Deciding which system owns the stock number and what happens when two disagree. This is a governance decision before it is a technical one, and getting it the wrong way round is why most integrations synchronise the disagreement faster.
Channel and marketplace integration
Marketplace panels, quick commerce partners and retail customers, each with its own API behaviour and its own idea of a business day. Built with the error handling and reconciliation any other interface would get.
Order to cash into finance
Orders, payments, refunds and settlements landing in the finance system in a form that reconciles. Usually the least glamorous part of the project and the one that decides whether anyone trusts the numbers.
Returns and margin recovery
Matching returns to original orders, routing them to the right disposition, and reporting the true landed margin per channel rather than the gross number the storefront shows.
Customer data and lifecycle
A single customer record across store, web and marketplace, so lifecycle reporting is not counting the same person three times and engagement tooling is working from something real.
What you end up holding
Named artefacts, handed over. Not a slide deck summarising them.
- Channel and system map showing where each version of stock truth currently lives
- Inventory ownership model with conflict resolution rules
- Scored platform comparison where a selection or replatform is in scope
- Interface specifications with error handling and reconciliation design
- Returns matching logic and true margin reporting by channel
- Cutover plan and post go-live reconciliation reports
When to call us
Any one of these is enough. You do not need a defined project first.
- The website, the marketplace, the warehouse and the store each hold a different number for the same product.
- Oversells and cancellations are frequent enough that someone monitors them manually.
- Returns are reconciled at quarter end, if at all, and nobody can state true margin by channel.
- You are adding quick commerce and the replenishment planning was built for weekly cycles.
- Your commerce platform was chosen for the storefront and is now the accidental system of record for stock.
An assessment, not a proposal
Two to four weeks at a fixed price, delivered as a decision document. You own the output whether or not you carry on with us.
Start with an assessmentWe are an independent consulting firm. Software vendors do not pay us, so our recommendations come with the scoring behind them.