The Compliance Checklist Most Suppliers Wish They Had Six Months Ago

Determine exactly which specs, tags, and processes your product categories require before spending a dollar on hardware.

• Identify all your Walmart departments and product categories

  Different categories may require different tag specs. Map every SKU to its Walmart department.
• Look up your Inlay Spec code in Walmart's RFID Playbook

  Walmart publishes a playbook with spec codes (W5, W6, C2, F, etc.) for each category. This is your source of truth.
• Check if you're on a legacy spec (W1–W4) that requires migration

  Previously compliant suppliers may need to re-certify under updated specs. The August 1, 2025 migration deadline has passed — if you haven’t migrated from W1–W4, you are out of compliance now.
• Document your GS1 Company Prefix and GTIN structure

  SGTIN-96 encoding requires a valid GS1 Company Prefix. If you don't have one, apply at gs1us.org.
• Assess current packaging for tag placement feasibility

  Metal, liquids, and certain package shapes interfere with UHF signals. Identify problem products early.

Choose the right inlay, convert it to a label or hangtag, and source from ARC-approved manufacturers.

• Source RFID inlays from an ARC-approved manufacturer

  Auburn University maintains the list of certified inlay manufacturers. Non-ARC inlays will fail certification.
• Match inlay type to your spec code and product characteristics

  Inlay performance varies by spec. A tag certified for apparel (W-series) won't work for hardlines (different spec).
• Choose tag form factor: smart label, hangtag, sticker, or embedded

  Consider your application method, product type, and consumer experience.
• Request samples from your tag converter with pre-encoding

  Test before committing to a production run. Verify both print quality and RF performance on your actual products.
• Budget for tag costs at volume: $0.08–$0.15 per tag at scale

  Specialty tags for metal-mount or liquid-adjacent products can run $0.30–$0.50+. Plan accordingly.

Get the data structure right. Encoding errors are the #2 cause of ARC rejection after wrong-spec inlays.

• Set up SGTIN-96 encoding with your GS1 GTIN + unique serial

  Each tag must combine the product's GTIN with a unique serial number. No two tags should have the same EPC.
• Implement serial number uniqueness management

  Duplicate serialization is a compliance violation. Your system must guarantee uniqueness across all production runs.
• Configure EPC memory permalock after encoding

  Walmart requires EPC memory to be locked. Tags that aren't permalocked will fail Auburn testing.
• Validate encoding with a reference reader before production

  Spot-check that your EPC data matches the expected SGTIN-96 format. Use GS1's EPC Tag Data Standard as reference.
• Print human-readable data on the tag: UPC, EPC logo, description

  The physical tag must show three things: barcode/UPC number, the EPC logo, and a text item description.

Where the tag goes on the product determines whether it reads reliably in-store. This is physics, not preference.

• Review Auburn's Tag Placement Guide for your packaging type

  Placement varies by product: belly bands, backer cards, polybags, heat shrink, and rigid packaging each have specific rules.
• Avoid tag placement near metal surfaces or liquids

  UHF RFID signals are absorbed by liquids and reflected by metal. Maintain minimum clearance from both.
• Never place RFID tags at the bottom of polybags

  Walmart specifically calls this out. Tags at bag bottoms get obscured and read poorly on shelves.
• Test read rates with tags applied to actual product samples

  Bench testing on flat surfaces doesn't reflect real-world performance. Test on your actual packaged product.
• Document your placement standard for production line workers

  Create visual guides showing exact tag position for each product type. Inconsistent placement kills read rates.

The step most suppliers underestimate. Your RFID data has to flow from encoders through your systems and into Walmart's.

• Select RFID middleware that supports SGTIN-96 and your ERP

  Middleware translates raw tag reads into business events. It must speak both RFID protocol and your WMS/ERP language.
• Map EPC data to your existing SKU and inventory systems

  Each serialized EPC must resolve back to a known SKU in your system. Build this mapping before go-live.
• Set up ASN (Advanced Shipping Notice) integration with RFID data

  Walmart's systems expect RFID-enriched ASNs. Your EDI 856 must include serialized SGTIN data.
• Configure exception handling for encoding failures on the line

  What happens when a tag doesn't encode? Dead tags need to be caught, logged, and replaced automatically.
• Build verification stations into your pack-out workflow

  A final read-verify step before carton close catches bad tags before they reach Walmart's dock. This is your last line of defense.

The gate that determines whether you can ship. Submit early—rejection means re-testing, and the queue isn't short.

• Compile your RFID-tagged item list (all SKUs with tag details)

  Auburn requires a complete list of every item that will carry an RFID tag, with encoding and placement details.
• Prepare physical samples: fully encoded, correctly placed, production-representative

  Samples must reflect actual production output, not hand-assembled prototypes. Auburn tests real-world performance.
• Complete the Auburn RFID Lab ARC Program submission form

  Double-check that form details match your physical samples exactly. Mismatches between form and product are a common rejection reason.
• Ship samples to Auburn and plan for 10+ business day review

  The lab runs standardized performance tests. Turnaround is approximately 10 business days, longer during peak submission periods.
• If rejected: diagnose, fix, and resubmit (common reasons below)

  Top rejection causes: unpermalocked tags, incorrect spec for category, form/sample mismatch, poor read performance, wrong printing.

Certification is not the finish line. Ongoing compliance is what keeps you off the chargeback list.

• Run a pilot production batch and verify end-to-end read rates

  Tag at production scale, verify at your dock, and confirm readability at a test DC if possible.
• Train production line staff on tag application standards

  Operator error (wrong placement, wrinkled tags, missed items) is the leading cause of post-certification compliance failures.
• Establish quality sampling: check X tags per Y cartons

  Define a sampling rate that catches encoding and placement errors before shipment. 100% verification is ideal; sampling is the minimum.
• Monitor Walmart supplier scorecard for RFID compliance metrics

  Walmart is integrating RFID compliance into supplier scoring. Poor performance affects your overall standing, not just RFID.
• Track Walmart's spec update announcements for your categories

  Specs evolve. What's compliant today may need updating. Subscribe to Walmart's supplier communications for changes.
• Plan for other retailers: Target, Nordstrom, and others are following

  Walmart's mandate is accelerating industry-wide RFID adoption. Invest in scalable processes now.