8 min read

Product Data Glossary: Key PIM, Ecommerce and Supplier Data Terms Defined

Plain definitions of the PIM, ecommerce and supplier data terms retail and distribution teams use, from attribute schema to variant axis.

Ben Adams

Ben Adams

Founder

Product Data Glossary: Key PIM, Ecommerce and Supplier Data Terms Defined

Plain definitions of the PIM, ecommerce and supplier data terms retail and distribution teams use, from attribute schema to variant axis.

This product data glossary defines the terms retail, distribution and ecommerce teams meet in product information management, supplier onboarding and catalogue enrichment. Each entry gives a short, standalone definition, from attribute schema and GTIN to taxonomy and variant axis. Where a term has a dedicated guide, the entry links to it, and the product catalogue enrichment software pillar ties the topics together.

How to use this product data glossary

Terms are grouped alphabetically under letter headings, and acronyms are listed by their short form. Each definition is one to three sentences, written to make sense on its own.

A

ACES and PIES

Two North American data standards for automotive aftermarket parts. ACES describes which vehicles a part fits, and PIES describes the part itself: dimensions, packaging, pricing and marketing copy. See ACES and PIES explained.

Answer engine optimisation (AEO)

Structuring product content so AI assistants and answer engines can read, trust and quote it. It depends on complete attributes, clear specifications and consistent identifiers more than on keyword-heavy copy. See answer engine optimisation for products.

API (application programming interface)

A defined way for two systems to exchange data and trigger actions in each other. In product data, APIs connect a PIM to a commerce platform, a supplier feed to an ERP or a marketplace to a catalogue. See the integrations overview.

Attribute

A single property of a product, such as colour, voltage, material or chuck size. Some attributes apply to every product (brand, weight), while others belong to one category. See the guide to product attributes.

Attribute extraction

Pulling structured attribute values out of unstructured sources such as PDFs, images and web pages. A datasheet line reading "18V, 2.0Ah, 1.4kg" becomes three separate values. See extracting product attributes from PDFs.

Attribute normalisation

Converting equivalent attribute values into one accepted form, so "12V", "12 volts" and "12 Volt" all become 12 V. Without it, filters show duplicate options and reporting splits one value into several. See data normalisation.

Attribute schema

The definition of which attributes each category requires, with data type, unit, allowed values and whether each is mandatory. It is what makes a catalogue filterable and measurable. See schema and attributes.

B

BMEcat

An XML format for exchanging electronic product catalogues between suppliers and buyers, developed in Germany under the BME purchasing and logistics association. It is common in European B2B and technical distribution and can carry ETIM classification. See what BMEcat is.

Bulk onboarding

Loading hundreds or thousands of products in one batch from a spreadsheet, BMEcat file or supplier feed. The hard part is rarely the load itself. It is making sure the records arrive classified, consistent and complete. See bulk SKU imports.

C

Catalogue completeness

The share of required attributes holding valid values, usually measured per category and per channel. If a category needs 30 attributes and a product has 24, it is 80% complete. See the causes of incomplete product data.

Catalogue enrichment

Bringing a whole catalogue up to channel-ready quality: classifying products, filling missing attributes, normalising values and adding content. It is usually run continuously at intake rather than as a one-off project. See product catalogue enrichment software.

Catalogue management

The operating process of bringing products into a catalogue, keeping records complete, publishing them to channels and retiring them. American sources spell it catalog management. See the guide to product catalogue management.

Category

A grouping of related products within a taxonomy, such as Power Tools > Drills > Combi Drills. Categories shape navigation, filters and reporting, and decide which attributes a product needs.

Channel

A destination where product data is published, such as a webstore, Amazon, Google Shopping or a B2B portal. Each channel has its own required fields, image rules and category tree. See ecommerce sync.

Classification

Assigning a product to a category in a taxonomy or external standard. It can be manual or automated from the product's title, description and attributes. See automatic product categorisation.

Cleansing (data)

Fixing errors, duplicates and gaps in existing product data. Typical jobs include removing duplicate records, correcting units, stripping HTML from descriptions and filling blanks.

Completeness score

A percentage showing how many of a product's required attributes are filled with valid values. Scores roll up by category, supplier and channel to show where enrichment effort should go. See measuring completeness by category and channel.

Content generation

Producing product titles, descriptions and bullet points from structured attributes, usually with AI and a brand voice prompt. Output quality depends on the attributes underneath it. See content generation.

Controlled value list (LOV)

A fixed list of allowed values for an attribute, also called a list of values or picklist. Colour might allow Black, White and Grey but not "blk" or "Jet Black". See turning free text into controlled value lists.

Country of origin

The country where a product was manufactured, needed for customs, tariffs and many marketplace listings. It should be stored as an ISO 3166-1 country code rather than free text such as "Made in PRC".

