Option Name Integration Guide: Marketplaces, GTINs, And WMS Mapping

Option Name

The label for a variant selector, such as Size, Color, Flavor, Scent, Material, or Pack Size. When integrating catalogs with marketplaces, ERP, or a WMS, option names are the fields that must be translated, validated, and synchronized to keep SKUs, inventory, and listings accurate.

Integration failures often stem from mismatched option names or value formats. Marketplaces and shopping feeds might require specific attribute names and normalized values; your WMS expects attributes to map to product codes and pick lists. Create a mapping layer and validation rules to ensure your option names line up across every system in your stack.

Marketplace And Feed Requirements

Each marketplace has its own expectations:

• Google Merchant Center: Requires distinct fields for color and size in apparel and expects consistent value formatting; mismatches cause disapprovals.
• Amazon: Uses variation themes (e.g., Size, Color) and often requires sellers to use specific attribute names and controlled vocabularies for some categories.
• Other Marketplaces: Each platform may have category-specific required attributes — consult the marketplace docs and maintain a mapping file for each destination.

GTINs, Barcodes, And Variant Identification

Assigning GTINs (or EAN/UPC barcodes) is typically done at the variant level. That means each unique combination of option values should have its own GTIN when required. Follow these guidelines:

• Unique SKUs For Variants: Treat each option-value combination as a separate sellable unit with its own SKU and barcode when items differ materially.
• GS1 Guidance: Use GTINs per GS1 rules — assign at the item level that is priced and sold separately.
• Feed Mapping: Ensure your product feed includes the GTIN for each variant and that option names align with the variant's attributes.

WMS And ERP Mapping

Internal systems use option names to trigger specific operational behaviors:

• Putaway Rules: Pack size option values can determine case vs. piece putaway strategies.
• Pick Logic: Variant attributes may drive batch picking or wave logic (pick all Medium sizes together).
• Packaging Templates: Material or pack-size options can select the right box or polybag template automatically.

Technical Implementation Checklist

• Create A Canonical Schema: Define your internal option names and acceptable value lists; include data types and units.
• Build Translation Tables: For each target channel, map internal names/values to channel-required attribute names and controlled vocabularies.
• Validate On Export: Run schema validation when generating feeds to catch missing or non-standard option values before upload.
• Version Control: Track changes to option-name mappings and values so you can roll back or audit listing changes.

Example: From PIM To Marketplace

A manufacturer stores variants in a PIM with option names like "Fabric" and "Length." The marketplace requires "Material" and "Size." The integration layer translates Fabric→Material and Length→Size, converts values (e.g., "100% cotton" → "Cotton"), and appends GTINs per SKU. The WMS receives SKU-level data with Material and Size fields, enabling correct pick locations and packing rules.

In short, the Option Name is a cross-system anchor: standardize it in your PIM, translate it for each marketplace, and ensure your WMS and ERP reference the same attribute values to keep listings accurate and fulfillment predictable.