Brand & Manufacturer Matching

Who Actually Makes This?

Every supplier, distributor and feed names brands and manufacturers its own way: a trading name here, a legal entity there, an abbreviation or a subsidiary somewhere else. Questions about sourcing, sustainability or concentration need the real company, and the product data never says it consistently.

Products By ManufacturerWithout an identity layer
supplier_a.feedUnileverDove, Hellmann’s · 214 SKUsManufacturer 1
supplier_b.feedUnilever PLCKnorr · 96 SKUsManufacturer 2
distributor.feedUNILEVER UK LTDBen & Jerry’s · 41 SKUsManufacturer 3

Three manufacturers in the report. It is one company, and its share of your range is three times what it looks.

The Problem

One Company, Many Names

Product data names the company behind a product in whatever way the source chose. One feed has the consumer brand, another the parent company, a third the local legal entity with “Ltd” or “GmbH” on the end. Abbreviations, typos and old names after a rebrand add more variants.

That breaks every question asked at company level. How much of the range comes from one manufacturer? Which products are covered by a supplier’s sustainability commitments? Where are you exposed if a single company has a problem? Each answer is too low, because the company is split across several names.

Claims and certifications make it harder. They are made by a company, about its products, and they only reach the right products if the company in the claim and the company in the product data are recognised as the same.

Split Companies

One manufacturer appears under brand, parent and legal-entity names.

Understated Concentration

Dependence on a single company is spread across names and looks smaller.

Claims That Do Not Attach

Sustainability and sourcing claims miss products listed under another name.

The Solution

Resolve The Company Behind Each Product

Resolve brand and manufacturer names as entities in their own right. Match them across every feed on name, address, registration details and the brands they own, so each company has one ID however a source writes it.

Then link products to that company ID. Reporting by manufacturer, claims made by a company and risk checks on a supplier all reach every product the company is behind.

One Manufacturer
Names in product data3 records
supplier_a.feedUnilever214 SKUs
supplier_b.feedUnilever PLC96 SKUs
distributor.feedUNILEVER UK LTD41 SKUs
Zingg
Resolved company1 entity
ZINGG_ID · c4d8-0b31Resolved
Unilever
supplier_a.feedsupplier_b.feeddistributor.feed

351 products now roll up to one manufacturer for sourcing and sustainability reporting.

One ID Per Company

Brand, parent and legal-entity names for the same company share one ID.

Products Linked To It

Every product points to the resolved company, whatever its feed said.

Claims Reach Every Product

A company’s certifications apply to all of its products.

Where Zingg Sits

The Identity Layer Under Product 360

Zingg runs as a workload inside your data platform and gives every entity one persistent ZINGG_ID. Everything above it reads the same resolved entities.

Used by
BI & dashboardsAI agents & RAGOperational appsReverse ETLData science
Your data platform
DatabricksSnowflakeMicrosoft FabricGCPAWS

The same layer powersCustomer Analytics & MarketingFinancial Crime & RiskPrivacy & ComplianceSupply Chain & ProcurementMaster Data ManagementAI & Data Foundations

Brand Matching With Zingg

Company Name Matching

Built-in handling for abbreviations and legal suffixes like Ltd, PLC and GmbH. Company name matching

Persistent ZINGG_ID

Each manufacturer keeps one ID across every feed and run. ZINGG_ID

Any Entity Type

Resolve products and the companies behind them in the same platform.

In Practice

See how Provenance resolves brands and products for sustainability claims. Read the story

FAQ

Brand & Manufacturer Matching Questions

Why match brands and manufacturers separately from products?

Because questions about sourcing, sustainability and risk are asked about companies. Resolving the company gives every product a reliable link to who is behind it.

Can Zingg tell a brand from its parent company?

Zingg resolves records that refer to the same entity. You decide what the entity is, for example the legal manufacturer, and label examples so Zingg learns that definition.

Does it handle legal suffixes and abbreviations?

Yes. Company name matching handles suffixes like Ltd, PLC and GmbH and common abbreviations.

Where does the matching run?

Inside your data platform: Databricks, Snowflake, Microsoft Fabric, Google Cloud or AWS.

Know The Company Behind Every Product

Resolve brands and manufacturers across your product data in your own data platform.