Same product, three suppliers, three SKUs
Each supplier feed brings the same drill bit under a different SKU and a different attribute set. Procurement and merchandising see three products, customers see one — and pick wrong.
Retail / DIY — DACH
Hundreds of suppliers, millions of SKUs, mismatched ETIM. Your catalog cleaned, GS1-validated, and consumable through one API.
Standards & catalogs we work with
Five pains we keep seeing
Every retailer with 100,000+ SKUs across multiple suppliers we've talked to runs into some version of these. Most are data problems wearing operational clothes.
Each supplier feed brings the same drill bit under a different SKU and a different attribute set. Procurement and merchandising see three products, customers see one — and pick wrong.
Half the catalog isn't ETIM-classified. The half that is, is partially wrong. Filtering breaks. Search breaks.
Old GTINs, recycled GTINs, mistyped GTINs. Returns track back to GTIN errors more often than you'd think.
One brand uses parent/child variants properly. Three don't. Your catalog system squashes them. Your customers see noise.
Procurement systems want OpenAPI. Marketplaces want feeds. AI procurement (the new buyer) wants typed JSON with provenance. Spreadsheet exports don't cut it anymore.
How it composes
Supplier feeds come in as they are — BMEcat, ETIM CSV, JSON, FTP. Meshbase dedupes, classifies to ETIM, validates GTINs, and exposes the cleaned graph through one governed surface.
Suppliers → Import → Dedupe → ETIM-class → GS1 → API.
What it looks like
Once your catalog is in, e-procurement systems and AI buyers query it through the same governed surface — typed, audited, rate-limited, and policy-checked.
Plain HTTP under `/rest/v1`. Lowest-friction option for marketplaces, e-procurement portals, and B2B buyers on legacy stacks.
bash
# Cordless drills, ETIM-class EC000123, in stock
curl -H "Authorization: Bearer $KEY" \
"https://api.meshbase.ai/rest/v1/products?etimClass=EC000123&inStock=true" \
| jq '.data[] | {sku, gtin, brand, etimClass, etimAttributes}'Federated GraphQL across catalog, inventory, and pricing. Best when partners need precise field selection and typed cross-domain queries.
graphql
query CordlessDrills($etim: String!) {
products(etimClass: $etim, inStock: true, first: 50) {
nodes {
id
sku
gtin # validated GTIN (GS1)
brand { name }
etimClass
etimAttributes # cleaned, classified attributes
variants {
sku
priceTiers
}
}
}
}Model Context Protocol — AI buying agents call your catalog as a typed tool, under the same caller-governance and audit as a human partner.
json
{
"tool": "search_products",
"arguments": {
"etimClass": "EC000123",
"filters": { "inStock": true },
"limit": 50
}
}Two sides, one platform
Most retailers and B2B platforms are both. Meshbase keeps the two sides separated where it matters (governance, billing) and unified where it helps (data model, API surface).
01 · If you have data
You're a wholesaler, retailer, or distributor. Your catalog is your competitive surface — make it queryable and partner-ready.
02 · If you need data
You're an e-procurement system, marketplace, or AI procurement agent. Subscribe to verified provider catalogs without scraping or stitching.
Retail FAQ
Catalog cleanup that pays for itself
Email, contact form, or LinkedIn. We respond within one business day and don't waste your time with a generic deck.