Product types and taxonomy versions

How marketplace schemas are versioned, what triggers a new version, and why the field reference always shows the current one.

Marketplace schemas change. A product type that required eight fields last quarter may require ten now, with two of last quarter's renamed. MarketplaceHub handles that by versioning the taxonomy rather than overwriting it.

What a version is

A product type version is one marketplace product type, for one marketplace and country, as it stood at one import. It holds the field list — which fields exist, which are required, what each means and what an accepted value looks like — plus the marketplace's own schema version string.

How versions are created

A recurring taxonomy import pulls product types and categories from each connected marketplace. When it finds a schema that differs from the stored one it creates a new version and activates it; the previous version stays until it is pruned.

Two consequences worth knowing:

• A new version does not invalidate your listings. Existing listings keep working against the version they were built on until they are next published.
• The required-field list you build against should be the current one. This is why the field reference always reads the latest version and offers no version picker: a superseded field list is a list of fields the marketplace may already have stopped accepting.

Why a product type may have no fields yet

If the field reference tells you a product type has not been imported, its taxonomy import has not completed for that marketplace and country. It resolves on its own once the next import finishes — there is nothing to configure.