GTIN, GLN, and CNP Attributes by category Publishing by channel

PIM · Product Information Management

PIM: consistent product information across every channel.

PIM (Product Information Management) is the discipline that centralizes each item's description, attributes, images, GTIN and commercial content and distributes that information to e-commerce, marketplaces, POS and catalogs. The 4MDG platform delivers PIM functions inside an MDM (Master Data Management) — which means the right product in every channel and, at the same time, tax, procurement and supplier master data under governance.

Trusted by 160 clients

NestléCarrefourGeneral MotorsHeinekenWhirlpoolHershey'sDasaSoftysJactoPanasonicIntelbrasiFoodNestléCarrefourGeneral MotorsHeinekenWhirlpoolHershey'sDasaSoftysJactoPanasonicIntelbrasiFood

Integrations

SAP ECC SAP S/4HANA SAP Ariba Oracle TOTVS Microsoft Dynamics Salesforce ServiceNow WMS and TMS Data lake and BI API REST IDoc, BAPI and file and other systems on demand
See architecture and integration →

Concepts

PIM, MDM, PXM, DAM and ERP: what each one is.

The acronyms overlap in vendor pitches. In practice, each one solves a piece of the problem — and it is the combination that gets the product to the customer correctly.

PIM — Product Information Management

Centralizes the product's commercial and technical information: description, attributes by category, hierarchy, GTIN, media and content for each channel. It is the source of what the consumer reads.

MDM — Master Data Management

Governs the company's master records: product, supplier, customer, material, service and reference data, with rules, approval, deduplication and an audit trail. It is the source of what the company operates on.

PXM — Product Experience Management

The experience layer: adapting the same product to the context of each channel, audience and campaign. It depends on a well-structured PIM to exist.

DAM — Digital Asset Management

Stores and versions product images, video and documents. It complements the PIM, which references these assets by SKU and by channel.

ERP

Executes the transaction: purchasing, inventory, invoicing. It consumes product data, but it was not built to standardize, enrich and distribute commercial content.

Talk to a specialist See the data domains →

We show where each layer fits in your current scenario.

PDM and PDS

Before publishing to any channel, the item needs to be described.

PDM and PDS are the descriptive standardization disciplines behind any PIM initiative. Without them, the channel receives free text dressed up as a catalog.

PDM

Descriptive standardization of materials

Describing each item in a unique, structured way: taxonomy by family, attribute templates, short and long descriptions generated by rule, units of measure, packaging and tax classification. It is what makes the product findable in the channel's search and in the warehouse.

See the PDM page →

PDS

Descriptive standardization of services

The same discipline applied to the service catalog: clear scope, units of measure, measurement criteria and tax linkage. Without it, "preventive maintenance" becomes thirty records, each with its own price and terms.

See the PDS page →

PDM feeds the PIM

Structured attributes in PDM are what fill filters, search and spec sheets in the channel. The PIM distributes; the PDM defines.

One standard, many destinations

The same standardized description serves e-commerce, marketplaces, POS, ERP and print catalogs, with no rewriting per channel.

Services are catalog too

Distributors and retailers sell installation, assembly and support: PDS treats these items with the same rigor as materials.

Standardize my catalog How AI standardizes descriptions →

The assessment measures how many items are missing attributes or off standard.

PIM or MDM

An MDM does what a PIM does — and what a PIM cannot reach.

Buying a PIM solves the storefront and leaves the rest of the master data out. Items still come in duplicated, without the correct product classification, with unapproved suppliers and no defined owner. 4MDG treats the product as master data: channel content and the operational record come from the same place.

PIM functions the platform delivers

A product model per category, with required attributes, value domains and assortment hierarchy.

Standardized descriptions generated by rule, with translation into English and Spanish.

GTIN, GLN and packaging hierarchy validated, with preparation for GS1 Brasil's CNP.

Spec sheet, packaging attributes, units of measure and image references per SKU.

Completeness per channel: the item is only published when it meets what that channel requires.

