Most stores go into November with the email setup they had in March: nine default WooCommerce templates and nothing behind them. The season does not reward sending more email. It rewards email that arrives because something happened in the store, and that has to be built before the traffic shows up, not during it.
What to automate before the season starts
Four automations cover most of what a seasonal store needs, and all four can be built in an afternoon. This is the order they repay the work in.
Cart recovery comes first. A customer who reached the cart and left is the warmest audience the store has, and a single email a few hours later recovers a share of those orders without any discount at all. The second email, sent the next day, is where a discount belongs if you want one.
Post-purchase follow-up comes second. It lands a few days after delivery, says nothing about selling and asks whether everything arrived as expected. It costs nothing and it is the cheapest way to stop a problem turning into a chargeback or a public review.
Review requests come third, timed for when the customer has had the product long enough to have an opinion, which for most physical goods is seven to fourteen days after delivery rather than after payment.
Win-back comes fourth and is the one most stores skip. It targets customers who bought once and never returned, which in a seasonal month means people who already trust the store. It is also the only one of the four that needs a filter rather than a plain trigger.
Why the default WooCommerce emails are not enough
WooCommerce ships with nine transactional templates and every one of them reacts to an order status. That is the whole of their logic. Nothing in the default set can wait three days, check what the customer bought, or do anything at all when no order exists.
So the defaults cannot send any of the four, not because they are badly written but because they have no concept of time or condition. An automation adds the three missing parts: the event that starts the email, the filter that decides whether it runs for this customer, and the delay that decides when it lands.
What to set up now and what can wait
Build cart recovery and the follow-up now, because both depend on volume that has not arrived and neither can be backfilled. An abandoned cart from last Tuesday is gone. Review requests can go in now too and will fire on their own. Win-back can wait until early December, when the data exists and the audience is largest. While you are in there, the nine default notifications are worth restyling, since they are the emails every customer is guaranteed to open.
Whatever you build, send yourself a test first. Automations fail quietly, and the failure mode is an empty inbox rather than an error, which is why it is worth knowing how to test WooCommerce emails before the season rather than during it.
All four automations are built from the same three parts, so once you have made one the rest take minutes. ShopMagic is free, works on the event, filter and action model described above, and handles the delays without a separate cron plugin.
Summary
Four automations are worth building before a seasonal peak, in the order they repay the work. Cart recovery reaches the warmest audience the store has, with the first email a few hours after abandonment carrying no discount and the second, the next day, carrying one if you want it. Post-purchase follow-up lands a few days after delivery, sells nothing and asks whether everything arrived. Review requests go out seven to fourteen days after delivery rather than after payment. Win-back targets one-time buyers and is the only one of the four that needs a filter.
None of them can be sent by the nine default templates, because every default reacts to an order status and nothing else: they cannot wait, cannot check what was bought, and do nothing when no order exists. An automation supplies the missing three parts, the event, the filter and the delay. On timing, cart recovery and the follow-up are built now because neither can be applied retrospectively, review requests can be set up now and fire on their own, and win-back waits until December. Everything gets a test send first, since a broken automation shows up as an empty inbox rather than an error.
Frequently asked questions
These three come up whenever a store automates email for the first time.
Do automated emails need a separate sending service?
Not to start with. They go out through whatever WordPress already uses for mail, and the time to move to a dedicated service is when volume or deliverability becomes the constraint.
Will customers get too many emails?
They can, if several automations fire on the same order. Decide early which one wins when two could run, and check the order of the delays rather than the emails themselves.
Does cart recovery need consent?
That depends on your jurisdiction and on whether the customer reached a point where they knowingly gave you their address. Check it for your market before you switch it on, not after.
