Product Data for Collectible Figures: Series and Variants

A single character in a popular license can exist a dozen times over on your shelf: the base figure, a chase variant, a convention exclusive, a glow-in-the-dark edition, a re-color, a different scale. Each one is a separate article with its own EAN/GTIN — and almost identical text. That is the defining shape of the collectible-figures assortment, and it is why the category behaves nothing like the rest of the toy shop.

Product data for collectible figures is defined by series and variant logic: license, series, character, edition and scale. Collectors search and filter by exactly those attributes — not by article number — so the whole job is to capture that structure cleanly. This is a sub-category of the broader toy retail challenge, and it is the sharpest example of variant longtail anywhere in toys.

What makes product data for collectible figures so difficult?

The core problem every multi-supplier retailer knows — no two suppliers deliver alike — is intensified here by the sheer variant density:

• Variant families: one character spawns base, chase, exclusive, re-color and scale variants — each a distinct SKU with its own EAN/GTIN but near-identical copy.
• License-first search: buyers look for a license and a character (Marvel, Star Wars, a specific anime), so license, series and character must be structured attributes, not words in a title.
• Fast release cadence: new waves, pre-orders and exclusives drop weekly, often as a supplier Excel or a PDF wave sheet weeks before availability.
• Many small labels: the assortment spans dozens of manufacturers and importers, each with its own column layout and naming — soft, inconsistent data by default.

Done by hand, every wave means re-typing the same distinctions across dozens of near-duplicate rows. The fix is the same as everywhere else: consolidate, normalize, enrich and publish — here with variant structure at the center.

Which standards help — and where do they stop?

Collectible figures do have one reliable anchor: the GTIN/EAN, which uniquely identifies each variant and lets you match and dedupe records. Beyond identification, though, no classification standard carries the attributes that actually matter here. ETIM and eCl@ss were built for technical trade; they do not model license or character. Here is the honest split:

In short: the GTIN identifies the variant, but everything that makes it findable and desirable — license, series, character, edition, scale, collector context — has to be built from raw manufacturer Excel and PDF. That is the gap.

How does Productbay help with collectible figures?

The throughline is a three-step job with variant structure at its heart — and that is exactly what Productbay is built for:

• Consolidate: import every source once — supplier Excel, CSV, feed URL, FTP, API — and match by SKU or EAN/GTIN so pre-orders and restocks update in place and new waves are created cleanly.
• Enrich: AI parses license, series, character and edition out of titles and PDF wave sheets, writes descriptions, assigns categories, fills gaps from whitelisted sources and translates via DeepL — always with a review queue before publishing. Attribute groups let you model a character once and hang all its variants off shared attributes, so the storefront gets real filters instead of a wall of near-duplicates.
• Publish: two-way sync to Shopify and Shopware, ERP connections (Xentral, weclapp) and feed exports for Amazon, OTTO and Kaufland — each with per-channel transformations.

Productbay starts where the standards end: it turns the license-and-variant longtail into structured, filterable data instead of a spreadsheet grind. For the full category picture, see product data in toy retail. It is built for specialist retailers running multi-supplier, multi-channel catalogs — from a focused collector shop to a large chain.

Frequently Asked Questions