Pick the book and marketplace
Choose the manuscript and the storefront. One project maps to one marketplace, which keeps sizes and module names unambiguous.
One project, four modules, built from what the manuscript already says. Copy it into the store’s marketing page after the book is live — it never goes into the upload pack.
A+ content is generated from your manuscript, so the tool needs an account and a book. The free plan is enough to start one.
Choose the manuscript and the storefront. One project maps to one marketplace, which keeps sizes and module names unambiguous.
Each module is written from the profile and chapter list. Edit the lines that do not sound like the book before using them.
The check lists specific lines that overclaim or repeat themselves. Clear those, then paste the module text into the store.
Most buyers decide on the product page, not at the cover. A+ content is the part of that page you control.
The copy is built from what the manuscript actually contains — chapters, audience, promise — instead of generic “must-read” language.
Modules reject the wrong pixel size quietly. Having the sizes and the check in one place prevents a rejected upload.
Build the modules before the book goes live so the page is not a bare listing on launch day.
If the listing converts poorly, rewrite the block from the manuscript before changing the cover or the price.
When a later book changes the series promise, rebuild the older books’ blocks so the reading order stays consistent.
The copy quotes the book you actually wrote: its chapters, its audience, its promise. There is no generic marketing template to fill in.
Module names, pixel sizes and the copy check live beside the text, so the rules are applied where the writing happens.
A+ content never enters the EPUB or DOCX export. The pack stays the book; the marketing block stays on the product page.
The copy is built from the manuscript, not from a blank template: the title, the blurb, the audience and the chapter list. Without a book there is nothing honest to say on the product page.
A banner, a feature block, an image-and-text pair, and a comparison table. They are the formats the store already allows in the marketing section, so no module has to be custom-approved.
No. The tool writes the copy and lays out which image goes where, with the exact pixel sizes the store accepts. You supply or generate the images and check them against those sizes.
No. It never touches the upload pack. It is copied into the store’s marketing page after the book is live, one marketplace per project.
The copy can be reused with edits, but the module rules and pixel sizes here follow Amazon’s product page. Another store is a different format, not a different file size.
Claims the listing cannot support, repeated phrases, missing specifics and text that outgrows the module. It flags the line, not just the page, so the fix is a sentence rather than a rewrite.
Yes. If the publish profile has a series name, the copy can reference the series and the reading order instead of pretending the book is a standalone.
After the manuscript and the blurb are stable. The modules quote both, so building them earlier means rebuilding them once the book changes.

The interesting question is not whether the prose is pleasant. It is whether the prose obeys: a point of view, a tense, a rule, a fact, an ending.

The question is not which one writes better sentences. It is which parts of the job you are actually buying, and which parts stay with you either way.

A generator can produce a competent draft in an afternoon. It cannot produce your cases, your numbers, your taste, or the decision about what the book is willing to say.