- Do Handmade Products Need a GTIN?
- How Do You Declare the Exemption Correctly?
- What Happens If You Set It Incorrectly?
- Why Does This Matter Beyond Shopping?
- What Other Feed Problems Affect Handmade Stores?
- How Do You Audit a Product Feed?
- Last Thoughts on Merchant Center for Handmade Goods
- Frequently Asked Questions
This is the single most common reason a handmade store’s products never appear in Google Shopping, and it is entirely fixable. Makers submit a feed, receive disapprovals demanding a GTIN or barcode they cannot possibly have, and conclude the channel is not for them.
Handmade goods are explicitly exempt. The exemption simply has to be declared, and declared completely, or the products are rejected for a different reason than the one the seller thinks.
Do Handmade Products Need a GTIN?
No. Custom, one-of-a-kind and handmade goods are exempt from GTIN requirements in Google Merchant Center. There is no application process and no approval to wait for.
Products that qualify include:
- Artisan-made goods such as handmade pottery, custom jewellery and made-to-order furniture
- Vintage items produced before GTIN assignment was standard practice
- Products where the manufacturer genuinely assigned no identifier
What the exemption does not do is apply itself. A feed submitted without the correct attributes is treated as a feed missing an identifier.

How Do You Declare the Exemption Correctly?
Set identifier_exists to false, and supply a brand, and give the title and description the specifications an identifier would otherwise carry. All three are required together.
| Attribute | Value | Why |
|---|---|---|
| identifier_exists | false | Declares the product has no GTIN or MPN |
| brand | Your brand or maker name | Mandatory. Products with identifier_exists false and no brand are disapproved |
| title | Descriptive, with key specifications | Carries the identifying information a GTIN would |
| description | Full specifications | Supports matching and eligibility |

What Happens If You Set It Incorrectly?
Setting the attribute incorrectly triggers account warnings, and setting it on products that do have identifiers is a misuse.
Two errors in opposite directions:
- Claiming exemption for products that have a GTIN, which misrepresents the catalogue and can generate warnings against the account rather than the item
- Omitting the exemption on genuinely handmade goods, which produces disapprovals for a missing identifier the product will never have
A mixed catalogue needs the attribute applied per product rather than across the feed, which is where stores selling both handmade and bought-in stock usually go wrong.
Why Does This Matter Beyond Shopping?
Feed data and organic product markup draw on the same underlying information, so a feed that disagrees with the page causes problems in both.
Keeping them aligned matters for:
- Price and availability, which must match between feed, page and structured data or the markup contradicts the page
- Titles and attributes, which should reflect how buyers search rather than internal naming
- Brand consistency, since the maker name is doing identifier work in the absence of a GTIN
- Finding organic opportunities, because Shopping data shows which products convert and at what price
What Other Feed Problems Affect Handmade Stores?
Missing identifiers are the headline problem, but three others suppress handmade products routinely.
- Price and availability mismatches between the feed, the page and the structured data, which is more common on one-off stock that sells and is not restocked
- Image requirements, where lifestyle photography without a clean product shot causes disapprovals despite being better selling imagery
- Category assignment, where handmade items sit awkwardly in a taxonomy designed for mass-produced goods and get mapped to something unhelpful
- Shipping configuration, which matters disproportionately when items are fragile, heavy or shipped internationally
Each of these disapproves silently. The product simply does not appear, and no one is told unless the account is checked.

How Do You Audit a Product Feed?
Start from the disapprovals rather than from the feed file, because the account tells you exactly which products are excluded and why.
A practical sequence:
- Open the diagnostics in the account and list every disapproval and warning by reason
- Count how many products are affected against the total submitted, which is usually higher than expected
- Fix identifier and brand attributes first, since that is the largest single cause on a handmade catalogue
- Reconcile price and availability against the live pages and the structured data
- Recheck after the next feed fetch rather than assuming a fix applied
Last Thoughts on Merchant Center for Handmade Goods
This is a configuration problem that looks like a platform problem, which is why so many makers give up on the channel. The exemption exists specifically for the kind of work you do.
Audit the feed for disapprovals first, apply identifier_exists and brand together on the products that qualify, then check that price and availability agree with the page and the structured data. The handmade and craft store SEO service covers the feed alongside the organic work, and how to rank handmade products covers the wider build.
Key Takeaways
- Handmade, custom and one-of-a-kind goods are exempt from GTIN requirements. No application is needed.
- Set identifier_exists to false AND supply brand. Products with the attribute and no brand are disapproved.
- Titles and descriptions must carry the specifications an identifier would otherwise provide.
- Apply the attribute per product, not across the whole feed, on catalogues mixing handmade and bought-in stock.
- Setting the attribute incorrectly triggers account warnings, so do not claim exemption for products that have a GTIN.
- Feed data and organic product markup share the same information. A disagreement between them causes problems in both.
Frequently Asked Questions (FAQs)
Do handmade products need a barcode for Google Shopping?
No. Custom, handmade and one-of-a-kind goods are exempt from GTIN requirements, provided the exemption is declared in the feed.
How do I declare the GTIN exemption?
Set identifier_exists to false and supply a brand attribute. Both are required. A descriptive title and full specifications support it.
Why are my products still disapproved after setting identifier_exists?
Almost always a missing brand attribute. Products submitted with identifier_exists false and no brand are disapproved.
Can I apply the exemption to my whole feed?
Only if every product genuinely qualifies. On a mixed catalogue apply it per product, because claiming exemption for items that have a GTIN can trigger account warnings.
Does the feed affect my organic rankings?
Not directly, but feed and product markup share the same price, availability and title data. Disagreement between them causes problems in both channels.
Want More Sales From Search?
Get a free, no-obligation store audit and a clear plan to grow your revenue.