DIRECT ANSWER
For a Walmart U.S. supplier on Scintilla Charter, compare the exact Board card with Channel Insights on the same metric, dates, products, channels, and data freshness. Check card settings as well as page filters. Then use a matched Report Builder extract to isolate the remaining difference.
The Business Overview Board shows one sales total. Channel Insights shows another. Both screenshots say “last week,” and the merchant meeting is tomorrow. The fastest useful response is to document the comparison before deciding which number belongs in the deck.
This guide is for U.S. first-party Walmart suppliers using Scintilla Charter. It focuses on comparing sales in the Business Overview Board with Channel Insights. The investigation below is Retail Reason’s method for finding a difference. It does not assume that every Board card uses the same data or that Report Builder automatically resolves every mismatch.
For an optional first-five-minutes start, use the short side-by-side comparison to record the two views and the first difference to investigate. Fill in what you know and mark missing evidence as unknown. The detailed log below also captures the Report Builder comparison.
If you cannot obtain or open the report at all, start with the Scintilla download investigation. Return to this comparison when the report is available and the unresolved question concerns its sales figures.
Are you comparing the same question?
Write one sentence that defines the intended number: “Net Sales for these product IDs, across these service channels, for these calendar dates.” Then record the Board name, tab, card, metric label, and Channel Insights view that supposedly answer it.
A screenshot titled “sales” is insufficient. Dollars, units, percentage change, and sales per store answer different questions. A shopper measure on another tab is also a different comparison. Copy the displayed metric definition and calculation basis into your notes. The Scintilla Data Dictionary, which requires login, is the place to check the precise field and product context.
If the question is actually about plan access, resolve that with our Basic versus Charter guide before trying to recreate a view that the account cannot use.
Which settings should you compare side by side?
Use the following comparison fields before changing the report recipe.
| Comparison field | What to record |
|---|---|
| Metric | Exact label, dollars or units, total or rate, and comparison basis. |
| Time | Start and end dates, Walmart week codes, and complete period or week to date. |
| Products | Product IDs and counts, brand or hierarchy filters, and exclusions. |
| Channels | Each included sales or fulfillment channel, not only “online” or “all.” |
| Card settings | Any additional filter, breakdown, or calculation choice. |
| Freshness | Displayed refresh timestamp and your extraction time for each result. |
Walmart’s current Board page-filter documentation explains that Boards maintain independent filters and that selections reset on refresh, close, or sign-out. It also distinguishes sales channels from fulfillment channels. Access requires login. Recheck the visible selections after returning to a Board; the label remembered from yesterday is not today’s evidence.
Resolve dates explicitly. Walmart weeks run Saturday through Friday, while a calendar-week extract might use different boundaries. The Board’s custom range uses complete Walmart weeks. Our Walmart week reference and fiscal calendar tool help translate the dates for the review.
Compare product membership, not just the saved filter’s name. Two selections named “Brand A” can still need investigation if their included IDs differ. If account sharing or access settings are relevant, record the current notice and available controls. Confirm their behavior with the current help or support team; do not presume a fixed Item Share default explains the gap.
Could the card be fresher than the other report?
Read the timestamp on the specific card. Walmart’s Card Features & Settings guide explains that a card marked Mixed uses its oldest refresh time when its metrics update on different schedules. The guide also documents card settings and downloads of underlying numbers. Login is required.
Export both sides close together and retain their actual refresh stamps. The download time records when you retrieved a result; it does not prove the underlying data was updated then. If one side is stale, refresh the comparison after its data updates before treating the difference as a persistent defect.
How do you isolate the remaining difference?
Use Report Builder to produce an inspectable comparison with the same definition and scope. Walmart’s public Report Builder overview describes building, customizing, and scheduling reports. Select the dataset and fields that answer the stated question, and preserve the recipe with the extract.
Begin with one completed week and a small explicit product set. Compare additive sales totals at item and channel level. Then expand the scope once that comparison is understood. Watch the row grain: a file containing detail rows and subtotals must not count both. Rates and distinct counts also require their own aggregation rules; summing them is not a sales reconciliation.
What can an explained difference look like?
Fictional example. A Board shows $120,000 and Channel Insights shows $108,000 for the same completed week. All figures and findings here are invented, not customer results.
The reviewer confirms the same metric, products, and freshness. The channel checklist then reveals that one result includes Ship To Home and the other excludes it. A matching item-by-channel extract shows $12,000 in that channel. The difference is therefore fully explained in this example: $120,000 - $108,000 = $12,000.
The reviewer records both original scopes and agrees on the intended channel scope with the commercial owner. The deck uses the result that answers that question. This proves an arithmetic reconciliation under the example’s assumptions. It does not prove why sales changed or establish that channel selection explains another supplier’s mismatch.
What should you do if the totals still differ?
Download the detailed Scintilla sales reconciliation log. Keep one row per comparison and preserve the original Board and Channel Insights values. Enter the two matched-scope sales values separately, with a reference to the matched period, products, channels, metric, filters and refresh times. Define the remaining difference as matched-scope Board sales minus matched-scope Channel Insights sales. Keep the Report Builder refresh and extraction times with its comparison. Enter the arithmetic yourself; the CSV contains no formulas or Walmart data and runs no reports.
If a difference remains after matching the documented basis, send the Board/card names, Report Builder recipe or report identifier, affected period and products, metric definitions, timestamps, and a small reproducible comparison through Scintilla Support. Use the support channel for account-specific evidence.
For the merchant discussion, read Startup Success Lab’s line-review data guide. For help applying that work, SSL’s Scintilla Charter advisory connects analysis to decisions and a repeatable review. Retail Reason’s guidance can help structure the diagnosis from supplied context. The current guidance product does not independently open your Scintilla account or validate your live totals.
Verification notes
The Board filter and card documentation and Data Dictionary were checked September 13, 2026. They require login and displayed no publication or revision date. The public Report Builder source was also checked that day. This article makes no universal claim about current Item Share defaults and does not cover Marketplace sales or Sam’s Club reporting.