Skip to main content

GS1 data lookup

Look up official GS1 product data by GTIN/EAN inside an AI Workflow and use it to complete and standardize your catalog.

Elovate can look up product data in GS1 directly from an AI Workflow. GS1 is the global organization behind barcodes (GTIN/EAN). Brand owners register their products with GS1, so the data there comes from the source instead of from a reseller or a supplier spreadsheet.

With GS1 lookup you use that registered data to fill gaps, check existing values and give your catalog one consistent basis.


What GS1 lookup does

For every product in the workflow scope, Elovate uses the product's GTIN/EAN to find the matching record in GS1. The data that comes back is used by the workflow to fill or check attributes in Elovate.

Depending on what the brand owner has registered, GS1 data can include:

  • brand name

  • product description

  • product category (GPC)

  • net content and unit of measure

  • product image

  • country of sale

Not every product has a complete GS1 record. When a value is not available, the workflow leaves the attribute as it is.


Why use GS1 data

  • Reliable source – data comes from the brand owner, not from a copy of a copy.

  • Fewer gaps – fill missing brands, contents and categories without manual research.

  • Consistency – the same product gets the same values, whichever supplier delivered it.

  • Better feeds – correct GTINs and brands improve Google Shopping and marketplace listings.


Requirements

  • Products need a valid GTIN/EAN in Elovate. Products without one are skipped.

  • GS1 lookup must be available for your account. If you don't see it in your workflows, contact Elovate support.


Using GS1 lookup in a workflow

  1. Open the workflow, or create a new one.

  2. Set the scope to the products you want to check, for example new products or one category.

  3. Add the action that uses GS1 lookup and select the attributes it should fill.

  4. Test the action on a few products and review the results.

  5. Run the action.

As with every workflow action, results go through moderation when that is enabled. Values only sync to Magento after they are approved.


GS1 and standardization

GS1 data is a strong starting point, but it doesn't always match the format your webshop uses. A brand can be written in capitals, a content can be "500 ML" where your filters expect "500 ml".

Combine GS1 lookup with Standardization to bring the values into your own format. See the article Standardizing values and terminology.


Example workflow

A webshop imports new products from several suppliers. Brands and contents are missing or written differently per supplier.

  1. Trigger selects new products with a GTIN

  2. GS1 lookup fills brand, net content and category

  3. Standardization brings units and brand names into the shop's format

  4. Content Enrichment writes the product description

  5. Translation creates the other storeviews

  6. Approved data syncs to Magento


Best practices

  • Check your GTINs first: a wrong or missing GTIN means no match.

  • Start with a small group of products and compare GS1 values with your current data.

  • Decide per attribute whether GS1 may overwrite existing values or only fill empty ones.

  • Use moderation for the first runs, so you see what changes before it goes live.

Did this answer your question?