By Bernardo Campelo, Forbes Business Council E-Commerce Leader, Amazon SPN Certified provider, Amazon SP-API authorized partner, and Founder of PrepVia.
A pallet lands at our dock in Miami. The seller wants 60 percent of it in Amazon FBA and 40 percent in Walmart WFS. Same SKU, same cases, same supplier. To the untrained eye, that is one prep job with two shipping addresses.
It is not. It is two prep jobs that happen to share a pallet. Amazon and Walmart run incompatible identity systems, incompatible case rules, different date formats, different routing paperwork, and, as of this year, two different storage clocks. The most expensive assumption in multichannel fulfillment is that the FBA playbook transfers to Walmart with a different login. It does not, and Walmart enforces the differences at the receiving dock, where fixing them costs the most.
We covered the strategic picture of running one inventory pool across channels in the multichannel prep overview. This post is the technical companion for the Walmart front: exactly where WFS prep diverges from FBA prep, line by line, and what the 2026 fee schedule now charges you for getting the storage math wrong.
The 60-second version
Labels: Walmart WFS requires a scannable UPC-12 or GTIN-14 on every sellable unit and explicitly refuses FNSKU, EAN, and vendor SKU numbers as item identifiers. The FBA habit of covering the manufacturer barcode is exactly backwards at Walmart: the UPC must stay visible and scannable.
Case packs: WFS allows master cases up to 150 lb but recommends keeping them at 50 lb, wants a WFS receiving label printed from Seller Center on every case, and does not want the item-level barcode on the outside of the box.
Dates: Expiration dates go on the sellable unit of every perishable item in one of three full numeric formats, MM-DD-YYYY being the usual choice. A Julian code, a production date, or a lot number alone does not count.
Fees: As of 2026, WFS fulfillment starts at $3.45 for items of 1 lb or less, storage runs $0.75 per cubic foot per month from January through September, peak season adds a $1.50 surcharge for units stored over 30 days, and long-term storage has cost $2.25 per cubic foot per month past 365 days since August 1, 2024, with a second band effective June 30, 2026: $7.50 per cubic foot per month beyond 450 days.
The workflow: split the pallet by channel before any label touches a unit, run two labeling regimes, and create two separate inbounds. Never mix them.
The One-Sentence Difference
Amazon runs a private namespace. Walmart runs the public one.
When you send inventory to FBA as a reseller, Amazon assigns your listing an FNSKU, a barcode that exists only inside Amazon and ties every unit to your specific seller account. The prep job is to print that FNSKU and apply it over the manufacturer barcode so Amazon scanners read only Amazon identity. We have written extensively about that regime and its failure modes in our FBA labeling service documentation.
Walmart made the opposite choice. WFS identifies inventory by the barcode the product was born with: the 12-digit UPC or 14-digit GTIN registered to the item. There is no Walmart-private barcode for standard items. Walmart's label guidance is explicit that EAN, vendor SKU numbers, and FNSKU numbers are not acceptable item identifiers, as of the current 2026 guidance.
Every downstream difference in this post flows from that single design decision. One channel wants the manufacturer barcode erased from view. The other channel depends on it.
Labels: FNSKU vs GTIN/UPC, Side by Side
| Label rule | Amazon FBA | Walmart WFS |
|---|---|---|
| Unit identifier | FNSKU (Amazon-assigned, account-specific), unless the listing qualifies for the manufacturer barcode program | UPC-12 or GTIN-14, readable and scannable, on every sellable unit |
| Explicitly refused | Uncovered conflicting barcodes on the unit | FNSKU, EAN, and vendor SKU numbers as item identifiers |
| Manufacturer barcode | Cover it completely with the FNSKU label | Leave it visible; it IS the identifier |
| Variants | Each variant gets its own FNSKU | Each variant must carry a unique barcode; duplicates will not be received and can be returned at your expense |
| Barcode on the master case | Box gets the shipment label; FNSKU stays on units | Item barcode goes on sellable units only, never on the outside of the case |
There is a second-order effect worth naming. Because WFS reads the public barcode, label quality problems shift upstream: a supplier who prints low-contrast UPCs on dark packaging, or wraps the barcode around a curved edge, has shipped you a receiving problem. A prep center serving both channels should be scan-verifying the manufacturer barcode at receiving, not just the labels it prints itself.
Case Packs: Where the Scale Decides
Both networks limit what a human can safely lift, but the rules around the box diverge.
| Case rule | Amazon FBA | Walmart WFS |
|---|---|---|
| Max box or case weight | 50 lb standard (heavier only for single oversize units, with team-lift labeling) | 150 lb per case as of the August 2026 guide; Walmart recommends 50 lb and 31.5 x 23.25 x 16 inches for efficient receiving; a single unit over 50 lb needs team-lift labels |
| Case identifier | Amazon shipment box label (FBA box ID) | WFS receiving label with the shipment ID, downloaded from Seller Center |
| Item barcode on the case | Not required; box label carries identity | Explicitly no: item barcodes belong on sellable units only |
| Dimensions | Published box size caps for standard-size shipments | Recommended case size 31.5 x 23.25 x 16 inches; containers that miss the guide's requirements can be refused and returned |
| Contents | Box content information required per box | Single-SKU cases with consistent case quantity matching the GTIN-14 |
The WFS receiving label has a rough FBA equivalent in the FBA box ID label. Print one per case from Seller Center, place it left of center on the longest side, and Walmart scans the whole case in at receiving.
Weigh the case before it is sealed, not after. Walmart's 150 lb allowance is not a target. A 50 lb case is the one a receiving associate moves without slowing down, and 50 lb is also Amazon's hard box cap. Build every case to 50 lb and your floor never has to ask which lane the scale is serving.
Expiration Dates: Same Product, Different Grammar
Dated goods are where sellers get burned quietly, because nothing fails until receiving reads the package.
WFS wants the expiration or best-by date visible on the sellable unit in one of three numeric formats, per the August 2026 routing guide: MM-DD-YYYY, YY-MM-DD, or YYYY-MM-DD. A Julian code, a production date, or a lot number alone does not satisfy that. If you only know the month, Walmart's instruction is to use the first day of that month, which is the conservative direction: it shortens the shelf life on paper rather than extending it.
Amazon accepts MM-DD-YYYY, its preferred format, plus MM-YYYY, which it reads as the first day of the month, and a day with an abbreviated month such as 15-MAR-2026. At check-in it applies its own remaining-shelf-life minimums: enough life to consume the product in full plus 90 days, with a category table that runs from 90 days for snacks to 900 for personal care and beauty. The two channels also age inventory differently in their systems, which is a deeper subject we cover in the virtual expiration dates guide. Both channels set minimum remaining shelf life thresholds for receiving dated goods. Verify the current threshold for your category in each portal before you commit a short-dated lot. A lot that clears one channel's floor can miss the other's.
Routing and Scheduling: Two Sets of Paperwork
Walmart maintains a WFS Routing and Packaging Guide and refreshes it through the year; the edition current as of this writing is dated August 2026. It governs carton labeling, pallet build, inbound order creation in Seller Center, and delivery appointments. Treat it the way you treat Amazon's inbound requirements: a living document that quietly changes. Non-compliance does not surface as an error message at shipment creation. It surfaces as a rejection or a chargeback at the dock.
The structural differences a prep center plans around:
- Inbound creation: FBA generates a shipment plan that may split your inventory across fulfillment centers, with placement fee mechanics attached. WFS inbound orders are created in Seller Center against Walmart's network with its own routing logic.
- Carrier arrangements: Amazon's partnered carrier program is deeply integrated into FBA inbound, with its own 2026 rate mechanics we break down in the partnered carrier fee guide. On the Walmart side you choose between the Walmart Preferred Carrier Program, which offers discounted parcel, LTL and FTL rates, and your own carrier. Either way, LTL and FTL deliveries require an appointment booked per the routing guide.
- Labels per shipment: both channels issue inbound-specific labels for cases and pallets. They look similar. They are not interchangeable, and a WFS case label on an Amazon box is a mis-receive waiting to happen.
24 to 36h prep. 35-hour end-to-end guarantee or the prep is free. Net-30 terms. From 50 units to full truckloads.
The 2026 WFS Fee Schedule, Including the New Long-Term Storage Fee
Numbers below are the published WFS structure as of 2026. Confirm current rates in Seller Center before you model a SKU, because Walmart, like Amazon, revises mid-year.
| Fee | Rate as of 2026 | Notes |
|---|---|---|
| Fulfillment fee | Starts at $3.45 per unit for items of 1 lb or less | Scales with size tier and weight |
| Storage, Jan through Sep | $0.75 per cubic foot per month | Flat across the off-peak months |
| Storage, Oct through Dec (peak) | $0.75 base, plus $1.50 surcharge for units stored more than 30 days | Effectively $2.25 per cubic foot per month on aging units in Q4 |
| Long-term storage, 366 to 450 days | $2.25 per cubic foot per month | In force since August 1, 2024 |
| Long-term storage, beyond 450 days | $7.50 per cubic foot per month | New; effective June 30, 2026 |
The 450-day band is the headline change. WFS was the network where slow inventory sat cheaply until August 1, 2024, when the 365-day fee arrived, and June 30, 2026 closed the last gap with a punitive band beyond 450 days.
The peak-season line matters because the surcharge keys on how long the unit has been sitting, not when it arrived. Inventory inbounded in September crosses the 30-day mark during October, so anything still sitting when peak pricing starts pays triple storage for the rest of the quarter. The two-wave logic we preach for FBA applies to WFS unchanged.
One Pallet, Two Regimes: The Actual Workflow
Here is how a prep center that serves both channels processes the mixed pallet from the opening paragraph. The full FBA-side version of this flow, from pallet to check-in, is in the wholesale prep workflow guide; this is the two-channel variant.
- Receive and count once, against the PO. Photograph condition, scan-verify the manufacturer barcode on a sample of units. That scan check protects the Walmart lane specifically, because WFS will live and die by that barcode.
- Split by channel allocation before any label touches a unit. The split is a physical event: two staged lanes, two colored license plates, whatever your system uses. Relabeling costs double; splitting first costs nothing.
- FBA lane: print and apply FNSKUs over the manufacturer barcode, poly bag and suffocation-warning where required, pack to the Amazon shipment plan, capture box content information.
- WFS lane: verify the UPC or GTIN scans on every unit and leave it exposed, apply or verify a full numeric expiration date where the SKU is dated, build cases to the 50 lb recommendation, apply the WFS receiving label downloaded from Seller Center to every case.
- Create two inbounds in two portals. An Amazon shipment plan and a WFS inbound order, each generating its own case and pallet labels.
- Stage and ship separately. Two BOLs, two appointments, two tracking loops. A mixed pallet saves one freight line and risks two receivings.
The Classic Mistakes of Running the FBA Playbook at Walmart
Every one of these has arrived at our dock in the form of someone else's rework.
- FNSKU labels on WFS units. The single most common error, usually from redirecting FBA overstock. Walmart refuses FNSKU as an identifier; every unit needs the label removed or a GTIN label applied over it.
- Covering the UPC. Pure FBA reflex. On the Walmart lane the manufacturer barcode is the product identity; cover it and the unit is anonymous.
- Item barcodes stuck on the master case. Walmart wants the unit barcode on sellable units only. A case wearing a unit UPC can be scanned as one unit instead of a case.
- Amazon date grammar. Month-year shorthand such as 03-2026 and abbreviated months such as 15-MAR-2026 pass at Amazon but do not satisfy the WFS requirement of a full numeric date on the unit. A lot code alone passes at neither: Amazon requires an expiry or manufacturing date on every ingestible product.
- Reading 50 lb as the Walmart cap, or 150 lb as the Amazon one. Walmart's current guide allows cases up to 150 lb and treats 50 lb as a recommendation; Amazon's 50 lb box cap is hard. Learn one network's number and apply it to the other, and you either build cases Amazon refuses or cases Walmart receives slowly.
- Duplicate variant barcodes. Two colorways sharing one UPC is a listing shortcut that WFS receiving turns into returned inventory.
- Assuming Walmart storage is still clock-free. It stopped being clock-free on August 1, 2024, when the 365-day fee arrived, and June 30, 2026 added a harsher band past 450 days. Slow SKUs parked in WFS as a warehouse strategy age into both.
- One mixed pallet to save freight. Two networks, two appointments, two receivings. Mixing them creates the multichannel version of a shipment stuck in transit, except it is stuck at a dock.
Frequently Asked Questions
Can I use FNSKU labels for Walmart WFS?
No. Walmart WFS identifies inventory by the 12-digit UPC or 14-digit GTIN on each sellable unit, and its label guidance explicitly lists FNSKU, EAN, and vendor SKU numbers as unacceptable identifiers. If you redirect FBA-prepped inventory to WFS, the FNSKU labels must be removed or covered with a valid GTIN label before Walmart will receive the units.
How is WFS prep different from FBA prep?
The physical skills are the same but the regime is inverted. FBA prep applies an Amazon-private FNSKU over the manufacturer barcode, while WFS prep keeps the manufacturer UPC or GTIN visible and scannable because that is the identifier Walmart uses. On top of that, WFS has its own case rules, a 150 lb ceiling with 50 lb recommended, a Seller Center receiving label on every case, its own full-date expiration formats, and its own routing guide and inbound paperwork.
What are the WFS case pack requirements?
As of the August 2026 routing guide, master cases can weigh up to 150 lb, though Walmart recommends keeping them at 50 lb and about 31.5 x 23.25 x 16 inches for efficient receiving, and a case holding a single unit over 50 lb needs team-lift labels. Every case carries a WFS receiving label downloaded from Seller Center, and the item-level barcode stays off the outside of the box.
Does Walmart WFS charge long-term storage fees now?
Yes, and the clock is older than most sellers think. WFS has charged 2.25 dollars per cubic foot per month on inventory past 365 days since August 1, 2024, and on June 30, 2026 it added 7.50 dollars per cubic foot per month beyond 450 days. Any strategy that used Walmart as cheap long-term warehousing needs to be rebuilt around both bands.
Talk to PrepVia about Walmart plus Amazon prep →
24-36h prep · FBA and WFS lanes under one roof · Amazon SPN Certified · Miami, FL
Related Reading
- One Inventory Pool, Three Channels: the strategic overview this post goes deep on
- TikTok Shop FBT Prep in 2026: the third regime in the multichannel stack
- Q4 Peak Storage Fees: FBA vs 3PL: where staged inventory should sit in the fourth quarter
- FBA Labeling Service: the Amazon side of the labeling regime, done at scale