D

DAM (digital asset management)

A system for storing, tagging and distributing media files such as images, videos and PDFs. It handles the files, while a PIM handles the product records that reference them. See PIM vs DAM vs MDM.

Data governance

The rules, ownership and approvals that control how product data is created and changed. It answers questions such as who owns the colour attribute and who can add a category.

Data normalisation

Standardising values, units and formats across a catalogue so equivalent data looks the same everywhere. It covers units of measure, value spellings, number formats and casing. See the guide to product data normalisation.

Data quality

How fit for purpose product data is, usually split into completeness, accuracy, consistency and timeliness. Each dimension needs its own measure. See product data quality.

Datasheet

A manufacturer document, usually a PDF, listing a product's technical specifications. It is the main source for technical attributes and the usual starting point for extraction. See product data extraction.

Digital product passport

A structured digital record of a product's composition, sustainability and circularity data, introduced in EU law under the Ecodesign for Sustainable Products Regulation. Requirements apply product group by product group. See digital product passports.

Digital shelf

All the places customers find and buy products online: own site, retailer sites, marketplaces and search results. The term is most common in consumer brands.

DTC (direct to consumer)

A model where a brand sells straight to end customers without a retailer or distributor in between. DTC catalogues tend to be smaller and lean more on imagery and brand copy than on technical standards.

E

EAN (European Article Number)

The former name for the GS1 barcode numbers now called GTIN-13 and GTIN-8, used for retail products across most of the world. EAN-13 is the familiar 13-digit supermarket barcode. See product identifiers: GTIN, UPC, EAN and MPN.

End node

The lowest level of a taxonomy branch, where products are actually classified. Also called a leaf node or product type, it carries the most specific attribute set.

ERP (enterprise resource planning)

The business system for finance, stock, purchasing and orders, such as SAP, Microsoft Dynamics or NetSuite. It usually masters cost, price and stock, but is poorly suited to marketing content and media.

ETIM

A classification model for technical products, maintained by ETIM International. Product classes sit in groups, and each class defines features with units or fixed value lists. See what ETIM is.

F

Faceted search

Search that lets shoppers narrow results with filters on attributes such as brand, voltage or IP rating. It only works when values are complete and normalised within each category. See faceted search for distributors.

Feed

A structured file, such as CSV, XML or JSON, that carries product data from one system to another on a schedule. Feeds are simple but brittle: an unannounced column change can break an import. See syncing product data.

Fitment data

Data stating which vehicles, machines or equipment a part fits, typically by year, make, model and engine. Customers buy on fitment first, so errors cost sales directly. See fitment data.

G

GDSN (Global Data Synchronisation Network)

A GS1 network of certified data pools through which suppliers publish product data once for retailers to subscribe to. It is strongest in grocery and healthcare supply chains.

Golden record

The single, trusted version of a product record built by merging data from the ERP, suppliers and other sources. Rules decide which source wins for each attribute. See bringing ERP, PIM and supplier data together.

Google product category

A category from Google's own product taxonomy, used in Merchant Center feeds. Google lists the attribute as optional and assigns a category automatically, while your own classification goes in product_type. See Google Merchant Center product data.

GS1

The not-for-profit standards organisation behind barcodes, GTINs, GPC and GDSN. It runs national member organisations, such as GS1 UK, that issue company prefixes.

GS1 GPC (Global Product Classification)

A GS1 classification with four levels: segment, family, class and brick. Each GTIN is classified to one brick, and bricks carry attributes with predefined values. See mapping products to GS1 GPC.

GTIN (Global Trade Item Number)

The GS1 identifier for trade items, in four structures: GTIN-8, GTIN-12, GTIN-13 and GTIN-14. UPC, EAN and ISBN numbers are all GTINs. See the guide to GTINs and other identifiers.

H

Hallucination (in AI)

An AI model producing a confident answer that is wrong, such as an invented specification value. Confidence scores, source references and human review of low-confidence output catch most cases. See product data extraction accuracy.

Headless commerce

An architecture where the storefront is separate from the commerce engine, PIM and order systems, connected by APIs. It is the H in MACH.

Hero image

The main image on a product page or listing, usually the full product on a clean background. Marketplaces often set strict rules for it, such as a white background.

HS code (Harmonised System code)

A customs classification code whose first six digits are set internationally by the World Customs Organization. Countries add further digits for their own tariffs and statistics.

I

Image metadata

Structured information attached to an image, such as alt text, file name, dimensions and the view shown. It supports accessibility, image search and channel rules.

Integration

A connection that moves data automatically between two systems, by API, scheduled feed or event-driven webhook. Common examples connect a PIM to a webstore or a supplier portal to a PIM. See PIM integration.

