Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Emporix Product Data

Use the emporix-product-data skill to onboard and sync products, categories, availability, prices, and media.

Use the emporix-product-data skill to onboard or sync a catalog into Emporix. A sellable product is assembled from the Product, Category, Catalog, Availability, Price, and Media services. There is no single import call.

This page explains when to use the skill and how to work with it. For the product model and related setup, see Products, Availability and Stock Levels, and Pricing.

Skill details

Property
Value

Skill name

emporix-product-data

Package path

skills/emporix-product-data/ (contains SKILL.md)

Install it once using Installing skills.

When to use it

Use this skill when you need to:

  • Import a catalog from a PIM or ERP

  • Create products or variants, including the choice between dynamic and template variants

  • Set stock and availability, prices or price lists, and product images

  • Assign products to categories

  • Diagnose availability, stock, or prices that do not show on the storefront

For tokens and scopes, use the Emporix Auth skill. For custom fields on products, use the Emporix Extensibility skill. For the exact endpoint or schema, use the Emporix Docs Navigation skill.

How it works

Create records in reference order. Configuration that other calls point at comes first, then the product, then the services that reference the product id.

Base URL: https://api.emporix.io. Tenant names are lowercase.

For stock and variants to appear on the storefront, use these rules:

  • Write availability to a real site code. main is a read-only aggregator and does not hold per-site stock.

  • For a PIM-led sync, use DYNAMIC_VARIANT, then a recalculation job. Template variants force parent-template edits before children can load.

Prerequisites

Before you use this skill, make sure you have:

  • A custom API key with the manage scopes for the services in the pipeline – do not guess scope names

  • At least one site whose code is not main. For the verification steps in the skill, use two such sites.

  • A currency, a tax configuration with tax classes, and a price model for priced products

  • A service access token – see Emporix Auth

How to use it

After install, work in your AI tool with natural-language requests. Examples:

Import this product into tenant mytenant on site store-de, with stock, a gross price, and one image.

Why is imported stock invisible on the storefront when the availability call returned 201?

Should this PIM catalog use dynamic variants or template variants?

Provide the tenant name, the real site code, and the scopes on your token.

Usage notes

  • Never write availability to main. If main already holds stock rows, contact Emporix staff. Do not try to repair it with another POST.

  • After a dynamic-variant bulk import, run product recalculation and wait until the job is finished before you read the parent variants map.

  • Send Content-Language: * when you create localized fields as language maps. Without it, the API returns 400. If you name a single language, send plain strings instead.

  • For a dynamic-variant import, set each product id yourself, for example the ERP SKU, so a child can reference its parent before the parent exists.

  • A BLOB media upload is limited to 30 MiB of total request body. Larger requests fail with 413 from the API gateway.

  • A price that does not match is usually a site, currency, or location restriction, or a price list that overrides the catalog price.

  • Key taxClasses on a configured country code, such as DE, not on a language code.

Last updated

Was this helpful?