Skip to contentv0.1.0
PIMgate
// OPEN DATA2026

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.

Open Data publishingA governed catalog filtered by selection rules, published as JSON-LD, versioned feeds, a read-only API and a GS1 identifier, read by search engines, marketplaces and AI agents.Governed catalogFull catalog20,418 SKUsValidated · versioned · entitledmessara.pimgate.aiSelection rulesWhat is public6,204 publishedPer market · per categoryOutputsschema.org/ProductJSON-LD on every pageVersioned feedsJSON · CSV · XMLPublic read-only APIGET /v1/productsGS1 Digital LinkResolvable product URLllms.txt · AI endpointMachine-readable indexConsumersSearch enginesMarketplacesComparison portalsAI assistantsPartnersPublic data is a deliberate selection, never the whole catalog

Illustrative figures based on the fictional MESSARA demo catalog.

  1. 01

    Select.

    Define which products, attributes and languages are public — by category, market, lifecycle status or flag.

  2. 02

    Validate.

    Only records that pass your quality rules for the Open Data profile are published. Incomplete records are held, not exposed.

  3. 03

    Publish.

    PIM Gate generates JSON-LD, feeds and the public endpoint from the selection and versions every release.

  4. 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
SELECTION RULES
RULE 01  category IN [Pressure, Temperature, Level]   → includeRULE 02  lifecycle = "active" AND market IN [DE, AT, CH] → includeRULE 03  attribute.visibility = "internal"            → exclude fieldLANGUAGES  de-DE · en-GB · fr-FRRESULT     6'240 SKU · 38 attributes · 3 languages
PublicStays entitled
Name, description, dimensions, measuring range, materials, GTIN, images, data sheetList 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.

OutputWhat you getTypical consumerStatus
schema.org/Product JSON-LDOne JSON-LD document per product, embeddable in your own product pages (script tag or server-side include)Search engines, AI assistants2026
Versioned feedsFull and delta feeds in JSON, CSV and XML; every release numbered and retainedMarketplaces, comparison portals, wholesalers2026
Public read-only APIGET endpoints for products, categories and feeds; no write access; caching and rate limitsPartner systems, apps, AI agents2026
Product data sitemapMachine-readable index of all public product URLs and their last modification dateSearch engines, crawlers2026
GS1 Digital Link compatibilityProduct URIs in GS1 Digital Link syntax (/01/{GTIN}) that resolve to your public recordScanners, retail systems, DPPPLANNED
AI-agent indexA manifest in the style of llms.txt that points agents to your datasets, endpoints and licenceAI agents and assistantsPLANNED

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.

application/ld+json
// GET https://data.messara.com/v1/products/MS-12011?lang=en-GB// 200 OK · application/ld+json · dataset: messara-public · v2026.38{  "@context": "https://schema.org",  "@type": "Product",  "@id": "https://data.messara.com/id/MS-12011",  "sku": "MS-12011",  "mpn": "RF63-010-G14R",  "gtin13": "4260999120110",  "name": "Bourdon tube pressure gauge RF63, 0–10 bar, G 1/4 bottom",  "description": "Robust pressure gauge for heating and sanitary systems. Nominal size 63 mm, accuracy class 1.6.",  "brand": { "@type": "Brand", "name": "MESSARA" },  "manufacturer": {    "@type": "Organization",    "name": "MESSARA Mess- und Regeltechnik GmbH"  },  "category": "Pressure measurement > Bourdon tube pressure gauges",  "image": "https://data.messara.com/media/MS-12011/main.png",  "additionalProperty": [    { "@type": "PropertyValue", "name": "Measuring range",      "minValue": 0, "maxValue": 10, "unitCode": "BAR", "unitText": "bar" },    { "@type": "PropertyValue", "name": "Nominal size",      "value": 63, "unitCode": "MMT", "unitText": "mm" },    { "@type": "PropertyValue", "name": "Accuracy class", "value": "1.6" },    { "@type": "PropertyValue", "name": "Process connection", "value": "G 1/4, bottom" },    { "@type": "PropertyValue", "name": "Connection material", "value": "Brass, nickel-plated" }  ],  "subjectOf": {    "@type": "DigitalDocument",    "name": "Data sheet RF63",    "encodingFormat": "application/pdf",    "url": "https://data.messara.com/media/MS-12011/datasheet-en.pdf"  }}

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
GET /v1/feeds
// GET https://data.messara.com/v1/feeds{  "dataset": "messara-public",  "version": "2026.38",  "published": "2026-09-24T06:00:00Z",  "license": "https://creativecommons.org/licenses/by/4.0/",  "attribution": "MESSARA Mess- und Regeltechnik GmbH",  "languages": ["de-DE", "en-GB", "fr-FR"],  "records": 6240,  "changes": { "added": 112, "changed": 486, "withdrawn": 9 },  "changelog": "https://data.messara.com/v1/feeds/messara-public/changelog"}

07 · Operations

Public, but never unguarded.

Cached and fast.

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.

See full pricing →

09 · FAQ

Open Data

Put a gate between your catalog and chaos.