Collect one raw line from each bookseller, give an AI assistant those lines plus a short voice guide, and ask it to polish without adding facts. Then drop the polished picks into a fixed template with an event block, check every title, date and price yourself, and send on a set schedule, such as every second Thursday.
The voice is the product. People subscribe to a bookshop newsletter because someone they trust recommends books, and a line that reads like a publisher's blurb loses that. So the AI's job is trimming and tidying, never inventing a plot point, a quote from the book or an opinion that nobody on staff holds.
Write the voice guide before you polish a single line
A voice guide is a short block you paste above every batch of lines, so the AI edits in your shop's register instead of its own. Keep it to what you would tell a new bookseller on their first day. The banned-word list matters more than it looks: models reach for the same few adjectives, and readers learn to skip them.
Voice guide for [Shop name] newsletters:
- Sound like a bookseller talking across the counter: warm, specific, a little dry.
- Keep the bookseller's own words wherever they work. Change only spelling, punctuation and clumsy phrasing.
- One or two sentences per pick: what it is like, and who should read it.
- Never add plot details, quotes, awards, comparisons or opinions that are not in the bookseller's line.
- Never change a verdict. If the bookseller says "not for bedtime", it stays "not for bedtime".
- Banned words: unputdownable, gripping, page-turner, must-read, masterpiece, tour de force, a journey.
- Keep our usual spelling and punctuation. No exclamation marks.
Here are three lines I wrote myself that sound right: [paste three past favourites]That last line is worth the extra minute. Examples teach register better than rules do, so keep a small "voice bank" of the ten lines your team is proudest of and paste three of them each time.
Four staff lines, before and after the AI pass
Ask each bookseller for one raw line in the same shape: title, author, what it is like, who to give it to. Two minutes each, typed straight into a shared note, no polish. The titles below are invented, and [first name] stands for the bookseller who picked each one.
| Raw line from staff | What the AI returned (illustrative) | What to fix |
|---|---|---|
| The Orchard Year: cried on the bus, twice. Good for anyone who liked slow books about growing things. | The Orchard Year is a quiet, slow-burning novel about growing things that made [first name] cry on the bus, twice. One for readers who like their stories unhurried. | It called the book a "novel" when nobody said so. Check the format on the cover; this could be memoir. |
| Small Hours (paperback, out now): scary in the way a quiet house is scary. Not for bedtime. | Newly out in paperback, Small Hours is scary the way a quiet house is scary. Maybe not one for bedtime. | "Maybe not" softens a firm verdict. Restore "Not for bedtime." |
| Tin Roof Summer: I read this in one go on a Sunday. For fans of big-hearted family stories. | A big-hearted family story you can finish in a Sunday afternoon. | This turned the bookseller's experience into a claim about the book's length. Put "[first name] read it in one sitting on a Sunday" back. |
| The Goose and the Cartographer: YA but honestly everyone should read it. Fantasy, maps, a very good goose. | A fantasy for young adults and anyone else who loves maps, with a very good goose. | "Honestly everyone should read it" was the verdict, and it has gone. Restore it; keep the goose. |
The pattern across all four is the same. The AI is good at tidy sentences and bad at leaving opinions alone: it guesses formats, softens verdicts and turns a personal experience into a general claim. That is why every line goes back to the bookseller who wrote it for a 30-second yes or no before it appears in a template.
From four approved lines to a fixed staff-picks block
Once the bookseller has said yes to a line, the layout never changes: bold title, author, format and price on one line, then the line itself, then who picked it. Readers learn where to look, and you stop redesigning the email every fortnight. Type the author, format and price from your till or stock system, because a model will happily guess a price. Then let the AI do the mechanical filling.
Fill the newsletter template below.
- Use the staff lines exactly as given; they are already polished and approved.
- Use the event facts exactly.
- Do not add books, prices, dates, opening hours or claims.
- If a field is missing, leave it as a placeholder in square brackets.
TEMPLATE
Subject / Preview text
Greeting: two sentences from the owner
STAFF PICKS: for each pick, bold title, author, format and price on one line; the staff line; "Picked by [first name]."
EVENT: headline, date line, 40-word description, price line, booking line, access line
JUST IN: two lines
Sign-off and opening hours
STAFF LINES: [paste four approved lines with author, format, price]
EVENT FACTS: [paste the event fact sheet]The event block: facts first, one warm line after
An event block works when a reader can act on it without clicking anywhere: what, when, how long, how much, how to book, and how access works. Write those six facts yourself on a fact sheet, and let the AI write only the one warm sentence that sounds like your shop. If you are planning the events themselves too, the author night and book club tutorial covers the plan, the publisher email and the ticket page that feed this block.
Event: [Author] in conversation about [Title] with [host name]
Date: [day, date]; doors 6:30 pm; talk 7:00 pm; ends about 8:30 pm
Price: $8, counts as credit towards the book on the night
Seats: 36
Booking: [link]
Access: [access facts]
Write the event block: a bold headline, a date line, a description of about 40 words, then price, booking and access lines. Use only the facts above.Author night: [Author] on [Title]
[Day, date]. Doors 6:30 pm, talk 7:00 pm, finishing around 8:30 pm.
[Host name] talks with [Author] about [Title], then it is over to your questions, then a signing at the till.
$8 a ticket, counted as credit towards your copy on the night. 36 seats.
Book here: [link]
Access: [access facts]
That output (illustrative) is clean, which is the point of the fact sheet. Four slips still deserve a deliberate check. The weekday and the date must agree, because models sometimes pair them wrongly. The start time must match: a realistic failure is a draft that says "7:30 pm" because an earlier event in the same long chat started at 7:30, so open a fresh chat, or a Project, for each issue and paste only that issue's facts. Delete any urgency the model adds, such as "selling fast". And never let the access line say "fully accessible" unless you supplied the facts behind it.
Smaller recurring events need only a line. A book club entry might read: "Book club: first Thursday, 7 pm. This month: [Title]. 12 seats, join here: [link]." Keep a fixed spot for it in the template so members stop searching for it.
Just in: two lines from a delivery note
The "Just in" block suits readers who already know what they want, and it is quick to produce because the source is a list you already have. Paste the delivery note lines (title, author, format) and ask for two lines using only those items, grouped by theme where that helps.
New this fortnight: [Title] by [Author] (hardback), [Title] by [Author] (paperback) and the full [Series] set again. Ask us if you want something you cannot see on the shelf and we will order it in.
That is the sort of output to expect (illustrative). Strip "bestselling" and "hotly anticipated" if they appear, because the AI cannot know either. Say "back on the shelf" only for titles that really were out of stock, not merely reordered. And never put a customer's name or a special order's details in a bulk email.
A gift issue: eight picks grouped by budget
Once a year the picks become a gift guide, and sorting is a job the AI does well. Give it the eight picks with the prices typed from the till and ask for three bands. Then check each band yourself.
| Band | Picks | What the picks look like |
|---|---|---|
| Under $12 | 3 | A stocking-filler paperback, a pocket poetry volume, a children's board book |
| $12 to $25 | 3 | A new paperback novel, a cookery title, a graphic novel |
| Over $25 | 2 | An illustrated gift edition, a signed hardback from a recent author night |
The realistic mistake here is a price typed without its decimal point: a $26 hardback typed as $2.60 will land in the cheapest band, and a $9.95 paperback typed as $99.5 in the dearest. Read every price against the till before the issue goes anywhere.
One whole issue, assembled and ready to proofread
Here is the finished email with invented titles. Square brackets mark the facts your till, diary and ticket page supply. It runs to roughly 250 words, which is the right size: a reader gets through it in a couple of minutes and finds the event without scrolling.
Subject: Four staff picks and an author night
Preview: Cried-on-the-bus novels, one very good goose, and a ticketed evening.
Hello [first name],
A quiet fortnight in the shop, which means we have been reading. Four books the team keeps pressing into hands, and one evening worth putting in the diary.
Staff picks
The Orchard Year, [Author]. Paperback, [price]. A quiet, slow-burning book about growing things that made [first name] cry on the bus, twice. For readers who like their stories unhurried. Picked by [first name].
Small Hours, [Author]. Paperback, [price], out now. Scary in the way a quiet house is scary. Not for bedtime. Picked by [first name].
Tin Roof Summer, [Author]. Hardback, [price]. A big-hearted family story that [first name] read in one sitting on a Sunday. Picked by [first name].
The Goose and the Cartographer, [Author]. Paperback, [price]. YA, but honestly everyone should read it: fantasy, maps and a very good goose. Picked by [first name].
Author night: [Author] on [Title]
[Day, date]. Doors 6:30 pm, talk 7:00 pm, finishing around 8:30 pm. [Host name] talks with [Author], then it is over to your questions, then a signing. $8 a ticket, counted as credit towards your copy on the night. 36 seats. Book here: [link]. Access: [access facts].
Just in
[Two lines on new arrivals or special orders.]
Until next time,
[Owner first name] and the team
Open [days and hours]
Proofread it against the sources, not against itself: titles and authors against the stock system, prices against the till, event facts against the fact sheet, every link by clicking it. The newsletter QA checklist is the long version of that routine. If you want a designed layout rather than a plain one, building newsletter templates in Canva with AI shows how, and the structure above transfers unchanged.
Subject lines and preview text that sound like a shop
The subject line should say what is inside, and the preview text (the short grey line most inboxes show after the subject) should finish the thought. Both need to be short enough to read on a phone screen. Ask for six options, then pick one and fix it.
Write six subject lines and one preview text for the issue below. Each subject line should say what is inside, be short enough to show in full on a phone, and sound like a friendly bookseller. No capital-letter shouting, no exclamation marks, no "don't miss".
ISSUE: [paste the issue]A typical set (illustrative): "Four staff picks and an author night"; "Cried on the bus, twice (and three more picks)"; "A very good goose, and other recommendations"; "Don't miss our MUST-ATTEND author night!!!"; "Your next read is on page two"; "Newsletter: staff picks and events". Keep the first three. The fourth breaks your own rules and the fifth is a gimmick that tells the reader nothing. The sixth is accurate and flat; use it as the fallback if you are short of time.
A send schedule you can keep, and what the free plans allow
Regularity beats clever timing. Pick a day and a time, keep it for eight sends, then look at what happened. A rhythm that suits a shop with Thursday evening events and busy Saturdays might be:
| Message | When | Who gets it | Built from |
|---|---|---|---|
| Main issue: staff picks, event block, just in | Every second Thursday, 9:00 | Whole list | The fixed template and four approved lines |
| Event push | 8 to 10 days before a ticketed event | Whole list | The event block plus a real "seats left" number |
| Ticket-holder reminder | 2 days before | Ticket holders only | Arrival time, access details, what to expect |
| Seasonal gift issue | Once in late autumn | Whole list | Eight picks grouped by budget |
A fortnightly issue is 26 a year. At 45 minutes each (the routine below), that is 19.5 hours a year, about the time you would spend on one afternoon event, so the schedule has to earn its place. Judge it on what readers do, not on opens. Mailchimp's own help pages explain that bot activity, including Apple's mail privacy feature, can open emails and click links before your readers do, which inflates both opens and clicks. Better signals: tickets booked through a link tagged for the newsletter, a "newsletter pick" sticker on the featured copies so you can count what left the shelf, replies, and customers saying they saw it in your email.
The free plans will not carry a real list. As of October 2026, Mailchimp's free plan is limited to 250 contacts and 500 sends a month (250 a day) and does not include its generative AI features. MailerLite's free plan allows 250 subscribers and 2,500 emails a month. Take a shop with 1,200 subscribers: two issues a month is 2,400 sends, and one event push to the whole list brings it to 3,600. That is beyond both free limits, so you would need a paid tier priced for your list size. Check the live pricing page, because the figures can display in a local currency depending on where you are browsing from, and confirm the USD list price for your subscriber count before you commit.
Does the newsletter pay? A quick sum
Use your own figures, but the shape of the sum is worth doing once. Say an issue takes 45 minutes of staff time at $20 an hour, so $15, and you make about $7 on an average book (illustrative). Three extra book sales per issue covers the time (15 divided by 7 is just over two, so round up to three). If an issue sells six extra books, that is $42 against $15, or $1,092 across 26 issues against $390 of time, before the email platform's fee. The hard part is knowing which sales are extra, which is why the shelf stickers and tagged links matter: count them for eight issues and the sum stops being a guess.
A 45-minute routine for every second Thursday
- Monday (2 minutes): message the team: one raw line each by Tuesday noon, same shape as last time.
- Tuesday afternoon (15 minutes): paste the voice guide and the lines into a fresh chat. Read the output against the originals and fix what the table above showed you to expect.
- Tuesday afternoon (10 minutes): send each polished line back to its bookseller for a yes or no. Type author, format and price from the till.
- Wednesday (10 minutes): fill the template with the assembly prompt, add the event block, write the subject line, and load it into your email tool.
- Wednesday (8 minutes): proofread against the sources and send yourself a test. Open it on a phone.
- Thursday 9:00: it sends on schedule. Count sticker sales and link clicks the following week.
The Monday message is worth standardising, because late and shapeless lines are what stretch the routine. Something like this works (an illustration of the wording, to adapt):
Hi all, newsletter lines are due Tuesday noon. One line per book, in this shape:
Title, author | what it is like, in your own words | who to give it to | anything to avoid (spoilers, content notes)
Write it the way you would say it at the till. Do not polish it; I will tidy it and send it back for your OK.
Example: The Orchard Year, [Author] | cried on the bus, twice | slow books about growing things | noneThat adds up to 45 minutes. If it regularly takes longer, the usual cause is staff lines arriving late or in different shapes, not the AI step. For a wider introduction to writing customer newsletters with AI, how to write a customer newsletter with AI in 30 minutes is the general version of this routine.
Guessed formats and softened verdicts: what AI polish breaks
- Guessed formats. Novel, memoir, collection, picture book. Confirm against the cover or your stock system.
- Softened verdicts. "Not for bedtime" becomes "maybe not". The strong opinions are why people read.
- Series and edition details. The AI may state a book is "the first in a series" or "newly out" without knowing. Keep only what the bookseller or the publisher's page says.
- Stock claims. "In stock now" is true only if someone checked. Write "ask us" instead.
- Context bleed. Old issues in the same chat leak into new ones: the wrong time, a previous price. One chat per issue.
- Spoilers. If a bookseller's raw line gives away a turn in the plot, the polish will keep it. Read each pick as a stranger would.
- Cover images. Use the images your supplier or the publisher provides for retailers; do not let an AI tool generate a cover.
Keep the human parts human. The opinion, the verdict and the greeting from the owner are what a reader would miss if they were gone, and they are also the parts that cost the least time to write yourself.
Questions about a bookstore newsletter written with AI
How many staff picks should one issue have?
Three or four. More than that and each pick gets less attention, and the issue stops feeling like a person's recommendation. Rotate booksellers so everyone appears every second or third issue, and make one pick a paperback or a lower-priced title so there is always an easy first purchase.
Should I paste my subscriber list into an AI tool?
No. The AI never needs names or email addresses to polish a line or fill a template, and your email tool already handles first-name greetings and unsubscribes. Keep subscriber data inside the email platform and give the assistant only the text and facts for the issue.
Will readers mind that AI helped write the newsletter?
Readers mind hollow copy, not tidy copy. What matters is that each pick is a real bookseller's opinion. If the AI only fixes spelling and clumsy phrasing in a line the bookseller wrote, the opinion is still theirs. If it writes the opinion, it is not, so do not let it.
How long should a bookstore newsletter be?
Short enough to read in two minutes, roughly 250 to 400 words plus a cover image or two. Lead with the picks, put the event block where it is easy to find, and finish with opening hours. If you have more to say, save it for the next issue rather than stretching this one.
Further reads
- AI for Boutique Owners: A Weekly New-Arrivals Email Routine — Another shop's weekly email routine, built around new stock.
- Yarn Shop Marketing: Fill Knitting Classes and Promote New Stock With AI — Fill classes with a newsletter in a small specialist shop.
- Virtual Receptionist for a Small Bookstore: AI or Human Answering? — AI or human phone cover for a bookshop: monthly costs, what each does with stock checks, special orders and events calls, and a worked sum.
- Comic Book Store Software: Pull Lists, Back Issues and AI Listings — Set up pull lists, list back issues from phone photos and send a weekly new-release email, with AI drafting the words and you checking the facts.
- Local SEO for a Retail Shop: Profile, Stock Posts and Reviews With AI — Complete the Google Business Profile, post weekly stock updates and reply to reviews with AI drafts: a 55-minute weekly routine for an independent shop.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Mailchimp pricing page (free plan limits) and help pages on bot activity and Apple Mail Privacy Protection; MailerLite pricing page (free plan limits); checked October 2026.