Product-specific post-purchase emails with Brevo integration

Hello,

I would like to submit a feature request regarding product-specific post-purchase emails in J2Commerce 6.

Our use case is the following.

We sell different products and services through J2Commerce, and after an order reaches a specific status — for example, confirmed or paid — we would like to send the customer a different transactional email depending on the product purchased.

For example:

• Product A → Brevo transactional template ID 17
• Product B → Brevo transactional template ID 24
• Product C → no additional email

Ideally, each J2Commerce product could have settings such as:

• enable/disable the specific post-purchase email;
• transactional template ID;
• order status that triggers the email;
• optionally, parameters to pass to the template.

In our case we use Brevo, so the ideal workflow would be:

J2Commerce order → payment/order status confirmed → identify purchased products → send the corresponding Brevo transactional template(s).

This would be particularly useful for products such as courses, treatments, services, events or digital products, where each purchase may require different instructions or follow-up information.

An important requirement would also be to prevent duplicate emails if the order status is saved or changed more than once.

Before developing a custom J2Commerce plugin for this, I would like to know:

1. Does J2Commerce 6 already provide a native way to achieve this?
2. If not, would you consider this functionality suitable for J2Commerce itself or for an official extension/plugin?
3. If a custom plugin is currently the recommended solution, which J2Commerce 6 event/hook would you recommend for reliably detecting the relevant order status change after payment?
4. Is there a recommended J2Commerce API/service for retrieving the order items and their product IDs from that event?

Our intention is to keep the integration completely separate from the J2Commerce core and use the new J2Commerce 6 plugin/event architecture wherever possible.

Thank you!

Hello,

thank you again for your previous advice regarding the Brevo integration.

After evaluating both solutions, we decided to purchase and use both the J2Commerce Brevo Integration and Advanced Notifications, as we found that they are useful for two different purposes in our project.

We are using Brevo Integration for the broader eCommerce/marketing side: synchronizing customers, orders and products with Brevo, and for future marketing automations, segmentation and follow-up funnels.

We purchased Advanced Notifications for a more specific transactional requirement: each of our orders contains a single product, and each product needs to send the customer a different post-purchase message. The Product Rule functionality in Advanced Notifications is exactly what we need for this.

The functionality itself is working correctly, but during configuration we found what appears to be an editor compatibility issue.

When creating/editing a Product Rule, if a Joomla WYSIWYG editor is enabled for the administrator user, we can enter content in the Custom Message field, but after clicking Save, the Custom Message is not persisted and the field is empty when we reopen the rule.

We tested the same rule after changing the administrator user's editor setting to Editor – None. In this case, the Custom Message is saved correctly and remains stored after reopening the rule.

So the Product Rule and Custom Message persistence appear to work correctly; the problem seems specifically related to the editor integration or to the synchronization of the editor content before the Advanced Notifications form is submitted.

Our environment is:

• Joomla: 6.1.4
• J2Commerce: 6.6.4
• Advanced Notifications: [insert version]

At the moment we can work around the issue by disabling the editor for the administrator user, but this is obviously not ideal for normal day-to-day management.

Could you please check whether this is a known compatibility issue with Joomla 6 editors and Advanced Notifications, and whether a fix is available?

If useful, we can also provide a short screen recording showing the issue.

Thank you again for your support.

Best regards,
Andrea