{"id":11843,"date":"2026-03-26T16:18:37","date_gmt":"2026-03-26T16:18:37","guid":{"rendered":"https:\/\/www.vappingo.com\/word-blog\/?p=11843"},"modified":"2026-04-06T15:28:12","modified_gmt":"2026-04-06T15:28:12","slug":"amazon-kdp-bisac-codes","status":"publish","type":"post","link":"https:\/\/www.vappingo.com\/word-blog\/amazon-kdp-bisac-codes\/","title":{"rendered":"BISAC Codes and Amazon KDP: What They Are and Whether They Still Matter"},"content":{"rendered":"

<\/p>\n

\n
\n
KDP Categories \u00b7 Vappingo<\/span><\/div>\n
BISAC Codes and Amazon KDP: What They Are and Whether They Still Matter<\/em><\/div>\n

BISAC codes were once central to KDP category selection. The system changed in 2023. Here’s what BISAC codes are, how they work now on Amazon, and where they still matter for authors publishing wide.<\/p>\n

\n\n\n\n
8-minute read<\/span><\/td>\nAll levels<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

BISAC codes appear in a lot of self-publishing advice \u2014 and a lot of that advice is now outdated. The Book Industry Standards and Communications subject classification system has been a standard part of book metadata for decades, and for years KDP authors selected BISAC codes directly as part of their category assignment process. That changed in 2023, when Amazon overhauled how KDP categories work. Understanding what changed, what BISAC codes still do, and where they remain relevant will help you navigate category decisions without confusion.<\/p>\n

\n
\n Stop guessing what sells on Amazon.
\n Find it. Write it. Sell it.<\/span>\n <\/div>\n
\n Real Amazon data + 15+ years of copy expertise\n <\/div>\n
\n
<\/div>\n <\/div>\n
\n
\n
Validate
Before You Write<\/div>\n
Reduce Risk<\/div>\n <\/div>\n
\n
Stop Losing
Money on Ads<\/div>\n
Fix Fast<\/div>\n <\/div>\n
\n
Turn Searches
Into Sales<\/div>\n
Convert More<\/div>\n <\/div>\n <\/div>\n \n Start Finding Profitable Books\n <\/a>\n
\n Powered by Vappingo\n <\/div>\n <\/div>\n \n

What BISAC Codes Are<\/h2>\n

BISAC codes are a standardised subject classification system maintained by the Book Industry Study Group (BISG), a US trade association. The system consists of a hierarchical list of subject headings \u2014 currently around 3,500 codes \u2014 each represented by a short alphanumeric string. For example, FIC022000 represents “Fiction \u2014 Mystery & Detective \u2014 General”, and BUS070000 represents “Business & Economics \u2014 Personal Finance \u2014 General.”<\/p>\n

The purpose of BISAC codes is interoperability across the book industry supply chain. When a publisher submits a book’s metadata to a retailer, library, or distributor, BISAC codes provide a standardised signal about the book’s subject that every system in the chain can interpret consistently. Without standardised subject codes, every retailer would need to map your custom genre descriptions to their own internal categories \u2014 an impractical process at scale. BISAC codes solve this by giving the entire industry a shared vocabulary.<\/p>\n

For readers browsing Amazon, BISAC codes are invisible. They’re a backend metadata element, not a consumer-facing label. Readers see Amazon’s own category names in the browse sidebar and on product pages, not BISAC strings. The relevance of BISAC codes to your daily publishing decisions depends entirely on where and how you publish.<\/p>\n

How BISAC Codes Changed on KDP in 2023<\/h2>\n

Prior to mid-2023, KDP authors selected two BISAC codes directly during the book setup process. These BISAC selections were one of the primary inputs into Amazon’s category placement system. Authors could also request up to ten additional categories by contacting KDP support \u2014 a manual process that gave prolific self-publishers broad category coverage.<\/p>\n

The 2023 update replaced direct BISAC selection with Amazon’s own category taxonomy. Authors now choose up to three categories per format from Amazon’s hierarchical browse category structure \u2014 the same structure readers see when browsing. Amazon’s system then automatically derives the corresponding BISAC codes from your category selections in the background. You don’t choose BISAC codes; Amazon infers them from the Amazon categories you select.<\/p>\n

This change removed BISAC codes from the author-facing KDP workflow entirely for Amazon purposes. You can no longer override Amazon’s BISAC assignment, and you don’t need to know what BISAC code your book has been assigned. The KDP dashboard doesn’t show you the derived BISAC codes \u2014 they exist in the backend metadata but aren’t surfaced to the author.<\/p>\n

\n

What this means in practice:<\/strong> If you’re publishing only on Amazon KDP, you don’t need to think about BISAC codes at all. Focus entirely on choosing the right Amazon category paths. The BISAC codes will be handled automatically.<\/p>\n<\/div>\n

Where BISAC Codes Still Matter<\/h2>\n

BISAC codes remain directly relevant for authors publishing through channels outside Amazon. IngramSpark, Draft2Digital, Smashwords, and other wide-distribution platforms still use BISAC codes as a core metadata requirement. When you set up a title through IngramSpark for distribution to Barnes & Noble, libraries, independent bookshops, and international retailers, you select BISAC codes directly and those codes are submitted as part of your title metadata to every retailer in the distribution network.<\/p>\n

Library metadata is particularly BISAC-dependent. Libraries use BISAC codes to classify and shelve books in their cataloguing systems \u2014 a correctly assigned BISAC code determines whether your book appears in a librarian’s search results when they’re purchasing for a particular subject collection. Authors aiming for library distribution should research and apply BISAC codes carefully through their wide-distribution channels, even if those codes are invisible on Amazon.<\/p>\n

Some metadata aggregation services and book discovery platforms also use BISAC codes for classification. Goodreads genre assignments, for example, are partly informed by BISAC codes submitted through publisher metadata feeds. Authors publishing wide who want consistent genre classification across discovery platforms benefit from choosing BISAC codes deliberately in their wide-distribution metadata, rather than leaving the assignment to whatever default their distributor infers.<\/p>\n

Choosing BISAC Codes for Wide Distribution<\/h2>\n

If you are publishing through IngramSpark or another wide distributor and need to select BISAC codes directly, the BISG maintains a publicly accessible subject heading list at bisg.org. The list is hierarchical \u2014 you’ll find a top-level section (FIC for fiction, BUS for business, HEA for health, and so on) with progressively specific sub-codes beneath it. Always select the most specific code that accurately describes your book’s primary subject, plus up to two additional codes if your book legitimately spans multiple subjects.<\/p>\n

For fiction, the relevant BISAC top-level section is FIC, with sub-codes for every major genre and subgenre. For nonfiction, identify your subject domain first \u2014 SEL (Self-Help), HEA (Health & Fitness), FAM (Family & Relationships), etc. \u2014 then find the most specific sub-code within it. The full BISAC list runs to thousands of entries and is updated annually, so it’s worth checking the current version rather than relying on older lists that may reference deprecated codes.<\/p>\n

When publishing both on Amazon KDP and through a wide distributor like IngramSpark, your BISAC codes for the wide version should reflect the same genre and subject as your Amazon category selections, even though they’re maintained in separate systems. Consistency in your metadata across platforms ensures that aggregators, comparison sites, and library systems classify your book consistently \u2014 an important factor if you’re building discoverability across multiple retail channels rather than relying solely on Amazon.<\/p>\n

For all publishing preparations, having a clean, professional manuscript description and metadata copy is essential. Vappingo’s manuscript proofreading service<\/a> ensures your book is ready for scrutiny across every retail channel you publish through.<\/p>\n

\n
\n Stop guessing what sells on Amazon.
\n Find it. Write it. Sell it.<\/span>\n <\/div>\n
\n Real Amazon data + 15+ years of copy expertise\n <\/div>\n
\n
<\/div>\n <\/div>\n
\n
\n
Validate
Before You Write<\/div>\n
Reduce Risk<\/div>\n <\/div>\n
\n
Stop Losing
Money on Ads<\/div>\n
Fix Fast<\/div>\n <\/div>\n
\n
Turn Searches
Into Sales<\/div>\n
Convert More<\/div>\n <\/div>\n <\/div>\n \n Start Finding Profitable Books\n <\/a>\n
\n Powered by Vappingo\n <\/div>\n <\/div>\n \n

The Historical Context: Why BISAC Still Comes Up<\/h2>\n

If you’ve been publishing since before 2023, you may remember selecting BISAC codes as part of the standard KDP upload workflow. The interface presented a searchable dropdown of BISAC subject headings, and your two selections anchored your primary category placements. Industry training materials, YouTube tutorials, and self-publishing blog posts from that era are full of BISAC selection advice \u2014 which specific codes perform best, how to pick the most strategic BISAC for discoverability, and how to combine codes across different subject branches to maximise category coverage.<\/p>\n

Much of that content is still indexed and ranking in search engines, which is why so many authors arrive at the category selection stage in 2026 with BISAC on their minds. The underlying category strategy thinking in those older guides is often still valid \u2014 the logic of choosing an accurate primary category alongside a less-competitive secondary placement hasn’t changed. But the specific mechanism (selecting BISAC codes in KDP) has been replaced, and any advice tied to the old dropdown interface or the support-request process for additional categories no longer applies.<\/p>\n

BISAC Codes in Amazon’s Metadata Backend<\/h2>\n

Even though authors no longer interact with BISAC codes directly in KDP, the codes themselves haven’t disappeared from Amazon’s systems. When you select an Amazon store category \u2014 say, “Books \u2192 Mystery, Thriller & Suspense \u2192 Mystery \u2192 Cozy Mysteries” \u2014 Amazon maps that selection to the closest corresponding BISAC code in its backend systems. That BISAC code is then included in the book’s industry metadata, which is used in data feeds to third-party catalogues, comparison shopping services, library systems, and book discovery platforms that still rely on BISAC as a common language.<\/p>\n

This automatic mapping is generally accurate for well-established genre categories where clear BISAC equivalents exist. It’s somewhat less precise for highly specific Amazon subcategories that don’t have a clean BISAC equivalent \u2014 Amazon’s taxonomy has become more granular than BISAC in some genre fiction areas, and the auto-derived BISAC code may be a broader category than the Amazon selection. For most authors publishing on Amazon alone, this imprecision doesn’t matter. For authors who also care about metadata quality in library and wide-distribution contexts, manual BISAC selection through IngramSpark provides more control.<\/p>\n

Practical Guidance: Amazon-Only vs Wide Publishing<\/h2>\n

If you publish exclusively through Amazon KDP, your BISAC workflow is zero-effort: select the best Amazon categories for your book, and let Amazon handle BISAC derivation automatically. Spend your metadata research time on Amazon’s category taxonomy, not on BISAC codes you’ll never interact with directly.<\/p>\n

If you publish through both Amazon KDP and IngramSpark (for wide distribution to other retailers, libraries, and international markets), you maintain two separate sets of category metadata: Amazon categories in KDP and BISAC codes in IngramSpark. These should be aligned \u2014 your BISAC selections in IngramSpark should describe the same genre and audience as your Amazon category selections \u2014 but they’re managed separately in each platform’s interface. IngramSpark’s setup process walks you through BISAC selection with its own dropdown interface, and their help documentation provides guidance on choosing appropriate codes.<\/p>\n

The key practical point for wide publishers is not to confuse the two systems. Amazon category optimisation strategies (targeting specific Amazon category paths for competition analysis and badge potential) don’t translate directly to BISAC selection. BISAC is a much flatter taxonomy with fewer granular subdivisions \u2014 you can’t target “cozy mysteries featuring cats” as a BISAC code the way you can as an Amazon category. Focus Amazon-specific strategy on Amazon’s taxonomy and approach BISAC as a broader classification exercise for non-Amazon distribution.<\/p>\n

Regardless of which distribution channels you use, a clean, accurate book description is the foundation of correct category assignment across all systems. Professional manuscript proofreading<\/a> ensures your book and its listing copy are ready for distribution through every channel you choose.<\/p>\n

A Quick Reference: BISAC in 2026<\/h2>\n

New KDP author publishing exclusively on Amazon: you will never encounter BISAC codes in your workflow. Select Amazon categories in the KDP dashboard and ignore BISAC entirely. Existing KDP author who used to select BISAC codes: your previously selected codes have been replaced by Amazon’s automatic derivation from your current category selections. Nothing needs updating on your end \u2014 it happened automatically with the 2023 system change.<\/p>\n

Publishing wide through IngramSpark alongside KDP: you’ll select BISAC codes separately in IngramSpark’s setup process. Treat this as a distinct metadata task from your Amazon category selection. Align the BISAC codes with your Amazon categories in terms of genre and subject, but use IngramSpark’s own interface to make the selection. Wondering whether your Amazon BISAC derivation is affecting discoverability: it isn’t something you can directly see or control. Amazon’s category placement is driven by your Amazon category selections and metadata signals. If your Amazon category placements are correct and relevant, the derived BISAC is correct by definition.<\/p>\n

\n
\n Stop guessing what sells on Amazon.
\n Find it. Write it. Sell it.<\/span>\n <\/div>\n
\n Real Amazon data + 15+ years of copy expertise\n <\/div>\n
\n
<\/div>\n <\/div>\n
\n
\n
Validate
Before You Write<\/div>\n
Reduce Risk<\/div>\n <\/div>\n
\n
Stop Losing
Money on Ads<\/div>\n
Fix Fast<\/div>\n <\/div>\n
\n
Turn Searches
Into Sales<\/div>\n
Convert More<\/div>\n <\/div>\n <\/div>\n \n Start Finding Profitable Books\n <\/a>\n
\n Powered by Vappingo\n <\/div>\n <\/div>\n \n
\n

Nail Your Amazon Categories<\/h3>\n

KDP Rank Fuel’s Category Research tools help you find the right Amazon categories \u2014 the ones that are live, relevant, and reachable for your book. No BISAC knowledge required.<\/p>\n

Try KDP Rank Fuel Free<\/a><\/p>\n<\/div>\n

\n
Related Reading<\/div>\n\n\n\n

\nStart Here<\/span>
\nHow to Choose Amazon KDP Categories: The Complete Guide<\/span>
\n<\/a><\/td>\n
\nRelated<\/span>
\nHow Many KDP Categories Can You Choose?<\/span>
\n<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/article>\n","protected":false},"excerpt":{"rendered":"

KDP Categories \u00b7 Vappingo BISAC Codes and Amazon KDP: What They Are and Whether They Still Matter BISAC codes were once central to KDP category selection. The system changed in 2023. Here’s what BISAC codes are, how they work now on Amazon, and where they still matter for authors publishing wide. 8-minute read All levels … Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[33,31],"tags":[],"class_list":["post-11843","post","type-post","status-publish","format-standard","hentry","category-kdp-listings","category-kdp-publishing"],"_links":{"self":[{"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/posts\/11843","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/comments?post=11843"}],"version-history":[{"count":1,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/posts\/11843\/revisions"}],"predecessor-version":[{"id":11844,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/posts\/11843\/revisions\/11844"}],"wp:attachment":[{"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/media?parent=11843"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/categories?post=11843"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vappingo.com\/word-blog\/wp-json\/wp\/v2\/tags?post=11843"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}