---
title: "Structured Product Data and Your Storefront UX"
canonical_url: "https://www.laioutr.com/en/blog/structured-product-data-pim-frontend-2026"
locale: en
meta:
description: "What structured product data really means: attributes, units, variants, classification. And where it shows up: filters, comparison tables, Schema.org, feeds."
"og:description": "What structured product data really means: attributes, units, variants, classification. And where it shows up: filters, comparison tables, Schema.org, feeds."
"og:title": "Structured Product Data and Your Storefront UX"
---
# Structured Product Data: How It Shows Up in Your Storefront
Table of contents
1. [1.What "structured" means in a product catalog](#what-structured-means-in-a-product-catalog)
2. [2.Filters and facets: where gaps show first](#filters-and-facets-where-gaps-show-first)
3. [3.Spec sheets and comparison tables: why shared identifiers matter](#spec-sheets-and-comparison-tables-why-shared-identifiers-matter)
4. [4.Variant selection: axes, availability and images](#variant-selection-axes-availability-and-images)
5. 5.Schema.org and feeds: the same structure, read by machines
6. [6.One data model across backends with Orchestr](#one-data-model-across-backends-with-orchestr)
7. [7.FAQ](#faq)
8. [8.Next steps](#next-steps)
1. [1.What "structured" means in a product catalog](#what-structured-means-in-a-product-catalog)
2. [2.Filters and facets: where gaps show first](#filters-and-facets-where-gaps-show-first)
3. [3.Spec sheets and comparison tables: why shared identifiers matter](#spec-sheets-and-comparison-tables-why-shared-identifiers-matter)
4. [4.Variant selection: axes, availability and images](#variant-selection-axes-availability-and-images)
5. 5.Schema.org and feeds: the same structure, read by machines
6. [6.One data model across backends with Orchestr](#one-data-model-across-backends-with-orchestr)
7. [7.FAQ](#faq)
8. [8.Next steps](#next-steps)
Structured product data means every product fact lives in a typed attribute with a unit, a stable identifier and a clear place in the variant hierarchy, not in a description text. Shoppers never see the data model, but they see its effects in five places: filters, comparison tables, variant selection, Schema.org markup and feeds. When the model is weak, each of those components has to guess, and shoppers notice.
## What "structured" means in a product catalog
"We have a PIM" and "our product data is structured" are two different statements. Structure is the set of modeling decisions you make inside the PIM:
- **Attribute model:** each attribute has a type (text from a value list, number, yes/no, range) instead of free text. "White", "white " and "wht" are three filter values; one value from a list is one.
- **Units:** the number and the unit are stored separately. "approx. 60 cm" in a text field never becomes a range slider, 60 with the unit cm does.
- **Classification:** in technical B2B assortments, standards like ETIM and ECLASS define these rules for you. ETIM describes products through classes and features of four types (alphanumeric, logical, numeric, range), and numeric and range features need a unit, apart from counts such as number of poles. ECLASS gives every property a globally unique identifier (IRDI) and supports value lists and convertible units.
- **Variants:** a parent product carries shared information, each purchasable variant carries its own SKU, GTIN, price and stock, and the variant axes (size, color, voltage) are explicit.
- **Multilingual data:** identifiers stay language independent, only labels and values get translated.
- **Media assignment:** images are linked to the variant or option they show, not just dropped into a gallery.
## Filters and facets: where gaps show first
A facet is only as good as the attribute behind it. In Laioutr, Orchestr defines one filter contract for listing pages: list filters, boolean toggles, continuous ranges and pre-bucketed intervals. Range bounds can be plain numbers, money or a measurement with a unit. The link to your data model is direct: a width stored as number plus unit becomes a slider, a width stored as text becomes a long, unsorted checkbox list at best.
Facet values and counts come from your backend or search provider; components such as the filter bar and the off-canvas filter sheet render what Orchestr returns. If you want semantic search and filters that adapt to the result set on top of that, [AI Search & Discovery](https://www.laioutr.com/en/product/search-and-discovery) covers it as an add-on. The foundation of your facets is still your attribute model.
Filters also matter for crawling: Google's guidance on faceted navigation recommends preventing crawling of filter URLs if you don't need them indexed. If you want them indexed, keep the parameter order consistent and return a 404 for empty combinations. How often shoppers start with a filter rather than search is the subject of [our analysis of AI search, category browse and faceted filters](https://www.laioutr.com/en/blog/ai-search-vs-category-browse-shopper-entry-points-2026).
## Spec sheets and comparison tables: why shared identifiers matter
In the canonical product model Laioutr uses, specifications are ordered rows: a display name, a typed value (text, number, boolean, measurement or money) and an optional section such as "dimensions" or "technical". The product specifications table formats each value per locale and groups rows into sections. A shopper in Germany sees "1,5 kg", a shopper in the US sees "1.5 kg", from the same data.
A comparison table puts these rows for several products side by side, which only works when rows share identifiers. If one product calls it "Weight" and the next one "Net weight (kg)", the table has holes, and a "differences only" view ends up comparing labels instead of values. Well-known property names exist precisely so that rows from different connectors line up.
Once the rows are consistent, placing the specifications table on a product detail page is layout work, not a data project, handled by editors in Studio, the visual editor of Laioutr. A product comparison view, if your project builds one, reads the same rows.
## Variant selection: axes, availability and images
In the canonical model, a product holds its option groups (for example size with S, M, L and color with red and blue), and each variant carries its selected options, SKU, optional GTIN, availability and prices, including unit prices.
Typical failure patterns:
1. **Colors modeled as separate products.** The selector cannot offer them, so shoppers jump between product pages.
2. **Availability only per value.** Graying out "XL" works per axis value, but "red in XL" is a combination and needs variant-level stock.
3. **Images attached to the parent only.** Selecting blue changes the price, but not the photo.
All three get fixed in the data model, not in the component.
## Schema.org and feeds: the same structure, read by machines
Search engines and AI answer engines read the same facts as your filters. Schema.org lets a Product carry additional properties as PropertyValue pairs: propertyID holds a standard code for the characteristic, which is where an ETIM or ECLASS identifier fits, and unitCode takes a UN/CEFACT unit code. For variants, Google documents a ProductGroup with a productGroupID, the attributes it varies by, and nested variants.
In a Laioutr frontend, you can generate JSON-LD with the Nuxt Schema.org module from the entity a section renders, instead of from separately maintained SEO fields. That way markup and visible page share one source, see [SEO and GEO](https://www.laioutr.com/en/product/seo-and-geo).
Feeds follow the same rules. Google Merchant Center expects the same item group ID across all variants of a group and different values for color, size, material or pattern. Why forty channels turn into forty truths is covered in [our post on product data consistency across channels](https://www.laioutr.com/en/blog/product-data-consistency-multichannel-distribution-2026). For channel exports straight from the frontend layer, [Distributr](https://www.laioutr.com/en/product/data-distribution) is available as an add-on: zero imports because the data is already there, one direction, out. It is not a PIM.
## One data model across backends with Orchestr
Product data rarely lives in one system: the PIM owns attributes and media, the ERP prices and stock, a search provider the facets. Orchestr maps these sources into one canonical model of products, variants, specifications and filters, so components receive the same shape regardless of where a field comes from. It bundles several sequential API calls into one request and uses three-tier caching. Laioutr connects to 50+ backends through 300+ integrations; other sources can be connected through an Orchestr integration. More on the architecture: [Composability and Orchestration](https://www.laioutr.com/en/product/composability-orchestration).
Where to start:
1. Audit the 20 attributes your most important category filters use: type, unit, value list.
2. Decide the variant axes in the PIM before the next frontend release.
3. Map attribute identifiers to shared names so comparison rows line up.
4. Generate structured data from the rendered entity, then check your feeds against it.
## FAQ
### Do we need ETIM or ECLASS?
Only if your market expects them, typically in technical wholesale, electrical and building services, or industrial procurement. For fashion or consumer goods, a clean in-house attribute model with typed values and units is usually enough.
### Does Laioutr replace our PIM?
No. The PIM stays the system of record for product data. Laioutr is the frontend layer: it reads the data through Orchestr, renders it in components and keeps the storefront consistent across backends.
### Who maintains filters and spec tables, developers or marketing?
Both, with a clear split. Developers define components and data bindings once. Product and marketing teams place and configure them in Studio, without a ticket for every category page.
## Next steps
Want to see how your attribute model behaves in filters, spec tables and variant selectors? [Book a demo](https://www.laioutr.com/en/contact) and bring a sample category. We will look at it together on a [Composable Headless Frontend](https://www.laioutr.com/en/composable-headless-frontend).
### More from the Laioutr Platform
- [AI Search & Discovery](https://www.laioutr.com/en/product/search-and-discovery)
- [SEO and GEO](https://www.laioutr.com/en/product/seo-and-geo)
- [Composability and Orchestration](https://www.laioutr.com/en/product/composability-orchestration)
- [Composable Headless Frontend](https://www.laioutr.com/en/composable-headless-frontend)
- [PIM integration for the frontend](https://www.laioutr.com/en/system/product-information-management-pim)
---
Share this article
[Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Fstructured-product-data-pim-frontend-2026) [Share on X](https://x.com/intent/post?url=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Fstructured-product-data-pim-frontend-2026&text=) [Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Fstructured-product-data-pim-frontend-2026) [Share on Pinterest](https://pinterest.com/pin/create/button/?url=https%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Fstructured-product-data-pim-frontend-2026&description=) [Share via email](mailto:?subject=&body=%0A%0Ahttps%3A%2F%2Fwww.laioutr.com%2Fen%2Fblog%2Fstructured-product-data-pim-frontend-2026)
## More interesting articles
Practical know-how for frontend development, smart agents, and headless
[To the blog](https://www.laioutr.com/en/blogs)
[iPhone Duo and Ecommerce: What Merchants Need to Know Now
iPhone Duo goes on sale on October 23, 2026. Online stores don't need a dedicated app or a custo…](https://www.laioutr.com/en/blog/iphone-duo-ecommerce-foldable-storefront)
[Structured Product Data: How It Shows Up in Your Storefront
Structured product data means every product fact lives in a typed attribute with a unit, a stable id…](https://www.laioutr.com/en/blog/structured-product-data-pim-frontend-2026)
[44% Decide via Trial or PoC: How to Run a Storefront PoC in DACH
In DACH, software decisions are increasingly made hands-on: in the study "Software Buying in DA…](https://www.laioutr.com/en/blog/storefront-proof-of-concept-dach-buyers-2026)
[Frontend Management Platform Comparison: How to Choose the Right FMP
Choosing a frontend management platform (FMP) is less about feature lists and more about where your …](https://www.laioutr.com/en/blog/frontend-management-platform-comparison-how-to-choose-2026)
[DAM, PIM, and CMS Are Converging: What It Means for Your Storefront
DAM, PIM, and CMS vendors are moving into each other's territory, and more teams now evaluate on…](https://www.laioutr.com/en/blog/dam-pim-cms-convergence-content-hub-storefront-2026)
[Contentful Live Preview: What Your Frontend Has to Deliver
Contentful Live Preview lets editors see a draft right next to the entry editor and watch changes ap…](https://www.laioutr.com/en/blog/contentful-live-preview-frontend-perspective-2026)
[Content Governance at Scale: Product Content and Brand Assets
Content governance at scale means that roles, approvals, brand rules, asset rights and translations …](https://www.laioutr.com/en/blog/content-governance-product-content-brand-assets-frontend-2026)
[AI Agents as Frontend Operators: Architecture and Control Model
An AI agent becomes a frontend operator when it watches the running storefront, spots concrete issue…](https://www.laioutr.com/en/blog/ai-agents-as-frontend-operators-2026)
[Shopping Agents Read Your Feed: What Agentic Commerce Changes
Agentic commerce adds a new reader to your product data: shopping agents in ChatGPT, Google AI Mode,…](https://www.laioutr.com/en/blog/shopping-agents-product-feeds-agentic-data-distribution-2026)
[Server-Side Tracking in E-Commerce: Making Measurement Complete Again
Server-side tracking moves the forwarding of analytics and conversion events from the visitor's …](https://www.laioutr.com/en/blog/server-side-tracking-ecommerce-complete-measurement-2026)
[Product Image Deep Links, Not ZIP Files: Assets That Stay Current
If you still send product images to retailers, marketplaces and press as ZIP files, every package st…](https://www.laioutr.com/en/blog/product-image-deeplinks-asset-distribution-2026)
[PrestaShop 8 to 9 Upgrade Without Replatforming: Decouple the Frontend
You can take most of the risk out of the PrestaShop 8 to 9 upgrade by moving the storefront off the …](https://www.laioutr.com/en/blog/prestashop-8-to-9-upgrade-without-replatforming-2026)
[Order Management With an OMS Like fulfillmenttools: The Frontend View
An efficient order management system decides which location fulfills an order, how much stock is rea…](https://www.laioutr.com/en/blog/order-management-fulfillmenttools-oms-frontend-2026)
[No Replatforming Budget in 2026? Why the Frontend Gets Approved
If your 2026 budget has no room for a replatforming project, you are not alone, and you do not have …](https://www.laioutr.com/en/blog/no-replatforming-budget-frontend-project-approval-2026)
[Garden Retail Order Management: What Your Storefront Must Show
In garden and DIY retail, one cart can hold a parcel item, a patio set that ships by freight, live p…](https://www.laioutr.com/en/blog/garden-retail-order-management-seasonal-frontend-2026)
[](https://www.laioutr.com/en/apps/shopify)
Laioutr
[Shopify](https://www.laioutr.com/en/apps/shopify)
Shopify is a commerce platform for selling online and in physical retail.
[](https://www.laioutr.com/en/apps/shopware)
Laioutr
[Shopware](https://www.laioutr.com/en/apps/shopware)
Shopware is a flexible ecommerce platform from Europe for product catalogs and omnichannel commerce.
[](https://www.laioutr.com/en/apps/adobe-commerce)
Laioutr
[Adobe Commerce](https://www.laioutr.com/en/apps/adobe-commerce)
Adobe Commerce is an enterprise commerce platform for complex, global B2C and B2B scenarios.
Planned
[](https://www.laioutr.com/en/apps/b2b-sellers)
Laioutr
[B2Bsellers](https://www.laioutr.com/en/apps/b2b-sellers)
B2B suite for Shopware that turns an online store into a professional B2B commerce platform.
Planned
[](https://www.laioutr.com/en/apps/commerce-layer)
Laioutr
[Commerce Layer](https://www.laioutr.com/en/apps/commerce-layer)
Commerce Layer is a headless commerce platform for making inventory and catalogs available online.
[](https://www.laioutr.com/en/apps/commercetools)
Laioutr
[Commercetools](https://www.laioutr.com/en/apps/commercetools)
Commercetools is a SaaS-based headless ecommerce platform used worldwide.
[](https://www.laioutr.com/en/apps/emporix)
Laioutr
[Emporix](https://www.laioutr.com/en/apps/emporix)
Emporix is a composable, API-first commerce platform for scalable B2B and B2C scenarios.
Planned
[](https://www.laioutr.com/en/apps/hcl-software)
Laioutr
[HCL Software](https://www.laioutr.com/en/apps/hcl-software)
Enterprise suite for digital commerce and experience with extensive configurability.
Planned
[](https://www.laioutr.com/en/apps/intershop)
Laioutr
[Intershop](https://www.laioutr.com/en/apps/intershop)
Enterprise commerce platform for complex B2B and B2C business models.
Planned
[](https://www.laioutr.com/en/apps/magento-2)
Laioutr
[Magento 2](https://www.laioutr.com/en/apps/magento-2)
Widely used, extensible commerce platform for B2C and B2B scenarios.
[](https://www.laioutr.com/en/apps/oxid-eshop)
Laioutr
[OXID eShop](https://www.laioutr.com/en/apps/oxid-eshop)
OXID eShop is an extensible commerce platform for complex B2B and B2C requirements.
Planned
[](https://www.laioutr.com/en/apps/patchworks)
Laioutr
[Patchworks](https://www.laioutr.com/en/apps/patchworks)
Patchworks is a low-code iPaaS that connects ecommerce, ERP, WMS, 3PL, and marketplaces.
Planned
[](https://www.laioutr.com/en/apps/PrestaShop)
Laioutr
[Prestashop](https://www.laioutr.com/en/apps/PrestaShop)
Open-source commerce platform for small and midsize merchants in Europe and beyond.
Planned
[](https://www.laioutr.com/en/apps/saleor)
Laioutr
[Saleor](https://www.laioutr.com/en/apps/saleor)
Open-source, API-first commerce platform built on GraphQL for custom storefronts.
Planned
[](https://www.laioutr.com/en/apps/salesforce-commerce-cloud)
Laioutr
[Salesforce Commerce Cloud](https://www.laioutr.com/en/apps/salesforce-commerce-cloud)
Salesforce Commerce Cloud is a cloud-based enterprise commerce platform for businesses of any size.
Planned
[](https://www.laioutr.com/en/apps/sap-commerce-cloud)
Laioutr
[SAP Commerce Cloud](https://www.laioutr.com/en/apps/sap-commerce-cloud)
Enterprise commerce platform for complex catalogs, pricing models, and omnichannel journeys.
Planned
[](https://www.laioutr.com/en/apps/scayle)
Laioutr
[Scayle](https://www.laioutr.com/en/apps/scayle)
SCAYLE is a commerce engine that helps brands and retailers scale their business.
Planned
[](https://www.laioutr.com/en/apps/spryker)
Laioutr
[Spryker](https://www.laioutr.com/en/apps/spryker)
Composable commerce platform for sophisticated B2B and B2C business models.
[](https://www.laioutr.com/en/apps/sylius)
Laioutr
[Sylius](https://www.laioutr.com/en/apps/sylius)
Sylius is a developer-friendly ecommerce framework for B2C and B2B shopping experiences.
Planned
[](https://www.laioutr.com/en/apps/vendure)
Laioutr
[Vendure](https://www.laioutr.com/en/apps/vendure)
Vendure is a headless commerce platform for businesses with complex requirements.
Coming Soon
[](https://www.laioutr.com/en/apps/vtex)
Laioutr
[VTEX](https://www.laioutr.com/en/apps/vtex)
Cloud-native, composable commerce platform for B2B and B2C at scale.
Planned
[](https://www.laioutr.com/en/apps/websale)
Laioutr
[Websale](https://www.laioutr.com/en/apps/websale)
Stable, enterprise-ready commerce backend for complex retail environments.
Strategy call
## Ready to turn your frontend into a control layer?
Show us your stack, your roadmap, your replatforming scenario, and we'll show you how Laioutr fits, what it costs, and how fast you go live.
*"After 30 minutes, we knew Laioutr makes our replatforming feasible." - Daniel B., CEO,* [*hygibox.de*](https://hygibox.de)
[Book a demo](https://www.laioutr.com/en/contact)
## Structured Data
```json
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://www.laioutr.com/#identity",
"name": "Laioutr",
"legalName": "Laioutr GmbH",
"url": "https://www.laioutr.com/",
"logo": {
"@type": "ImageObject",
"url": "https://www.laioutr.com/laioutr-logo.png",
"width": 400,
"height": 400
},
"email": "info@laioutr.com",
"telephone": "+49 30 75435715",
"address": {
"@type": "PostalAddress",
"streetAddress": "Münchweilersteig 5",
"postalCode": "12559",
"addressLocality": "Berlin",
"addressCountry": "DE"
},
"vatID": "DE450905846",
"sameAs": [
"https://www.linkedin.com/company/laioutr",
"https://www.youtube.com/@Laioutr",
"https://x.com/laioutr"
]
},
{
"@type": "WebSite",
"@id": "https://www.laioutr.com/en/#website",
"url": "https://www.laioutr.com/en/",
"name": "Laioutr",
"inLanguage": "en",
"publisher": {
"@id": "https://www.laioutr.com/#identity"
}
},
{
"@type": "BlogPosting",
"@id": "https://www.laioutr.com/en/blog/structured-product-data-pim-frontend-2026#article",
"headline": "Structured Product Data: How It Shows Up in Your Storefront",
"description": "What structured product data really means: attributes, units, variants, classification. And where it shows up: filters, comparison tables, Schema.org, feeds.",
"image": [
"https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmu3z1z6x4ghn06mho6krl9rn"
],
"datePublished": "2026-09-16T10:43:38.460888+00:00",
"dateModified": "2026-09-16T10:43:33.559575+00:00",
"inLanguage": "en",
"articleSection": "Insights",
"keywords": "Information architecture, Headless Commerce, Storefront Experience, Composable",
"author": {
"@id": "https://www.laioutr.com/#identity"
},
"publisher": {
"@id": "https://www.laioutr.com/#identity"
},
"mainEntityOfPage": {
"@id": "https://www.laioutr.com/en/blog/structured-product-data-pim-frontend-2026#webpage"
},
"isPartOf": {
"@id": "https://www.laioutr.com/en/#website"
}
},
{
"@type": "WebPage",
"@id": "https://www.laioutr.com/en/blog/structured-product-data-pim-frontend-2026#webpage",
"url": "https://www.laioutr.com/en/blog/structured-product-data-pim-frontend-2026",
"name": "Structured Product Data: How It Shows Up in Your Storefront",
"description": "What structured product data really means: attributes, units, variants, classification. And where it shows up: filters, comparison tables, Schema.org, feeds.",
"inLanguage": "en",
"isPartOf": {
"@id": "https://www.laioutr.com/en/#website"
},
"breadcrumb": {
"@id": "https://www.laioutr.com/en/blog/structured-product-data-pim-frontend-2026#breadcrumb"
},
"primaryImageOfPage": {
"@type": "ImageObject",
"url": "https://eu-west-2.graphassets.com/cmii2mlqi0dux06l5543v7nkc/cmu3z1z6x4ghn06mho6krl9rn"
},
"datePublished": "2026-09-16T10:43:38.460888+00:00",
"dateModified": "2026-09-16T10:43:33.559575+00:00",
"mainEntity": {
"@id": "https://www.laioutr.com/en/blog/structured-product-data-pim-frontend-2026#article"
}
},
{
"@type": "BreadcrumbList",
"@id": "https://www.laioutr.com/en/blog/structured-product-data-pim-frontend-2026#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Laioutr",
"item": "https://www.laioutr.com/en/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Insights",
"item": "https://www.laioutr.com/en/blogs/insights"
},
{
"@type": "ListItem",
"position": 3,
"name": "Structured Product Data: How It Shows Up in Your Storefront"
}
]
}
]
}
```