Email marketing for ecommerce: a flow plan

Email marketing for ecommerce should follow customer events. Build a welcome flow for subscribers, a checkout recovery flow for eligible shoppers and a post-purchase journey for buyers. Give each flow a useful purpose, a clear entry rule and a stop condition before increasing message volume.

For an Indian D2C store, this means connecting email to the actual order and product experience. A welcome coupon should stop when someone has already used it. A product guide should arrive when it can help. Set the timing around delivery, product use and the next buying decision.

Separate flows from campaigns

A campaign is a scheduled message to a selected audience. A flow responds to a person doing something or becoming eligible for a particular journey. Both can reach the same customer, which is why they need a shared contact plan.

Begin with a simple map. Write the customer's state on the left and the message's job on the right. “New subscriber” is a state. “Explain the product range and help them choose” is a job. “Send a weekly offer” describes your calendar rather than the customer's need.

Do not activate everything at once. Map what is already running in Shopify and your email provider. A duplicate automation is still a duplicate when it lives in a different app.

Prepare the list and sending domain

Keep the permission record with the subscriber. You should be able to explain where the subscription happened and what the person expected to receive. Keep order notifications and optional marketing distinct in your planning.

Before sending, check the domain authentication instructions in your email platform. Google's sender guidelines distinguish requirements for all senders from stricter requirements for those sending more than 5,000 messages daily to personal Gmail accounts. The bulk requirements include SPF, DKIM and DMARC, along with one-click unsubscribe for marketing and subscribed messages.

A visible unsubscribe link remains useful to the reader. The one-click mechanism also needs the appropriate email headers; a preferences page alone is not the same mechanism. Ask whoever manages the domain and email platform to verify the setup with a received test message.

Use a sender identity the customer recognises. Check the reply address and confirm that a person actually reads replies. A message that asks customers to reply for help should not lead to an abandoned inbox.

Avoid importing an old list merely because it contains customers. Review permission and recent relationship before choosing who should receive marketing. Start with people who expect the messages and inspect bounces and complaints before expanding the audience.

Build the welcome flow around a buying decision

A welcome message should fulfil the promise made at signup. If the form offered a guide, send the guide. If it offered a first-order benefit, show the terms and expiry accurately. Avoid making the customer hunt for what they requested.

Example welcome sequence: send the promised information on signup. Follow with a product-selection note after enough time to read the first email. A later message can address a genuine buying objection. Check clicks and replies before shortening the delays.

For a homewares store, use the follow-up to compare container sizes by use: pantry staples, snack storage and small leftovers. The primary action is to view the size guide. That is a more specific job than displaying the entire catalogue again.

Check purchase status before each promotional welcome message. Move buyers into the appropriate post-purchase journey. If a subscriber receives the offer, buys and then sees “still deciding?” the sequence is ignoring the event that matters most.

Keep checkout recovery in its own lane

Checkout recovery serves a recent unfinished buying intent. Give it priority over a generic campaign if the two would collide, then document how that priority works in your platform. A manual note that “someone will remember” will fail as the list grows.

The key tests are a working checkout event and a working purchase exit. Test a customer who completes the order during the delay, a customer who unsubscribes and a shopper who changes the cart. Inspect what would be sent in each case.

A recovery email should contain the correct product information and a link that opens the intended basket or checkout. Check it on a phone in a fresh browser session. The abandoned cart recovery guide gives a sample sequence and the measurement definitions.

Make post-purchase email useful before it sells

Order confirmation, dispatch updates and product education have different jobs. List every message the customer already receives, including courier notifications, before adding your own. The buyer sees one conversation even if several suppliers send it.

Klaviyo's post-purchase guide describes an order-triggered flow with delays and customer splits. Use the split to distinguish a first-time buyer from someone who knows the product. Adapt the content rather than sending the same introduction indefinitely.

A planning example for a hypothetical kitchen product:

• On order confirmation, explain the delivery expectation and support route.
• After confirmed delivery, send the care instructions needed before use.
• Once there has been time to use the item, invite practical feedback.
• When a relevant complement makes sense, explain what it adds to the original purchase.

Use confirmed delivery events for care guidance and feedback requests. If the store supplies only an order-created event, add delivery-exception checks before sending. Allow time to use the product before asking for feedback.

Example copy: “The lid seal lifts out for cleaning. Here is the care guide with pictures. If the fit is wrong, reply with your order reference and we will help.” Match the care instructions and reply promise to your product and support process.

Add filters and test every exit

A flow diagram should show who leaves as clearly as who enters. Klaviyo's triggers and filters documentation explains the distinction between entry conditions and profile filters checked during a flow. Check your integration's event names rather than copying another store's configuration blindly.

Create a test sheet with the expected outcome before running each profile through the journey:

1. A subscriber with no order remains eligible for the welcome guidance.
2. A buyer is excluded from a first-order promotion after the purchase event syncs.
3. An unsubscribed customer does not receive optional marketing.
4. A cancellation or refund routes to the appropriate support treatment.
5. A repeat purchase prevents a stale replenishment reminder.

Use staff-owned test addresses and labelled test orders. Inspect dynamic values, product links, mobile layout and the unsubscribe route. Run each case through the integration and confirm that the template receives the required fields.

Keep test records out of performance reporting. Save a screenshot of the final flow logic, the date it was enabled and the person responsible for it. This makes the next audit much easier.

Measure email revenue after the order settles

Email attribution records what the platform associates with a send under its attribution rules. It does not, on its own, establish which purchases would have happened anyway. Review the attribution window and whether the report uses gross or net sales.

Here is a hypothetical accounting exercise for one flow. Assume tax-exclusive product values and no separate shipping revenue. Suppose the platform reports ₹50,000 in ordered product value. Discounts are ₹5,000 and cancelled or refunded product value is ₹6,000. The retained product revenue is ₹39,000 before product and fulfilment costs.

If product costs are ₹16,000, fulfilment and packaging are ₹4,000 and allocated email cost is ₹1,000, contribution is ₹18,000 before overhead and other acquisition costs.

Use your own returns window before finalising the number. Compare the same definition across flows. For a meaningful experiment, hold back a randomly selected comparable group from optional promotional messages where the sample allows it. Both groups should retain essential service communications.

Keep a contact calendar people can maintain

Give one person responsibility for the combined campaign and flow calendar. Mark sale campaigns, expected replenishment journeys and exceptional support periods in the same place. Ask what a single customer would receive if they qualified for everything that week.

When performance changes, inspect delivery, clicks, orders, opt-outs and replies together. An open is a diagnostic signal, not proof that a person read the content. Avoid choosing a winner from opens alone.

Change one significant part of a flow at a time where practical. Record whether you changed the audience, timing, offer or copy. Keep the earlier version available for comparison, and decide the next review date using the product's buying cycle. The purpose is a journey that remains useful as the customer moves from their first order to the next.