What You Should Know About Walmart’s New RFID Policies

Walmart’s RFID initiative is growing. Are you ready for it?

Walmart is requiring vendors in the electronics and home departments to include an RFID inlay on their items. We’ve prepared some essential information to assist you in your preparation.

Which departments will benefit from UHF RFID?

The following departments are the most recent to require RFID technology:

  • Entertainment departments
  • Home departments
  • Tires and batteries (Hardlines departments)

In these categories, Walmart wants all participating national, proprietary, supplier, and private brands to adhere to the mandate.

Specifications for RFID

Walmart requires its suppliers to use a Gen 2 UF RFID tag with a frequency of 902-928 megahertz to tag their products. The dimensions of your tags will vary based on the products you sell. Visit Auburn University’s lists to learn more:

  • Specifications for household products
  • Specifications for electronics
  • Specifications for the toy
  • Specifications for sporting goods

Please visit our RFID products which receive ARC certification from Auburn University’s RFID Lab.

What is the Best Way to Encode the Tags?

Suppliers must use GS1’s Electronic Product Code (EPC) standards to encode the tags. Your product’s UPC barcode is combined with a unique serial number to create an EPC. This is a 12-digit barcode that identifies your company, product, and kind of product.

A standardized label language was created by GS1, which means that an RFID label may be read anywhere, by any company. This allows large shops to receive your products in a more seamless manner and get them out on the floor sooner.

Altis is ready to assist you in meeting Walmart’s new standards as seasoned RFID system integrator. We can either encode your tags for you or help you discover the proper equipment to do it yourself. To get started, call us at +90-850-885 0950 or fill out the form here.

Important Deadlines

Walmart’s implementation schedule is rapidly approaching. These are the important dates to keep in mind.

THE DEADLINE TO SUBMIT RFID SAMPLES TO AUBURN UNIVERSITY IS JUNE 3RD

By June 3, send at least five RFID label samples to the Auburn University. Your product should not be included with your samples.

AUGUST 17: DELIVERY TO THE DISTRIBUTION CENTER IS REQUIRED (MABD)

By August 17, all RFID-tagged products must be delivered to the appropriate distribution center or facility. This suggests that the dates of August 13 to 17 are permissible.

SEPTEMBER 2: ALL PRODUCTS MUST BE TAGGED WHEN THEY ARRIVE AT THE STORE

All products heading into retailers must be marked starting September 2. Walmart will commence in-store testing after that, followed by rollout and implementation.

Walmart'ın Yeni RFID Politikaları Hakkında Bilmeniz Gerekenler

Additional Information About wmrfid

Visit Walmart’s Supplier Academy Page and download the RFID Playbook for additional information on Walmart’s new RFID mandate.

Steps to Follow

Please contact us if you have any concerns or would want to discuss your RFID requirements. We’re here to assist you in achieving your goals.

Firmware Update for Impinj R700 IoT Device

With the Impinj R700 Firmware Update, you may improve your security and get new UI tools.

A firmware update for the Impinj R700 RAIN RFID reader now includes enhanced security features and additional developer-friendly tools. Impinj R700 readers can now be used in RAIN solutions and RAIN data can be integrated into enterprise applications thanks to new capabilities in version 8.0 of the reader firmware.

The following are some of the new features:

  • REST API and web UI have been updated to provide new features.
  • Access to RAIN RFID data has been improved, and diagnostic logs are now available.
  • Security tools and settings have been beefed up.
  • Firmware version 8.0 is a significant advancement in Impinj’s software and hardware architecture, allowing Impinj partners to develop custom solutions that improve the performance and range of RAIN RFID applications in a variety of industries.

IoT interface allows for faster setup and development

IoT solution developers can use the Impinj IoT interface, which comprises a REST API and a web user interface, to simply configure RAIN RFID readers and connect data to enterprise applications. Users can customize how RAIN data is presented and supplied to external applications, as well as manage some RFID radio functionalities using web services or common protocols like MQTT for cloud-based applications. Customers with numerous locations will benefit from these cloud possibilities.

Version 8.0 offers enhancements that make certain functions more user-friendly for developers, such as:

  • Additional options for customizing the reader network, operating region, outputs, antenna hub, and power settings have been added to the online UI.
Warehouse RFID
  • Improvements to the device interface, host configuration, and default file transfer settings, all of which increase usability and security.
  • The Impinj R700 reader’s general-purpose outputs can be controlled via the API (GPO)

Impinj provides complete developer tools, documentation, and examples to assist IoT developers in constructing Impinj R700-based RAIN RFID solutions. The Impinj Developer Portal has been updated with new documentation and programming examples. The Impinj R700 RAIN RFID reader may be configured and deployed for popular inventory use cases including smart shelves, portals, and conveyors using these resources.

Access to data and diagnostics has been improved

Improve system tuning and uptime by having easy access to reader diagnostics files for performance analysis and troubleshooting. The following are some of the new features in version 8.0:

  • Webhooks enable event-driven HTTP POST data publishing that can be configured by the REST API or the web UI, with communication status indication via the web UI.
  • The API provides access to diagnostic data as well as log file storage in folders.

Enterprise security tools and settings have been improved

Impinj has improved the security capabilities of the R700 reader in response to increased system security demands. The following security enhancements have been implemented to firmware version 8.0:

  • A new Certificate Manager has been added to the reader API, with support for loading SSL certificates, requesting certificate signings, and auto-updating certificates. The X.509 international cryptography standard is followed by the Certificate Manager.
  • Update to Linux kernel 5.10.49 Long Term Support, which includes security-optimized default settings and the most up-to-date security features.

Firmware upgrades for the Impinj R700 RAIN RFID reader are now available for download.

Contact us to learn more about how an Impinj R700 RAIN RFID reader and its associated developer tools will help you expand your solutions. If you want, you can check other Impinj RFID readers such as Impinj R420 or Impinj R220.

Confidex Survivor B

As part of the product lifecycle management of its products that continue to be produced, Confidex is putting the Survivor B product in End of Life (stopping production and after-sales support).

Production and sales of standard Survivor labels will continue. The Standard Survivor product is currently recommended as a replacement product for projects using Survivor B.

In addition, the Confidex Viking product family offers alternative BLE solutions for applications requiring extended reading distances of up to 200 meters. You can also consider alternatives in this product group instead of Survivor B.

End of Life Statement: Confidex Survivor B™ Altis

Program

Since the End of Life transition is put into use immediately, the products remaining in Confidex ‘s stocks will be sold and will not be produced afterwards. Survivor B’s current stock will be sold on a first come, first served basis, without further production.

If you have any further questions, please contact the Altis sales team.

As Altis , we have stopped the sale of this product with immediate effect, since it is in EOL status and its continuation cannot be ensured.