PUBLIC EVIDENCE
The public-evidence count is not a coverage limit. Every listed article carries its own last-verified date; the current verification index shows the latest date on each public article.
COVERAGE · SIX AREAS
Where the work actually lives.
Walmart and Sam’s Club supplier work and Walmart Marketplace selling span systems that don’t explain each other: compliance programs, payment routes, the item file, data products, and seller tools. Coverage is organized the way the work is, with dedicated areas for Sam’s Club and Walmart Marketplace.
THE COVERAGE MAP
Start with the operating area, then follow the evidence.
The coverage map separates supplier, data, club, and Marketplace contexts before an answer is formed.
Scroll sideways for scope and public evidence →
| № | Coverage area | Scope | Public evidence |
|---|---|---|---|
| C-01 | Walmart supplier operations | Supplier One and Retail Link; onboarding; EDI; item setup; orders and replenishment; payments and disputes; transportation; OTIF and SQEP compliance; reporting, forecasts, integrations, and merchant preparation. | 6 articles |
| C-02 | Scintilla and supplier reporting | Basic, Charter and Category Advisor; Channel Performance, Boards, Channel Insights, Report Builder, Shopper Behavior, Customer Perception, Insights Activation, supplier-facing metrics, dashboards, reports, in-stock and demand questions, APIs and data delivery. The tier is established before the answer. Retail Reason does not retrieve or analyze your dataset. | 2 articles |
| C-03 | Sam’s Club | Supplier onboarding, item data, MADRID, MAP, deductions, DSV, merchandising, packaging, OTIF and compliance. | 1 article |
| C-04 | Marketplace | Seller onboarding; listings and content; pricing and Buy Box; WFS and fulfillment; orders and returns; performance and appeals; payments, fees and payouts; growth and ads; analytics and reports; APIs, integrations and support escalation. | 2 articles |
| C-05 | Walmart Connect | Sponsored Products; brand and video formats; display; Brand Shop work; measurement; campaign and growth questions; advertising APIs; and the operating context that changes the recommendation. | Coverage details |
| C-06 | Technical workflows and APIs | Supported supplier, Marketplace, and advertising APIs; authentication; reports and feeds; integrations; rate limits; errors; and the operating workflow around technical implementation. | Coverage details |
NO PORTAL CONNECTION
No portal connection or account access: Retail Reason provides expertise about these systems but never connects to or retrieves data from them. It processes only what you choose to submit.
PUBLIC ARTICLES, BY COVERAGE AREA
See the maintained answer behind the scope.
C-01
Walmart supplier operations
What is Walmart deduction code 22, and how do you dispute it?Last verified July 2026Supplier One vs Retail Link: which Walmart portal owns what?Last verified September 2026How do Walmart weeks work? WMYYWW and the fiscal calendar, explainedLast verified August 2026How do you dispute a Walmart chargeback?Last verified July 2026Why did Walmart stop paying us?Last verified July 2026Why did Walmart stop ordering your item?Last verified July 2026
C-02
Scintilla and supplier reporting
C-03
Sam’s Club
C-04
Marketplace
ADVERTISING AND TECHNICAL WORK
The operating question does not stop at the portal.
Retail Reason also covers Walmart Connect and supported technical workflows. These examples show the reasoning path, not customer results or live-account analysis.
ILLUSTRATIVE PATH · WALMART CONNECT
ROAS fell. Should we reduce bids?
Not from ROAS alone. First separate the reporting window, attribution view, availability, Buy Box, conversion, targeting, placement, and budget conditions that can move the result.
Retail Reason can structure the checks and help evaluate the plan you provide. It does not inspect a live campaign, retrieve advertising data, or change a bid.
ILLUSTRATIVE PATH · API WORK
An API request started failing. Do we change the payload?
Not until the failure class is clear. Identify the endpoint, environment, status code, request identifier, authentication state, and current rate-limit or retry signals before rewriting a previously accepted payload.
Retail Reason can explain supported APIs and troubleshoot from the details you provide. It does not call retailer APIs, hold retailer credentials, or execute the fix.
SAM’S CLUB, IN ITS OWN OPERATING CONTEXT
A separate supplier relationship.
Sam’s Club has its own supplier agreement, vendor number, merchant teams, systems and scorecards. Retail Reason treats Sam’s Club as its own operating context, not as a Walmart channel filter. Dedicated coverage includes supplier onboarding, item data, MADRID, MAP, deductions, DSV, merchandising, packaging, OTIF and compliance. Sam’s Club coverage is currently less broad and has been tested against fewer representative questions than Walmart coverage; see limitations.
PUBLIC-ARTICLE SUMMARY · SAM’S CLUB DATA QUESTION
Can I pull Sam’s Club member data in Scintilla?
No. Scintilla is Walmart-banner data. Sam’s Club member data lives in a separate product, MADRID 2.0, with its own subscription and Sam’s-side vendor credentials in Retail Link. There is no Sam’s data in Scintilla to reveal with a channel or banner filter. Scorecard-level Sam’s sales and inventory available without MADRID live in Retail Link under the Sam’s vendor number.
If you need both, you need both entitlements. Plan for two access paths; one does not unlock the other.
MARKETPLACE GUIDANCE
A Marketplace example.
Marketplace answers carry the same visible verification date and confidence class. Here is one example from a public article:
PUBLIC-ARTICLE SUMMARY · MARKETPLACE QUESTION
Why doesn’t my Walmart Marketplace payout match my sales?
Because the settlement data lives at two different grains (order lines and itemized amount-type rows), and summing across the wrong one is the classic reconciliation trap. Walmart-funded promotions and withheld facilitator tax make correct charges look wrong, and the payout cycle’s timing makes a correct deposit look short.
Diagnostic path · THREE CHECKS
CHECK 1
Stay at the order-line grain and sum Payable to Partner from Sale once per line. Do not multiply summary values across itemized amount-type rows.
CHECK 2
Compare the deposit with its settlement cycle, not a sales-dashboard period. Post-shipment holds can push an order into a later payout.
CHECK 3
Subtract statement-level reserves, Marketplace Capital repayment, and lines whose hold had not cleared by the cycle boundary. The remainder should tie to the bank deposit.
The full tie-out, including withheld facilitator tax and promotion treatment, is in the public article.