Google Merchant Center for Books & Publishers: ISBN, GTIN, and Feed Setup

Books and other media products (CDs, DVDs, vinyl) follow a distinct set of Merchant Center identifier rules that trip up a lot of sellers migrating from general e-commerce feed templates. The core issue: books use ISBN as their identifier, but Google's [gtin] field expects a GTIN — and the brand attribute means something different for media than it does for physical retail goods.

Why Books Are a Special Feed Case

Most product categories use [gtin] for a UPC or EAN and [brand] for the actual manufacturer. Books break both conventions: they're identified by ISBN, and there generally isn't a "brand" in the retail sense — there's a publisher. Google's GTIN attribute documentation and product data specification both carve out explicit rules for this category.

Converting ISBN to GTIN Correctly

The core rule: use the ISBN-13 of the book as the value for [gtin]. If you only have an ISBN-10, convert it to ISBN-13 first (prepend "978" and recalculate the check digit) — don't submit the ISBN-10 directly, as Google's validation expects the 13-digit format.

If your ISBN starts with fewer than 13 digits after conversion or has leading-zero formatting issues (e.g., a 9-digit legacy code converting to "0123456789"), pad correctly with a leading zero rather than dropping the identifier — Google's spec explicitly covers this conversion case.

The Brand Attribute Rule for Media Products

For books and other media products, enter the publisher's name as the [brand] value — not the author, not a generic "Books" placeholder, and not your own store name if you're a reseller. For a novel published by Penguin Random House, [brand] should be "Penguin Random House" (or the specific imprint, depending on how granularly your catalog tracks publishers), not the author's name.

• [brand] = publisher or imprint name
• [author] (custom label or description field, not a standard required attribute) = where the author's name belongs
• [gtin] = ISBN-13 (and UPC too, if both exist)
• [identifier_exists] = "true" once you have a valid GTIN — don't set this to "false" just because you're unsure how to format your ISBN; fix the format instead

Handling Multiple Editions and Formats

Hardcover, paperback, and ebook editions of the same title are different products with different ISBNs — treat them as separate feed items, each with its own correct ISBN-13/GTIN, rather than variants of a single listing sharing one identifier. Common mistakes here:

• Reusing the hardcover's ISBN for the paperback listing because "it's the same book" — this creates a GTIN mismatch that Google's product data review can flag.
• Listing an ebook with a physical shipping weight/dimensions attribute, which confuses both Google's review and customer expectations.
• Failing to distinguish box sets or bundles (multiple ISBNs) with their own unique identifier rather than reusing one component book's ISBN.

Self-Published and Small-Press Books

Self-published books still need a valid ISBN to populate [gtin] correctly — if your book was published without an ISBN (some print-on-demand and ebook-only titles skip this), you have two options:

1. Obtain an ISBN through your country's ISBN agency (in the US, Bowker) before listing on Google Shopping — this is the cleanest long-term fix and often required for wider distribution anyway.
2. If a true identifier genuinely doesn't exist, submit [identifier_exists] as "false" — but be aware this can limit visibility relative to identifier-complete listings, and Google's review may still request supporting documentation given how central identifiers are to the books category.

For [brand] on self-published titles without a formal publishing house, use your press/imprint name if you've established one, or your legal business name as a fallback — avoid leaving it blank or using the author's name.

Common Disapproval Causes

Books Feed Checklist

Feeding Multiple Marketplaces from One Book Catalog

Many book sellers run feeds simultaneously to Google Shopping, Amazon, and industry-specific marketplaces, and it's tempting to reuse one master feed across all of them. This works for most attributes but breaks down specifically around brand and identifier handling:

• Amazon's category conventions for books often use different brand/publisher mapping conventions than Google's — verify your feed mapping layer translates correctly for each destination rather than assuming a single export works everywhere.
• Some marketplaces accept ASIN as a primary identifier; Google Shopping does not — ASIN is not a substitute for a GTIN/ISBN-13 in your Merchant Center feed.
• If you use a feed management tool or middleware to distribute one catalog to multiple channels, add a validation step specifically checking that ISBN-13 (not ISBN-10, not ASIN) lands in Google's [gtin] field before each sync.

Rare, Out-of-Print, and Collectible Books

Used bookstores and collectible dealers face an additional layer of complexity: a single ISBN may correspond to many physical copies in wildly different condition, each individually priced. A few practices that keep these listings compliant:

• Disclose condition explicitly and specifically ("Good — moderate shelf wear, no markings" rather than a bare "Used") since vague condition grading is a common source of buyer disputes and misrepresentation-adjacent complaints.
• For genuinely rare or first-edition copies where the specific printing carries significant value beyond the ISBN's typical market price, note this clearly in the description so the price differential is understood rather than looking like a pricing error.
• Where a specific copy has unique characteristics (signed, inscribed, ex-library) that affect value, disclose these directly rather than relying on the buyer to infer it from price alone.

A Bulk Correction Workflow for Large Backlists

Publishers and booksellers with catalogs running into the thousands of titles can't realistically fix ISBN/GTIN and brand mapping one listing at a time. A practical bulk workflow:

1. Export your full feed to a spreadsheet and add a validation column that flags any [gtin] value not matching the 13-digit ISBN format.
2. Cross-reference your [brand] column against a known list of your publisher/imprint names — flag any row where brand matches a person's name pattern rather than a publisher, since this usually indicates the author field was mapped incorrectly.
3. For flagged rows, batch-correct using your source catalog system (most bibliographic databases store publisher and ISBN-13 as clean, separate fields) rather than manually retyping each one.
4. Re-upload the corrected feed as a full replace rather than an incremental update, so Google's review re-evaluates the whole corrected dataset together.
5. Monitor the Merchant Center diagnostics page over the following days for any remaining flagged items, and iterate on the correction logic for edge cases (multi-author titles, imprint-vs-parent-publisher naming) that a simple rule missed.

Frequently Asked Questions

Can I use my store name as the brand for books I resell?

No — for books and media, [brand] should reflect the publisher, not the reseller. Using your own store name as brand is a common misrepresentation-adjacent mistake in this category.

Do ebooks need a GTIN?

Ebooks typically have their own ISBN distinct from the physical edition — use that ISBN-13. If a digital-only title has no ISBN, follow the [identifier_exists] = false path described above.

Why was my book listing disapproved for "missing brand" when I did include a publisher?

Check whether you used an imprint name Google doesn't recognize as distinct from a generic term, or whether the field was populated with the author's name by mistake during feed mapping — this is a very common mapping error when repurposing an author-centric product database for Shopping feeds.

What if I have a large backlist and this feels overwhelming to fix manually?

Prioritize your top-selling titles first, and consider batch-correcting via spreadsheet formulas that swap author/brand fields and convert ISBN-10 to ISBN-13 programmatically before bulk-uploading a corrected feed.