Can Nonito run cross-sell on Email from Odoo?

Yes. Odoo's segment of past buyers event starts the flow, and Nonito sends the Email message with the customer's details filled in from Odoo. It runs on its own once switched on.

Which Odoo event starts it?

Segment of past buyers. Every Odoo order is kept against the customer, so a segment can pick who bought what, and how long ago.

Is email worth running next to WhatsApp?

For messages with several products or long details, yes. Email costs next to nothing per send and holds a grid of products. Keep the urgent, single-action messages on WhatsApp and let email carry the browsing.

Can the messages go out in Arabic?

Yes. A Language node sends Arabic speakers the Arabic template and everyone else the English one, using the language on the Odoo customer record.

Why email rather than WhatsApp?

Merchandising needs room: several products, images, a bit of story. WhatsApp carries the transactional moments; email carries the longer sell.

How good are the recommendations on a small catalogue?

They lean on tags and collections, so a small well-tagged catalogue often performs better than a large messy one. The tagging is the work.

Odoo × Email

Cross-sell on Email, straight from Odoo.

Odoo's segment of past buyers event starts a Nonito flow that sends the customer a Email message, in English or Arabic, and attributes every order that follows. Email has room for a full product grid and costs next to nothing per send, which makes it the right channel for anything that needs comparing.

Book an Odoo demo See the setup

What the flow uses from Odoo.

Nonito receives orders, order status changes and customers from Odoo. For this flow it listens for one event and uses a handful of fields from it.

From Odoo	What it is for
Segment of past buyers `order_created`	Every Odoo order is kept against the customer, so a segment can pick who bought what, and how long ago.
Purchase history	What each person has bought. Without it there is nothing to recommend from.
Email address	This flow carries images and several products, which is an email job.
Catalogue tags	How your products relate to each other. A well-tagged small catalogue beats a messy large one.
Stock levels	So you do not recommend something nobody can buy. Optional.
Browsing behaviour	Sharpens the pick where you have it. Optional.

The flow, as it sits in the builder.

Take a segment, work out what each person should buy next from what they already bought, and send it.

Cross-sell · Odoo → EmailLive in Nonito

Triggers

Get Audience

Event:Segment of past buyers

Source:Odoo

Recommendations

Product Recommendations

Source:Purchase history + tags

Messaging

Built with:AI email builder

Timing

Wait

Duration:5 days

Logic

Skip If

Skip when:Order already placed

Messaging

Content:Second pick, new category

The same builder your team logs into. Every node here is configurable.

First email, the obvious pair

Subject: The Leather Card Holder that goes with your Classic Tote You bought the Classic Tote three weeks ago. Here are the two things people buy next, and one of them fits it exactly.

Second email, different category

Subject: A different idea Not that one then. People who bought the Classic Tote also tend to pick up the Weekend Bag.

2 Email templates to copy.

Use them as they are or rewrite them in your voice. The variables in braces are filled from Odoo at send time.

First email, the obvious pairEnglish

Subject: The {{recommended_product}} that goes with your {{product_name}}

You bought the {{product_name}} {{time_since}} ago.

Here are the two things people buy next, and one of them fits it exactly.

Naming what they already own in the subject line is what separates this from a newsletter. It could only have been sent to them.

Second email, different categoryEnglish

Subject: A different idea

Not that one then. People who bought the {{product_name}} also tend to pick up the {{alternative_product}}.

Acknowledging that the first pick missed is more honest than repeating it, and it earns the second attempt.

Every message in this flow, with the reasoning behind each one: Cross-sell & Recommendations in the flow library →

How to set up cross-sell on Email from Odoo

Connect Odoo through Nitro

Nitro, Nonito’s enterprise platform, sends your Odoo orders and customers into the Nonito events API as they happen. It is set up with you during onboarding, against your own Odoo instance.

Connect email

Verify your sending domain so the email comes from your brand, not from us. Unsubscribes are handled for you and respected by every later flow.

Then build the flow

Build the segment first, usually one order and nothing since.
Create the flow and choose Get Audience as the trigger, then select the segment.
Add a Product Recommendations node reading purchase history and catalogue tags.
Exclude anything the customer has bought recently.
Add an Email node and build the campaign around the personalised product block.
Add a Wait node of 5 days.
Add a Skip If node on order placed.
Add a second Email node with a pick from a different category, then end the flow.
Turn it on. Every order that follows a message is attributed back to this flow in the dashboard, so you can see what it earned.

Where this goes wrong

Recommendations are only as good as your tagging. If products are not related to each other in the catalogue, the picks will look random.
A segment that never refreshes turns into a static list, and the same people get the same email repeatedly.
This is the newest flow here. There is no production data behind it yet, and the page says so.

Questions Odoo teams ask about this.

Can Nonito run cross-sell on Email from Odoo?: Yes. Odoo's segment of past buyers event starts the flow, and Nonito sends the Email message with the customer's details filled in from Odoo. It runs on its own once switched on.
Which Odoo event starts it?: Segment of past buyers. Every Odoo order is kept against the customer, so a segment can pick who bought what, and how long ago.
Is email worth running next to WhatsApp?: For messages with several products or long details, yes. Email costs next to nothing per send and holds a grid of products. Keep the urgent, single-action messages on WhatsApp and let email carry the browsing.
Can the messages go out in Arabic?: Yes. A Language node sends Arabic speakers the Arabic template and everyone else the English one, using the language on the Odoo customer record.
Why email rather than WhatsApp?: Merchandising needs room: several products, images, a bit of story. WhatsApp carries the transactional moments; email carries the longer sell.
How good are the recommendations on a small catalogue?: They lean on tags and collections, so a small well-tagged catalogue often performs better than a large messy one. The tagging is the work.