Skip to content

Jewelry · Structured data

Jewelry GTIN and Hallmark on Shopify

One-of-one and custom jewelry rarely has GTIN. The Shopify Barcode field2 stays empty for most artisan inventory — which is fine, because Catalog reads the substitute structured signal from material, metafields, and Product schema additionalProperty3 when it exists. The install populates hallmark, metal purity, gemstone grading, and certification authority into those fields. For certified diamonds, the GIA or AGS report number can occupy the Barcode field as the trade-item equivalent — a one-of-a-kind workaround that satisfies the field without misrepresenting the inventory.

Published

Why GTIN is usually empty for jewelry

GTIN exists for mass-produced products with manufacturer-assigned trade item numbers. One-of-one rings, custom-design pendants, art-jewelry pieces, and small-batch artisan inventory don't have manufacturer trade item numbers — they're made by the brand or sourced from suppliers who never assign GTIN. The Barcode field stays empty for these items, and Shopify Catalog requires no GTIN as a baseline eligibility condition.

Production-line jewelry (large brands selling thousands of identical SKUs) does have GTIN and should populate the field. Custom and artisan inventory does not, and the install accepts the empty field rather than fabricating a value. Fabricating GTIN risks downstream issues with Merchant Center, Catalog matching, and any retail-partner ingestion that validates GTIN against external databases.

The hallmark layer — physical-world barcode

A hallmark stamp on metal jewelry is the physical-world structured identifier for that piece. It carries the metal purity (18K, 14K, 925), the maker's mark (where assayed by an official assay office), and the assay date or convention mark in many jurisdictions. The install captures the hallmark detail as structured data on the PDP — both as metafield content rendered in the storefront and as Product schema additionalProperty consumed by Catalog and AI engines.

The hallmark fields the install adds per SKU: hallmark_purity (e.g., "18K Yellow Gold", "925 Sterling Silver"), hallmark_assay_office (e.g., "London Assay Office", "Birmingham Assay Office", "Dublin Assay Office"), hallmark_year_letter (where applicable), and hallmark_maker_mark. The schema.org Product type3 accepts these as PropertyValue blocks under additionalProperty, which is the structured surface Catalog reads.

Metafields and Product schema additionalProperty

The install ships the structured detail in two mirrored layers. Metafields are the merchant-editable layer — Shopify admin has a structured editor, the data lives per SKU, and the storefront theme renders the metafield content on the PDP as a 'Specifications' or 'Details' block. Product schema additionalProperty is the engine-readable layer — the theme's JSON-LD output includes the metafield content as PropertyValue blocks under the Product entity. Both layers carry the same data, and both are populated from the same source.

The metafield set for jewelry: material.metal (e.g., "18K Yellow Gold"), material.gemstone (e.g., "Round Brilliant Diamond, 1.2ct"), material.gemstone_grading (e.g., "GIA-certified, F color, VS1 clarity, Excellent cut"), hallmark.purity, hallmark.assay_office, certification.authority, certification.report_number. Each metafield maps to an additionalProperty block in the Product schema, which is what Catalog and the AI engines parse for structured discovery.

Gemstone certification and its structured place

Certified diamonds and high-value colored stones carry an external report from an independent grading authority — GIA, AGS, IGI, HRD, or AGL for diamonds; GIA, Gübelin, SSEF for colored stones; CIBJO-aligned bodies for pearls. The report number functions as a quasi-GTIN for that specific stone, and the install can carry it in either Catalog's Barcode field (where the field would otherwise be empty) or as a dedicated metafield mirrored to Product schema additionalProperty.

The GIA report process5 issues a report number unique to each graded stone. Putting that report number in the Shopify Barcode field is a defensible substitute when the SKU has no GTIN — the field stays populated (which helps with retail-partner ingestion that prefers populated Barcode), and the value is a verifiable external identifier. The trade-off: GIA report numbers are not GTIN-formatted, so any system strictly validating GTIN format will reject them. The cleaner pattern for most installs: leave Barcode empty for true one-of-one inventory, and carry the certification report number as a dedicated metafield with mirror to additionalProperty.

FTC Jewelry Guides as the claims overlay

The structured-data layer is necessary but not sufficient. The FTC Jewelry Guides regulate material claim language, and the install's claims scan checks every PDP, every metafield, and every collection description against them. 'Gold' without karat qualification implies 24K. 'Silver' without qualification implies sterling. 'Diamond' without qualification implies natural mined. 'Pearl' without qualification implies natural. Lab-grown, cultured, plated, and filled require explicit disclosure.

The FTC Jewelry Guides4 are the evergreen reference. The install applies them as a claims-scan layer: every product title, every PDP copy block, every metafield text value, and every collection description gets read for material claim language and verified against the actual material specification. Mismatches (a "diamond ring" that's actually cubic zirconia, a "gold necklace" that's actually gold-plated brass) get rewritten before Catalog publish. The structured-data layer carries the truth; the claims layer carries the disclosure. AI engines parse both.

Keep reading