J

JSON-LD

A format for embedding structured data in web pages using the schema.org vocabulary, such as Product, Offer and AggregateRating. Search engines read it to show prices, stock and ratings in results.

K

Kit

Several products sold together under one SKU, such as a tool kit or fixings pack. The kit has its own price and stock, and references its components.

L

Lead time

The time between an order being placed and the product being ready to ship. B2B buyers often decide on lead time as much as on price.

Line card

A list of the brands or manufacturers a distributor carries, often used as a sales one-pager. The underlying data sits in the distributor's catalogue.

LOV (list of values)

See controlled value list.

M

MACH architecture

An approach to commerce technology built on microservices, API-first, cloud-native and headless principles. Components can be swapped individually, at the cost of more integration work.

Mapping

Translating data from one structure to another, such as supplier categories to your taxonomy or your attributes to a marketplace's fields. Each source needs its own maintained map. See product attribute mapping.

Marketplace

A platform where many sellers list products, such as Amazon, eBay or a Mirakl-powered site. Each has its own taxonomy, required attributes and content rules. See marketplace syndication.

Master data

The agreed core record for a product, customer or supplier that other systems copy from. Deciding which system masters which fields is an early decision in any data programme.

MDM (master data management)

The discipline and software for managing master data across entities such as products, customers and suppliers. A PIM is a product-focused form of master data system. See how PIM, DAM and MDM differ.

Metafield

A custom field in Shopify used for data beyond the standard fields, such as technical specifications or warranty period. Typed metafields are what make a Shopify catalogue filterable. See Shopify integration.

Migration (data)

Moving product data from one system or structure to another, such as a replatform or PIM go-live. The work is in mapping and cleaning, not copying. See cleaning legacy data before a PIM.

MPN (manufacturer part number)

The identifier a manufacturer assigns to its own product. Trade buyers and engineers search by it, and many marketplaces ask for it alongside the GTIN.

N

Normalisation

See data normalisation and attribute normalisation.

NPI (new product introduction)

The process of taking a new product from range decision to live, sellable listing. It spans supplier data collection, enrichment, approval and publishing. See the new product introduction process.

O

OMS (order management system)

The system that captures, allocates and fulfils orders, sitting between the storefront and the warehouse. It reads product data so picking lists and confirmations show the right variant.

Onboarding

Bringing a new supplier, range or product into the catalogue, from first data file to live listing. The bottleneck is usually getting supplier data into usable shape. See supplier onboarding software.

P

Parent product

The shared record that groups variants, such as a T-shirt style that exists in several sizes and colours. It holds the common data, while each variant holds what differs.

PDP (product detail page)

The web page for a single product, with images, description, specifications, price and add to basket. Gaps in product data show up here first.

PIM (product information management)

A system for storing, governing and distributing product records across channels. A PIM holds what it is given and does not create missing data on its own. See the guide to PIM software, or SKULaunch's built-in PIM layer.

Product data

All the information that describes a product: identifiers, attributes, descriptions, media, classifications and prices. Its quality affects search, conversion and returns. See the cost of bad product data.

Product data enrichment

Adding missing attributes, improving content and bringing supplier data up to channel-ready quality. It is the work between a supplier spreadsheet arriving and a complete live listing. See product data enrichment.

Product record

The full set of fields, attributes, media and classifications describing one product in a system. A technical distribution record may carry 200 fields or more.

Q

Quality metrics (data)

The measures used to track product data quality, such as completeness, valid-value rate and records updated in the last 90 days. They turn "better data" into something trackable. See completeness by category and channel.

R

Rich snippet

An enhanced search result showing extra details such as price, stock status or star rating. It relies on structured data on the page and accurate data underneath.

RoHS

An EU directive restricting certain hazardous substances, such as lead and mercury, in electrical and electronic equipment. Distributors record compliance per SKU, often with a declaration document.

S

Schema

In product data, shorthand for the attribute schema: the rules for what fields a record can hold, their types and allowed values. See attribute schema.

SEO (search engine optimisation)

Structuring pages and content so they rank in search engines. For product pages it covers titles, descriptions, alt text, structured data and the attributes behind filters.

SKU (stock keeping unit)

An internal identifier for one sellable item, at the level that is stocked and priced. A T-shirt in three sizes and four colours is twelve SKUs.

Spec sheet

A short document listing a product's key specifications, often used interchangeably with datasheet. Spec sheets are a common source for extraction and a common output for trade customers. See the guide to product spec sheets.

Specification

A named technical property with a value and often a unit, such as torque 60 Nm or IP rating IP65. Specifications are the attributes engineers and trade buyers compare on.

Standards

Shared formats and vocabularies for exchanging product data, such as GS1, ETIM, UNSPSC and BMEcat. Adoption varies by sector.

