Make your product data findable — by search engines, marketplaces and AI agents.
The Open Data module publishes a governed selection of your catalog as structured, public product data: schema.org JSON-LD, versioned feeds and a read-only endpoint. You decide what is public. Everything else stays behind the gate.
SCHEMA.ORG / PRODUCTVERSIONED FEEDSREAD-ONLY PUBLIC ENDPOINT
FICTIONAL DEMO DATA · MESSARA
GET https://data.messara.com/v1/products/MS-12011200 OK · application/ld+json · cache: HIT · v2026.38{ "@context": "https://schema.org", "@type": "Product", "sku": "MS-12011", "name": "Bourdon tube pressure gauge RF63, 0–10 bar", ...
01 · Why now
Your product data is read by machines before it is read by people.
Buyers increasingly start with a search engine, a marketplace or an AI assistant. Those systems don't read your PDF data sheet — they read structured data. If your own, authoritative data isn't available in a form they can use, they rely on whatever copies they find elsewhere.
AI assistants and answer engines.
Assistants and AI search summarise products from structured, openly accessible sources. Clean attributes, units and identifiers make it more likely that answers reflect your current specifications — not an outdated reseller copy.
Search engines.
schema.org Product markup is the established vocabulary search engines use to understand product pages. Consistent JSON-LD on your own site describes each product unambiguously.
Marketplaces and comparison portals.
They need complete, current data in their format, on their schedule. A versioned feed replaces one-off exports sent by email.
Wholesalers, partners, planners and architects.
Partner systems, planning tools and specification platforms need reliable technical data they can pull on demand — without an account request for every download.
PIM GATE DOES NOT GUARANTEE RANKINGS OR INCLUSION IN THIRD-PARTY SERVICES. IT MAKES YOUR DATA AVAILABLE IN THE FORMATS THEY READ.
An AI assistant quotes a measuring range we changed two years ago — from a reseller's copy of our data.
SCENARIO · MEASUREMENT & CONTROL MANUFACTURER · 20K SKU
02 · How it works
One governed catalog. A public slice you define.
Open Data is not a second export. It is a published view of the same validated data your portals and APIs already use — filtered by rules you set.
Illustrative figures based on the fictional MESSARA demo catalog.
01
Select.
Define which products, attributes and languages are public — by category, market, lifecycle status or flag.
02
Validate.
Only records that pass your quality rules for the Open Data profile are published. Incomplete records are held, not exposed.
03
Publish.
PIM Gate generates JSON-LD, feeds and the public endpoint from the selection and versions every release.
04
Keep current.
Changes in your PIM flow through the gate; affected records, feeds and change logs update on the next publication run.
03 · 03 · What you control
Public by rule, private by default.
Nothing becomes public because it exists in your PIM. A record is published only when it matches your selection rules and passes validation. Prices, stock, customer agreements and internal attributes stay behind the gate — visible only to entitled users in your portals and APIs.
Rules by category, market, lifecycle status, brand or any attribute flag
Attribute allow-list per dataset — internal fields can never leak into a public payload
Languages per dataset, with fallback chains you define (e.g. de-CH → de-DE)
Preview the public result before you publish, including record counts
Every change to a rule is logged with user and timestamp
Name, description, dimensions, measuring range, materials, GTIN, images, data sheet
List and customer prices, stock, cost, internal notes, supplier data, unreleased products
04 · Outputs
The formats machines already read.
Every output is generated from the same selection and carries the same version number, so a feed, an API response and your website markup never disagree.
Output
What you get
Typical consumer
Status
schema.org/Product JSON-LD
One JSON-LD document per product, embeddable in your own product pages (script tag or server-side include)
Search engines, AI assistants
2026
Versioned feeds
Full and delta feeds in JSON, CSV and XML; every release numbered and retained
Marketplaces, comparison portals, wholesalers
2026
Public read-only API
GET endpoints for products, categories and feeds; no write access; caching and rate limits
Partner systems, apps, AI agents
2026
Product data sitemap
Machine-readable index of all public product URLs and their last modification date
Search engines, crawlers
2026
GS1 Digital Link compatibility
Product URIs in GS1 Digital Link syntax (/01/{GTIN}) that resolve to your public record
Scanners, retail systems, DPP
PLANNED
AI-agent index
A manifest in the style of llms.txt that points agents to your datasets, endpoints and licence
AI agents and assistants
PLANNED
05 · Sample payload
What a public product record looks like.
Standard schema.org vocabulary, units as UN/CEFACT codes, stable identifiers. The same record can be embedded in your product page or retrieved from the endpoint.
FICTIONAL DEMO DATA. MESSARA, GTIN AND PART NUMBERS ARE INVENTED.
data.messara.com / v1 / products / MS-12011Open Data
GEThttps://data.messara.com/v1/products/MS-12011
200 OKapplication/ld+jsonNo auth42 ms · 3.1 kB
{
"@context": "https://schema.org",
"@type": "Product",
"sku": "MS-12011",
"gtin13": "4012345680011",
"name": "Flowline FL-40 DN40 PN16",
"brand": { "@type": "Brand", "name": "Messara" },
"countryOfOrigin": "DE",
"additionalProperty": [
{ "name": "nominalWidth", "value": "DN 40" },
{ "name": "pressureRating", "value": "PN 16" }
],
"dateModified": "2026-09-24",
"url": "https://data.messara.com/p/MS-12011"
}
// published by selection rule: public_catalog · 14 of 52 attributes
Versioned feeds
products-full.jsonv42 · 18.4 MBLIVE
products-delta.jsonv42 · 0.9 MBLIVE
products.csvv42 · 11.2 MBLIVE
catalog.bmecatv41 · 24.1 MBQUEUED
Discovery
/.well-known/openapi.json
/llms.txt
/sitemap-products.xml
Every feed carries a version, a publication date and a change summary.
06 · 06 · Licensing and change log
Clear terms. A traceable history.
Each dataset carries a licence field you set — an open licence such as CC BY 4.0, or your own terms of use. Consumers see what they may do with the data and whom to credit. Every publication run writes a change log: which records were added, changed or withdrawn, and when.
Licence and attribution per dataset, included in every feed and in the endpoint index
Change log per feed: added · changed · withdrawn, with record IDs and timestamps
Withdrawn products are marked as withdrawn, not silently deleted
Earlier feed versions remain retrievable for the retention period you configure
Public responses are cached and invalidated when a new version is published, so crawlers and partners don't hit your source systems.
Read-only with rate limits.
The public endpoint accepts GET only. Rate limits protect the service; partners who need more can receive a token for the entitled API.
On your domain.
Serve Open Data from a subdomain such as data.yourbrand.com with its own certificate — part of the tenant's custom domain setup.
08 · Pricing
Priced by catalog size, not by traffic.
up to 5,000 SKU
€1,800 / year
up to 25,000 SKU
€3,600 / year
up to 100,000 SKU
€6,000 / year
up to 500,000 SKU
€9,600 / year
Add-on to any PIM Gate version. EUR list prices, annual prepayment, excl. VAT. Above 500,000 SKU on request. Book Open Data, Digital Product Passport and ETIM & BMEcat together and save 20% on all three.
No. Only products, attributes and languages that match your selection rules and pass validation are published. Everything else — including prices, stock and customer-specific data — stays entitled.
Your web team embeds the JSON-LD per product page, either as a script tag loaded from the endpoint or rendered server-side. Many CMS and shop templates have a slot for structured data. If your site runs on Ibexa DXP or Drupal, Netgen can help with the integration.
We can't promise that, and nobody honestly can. Open Data ensures that authoritative, current and consistently structured data about your products is available in the formats these systems read. How they use it is up to them.
As current as your publication schedule. Changes from your PIM pass through the gate and are published on the next run — scheduled or triggered. Every release carries a version number and a change log.
Yes. Each feed is available as a full file and as a delta against the previous version, in JSON, CSV or XML.
Yes. You can define several datasets — for example a general public dataset and a richer one for registered planners — each with its own rules, languages and licence. Access to non-public datasets uses the entitled API with tokens.
That's your decision, ideally with your legal team. PIM Gate stores the licence and attribution you set and includes it in every feed and in the endpoint index.
Both are planned. GS1 Digital Link–compatible product URIs will connect Open Data with QR codes on packaging and with the Digital Product Passport. An llms.txt-style manifest will point AI agents to your datasets and licence.