Pedro M. Baeza

@lmignon but AFAIK, that reward part is not tied to the applicability rules, so keeping the partner applicability at that level doesn't improve anything. Can you expand that use case?

But that means that this module is also changing other part of the `loyalty` behavior, not the partner applicability, so that should go in another module, not here. I think...

OK, don't worry, I don't argue more, so let's merge it. /ocabot merge major

You should check https://github.com/OCA/automation/tree/16.0/automation_oca as an alternative to Klaviyo

OK, I was just saying, but I think that going to an heterogeneous platform and waste a lot of time connecting them instead of improving Odoo is not the way...

Again that's because an heterogeneous system. I'm doing decent e-com implementations with Odoo, but everyone decides their way, and their pros and cons. And please don't do advertising here. Hiding...

/ocabot migration crm_klaviyo

cc @chienandalu I think there's more work to do for this to work

@xtanuiha please stop publishing that files here. Keep them and you upload them on Weblate once these modules are merged.

@hbrunn it's /ocabot migration account_statement_import_file The version is taken from the target branch. What can't be guessed is the module name.