Checkpoint 1
Fit and boundary
Confirm the workflow, plan capacity, decision owners, accepted fields, excluded data, retention, and written acceptance checks.
Written scopeImplementation
Four checkpoints from fit to a dependable operating rhythm.
Published plans start without a software migration. We still treat definitions, ownership, safe input, module mapping, and acceptance as real implementation work.
Checkpoint 2
Field mapping
Map a stable, buyer-normalized inventory export to the published data profile. Resolve definitions before processing a live cycle.
Approved field mapCheckpoint 3
Dry run
Use a limited, buyer-reviewed sample to test rejects, rule explanations, output structure, and handoff responsibilities.
Accepted dry runCheckpoint 4
Operating cadence
Deliver the inventory exception workbook on the plan cadence, review exceptions, record corrections, and improve the mapping without changing scope silently.
Scheduled deliveryResponsibility matrix
No vague handoffs.
These roles may be held by the same person in a smaller team, but the decisions stay explicit.
Inventory planner
Defines the review rules and makes every purchasing decision.
ERP export owner
Produces the frozen, normalized quantity snapshot.
Operations lead
Reviews recurring data and handoff problems.
Acceptance criteria
Done means reviewable, not merely delivered.
- Every exception shows the buyer-authored rule and supplied inputs.
- Data-quality warnings remain separate from planning exceptions.
- Sparse-history items are not given false precision.
- No forecast, reorder, transfer, valuation, or purchasing action is made.
A useful first conversation
Bring the current export and the person who owns the definitions.
Describe it in general terms. We will tell you which plan fits, what we would need, and where we would draw the line.