# Keep digital and physical product information aligned. > Physical Retail is the newest of the eight CommerceClarity areas and carries one agent, Shelf Label Content. It writes what an electronic shelf label or an in-store screen needs from the same product record the website reads: a short name that fits, the attributes that can be read at arm’s length, and the icons a regulated category has to show. It feeds the display system already installed rather than replacing it. Electronic shelf labels and in-store screens refresh as often as your site does. Each one still needs its own writing: a short name, the attributes that matter at arm’s length, and the icons the category requires. ![A shopper walking past a long grocery shelf run, the shelves streaking behind her.](https://cdn.sanity.io/images/xd4hrbt2/production/b66298118f51ca7fdec1692753c463df18a2d9dd-1774x887.jpg) [Book a demo](/book-a-demo) ## A store is a channel with less room In most retailers the digital catalog stops at the warehouse door, and the store runs on its own content: a name typed to fit the old paper label, a price, and whatever the category manager had time to add. Then the shelf edge became a screen, and could suddenly show anything. The constraint changed shape rather than going away. A shelf label is read at arm’s length in a couple of seconds, so it is not a shortened product page: it is a different piece of writing, with a hard character budget, the one or two attributes that actually decide the purchase in that category, and the allergen or safety marks the category makes mandatory. And it is needed for every product, in every store, in the local language, updated whenever the assortment moves. That is the real work, and it is why dynamic shelf content so often launches on one pilot aisle and stops there. ## The jobs in the store A single workflow today. This is the newest of the eight areas, and the list will grow. What runs here feeds the display system you already installed. - Shelf Label Content · Generate the content for in-store digital shelf labels. · Continuous ## Written for arm’s length *Shelf label content* The agent derives shelf content from the same master record the site reads, and writes it to the format the label actually has: a short name that fits the field rather than one truncated by it, the attributes that matter in that category, the promotional flag, and the allergen or safety icons where the category requires them. It runs per store and per language, and it pushes to the display system rather than producing a file for somebody to import. When the assortment or the price moves, the label follows without a person retyping it. ## What retailers ask us ### Do you replace our label system? No. The hardware and the display platform stay yours. We produce the content they show and push it there. ### Is this just a truncated product name? No. Truncation is the failure this avoids. A label is written to its own budget, so the words that survive are the ones that decide the purchase rather than the first thirty characters of a web title. ### What about price and stock? They stay with the systems that own them. The agent owns the descriptive content around them, which is the part that was never written per product in the first place. ### Can it run per store? Yes, and that is usually the requirement. Assortment, language and local rules differ store to store, and content that is right in one region can be wrong in the next. ### Who checks it before it reaches a shelf? You do, on the same review the other agents use. A category can be set to publish once it clears the rules, or to hold everything for a person. ### Whose data is it? Yours. The corrections your team makes are what the agents learn from, and both the data and the corrections stay exportable at any point. ## Related areas - [Catalog Foundation](/solutions/catalog-foundation) - [Compliance & Quality](/solutions/compliance-quality) ## Every correction makes the next run better *The feedback loop* Your team judges the output. A value is right, or it is wrong and gets fixed once. Each verdict changes the next run: the score on your own sample moves, and the agent starts from what the last one learned. So the share of values that need a person keeps falling, measured on your catalog and your rules rather than on an average of everybody else. ![The platform flagging a product description as too generic for the brand tone, with the suggested rewrite and the two answers.](https://cdn.sanity.io/images/xd4hrbt2/production/30815d23ee4d132352d037d84d401a32a7b48eec-2880x1620.webp) ## Live on your catalog in weeks, not months *How we work* We run all four phases with your team, on the stack you already have, and each one ends with a number you agreed in advance. - Design · We map how your data comes in and how the result goes back out, then agree the business KPI the agent has to move. - Implement · We build the agent and test it on a sample of your own catalog, agreed with you. Every change is scored against that sample, so the tuning runs on numbers. - Prove · Done means the KPI reached target on the full catalog, and you have seen the numbers yourself. - Evolve · We stay on the account. Your corrections keep improving the agent, the KPI holds where you need it, and the next use case starts from the context this one already built. ## Enterprise, on a catalog you cannot break ![A department store floor.](https://cdn.sanity.io/images/xd4hrbt2/production/61ee81a3eeab3410935b61002f453008efebb032-943x628.jpg) [Book a demo](/book-a-demo) - It runs on the stack you have · It reads your PIM, ERP and DAM through their APIs and writes the result back to them. - A person approves everything that publishes · Every value is checked against your rules, and anything uncertain goes to review before it reaches a channel. - Your data stays yours · Your own isolated workspace. It is never pooled into shared models, and you can export it at any point. - Every run is logged · Each value carries its source, its run and its score, so you can see why a wrong one went wrong. ## Start with one use case One use case, run end to end on your own catalog. That is enough to see what it moves and what it costs per product, before you commit the rest. [Book a demo](/book-a-demo) ## Entities - [GS1](https://www.gs1.org) · Organization, mentions - [EPREL](https://eprel.ec.europa.eu/screen/home) · Thing, mentions ## Sources - [European Product Registry for Energy Labelling (EPREL)](https://eprel.ec.europa.eu/screen/home) · European Commission - [Energy label and ecodesign product database](https://commission.europa.eu/energy-climate-change-environment/standards-tools-and-labels/products-labelling-rules-and-requirements/energy-label-and-ecodesign/product-database_en) · European Commission - [Regulation (EU) 2023/988 on general product safety](https://eur-lex.europa.eu/eli/reg/2023/988/oj) · EUR-Lex - [GTIN, the GS1 global trade item number](https://www.gs1.org/standards/id-keys/gtin) · GS1 --- Canonical: https://commerceclarity.com/solutions/physical-retail Every page of this site is available as markdown: append `.md` to its path. Index: /llms.txt