Record the current path
Prepare demand, stock, order release, work, handoff, return, and report fields. Include issue cases, not only a clean order.
Decision review for D2C operations
Demand-to-Fulfilment Fit Review
Start with where customers order, where stock sits, and where the order path breaks. Then decide whether to improve the current setup, change a provider, or study another inventory node.
Direct answer: The public worksheet helps a reader prepare demand, stock, order, return, and operating facts, mark unknowns, and discuss a next evidence gate. It does not promise a warehouse, city, postcode, delivery speed, capacity, price, integration, or outcome.
The decision
Do not start with a warehouse answer
A new stock point can shorten some routes. It can also split stock and add refill work. That creates another place where records can drift. A provider change may fix one weak handoff. It may also add a new tool, contract, or training burden. Do not ask where to open first. Ask which part of the current order path needs to change. Then ask which facts support that change.
This review keeps demand geography separate from company headquarters. It looks at where paid orders come from and which items buyers choose. It also checks where stock starts and which promise the brand is trying to keep. A city enters the decision only when the order facts and work case point there.
Intake checklist
Bring the facts that shape the operating choice
Use recent, comparable records where possible. Mark unknown fields instead of filling gaps with a guess. Remove names, phone numbers, addresses, and other personal buyer data from any sample shared for the review.
| Field | What to prepare | Why it matters |
|---|---|---|
| Demand geography | Paid orders by useful postcode, city, state, item, channel, and period. | Shows where repeat demand exists and where a route may be too long. |
| Current inventory origin | Each place where sellable stock starts, plus the items held there. | Connects demand to the real stock path. |
| Order volume and peaks | Normal pattern, campaign peaks, seasonality, and order mix. | Tests whether a setup works beyond an average day. |
| SKU and goods profile | Dimensions, weight, fragility, shelf rules, pack needs, and handling limits. | Stops a broad service label from hiding a goods mismatch. |
| Delivery promise and order release | Buyer promise, hold rules, cut-off logic, and the event that releases work. | Separates warehouse time from payment, review, and carrier dependencies. |
| Returns and RTO pattern | Reason codes, event trail, condition on return, and common exception paths. | Shows which failures belong to fulfilment and which do not. |
| Current operating model or provider | Who owns receiving, storage, order work, packing, handoff, returns, and reports. | Finds gaps, overlap, and unclear responsibility. |
| Channels and data flow | Order sources, stock source, files or tools used, and manual steps. | Finds where late, missing, or changed data can stop work. |
| Observed operating problem | Specific events, affected orders, time window, and available evidence. | Turns a broad complaint into a testable problem. |
| Timeline and constraints | Decision date, budget boundary, contract limits, team capacity, and non-negotiables. | Keeps the next step practical and bounded. |
Worksheet method
Prepare facts for the next discussion
Mark what is known
Separate supplied facts from guesses. Mark missing fields and questions that still need an owner.
Discuss the next gate
Use the prepared facts to discuss what needs more evidence. The worksheet does not choose the change or define a pilot.
Possible outcomes
The right answer may be less change, not more
The worksheet does not choose one result. These are options to discuss after the facts and unknowns are prepared. A later decision may keep the present model, repair one handoff, review provider scope, study stock placement, or collect more evidence.
- Keep the current model when the operating case is sound and the problem sits elsewhere.
- Improve the current setup when ownership, data, stock rules, or exception work can be repaired.
- Review a provider change when a required capability is absent or repeatedly fails a written test.
- Evaluate another inventory node when repeat demand and stock economics support a location study.
- Collect more evidence when the current records cannot separate cause from symptom.
Fit and non-fit
Who should use the review
The review fits a D2C team with a live work question. Routes may be too long, stock may be out of balance, or provider scope may be unclear. The team may have weak handoffs, repeat returns, a channel change, or new demand. It should bring real records and mark unknowns.
It is not a fit for a team seeking a blanket price or promised service map. It cannot give a location answer without order facts. It also does not replace legal, tax, product-safety, carrier, or contract advice. Those owners must confirm their part of any plan.
Evidence boundary
What the review can and cannot confirm
The worksheet can help prepare current-flow facts and mark missing fields. A discussion can identify questions and a possible next evidence gate. It does not compare providers, choose a change, or define a pilot. A live site, accepted goods, data link, capacity, or price needs current written proof. The same rule applies to a delivery promise, work schedule, or service level. The proof must cover the proposed scope.
A diagram or view does not prove that a node is live. A shorter route does not prove a delivery result. A named tool does not prove that the exact order and stock flow works. Unknown facts stay unknown until the owner gives dated proof.
Related tools
Prepare before the review
North India example
See one local order-data audit. Its local findings and context do not transfer to another market.
Review service scope
See the receiving, stock, order, packing, handoff, return, and reporting questions that need written answers.
Compare providers
Use one evidence method for every provider rather than relying on a sales label.
Frequently asked questions
Frequently asked questions
Does the review recommend another warehouse by default?
No. It starts with your demand and current setup. The result may be to keep the current model, improve it, review a provider change, evaluate another inventory node, or collect more evidence.
What should we prepare?
Prepare recent order data, current stock locations, item details, buyer promises, returns data, channel flows, provider scope, known problems, timeline, and constraints. Mask personal customer data before sharing any sample.
Does a review confirm service availability?
No. The worksheet helps prepare facts and mark unknowns. Any warehouse, place, workflow, price, capacity, service level, or pilot scope still needs current written confirmation.
Bring the operating question, not a preferred answer
Prepare the worksheet and mask personal buyer data. The discussion can test whether the available facts support a bounded next step.
Discuss a Demand-to-Fulfilment Fit Review