Digital teams optimise the site while operations absorb inventory, lead-time and return variance.
E-commerce manager guide
Align e-commerce conversion, promise and execution
Build a journey that remains coherent from traffic through delivery, return and customer service.
For: E-commerce, acquisition, digital product, supply chain, customer service and IT managersWhat to clarify before discussing a solution
Which promise genuinely improves conversion without creating cancellations or operating rework?
The answer does not lie in an isolated feature: it is built by connecting rules, actors, data and evidence.An e-commerce roadmap connected to inventory, fulfilment, transport and service capabilities.
Four decisions to make before configuration
These decisions make the scope testable and prevent structural choices from being discovered during the project.
Connect digital and operating metrics
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
Define promise rules by inventory and area
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
Test payment failure, cancellation and substitution
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
Design returns as a complete journey
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
A readable end-to-end flow
Scope is not a list of modules. It is a chain of events, ownership and decisions.
1Acquisition and intent
2Availability and promise
3Conversion and payment
4Fulfilment and delivery
5Returns and retention
In the first scoping
- One representative flow and its useful variants
- Authoritative events and minimum data
- Roles, decisions and escalation times
- Acceptance criteria and baseline measurement
To sequence in waves
- Additional sites, activities or populations
- Rare variants that do not condition the pilot
- Automations whose rule is not yet stable
- Advanced dashboards after source reliability
To decide explicitly
- Connect digital and operating metrics
- Define promise rules by inventory and area
- Test payment failure, cancellation and substitution
- Design returns as a complete journey
From direction to measured improvement
- 1Navigator
- 2Personalised review
- 3Scoping workshop
- 4Wave-based deployment
- 5KPI measurement
Each stage produces a decision or evidence reusable in the next. Deployment remains business-led and verifiable.
Measure to decide, not to fill a dashboard
Every KPI needs a definition, a source, a cadence and an associated decision.
KPIFormulaSourceDecision
Conversion rateTransactions or orders ÷ visits or opportunitiesChannels, opportunities, baskets and ordersTarget breaks in the buying journey
Order cycle timeAvailability time − validation timeOrder, allocation, picking and shippingIdentify the link slowing the promise
Stockout rateUnfulfilled demand ÷ total demandDemand, availability and allocationsReview allocation, thresholds and replenishment
Return rateReturned units ÷ delivered unitsOrders, returns, reasons and qualityReduce avoidable causes by product and channel
06 · Business scenario
Conversion measured through delivered service
- Situation
- Conversion improves while cancellations and service contacts increase.
- Approach
- The pilot connects web, order, availability, fulfilment, delivery and return events in one view.
- Target outcome
- Digital optimisation incorporates its effect on promise and operating cost.
Useful answers before the first discussion
01Where should we start in practical terms?
Choose a representative scope spanning “Acquisition and intent” and “Availability and promise”, then document one normal case and one frequent exception. The first flow should be important enough to matter but contained enough to observe end to end.
02Do all existing systems need replacing?
No. Scoping starts with decisions, authoritative events and ownership. It then determines what should be retained, integrated, replaced or simply better governed, wave by wave.
03What data should be prepared before a workshop?
Prepare a few real cases, the volumes shaping the operation, the main variance reasons and the sources used to measure Conversion rate. The quality of examples matters more than the quantity of documents.
04How should the right pilot scope be chosen?
Choose a scope with an available owner, accessible data, a meaningful exception and a measurable outcome. Avoid both an overly simple case that proves nothing and an overly broad scope that dilutes learning.
05How can scope changes during the project be limited?
Make assumptions, interfaces, variants, exceptions and acceptance criteria explicit. Every new request can then be classified: essential to the wave, suitable for a later wave, or outside the objective. Discussion focuses on impact rather than intuition.
Next step
Turn this guide into a personalised review
Complete Navigator to position your context, then use the review as the starting point for a scoping workshop.
- 1Navigator
- 2Personalised review
- 3Scoping workshop
- 4Wave-based deployment
- 5KPI measurement
Complementary guides
Guides by suite
EMS Logistics suite
Transform transport & logistics
Connect order, warehouse, transport, delivery and invoicing around the same events and responsibilities.
- Service promise
- Warehouse execution
- Transport plan
Guides by suite
EMS Industry suite
Connect planning to the shop floor
Build decision continuity across demand, materials, capacity, execution, quality, maintenance and cost.
- Demand and schedule
- Materials and capacity
- Execution and WIP
Guides by suite
EMS Commerce suite
Unify omnichannel commerce
Connect catalogue, availability, order, payment, fulfilment, delivery, return and customer relationship.
- Catalogue and pricing
- Available-to-promise inventory
- Order and allocation