Walmart Item 360 Is Now Supplier One. The Fields Still Reject.

Cinderhaven Provisions submitted four new SKUs to Walmart six weeks before reset day. Three cleared in a day. The fourth came back rejected: the brand name on the GTIN did not match the GS1 registration behind it, a hold with no appeal path. That rejection was the cheap news. The expensive submission was the second SKU, which passed: its case-pack field said 12 where the physical case held 6, so every purchase order written against it expects twice what arrives, and that field, accepted without comment, is how a $27,000-a-year shortage-deduction stream gets born.

Cinderhaven is a fictional company, its item file a synthetic dataset, and the two ways an item setup goes wrong, loudly now or quietly forever, are exactly how Walmart's portal behaves. Including the part where the loud way is the lucky one.

Item 360 is a redirect now

The tool most suppliers still search for no longer exists for them. Since September 18, 2024, Item 360 redirects US suppliers to Walmart Supplier One, which absorbed item setup, maintenance, and catalog management into its Items and Inventory tab; Canadian suppliers get a reduced version of it. Everyone at the trade show still says Item 360. The screens they mean live in Supplier One.

The workflow survived the rename intact: Setup Hub, add an item, pick the delivery path, enter the GTIN, then the required attributes: supplier ID, SKU, product name, dimensions, weight, packaging, and track the submission in Submissions Manager. A food item adds its category attributes on top. Ten minutes of typing when the data is ready, three months of chasing when it is not.

The name changed. The fields did not.

The portal rejects format, not fiction

What Supplier One checks, it checks hard. Walmart has required a GS1-licensed GTIN at every packaging level since 2019, each, inner, and case, and validates them against GS1. Walmart's product-identifier policy, published for its Marketplace sellers, spells out what that cross-reference rejects: an item registered to one brand but set up under another, an item registered by a company under a brand unrelated to it, and a product ID reused across separate items. None of those can be argued in the portal, only re-licensed.

What the portal cannot check is whether a well-formed value is true. A case pack of 12 formatted correctly passes. A height in clean decimal inches passes at the wrong number. The SupplyPike setup webinar, now hosted by SPS Commerce, makes the point: the errors that do not read as data errors at submission are the ones that turn into fines later.

A rejection is the portal doing you a favor. The expensive errors pass.

The accepted error bills you monthly

The two failure paths price differently:

| Error class | Portal catches it? | When the cost lands | What it looks like | |---|---|---|---| | Bad format: check digit, unlicensed GTIN, brand-prefix mismatch, missing attribute | Yes, at submission | Now: a resubmission cycle, a slipped reset | A held SKU, a delayed launch | | Wrong but well-formed: case pack, dimensions, weights, hierarchy links | No | Monthly, indefinitely | Deductions, SQEP defects, OTIF fines |

The second row is where Cinderhaven's ledger comes from. The case-pack field entered once at setup misprices every PO that touches the SKU, and shows up as the $27,000-a-year case-pack shortage family, the largest of the four families in the brand's invalid-deduction total. A case-cube figure four hundredths of a cubic foot off the physical carton produced a $4,200 fine on a single remittance, on a shipment that arrived on time and complete. And Walmart now prices the category by name: its Supplier Quality Excellence Program lists Item Setup Information as a Phase 1 compliance category, with defects billed at $200 per defect type plus a per-unit charge; the program's worked example, one pallet defect across two pallets at $4 a pallet, bills $208.

The rejection costs a week. The acceptance costs a fee schedule.

Verify the boring fields before the portal accepts them

The pre-submission pass is unglamorous and short. Check every GTIN against the GS1 registry, licensed, correct check digit, brand matching the prefix, before Walmart does it for you with a hold. Measure dimensions and weights from a physical case on a real scale, not the spec sheet the co-packer sent two revisions ago. Confirm the each, inner, and case values agree with each other and with the twelve product-master fields that generate most chargebacks, because the setup form is those fields, transcribed. And one Supplier One quirk from the training: for GDSN-synced items, leave the synced-item checkbox alone; the system pulls those configurations itself.

An hour of verification per SKU, against the second row of the table above. Item setup is the cheapest audit your product master will ever get, because it is the only one that runs before the errors start billing.

Send me the spreadsheet before you submit it

Next launch, send me the Supplier One item spreadsheet before it goes in, along with the co-packer spec sheets behind it. I will send it back field by field: what will reject, what will pass wrong, and which fee schedule each wrong field feeds. Send it before Walmart sees it. The portal checks your formats; someone should check your facts.