Executive Summary: Digital shelf labels (ESLs) are 2D-barcode-driven price tags Walmart and other major retailers are deploying. Each ESL pulls live product data from the retailer's central system, exposing a data governance question most manufacturers have not yet faced: is your NetSuite product data clean enough to power what shows on that shelf?
Walk into a Walmart today and you may notice something different about the shelves. The paper price tags are gone in select stores, replaced by digital shelf labels (ESLs) that pull live product data from the retailer's central system. Each ESL is driven by a 2D barcode tied to your product.
Earlier in the Scan Forward Series
Part 1 covered the Sunrise 2027 initiative.
Part 2 took the NetSuite WMS decision.
Part 3 mapped the hardware stack.
This piece takes the data question those three articles surface but do not answer: is your product data clean enough to power what those tags will display?
The barcode on the box is the visible half of readiness. The data behind it, flowing from your ERP through GS1 to the retailer's shelf, is the half most manufacturers have not audited.
How Digital Price Tags Actually Work
Electronic shelf labels are connected to a retailer's central pricing and inventory management platform. When a retailer like Walmart links their ESL system to the GS1 Digital Link on your product's 2D barcode, they are doing something new: they are pulling live, lot-level data from the supply chain and displaying it in real time on the shelf.
The digital price tag knows your product's expiration date because your 2D barcode tells the retailer's system what lot is on that shelf and when it expires. The tag knows the current promotional price because that data was synchronized from your ERP to the retailer, or more precisely, from the GS1 data layer that sits between you and the retailer. If that data is missing, stale, or inconsistent, the digital tag either goes dark or displays incorrect information. In the world of retailer compliance, incorrect information has consequences.
What Is the Sunrise 2027 Data Problem Manufacturers Aren't Discussing?
Here is the uncomfortable reality the digital shelf tag revolution is forcing manufacturers to face: do you actually know, right now, what data lives on your products in a retailer's system, and does it match what is in your ERP?
For many manufacturers, the honest answer is: not entirely. GTINs may be registered in the GS1 system but not fully enriched with lot, batch, and expiry data. Item master records in the ERP may carry pricing and description fields that have drifted from what was submitted to the retailer's product data portal. SKU changes, new formulations, size updates, packaging updates, may have been executed in the warehouse without a corresponding update in GS1's Verified by GS1 registry.
For CFOs scoping the cost of this gap, the question isn't theoretical. Mismatched product data shows up as retailer chargebacks, automatic markdowns on digital shelf labels, and compliance penalties that hit the bottom line before the marketing or ops team sees them. The data audit is cheaper than the chargeback cycle.
The Core Tension
Retailers use the GS1 Database to verify that the price and product information on a digital shelf tag exactly matches the brand owner's registered data. If your NetSuite item record says one thing and your GS1 registration says another, the digital tag cannot trust either source. The result is data reconciliation failures, and increasingly, retailer compliance penalties.
Walmart's Digital Shelf Label Pilot: A Signal Worth Heeding
Walmart's 2024 announcement of its digital shelf label initiative was not just a technology story. It was a supply chain story. The retailer explicitly connected its ESL rollout to its broader push for supplier data quality and GS1 compliance. The message to manufacturers was clear: the shelf of the future will be powered by your data, and if your data is not ready, your products will be disadvantaged on that shelf.
Practically, this means that a manufacturer whose 2D barcode data is correctly synchronized, lot number, expiry, GTIN, pricing tier, and promotional flags all flowing cleanly from ERP to GS1 to retailer, will have their products displayed accurately on digital tags, protected from automatic markdowns triggered by stale data, and positioned for the kind of automated shelf replenishment that ESL systems can eventually enable.
A manufacturer whose data is fragmented, inconsistent, or simply not enriched to the 2D standard will be on the wrong side of that equation.
The NetSuite Data Governance Question
For manufacturers running NetSuite as their ERP, the digital price tag question eventually becomes a NetSuite data governance question. The system of record for your product's lot numbers, expiry dates, pricing, and item attributes is your ERP. If that data is not clean, structured, and synchronized to the GS1 layer in a way that matches what your retail partners expect, all the 2D barcodes in the world will not save you. The foundation for this is correct lot and serial costing inside NetSuite itself, which we walked through in detail in our post on lot-numbered and serialized costing methods.
Some of the questions worth asking right now:
- Are your item records in NetSuite enriched with the fields that GS1 Digital Link requires, specifically batch, lot, and expiry data at the transaction level?
- Do your pricing records in NetSuite align with what is registered in your retail partners' product data portals? Who owns that synchronization, and how often does it happen?
- When you make a SKU change, a reformulation, a size update, a new regulatory label, how does that change flow from NetSuite to your GS1 registration to your retail partner's system? Is there a process, or is it ad hoc?
- If a retailer's digital price tag system queries the GS1 registry for your product data tomorrow, what will it find, and will it match what is in your warehouse?
These are not rhetorical questions. They are the diagnostic framework that separates manufacturers who will navigate the digital shelf label era confidently from those who will face chargebacks, readiness failures, and retailer friction when the ESL rollout reaches full scale.
What GS1 Digital Link Requires from Your Website
Here is a dimension of Sunrise 2027 that most conversations about labels and ERPs overlook: the GS1 Digital Link is not just a barcode. It is a URL. When a consumer, a retailer's system, or a store associate scans your product's 2D barcode, they are not just reading a number. They are following a web link to a destination that your company is responsible for maintaining.
That destination is your brand's digital product resolver, a structured web endpoint that serves product information based on the GTIN and any additional identifiers encoded in the barcode. For a basic rollout, this might resolve to a product detail page on your website. For a more advanced one, it could serve different content depending on who is scanning: a consumer gets nutritional info and recipes, a retailer's system gets lot and expiry data, a logistics partner gets compliance documentation.
The implication is significant: Sunrise 2027 readiness does not end at the label. It extends to your web infrastructure, your product content management, and your ability to serve accurate, structured, real-time product data from a URL that is always live and always current.
What This Means in Practice
For Supply Chain Managers responsible for the data pipeline between manufacturing, the ERP, and the retailer's portal, the resolver layer is where lot-level visibility either holds together or breaks. A clean, lot-aware resolver is what lets a single 2D barcode on a box mean different things to different scanners on different days.
- Your product pages must be structured to serve GS1 Digital Link-compatible responses, not just human-readable HTML, but machine-readable data that retailer systems and digital shelf label platforms can consume.
- Product data on your website must stay synchronized with what is in your ERP and your GS1 registration. A price change, a formulation update, or a new regulatory warning that lives in NetSuite but not on your product website creates a data inconsistency that retailer systems will detect.
- If you carry products with lot or batch-level variation, different expiry dates, different manufacturing origins, your resolver must serve lot-specific content, not just generic SKU-level information. The governance side of how long this lot-level data needs to live is worth thinking through in advance, see our notes on data retention best practices.
- Uptime matters. A resolver page that is down, slow, or returning errors when a retailer's ESL system queries it is a readiness failure, not just a technical inconvenience.
The Web Readiness Question
If a consumer scans your product's 2D barcode in a Walmart aisle right now, where does it take them? Is that destination live, accurate, and structured to serve the data that GS1 Digital Link requires? For most manufacturers, the honest answer is: we are not sure. That uncertainty is itself a gap worth addressing.
This Is Where the Journey Gets Interesting
Techfino's Supply Chain Advisory practice is not going to give you a simple checklist answer to the data governance challenge, because there is not one. The path from a 1D UPC on a shelf to a fully synchronized, lot-level 2D barcode feeding a Walmart digital price tag runs through your ERP configuration, your GS1 registration practices, your label printing workflows, and your retailer data relationships simultaneously.
What we can tell you is that the manufacturers who start this diagnostic work now, who audit their NetSuite item master, map their data flows to the GS1 layer, and identify the gaps before a retailer readiness audit does, will be in a very different position in 2027 than those who treat this as a label printing project.
The digital price tag is here. The question is whether your data will be ready to power it.
Supply Chain Advisory: How Techfino Can Help Manufacturers
Techfino's Supply Chain Advisory team, part of Techfino's NetSuite manufacturing practice, works with manufacturers across the full Sunrise 2027 readiness stack: NetSuite item master audits, GS1 registration mapping, label and resolver readiness assessments, and the cross-functional coordination that ties IT, marketing, and supply chain teams together around a single data governance plan. As a certified NetSuite Solution Provider, we configure the ERP layer to feed the GS1 layer cleanly, so the data on your retailer's digital shelf labels matches what is in your warehouse and your registry.
Curious how your current NetSuite data setup holds up against the demands of Sunrise 2027 and digital shelf label compliance? Schedule a free assessment with Techfino's Supply Chain Advisory team to map the gap between where your data is now and where your retail partners are heading.