Contributors mailing list archives
Re: connector_ecommerce dependency in v9by
Sodexis, Stephane Keller
Joël and Guewen,
Thanks for the feedback, much appreciated.
* Raise exception as now (from draft to open)* Check the matching of exceptions also when changing a confirmed order* Keep a way to force the validation even if an exception was raised
Yes agreed, as you know we are working on it.
=> +1, changing a confirm order must automate the action like if it was the initial order (e.g. adding a line should invoice it automatically, increasing quantitiy must invoice the difference, etc..)
Agreed, I think this will come somewhat automatically as the creation of the invoice should be triggered by the "Invoice Status".
We are thinking about adding filters on the Automatic workflow definition instead of having the filters setup in the code. One business case for us is that we want to create invoice and payment for Sales Order that are in the Done state instead of just confirmed. Easy also to trigger actions on custom fields. We can define default filters for the default case.
Could you give us some feedback about sale_payment_method ?
Do we need to create the payment on the sales order for the e-commerce module? Is there a business case where the sales order is imported and there is no need of an invoice? Once you do that there is a lot of code it seems that is needed to reconcile the invoice with payment, etc..
It would be simpler to follow the workflow that Odoo uses: create invoice from Sales order, and then payment from the invoice.
we can re-use the existing code. We still would need the payment method definition on the Sales Order as it is now. But we would propagate it to the invoice and use it to create the payment from the invoice (or refer to the Sales Order I guess).