Distribution to e-commerce, marketplaces, POS, EDI and catalogs, via API or file.

What only MDM solves

Deduplication and golden record: the same product for every system, not one copy per channel.

Tax and procurement classification: NCM, UNSPSC, CST and cClassTrib with evidence for the tax team.

The item's supplier vetted, with certificates and sanctions checked at the source.

Workflow with approval levels, SLAs and returns with reasons, plus an audit trail for every field.

Governance with data owners and data stewards, policies and quality indicators per domain.

Governed publishing to SAP and other ERPs, WMS, CRM and the data lake — not just to the storefront.

Request a demo Solution for retail →

The same approved record feeds channels and systems.

Features

What the platform does with product information.

Everything configured in low-code, with no development: fields, rules, steps and permissions are set by your own team.

Material photo in the record

An image attached to the record and visible in the queue and reports, so the analyst can check the item being approved — and the channel receives the right media.

Machine learning in descriptions

ADAM reads the free text, builds the standardized description and splits attributes by family, learning from your catalog.

Product classification and UNSPSC suggestions

Tax and procurement classifications proposed item by item, with evidence for the tax team to validate before publishing.

Item approval

Approval status per record, with sign-off by authority level, returns with reasons and SLAs per step.

Search and deduplication

Phonetic and similarity search flags look-alike items before a new SKU is born, with a score and a suggested surviving record.

Translation and units

Descriptions in English and Spanish, normalized units of measure with conversion factors and packaging attributes.

Layouts per profile

Each team sees the columns that matter to it in the same work queue, with saved filters and export.

Automations and integrations

Publishing to ERP, e-commerce, marketplaces and the data lake via API or file, with reprocessing and logs.

Auditing and indicators

Who created, who changed, the previous value and attached evidence, with completeness and duplication indicators per category.

Vídeo: o Iris em funcionamento
Veja o Iris em funcionamento.
See the platform Capabilities and architecture →

Low-code configuration, with no dependence on development.

Retailers and distributors

From the spec sheet the supplier sends to the published product.

Resellers don't create the product: they receive information from hundreds of suppliers, in different formats, and must turn it into a reliable catalog. That is where master data stalls.

1. Receiving the supplier's data

Spreadsheet, portal or EDI: information enters through a single flow, with required fields enforced at the source and OCR when data arrives as documents.

2. Verification at the source

GTIN validated and enriched against the GS1 base, with the supplier's registration and standing verified in official sources.

3. Standardization and enrichment

Rule-based descriptions, attributes by category, translation, units of measure, packaging and tax classification with ADAM's support.

4. Deduplication

Look-alike items are flagged before becoming a new SKU, with a score and a suggested surviving record.

5. Approval by authority level

Sales, tax and category teams approve what falls to them, with SLAs per step and returns with recorded reasons.

6. Publishing per channel

The approved record goes to e-commerce, marketplaces, POS, ERP and catalogs, with the completeness each destination requires.

How many SKUs in your catalog are missing required attributes, lack a valid GTIN or are duplicated right now? The free assessment measures it in your base.

Free assessment of your base

What changes

Less time to publish, fewer returns, more conversion.

SKU time to market

Items stop waiting days for missing information: rules enforce fields at entry and the flow shows where each item is stuck.

Search that finds

Structured attributes feed the channel's filters and search. A product that can't be found doesn't sell.

Fewer returns and complaints

Correct spec sheets, units of measure and packaging reduce wrong purchases and exchanges.

One record, many destinations

A new channel or marketplace consumes the same approved record, with no spreadsheet rebuilt.

Free assessment of your base Consumer goods solution →

From supplier data to published product, in one flow.

Contact

Let's look at your data before proposing anything.

A specialist reviews your scenario and shows the current state of master data in your industry. No commitment.

+55 11 4113-2510 atendimento@4mdg.com.br

Av. Queiroz Filho, 1700, Torre E, Suites 715 to 718
Vila Leopoldina, São Paulo, SP, 05319-000

Your data is processed in accordance with LGPD.

Common questions

Questions about PIM