Email Marketing for Small Online Stores: What to Send and When
If you run a small online store, you don't need forty automated flows and a dashboard full of charts. You need a handful of emails that go out reliably, reach the right customers, and give people a reason to come back. This guide covers which emails to send, how to build useful customer groups from a simple order export, what cart abandonment really involves, and how to decide between a store-native tool and a simpler email platform.
The six emails every small store should have
Start with these. Each one maps to a moment in the customer relationship, and together they cover most of what a store with a few hundred to a few thousand customers needs.
| When it goes out | What it should do | |
|---|---|---|
| Welcome | Shortly after someone subscribes | Introduce the shop, set expectations for how often you'll email, and point to bestsellers |
| Product launch | When something new goes live | Show the product, explain who it's for, and link straight to the product page |
| Restock | When a popular item comes back | Tell the people who were interested, quickly, before it sells out again |
| Seasonal | Around holidays, seasons, and shipping cut-offs | Gift guides, deadlines, and seasonal edits |
| Post-purchase care | Some days after an order arrives | Usage tips, care instructions, and a request for a review |
| Win-back | When a customer hasn't ordered in a long time | Remind them what they liked and show what's new |
Welcome
This is often the email new subscribers pay the most attention to, because they just raised their hand. Keep it short: who you are, what makes your products different, and two or three links to start with. If you can, set it up as a short series. Our welcome series guide has a full sequence you can adapt.
Product launch
Lead with the product, not the announcement. One strong photo, three lines on what problem it solves, the price, and one button. If you launch several items at once, pick a hero product and list the rest below it.
Restock
Restock emails work because the demand already exists. The hard part is knowing who wanted the item. If your store platform records waitlist sign-ups, export that list.
If it doesn't, send the restock email to past buyers of that product category, since they're the most likely to care.
Seasonal
Plan these around dates that matter to your customers, not just the big retail holidays. A garden shop's calendar looks very different from a stationery shop's. Always include your shipping cut-off dates, because they're useful information and they create a real deadline.
Post-purchase care
This is the most underused email in small ecommerce. A short "how to get the most out of your purchase" note cuts down on support questions and returns, and it builds the trust that leads to a second order. It also doesn't need to sell anything.
Win-back
Send this to customers whose last order was a long time ago relative to how often people usually buy from you. A coffee subscription store and a furniture store should define "lapsed" very differently. Keep the tone friendly, show what's changed, and don't assume a discount is necessary.
Building segments from your order export
You don't need a live integration to segment customers well. Almost every store platform lets you export customers and orders as a CSV file. With a little spreadsheet work, that export becomes useful segments.
Step 1: Export and clean
Export customers with at least these columns: email, first name, marketing consent status, total orders, and last order date. Also export the orders, so you can see which product categories each customer bought. Remove anyone who hasn't agreed to receive marketing email.
Step 2: Add the columns you'll segment on
In your spreadsheet, derive a few simple fields:
- last_order_date, kept as a date
- order_count, to tell first-time buyers from repeat customers
- main_category, the product category they buy most
- customer_type, such as "subscriber-only", "one-time buyer", or "repeat buyer"
Step 3: Import with column mapping
When you import the CSV into your email tool, map each column to a contact field. Standard columns like email and name map directly. The derived columns become custom fields or tags. For example, tag repeat buyers "repeat" and store main_category as a custom field.
Step 4: Build segments
Some segments that pay off for small stores:
- Bought from category X, for launches and restocks in that category
- One order only, for a second-purchase nudge
- Three or more orders, for early access and a thank-you
- Last order more than a set number of months ago, for win-back
- Subscribed but never purchased, for a bestseller introduction
For more ideas, see our list of 15 segments that matter.
The trade-off is freshness. A CSV is a snapshot, so re-export and re-import on a regular schedule, such as monthly, or before any campaign where recent purchases matter.
Cart abandonment, explained honestly
Cart and checkout abandonment emails are often the first automation people ask about. Before you chase it, it helps to know what it actually needs.
It needs live store event data
An abandoned cart email can only go out if something knows, in close to real time, that a specific person put specific items in a cart and didn't finish buying. That information lives inside your store. A general email tool can't see it unless the store sends that event data across.
How stores usually do it
- Built into the store platform. Shopify, for example, can automatically email customers who abandon checkout. Shopify treats a checkout as abandoned once it has been left incomplete for more than ten minutes after the customer entered their email.
- A store-integrated email platform. Tools like Klaviyo connect to the store and receive events such as "Added to Cart" and "Started Checkout". Klaviyo's own abandoned cart setup guide notes that your ecommerce platform must be integrated before the flow can work.
Cresca doesn't connect to store carts or receive ecommerce events, so it can't send cart abandonment emails. If you need them, use your store's built-in recovery email or a store-integrated tool. It's perfectly common to run that alongside a separate tool for newsletters and campaigns.
When a small store doesn't need it yet
Cart recovery depends on traffic. If only a handful of people start checkout each week, the number of carts you could recover is small, and your time may be better spent on a welcome series and a regular newsletter that bring people back in the first place. Check whether your store platform already includes a basic checkout recovery email.
Many do, and turning it on takes minutes.
Store-native tool or a simpler email platform?
This is a fit question, not a quality question. Here's an honest way to decide.
| A store-native tool (Klaviyo, Shopify Email, and similar) is the better fit if... | A simpler email platform is fine if... |
|---|---|
| You want automations triggered by browsing, cart, or checkout behaviour | Your email is mostly newsletters, launches, and seasonal campaigns |
| You want product blocks that pull live prices and stock from your catalogue | You're happy to write the email and link to product pages yourself |
| You need revenue attributed to each email inside the email tool | You're comfortable checking sales in your store's own reports |
| Your catalogue and order volume are large enough that manual exports become a chore | A monthly CSV export keeps your segments fresh enough |
| You sell only through one store platform | You sell across several channels or also run a services business |
Cresca sits in the right-hand column. It generates campaigns and templates from a prompt, which you then edit in a visual editor. It also handles your contacts, segments, and scheduling, sends from your own verified domain, and reports deliveries, bounces, complaints, and unsubscribes.
It also adds one-click unsubscribe headers and automatically suppresses addresses that bounce or complain. Sales attribution comes from your store's analytics, not from Cresca.
An example monthly calendar
The calendar below is illustrative, for a small store sending about one campaign a week plus ongoing automated emails. Adjust it to your season and product cycle.
| Week | Campaign | Audience |
|---|---|---|
| Week 1 | Monthly newsletter: what's new, a behind-the-scenes story, and one customer tip | All subscribers |
| Week 2 | Product launch or restock | Buyers of that category, then everyone two days later |
| Week 3 | Educational email: a how-to, care guide, or styling ideas | All subscribers |
| Week 4 | Seasonal or event email, with any shipping cut-offs | All subscribers. A win-back version goes to lapsed buyers. |
| Always on | Welcome series and post-purchase care | New subscribers and recent buyers |
Schedule the month's campaigns in one sitting. Write them, set send times, and you're done until next month. Our 50 marketing email ideas can help fill gaps when you run out of things to say.
Compliance basics
This isn't legal advice, but a few rules apply to almost every store sending marketing email. The rules depend on where your customers are. If you sell into the US, read the FTC's CAN-SPAM compliance guide. Among other things, it requires:
- Header information and subject lines that aren't false or misleading
- A valid physical postal address in each commercial email
- A clear way to opt out, with opt-out requests honoured within 10 business days
Major mailbox providers add their own requirements. Yahoo's sender best practices ask bulk senders to support one-click unsubscribe and to honour unsubscribes within two days. That's stricter than the legal minimum, so treat it as the standard to meet.
Getting consent right at checkout is up to your store setup, so only import customers who opted in to marketing.
Where to start this week
- Export your customers and remove anyone without marketing consent.
- Add last order date, order count, and main category, then import.
- Set up the welcome email or series.
- Turn on your store's built-in checkout recovery email, if it has one.
- Write and schedule next month's four campaigns.
That's a complete, working email program for a small store. Add complexity only when the simple version is running smoothly and you can see where more would help.
Continue learning
Related Cresca resources
External references