Campaigns that know what each account actually buys
Most distributor marketing is a monthly email to everyone, written by whoever has time, with no idea who opened it or what it sold. The advantage you have over a generic mailing list is that you already know exactly what every account orders, how often, and what they stopped ordering. Carrots puts that to work: promotions inside the storefront where the buying decision happens, and every trading event pushed into Klaviyo so campaigns run on real behaviour rather than a spreadsheet.
Promotions where the order is placed
Campaign cards in the storefront, promo codes, and bonus offers that add a free line when conditions are met. A promotion a buyer sees while filling their cart converts; one sitting in an inbox on Tuesday does not.
Broadcasts to the accounts it applies to
Message a segment of accounts, or put a notice on the storefront so it is read by the people ordering rather than by whoever checks the shared mailbox. Useful for a supply gap, a price change or a holiday cut-off.
Every trading event, in Klaviyo
Orders, applications, enquiries and newsletter sign-ups are pushed to Klaviyo as they happen, with the detail that makes a flow worth building: what was bought, by which account, for how much. The table below is the full list, not a sample.
Targeting from what they actually order
Because the order lines carry SKUs, quantities and line totals, a win-back flow can be built on 'has not ordered this line in six weeks' rather than on 'has not opened an email'. That is the difference between a campaign and a newsletter.
In the box
What marketing & engagement actually includes
Every line below is shipping today, in production, for distributors trading on it.
- Storefront promotion cards, promo codes and bonus offers
- Broadcasts to account segments, and storefront notices
- Four Klaviyo events pushed automatically, with full order lines
- Newsletter sign-up subscribed to your Klaviyo trade list with consent recorded
- Buyer spend analytics per account, for building segments
Works with
Klaviyo
Exactly what reaches Klaviyo, and when
Integrations pages usually stop at the logo. Here is the actual contract, so you can tell before you buy whether the flows you want to build are possible.
| Event | Fires when | What it carries |
|---|---|---|
| Placed Order | A buyer completes checkout | Order id, account and account name, the ordering channel, item count, subtotal, delivery fee and order value in AUD, plus every line with its SKU, product name, quantity, unit price and row total. |
| Submitted Partner Application | A prospect applies for a trade account | Name, business name, email and phone, written onto the Klaviyo profile so an onboarding flow can start before they are approved. |
| Submitted Contact Form | Someone sends an enquiry | Name, email, phone, subject and the enquiry id, so a reply flow can fire and the thread stays traceable. |
| Newsletter subscribe | Someone opts in, or applies for an account | The email is added to your Klaviyo trade list with email marketing consent recorded. Whether that is single or double opt-in is your Klaviyo list setting, not ours. |
It cannot slow down or break an order
Events are sent after the response has already gone back to the buyer, and every call swallows its own errors. A Klaviyo outage, an expired key or a rate limit costs you an event, never a checkout.
A retry cannot double-count revenue
Placed Order is sent with the order id as its unique key, so if the same order is ever submitted twice Klaviyo keeps one event. Your revenue attribution does not quietly inflate.
The key never reaches a browser
The private API key is held server-side only and the calls are made from our servers, so it cannot be read out of your storefront by a customer or a bot.
Nothing is sent until you connect it
With no key configured the integration does nothing at all, silently and safely. Connecting Klaviyo is a setting, not a deployment.
Want to see marketing & engagement on your own data?
We will load your catalogue and your pricing before the walkthrough, so you are looking at your business rather than a demo tenant.
