Automations
Let the store do the routine workwhile you get on with selling.
Pick one of 235 things that happen in your store, such as an order placed, a cart left or a parcel returned, and draw what follows: wait, check, email, tag, hold, issue a coupon. Bazuva runs it for every order and every customer, on your store's clock.
- 235 events to start from
- 86 steps
- Splits that pick a winner
- Approvals before big steps
An automation engine, counted
235
events in the store that can start a flow
86
steps to wait, check, send and act
10
flow templates ready to copy
2
flows already running in every new store
The difference
The same jobs come round every day. They do not need a person every time.
Without Bazuva
With Bazuva
Someone messages the buyers who left a cart, on the days there is time.
An abandoned cart starts a flow within the hour, and the reminder goes out whether anyone is at the desk or not.
A large cash order ships before anyone notices it should have been checked.
An order over your limit is held, a manager approves it from the approvals inbox, and the flow carries on.
Review requests go out by hand, weeks late or not at all.
Seven days after an order is completed the buyer is asked for a review, and a buyer who said no is not asked again.
Two versions of an email, and no way to tell which one sold more.
A test split sends each group its version and moves everyone to the winner once the numbers say so.
Triggers
Start from anything that happens in the store.
Orders, payments, parcels, returns, carts, customers, reviews, stock, forms and blog posts each announce what happened to them, and 235 of those events can start a flow. So can a schedule, such as every Monday at nine, or a date, such as seven days before a birthday or sixty days after a last order. A condition on the trigger narrows it to the cases you mean.
- Events from orders, payments, shipping, returns, stock and more
- Schedules on your store's clock, from every ten minutes to monthly
- Dates such as a birthday or a last order, with an offset
- Customers joining or leaving a segment
Steps and approvals
86 steps, from a reminder email to holding an order.
Waits and conditions shape the path: wait an hour, wait until your business hours, wait for the order to be paid, or wait for the first of three events. Then act on anything the store owns: send an email, tag or note a customer, hold, confirm or cancel an order, book a courier, approve a return, adjust stock or call a webhook. A step that matters can ask a person first.
- Waits for a time, a date, an event or a condition
- Conditions over 244 facts, grouped as all, any or none
- Order, payment, shipment, return, stock and product actions
- An approval step that waits for a yes, a no or a timeout
Test splits and reports
Try two versions. Keep the one that sells.
A split sends each run down one of up to five branches. Make it a test, choose what counts (clicks, orders or revenue), a minimum number of people and a deadline, and Bazuva picks the winner and sends everyone after that down its branch. Every flow shows a funnel step by step, and the orders that followed a click in its emails.
- Up to five branches, weighted as you like
- A winner chosen by clicks, orders or revenue
- A funnel showing who reached, waited at or skipped each step
- Revenue from the last email click before an order
Templates
Two flows are working the day you open.
Every store starts with the abandoned-cart reminder and the review request already running. Eight more templates are a click away: book the courier when an order is paid, follow up a failed delivery, tag customers who have not ordered in sixty days, route and follow up form leads. Each one opens on the canvas, ready to change.
- Abandoned cart and review request installed in every store
- Book a courier as soon as an order is paid
- Tag customers who have gone quiet for sixty days
- Pause, copy or change any template like your own flow
How it works
Draw it once. It runs for every customer.
- 1
Start from a template or a blank canvas
Ten templates cover the common jobs; anything else starts empty.
- 2
Choose the trigger
An event, a schedule or a date, narrowed to the orders or customers you mean.
- 3
Draw the steps
Drag waits, conditions, splits, approvals and actions onto the canvas.
- 4
Publish and watch the runs
Follow each run step by step, retry one that failed, and read the funnel.
Everything included
Triggers, steps, reports and control, in one canvas.
Triggers
- 235 events, from orders to reviews
- Schedules on the store's clock
- Dates with an offset, such as a birthday
- Customers joining or leaving a segment
Waits and logic
- Wait for a time, a date or business hours
- Wait for an event, or the first of three
- Conditions grouped as all, any or none
- Goals that end a run when they are met
Actions
- Emails from your own templates
- Tags, notes and coupons for a customer
- Hold, confirm, cancel or tag an order
- Webhooks and requests to your other tools
Sending with care
- Caps on emails per day and per week
- Quiet hours that hold a send until morning
- Marketing only to customers who agreed
- Order and delivery emails left out of the caps
Reports
- A funnel for every step
- Clicks and last-click revenue
- Test splits with a chosen winner
- Every run with its log, to cancel or retry
Control
- An approvals inbox with a count in the bell
- Versions of every flow
- Segments kept current as customers change
- Who may build flows decided by role
Questions about automations
Do I have to build anything before it is useful?
No. Every store starts with two flows running: the abandoned-cart reminder and the review request seven days after an order is completed. Pause them, change them or copy them like any flow of your own.
What stops a customer getting too many emails?
Caps per day and per week, one and four by default, and quiet hours that hold a send until they end. Order and delivery emails can be left out of the caps, and marketing goes only to customers who agreed to it.
How does a test split choose a winner?
You choose what counts, clicks, orders or revenue, a minimum number of people for each version and a deadline. When each version has its minimum, or the deadline passes, the version with the best rate wins and every later run takes its branch.
Can a person check a step before it happens?
Yes. An approval step holds the run and asks the people with the permission you choose. They answer from the approvals inbox, and the flow follows the approved, declined or timed-out branch.
Which time do schedules and waits use?
Your store's own time zone and business hours, so 'every Monday at nine' and 'wait until we open' mean your Monday and your opening time.
Your store is one sign-up away. Open it today.
Register, choose a design and add your first product. Cash on delivery, couriers and your buyers' language are ready when you are.
Your domain, your brand, no code to write.