current BISAC Subject Codes<\/a> rather than copying codes from an old blog post. BISG releases new editions over time, so a code that once existed can be renamed, replaced, or retired.<\/p>\nWhat Changed for KDP Authors<\/h2>\n KDP moved to direct category selection in 2023. In the current workflow, you choose categories from Amazon\u2019s own list during title setup or editing. KDP says the list depends on the primary audience and primary marketplace, and you can select up to three categories.<\/p>\n
That change removed the old practical habit of treating two BISAC choices as the front door to Amazon category placement. If your goal is Amazon discoverability, work with the current KDP category interface and verify what Amazon actually displays after publication.<\/p>\n
Where BISAC Still Matters<\/h2>\n BISAC still matters when your metadata travels through the wider book trade. If you use another distributor, an ISBN metadata service, a wholesaler, or an industry ONIX feed, subject classification may still require BISAC or a mapped standard such as Thema. In that environment, accurate subject coding helps trading partners understand and route the book.<\/p>\n
The key is to assign codes for the book\u2019s real subject, not to use BISAC as a secret marketing lever. BISG\u2019s own guidance emphasizes content-based classification, and its usage notes distinguish closely related subjects when audience or treatment changes.<\/p>\n
Does Amazon Still Use BISAC?<\/h2>\n BISG lists Amazon among the organizations that use BISAC headings in a variety of ways. That does not mean KDP authors can choose a BISAC code and force a specific Amazon browse placement. Amazon\u2019s customer-facing categories are its own taxonomy, and KDP gives authors a direct category selector.<\/p>\n\nAvoid the old mapping mindset<\/div>\n
Do not publish a fixed \u201cBISAC code X always maps to Amazon category Y\u201d table as if it were permanent. Amazon categories and BISAC editions both change, and KDP does not promise a one-to-one author-controlled mapping.<\/p>\n<\/aside>\n
Amazon-Only Publishing vs Wide Distribution<\/h2>\n If KDP is your only distribution route, spend most of your energy on Amazon\u2019s current categories, keywords, description, and audience metadata. BISAC knowledge is useful background, but it should not displace the work that readers actually encounter in the Amazon store.<\/p>\n
If you distribute widely, keep a separate metadata record for each edition that includes the current BISAC subjects requested by your distribution partners. This makes your metadata portable and reduces the temptation to force one retailer\u2019s taxonomy onto every other platform.<\/p>\n
How to Choose BISAC Subjects Well<\/h2>\n\n
A defensible BISAC choice<\/div>\n
\nStart with the book\u2019s central subject or genre, not the easiest-looking commercial label.<\/li>\n Use the most specific current heading that genuinely describes the content.<\/li>\n Add secondary subjects only when they represent meaningful additional content.<\/li>\n Check the current BISG edition instead of relying on archived code lists.<\/li>\n Keep audience, language, format, and merchandising themes in their appropriate metadata fields rather than trying to encode everything in BISAC.<\/li>\n<\/ul>\n<\/div>\nHow BISAC and KDP Categories Should Work Together<\/h2>\n Treat the two systems as parallel descriptions of the same book. A historical mystery might receive an accurate BISAC fiction subject for industry distribution while also receiving three relevant Amazon category selections in KDP. The labels may not match word for word, but the positioning should tell a coherent story about genre, subject, and audience.<\/p>\n
If your BISAC record says one thing while your Amazon categories and description say another, the problem is not an algorithmic \u201csignal conflict.\u201d It is a metadata-quality problem that can confuse retailers and readers. Fix the classification at the source.<\/p>\n
A Practical BISAC-to-KDP Workflow<\/h2>\n Use BISAC early in the publishing process as a language and classification check, especially if the book will also move through distributors, wholesalers, libraries, or non-Amazon retailers. Start by identifying the most accurate current BISAC heading for the book\u2019s central content, then write down the plain-English subject, audience, and use case that led you there. That record remains useful even if Amazon presents different labels in its category selector.<\/p>\n
When you reach KDP, begin again with Amazon\u2019s current category tree rather than trying to translate the BISAC code mechanically. Search for the closest reader-facing category paths, compare them with similar books, and select up to three accurate choices. If the BISAC heading and KDP category appear to point in different directions, revisit the positioning brief. The mismatch may reveal that one of the classifications is too broad, too narrow, or based on a secondary theme rather than the book\u2019s main subject.<\/p>\n