Supplier

The manufacturer, brand or distributor that provides products. Suppliers send data as spreadsheets, PDFs, BMEcat files or portal entries, with widely varying quality. See supplier data onboarding.

Supplier portal

A web interface where suppliers submit and update product data against your required fields and rules. It replaces the email and spreadsheet loop. See what a supplier portal is.

Syndication

Sending product data from one master source to many channels, each in its own required shape. It includes validation per channel and handling rejections. See syndication to marketplaces.

T

Taxonomy

The hierarchy of categories used to classify products, from departments down to end nodes. It decides each product's attribute set and shapes navigation, filters and reporting. See the guide to product taxonomy.

Template

A predefined spreadsheet suppliers fill in to submit product data. Templates often fail because suppliers edit, skip or misread them. See supplier data templates.

Time to list

The time from supplier data arriving to a sellable record going live on a channel. Also called time to live, it measures the whole onboarding pipeline rather than a single step.

U

UDI (unique device identification)

A system for identifying medical devices, run in the United States by the FDA and in the EU under the Medical Device Regulation. It requires specific identifiers and device data submitted to official databases.

Unit of measure

The unit attached to a numeric value, such as mm, kg or W. Mixed units across suppliers break filters and comparisons, so units are normalised to one per attribute. See normalising units of measure.

UNSPSC

The United Nations Standard Products and Services Code, an eight-digit classification used in procurement and spend analysis. Its four levels are segment, family, class and commodity. See what UNSPSC is.

UPC (Universal Product Code)

The 12-digit barcode number used mainly in North America, now called GTIN-12. It can be padded with a leading zero to 13 digits without changing the check digit.

V

Validation

Checking data against defined rules before it is accepted, such as a required field, an allowed value or a valid GTIN check digit. Most quality problems trace back to weak validation at intake. See validation rules on attributes.

Variant

One specific version of a parent product, differing by size, colour or another axis. Variants share the parent's description and category but carry their own SKU and identifiers. See product variants.

Variant axis

The attribute that distinguishes variants of the same parent, such as size, colour or length. Choosing the right axes per category decides how a range displays and filters.

How this product data glossary is maintained

The glossary is reviewed twice a year. New terms are added as they become standard in retail and distribution, and existing definitions are updated when standards such as ETIM, GS1 GPC or UNSPSC publish new versions.

Product data glossary FAQs

What is product data?

Product data is all the information that describes a product so it can be found, compared and bought. It includes identifiers such as GTIN and MPN, attributes such as size and voltage, descriptions, images and documents, categories and prices. Retailers and distributors usually receive it from suppliers, then classify, enrich and publish it to their webstore, marketplaces and other channels.

What is the difference between an attribute and a specification?

An attribute is any structured property of a product, including brand, colour, material or country of origin. A specification is a technical attribute with a value and usually a unit, such as torque 60 Nm or IP rating IP65. Every specification is an attribute, but not every attribute is a specification. Trade buyers mostly compare on specifications.

What is the difference between a GTIN, an EAN and a UPC?

GTIN is the umbrella term for GS1 product identifiers, which come in 8, 12, 13 and 14-digit structures. UPC is the 12-digit form used mainly in North America, now called GTIN-12. EAN-13 is the 13-digit form used across most of the world, now called GTIN-13. A system that stores GTINs should accept all four lengths.

What is the difference between a taxonomy and an attribute schema?

A taxonomy is the hierarchy of categories products are classified into, such as Power Tools then Drills then Combi Drills. An attribute schema defines which attributes each category requires, with types, units and allowed values. The two are designed together: classifying a product into an end node determines which attributes it needs and which filters it appears in.

Key takeaways

  • A shared product data vocabulary prevents the same field being defined three ways by three teams.
  • Taxonomy, attribute schema and controlled value lists are the structural core. Most other terms describe work done against them.
  • Identifiers (GTIN, UPC, EAN, MPN) and classifications (ETIM, GS1 GPC, UNSPSC) are different things and live in different fields.
  • Completeness, validation and time to list are the measures that turn data quality into something trackable.
  • PIM, DAM, MDM and enrichment tools each cover a different part of the job, and most catalogues use more than one.

See SKULaunch in action

Watch how we handle AI enrichment, supplier onboarding, and catalogue scale in a live 30-minute demo.

Book a free demo →

NEWSLETTER

Get this in your inbox

Fortnightly. The best thinking on product data ops, straight to you.

Subscribe free

SKULAUNCH PLATFORM

See how it works

Watch AI enrichment and supplier onboarding in a live demo.

Book a demo →
© 2026 SKULaunch Ltd. All rights reserved.
Built for e-commerce teams who are done doing it by hand.