Channels disagree
Customers see one availability message online and hear another in store. Teams use different definitions of stock, order status or return eligibility.
03 / Retail Transformation
Make the customer promise work across the whole operation.
Connect store, commerce, fulfilment and service decisions around the journeys customers actually experience. Expose the operational work behind the next retail capability.
Independent advice. A clear scope. Decisions your team can act on.
CustomerBuy
OperationsFulfil
ServiceReturn
01
Inventory promiseWhich availability can the customer trust?
02
Exception ownershipWho acts when the order leaves the happy path?
03
Consistent resolutionCan a store, service rep and warehouse agree?
Illustrative decision framework
Retail & DTC focusIndependent of platform vendorsAdvisory shaped around your decision
Can our operation consistently deliver what we promise?
An omnichannel feature changes responsibilities well beyond the screen. The difficult work often appears at the handoffs.
Exceptions depend on personal knowledge
Store and service teams know whom to call when an order breaks, but resolution depends on individual relationships and manual follow-up.
The feature is ready; the operation is not
A capability reaches launch with unresolved labour, training, reconciliation or ownership questions. The extra work lands on teams already at capacity.
Get close to the work.
Make the decision clearer.
We work with the people who own the outcome and the teams who will deliver it. Your constraints shape the recommendation.
- 01
Choose the customer promise
Agree which journey or capability matters most and how customers and operating teams should experience it.
- 02
Walk the complete journey
Review ordinary transactions and exceptions with the people who handle them. Trace where information, authority or capacity breaks down.
- 03
Agree the operating changes
Define responsibilities, required system changes and readiness criteria. Give sponsors a clear view of what must be true before launch.
A recommendation you can put to work.
Translate the proposed experience into decisions about process, people, systems and operational accountability.
A customer-to-operation journey map
Follow a representative journey through commerce, stores, fulfilment and service. Show the information, responsibilities and system handoffs needed at each step.
An exception ownership map
Identify foreseeable failures, the team authorised to resolve them and the escalation path when an issue crosses functional boundaries.
A capability readiness assessment
Evaluate inventory visibility, order orchestration, returns and service processes against the intended promise. Separate technology gaps from policy and operating gaps.
A practical rollout recommendation
Define a manageable starting scope, operating prerequisites and evidence required before expansion. Include the impact on store and support teams.
Put it to the test
Buy online, return in store
Illustrative scenario: a retailer wants customers to return online purchases at any store. The customer interaction looks simple, but the transaction crosses payment, promotion, stock disposition and financial reconciliation rules.
The questions worth answering
- Who decides the refund when promotions span several items?
- When does the returned item become available to sell again?
- Who resolves a refund accepted in store but rejected downstream?
The launch decision includes a supported exception process and clear ownership for the work that continues after the customer leaves.
Related case study
Read the case study Look beyond the commerce platform
A related case study on the relationship between replatforming and the operating model behind the customer experience.
A few practical questions.
Scope, ownership and the next step should be clear before an engagement begins.
Can we focus on one retail journey?
Yes. Returns, pickup, store fulfilment and service recovery are suitable starting points. A bounded journey often makes broader operating dependencies easier to understand.
Does this assume we need new systems?
No. Findings may point to better policies, ownership, training or use of existing capabilities. Any system recommendation should follow from a demonstrated operational requirement.
Who needs to participate?
Typically the people accountable for the journey across retail operations, commerce, supply chain, service, finance and technology. Participation is tailored to the chosen scope.
Let's talkBring the decision
Bring the decision
you need to make.
Tell us what is changing, what is at stake and where you need an independent perspective. We will discuss the right starting point and agree the scope before work begins.
Still framing the problem?
The free Retail Architecture Risk Score can help surface where systems, ownership or delivery capacity need a closer look.
Start with the Risk ScoreThe work rarely stops at one boundary.
Where we work
Independent advice for your regional team.
A pickup or returns promise must hold across stores, warehouses and service teams. We trace the full journey and clarify the operational changes needed before launch.
Remote collaboration, with workshop and meeting arrangements agreed during scoping.