A merchant asks for an account review. Before the team starts collecting every available report, take a moment to clarify the decision the meeting needs to support.
That decision might concern an existing item, an execution problem, a pack change, or a test. The brief may not tell you enough to know which. Treat your interpretation as a question to confirm, rather than a coded message whose meaning is already settled.
This one-page plan is my recommended way to organize the preparation. It is not a Walmart or Sam’s Club required format, and it cannot guarantee the outcome of a review.
Confirm the brief before committing the work
Record the meeting date, retailer, account, items or category in scope, requested outputs, and known decision deadline. Separate confirmed requirements from your team’s assumptions.
If the note says “space productivity,” ask what measure, item scope, and decision the merchant wants to examine. It might involve an assortment change, but do not assume it means cutting a fixed percentage of items.
If the note mentions service, clarify the specific issue and the relevant scorecard. Avoid applying Walmart compliance programs or thresholds to a Sam’s Club discussion by default.
A concise clarification might be: “We understand the priority is the performance of these items and the actions needed before the next review. Are there particular measures, locations, or decisions you want us to address?”
Connect each question to evidence and an owner
Keep the list short enough to guide the work, without forcing every review into a prescribed number of questions.
| Decision question | Evidence needed | Scope to define | Owner and next action |
|---|---|---|---|
| What changed in the existing business? | Sales and units with relevant context | Items, channel, locations, periods | Analyst: prepare a comparable view |
| Is execution affecting the result? | Available inventory, service, or issue evidence | Exact metric and supplier flow | Operations: investigate the flagged items |
| What action should we take? | Options, assumptions, constraints, and costs | The decision actually in scope | Account lead: prepare a recommendation |
| What happens after the meeting? | Dependencies and implementation plan | Proposed versus agreed commitments | Named owner: record next steps |
Give each question one coordinating owner, while naming the specialists who contribute. Ownership here means responsibility for assembling and resolving the answer, not personal responsibility for every underlying data source.
Check what you can actually answer
For Walmart Scintilla, identify Basic or Charter access before choosing the reports. Basic work should be planned around the supplier’s available own-item operational reporting; do not assign shopper, competitor, or category analysis as though every account has the same access. Check the specific module, fields, and permissions.
Keep Sam’s Club reporting separate. A Sam’s question does not become a Walmart Scintilla question because the supplier serves both retailers. Use the current Sam’s reporting and guidance appropriate to the account; the separate Sam’s learning materials are in Supplier Academy.
If the evidence is unavailable, mark the limitation. The next step may be a narrower question, an authorized source, or a request to confirm the missing information. Do not invent category benchmarks to fill the page.
Ask for the right strength of conclusion
A sales change describes what happened. An item-level breakdown can locate where the change is concentrated. Neither automatically proves the cause.
If the decision depends on incremental impact, define the comparison or study needed to support that claim. A before-and-after result or basket association alone should not become a promise that an assortment change will grow the category.
Keep observations, possible explanations, and recommendations visibly separate in the working plan.
Use the plan through the meeting and beyond
Schedule checks around the actual deadline and unresolved dependencies. Ask the merchant what pre-read would be useful and when, instead of treating a generic 24- or 48-hour window as a retailer rule.
After the discussion, update the same page with decisions made, questions left open, actions, owners, and dates. Confirm commitments through the agreed account process.
The useful result is a team that knows what it is preparing, what it can support with evidence, and what it will do next.
Before assigning the analysis, use Retail Reason’s Scintilla Basic and Charter guide to check the access questions your team needs to resolve. The guide has its own verification date; confirm the actual account and current retailer documentation.
Continue with a flexible review structure and reconciling the numbers behind it. Explore Retail Reason Intelligence for operating guidance, or talk to Matt about your account-review work.