Ecommerce Email Marketing Software, Wired To What Actually Happened.
We are not another email marketing platform. We are the backend underneath one: the cart, the order and the stock count live here, so a flow fires on a checkout that really stalled and mail goes out with the right details. Run campaigns in Klaviyo, which connects.
Mail That Starts From A Real Moment
Most email tools sit beside the store and learn what happened when an export arrives. These are events on the backend that took the order, so a flow can start on them within minutes.
storefront.added_to_cartSomething Went In The Cart
The earliest signal you get, and the one most systems never see because the cart lives in a different product from the mailer.
storefront.checkout_startedCheckout Began
A started checkout that never became an order is the abandoned cart, and it is an event here rather than a nightly reconciliation job.
order.placedThe Order Landed
Confirmation, receipt, a tag on the customer, a task for whoever packs it.
order.deliveredIt Arrived
Ask for the review while the parcel is still in their hands rather than a fortnight later.
order.payment_failedThe Card Failed
Send the repayment link straight away, before anybody has to chase it by hand.
inventory.stock.restoredIt Came Back
Back-in-stock mail on the variant that returned, not on the product it belongs to.
And What It Does Next.
A flow is not only a mailer. Once it has started, the same run can write to the customer, tell your team and create the work that follows.
Which is usually what you wanted: the review request and the packing task belong to the same delivery.
Send An Email
Written inline, or from a saved template with its variables filled from the event.
Update The Customer
Write back what the event told you, so the next message knows it.
Tag The Customer
So the next flow can behave differently for somebody who has already bought.
Draft It With AI
A generation step inside the flow, for copy that depends on what just happened.
Tell Your Team
An internal email or a dashboard notification, for the events a person should see.
Open A Task
When the right response is work rather than a message.
Templates That Cannot Go Out Blank.
Every template carries a subject, an HTML body, a plain-text body and a typed list of the variables it expects. A flow filling one in is filling in named fields, so the customer’s name cannot quietly become an empty space in a live send.
Reusable components for the parts every message shares, and revision history for the day somebody changes one and wishes they had not.
Where Klaviyo Fits.
What runs here is lifecycle and transactional email. There is no audience builder and no send-to-a-list campaign blast, so if your week is built around newsletters to segments, keep the tool that does that. Klaviyo connects, and that is the point rather than an apology.
Both get sold as “email marketing software”, and they are two different jobs. Campaigns go out to a list you chose. These go out because something happened to one customer. You want both, and you want the second one wired to the database that actually knows.
It Reads From The Same Records
Orders
Every Status Is A Moment
Placed, delivered, picked up, cancelled, refunded. The same statuses order management works from.
Stock
Back In Stock, Per Variant
The alert fires on the size that returned, because that is where the count lives.
Sites
Every Storefront
A cart on any of your storefronts starts the same flow, because they share one backend.
Questions People Ask
What is ecommerce email marketing software?
It is the system that sends the mail a store owes its customers: the confirmation, the abandoned-cart nudge, the shipping note, the review request, the back-in-stock alert. On DashForDevs it runs on the same backend as the orders and the catalog, so the emails are triggered by things that actually happened rather than by an export that arrives the next morning.
Does it handle abandoned cart emails?
Yes, and from a real event. Adding to cart and starting checkout are both triggers, so a checkout that never became an order can start a flow within minutes. Nothing is inferred from a nightly comparison of two systems, because there is only one system.
Can I use my own email templates?
Templates are first class, and editing them is the point rather than an afterthought. Each has a subject, an HTML body and a plain-text body, plus a typed list of the variables it expects, so a flow filling one in cannot quietly leave a blank where a name should be. Reusable components and revision history come with it, so every message the store sends can be made yours.
Is this a replacement for Klaviyo or Mailchimp?
No, and it is not trying to be. Klaviyo is a supported integration and it is where campaigns belong: audiences, segments, newsletters. What lives here is the layer underneath, the part that knows a checkout stalled or a variant came back and sends the mail the store owes because of it. The two do different jobs and they connect.
Can it send SMS?
Not today. Email, internal email, dashboard notifications and tasks are the channels a flow can use right now. SMS is something we are working on through Klaviyo rather than something you can switch on, and we would rather say so than have you find out after signing up.
What can trigger an email?
Cart and checkout events, all eight order events including pickup and refund, the three stock events, customer sign-up and email subscription, a submitted form, a webhook you call yourself, and plain schedules. If it happened in the backend, a flow can start from it.
Send The First One This Week.
Sign up, take your keys, and put a real abandoned cart through a real flow.