1. Mailing Lists
  2. Contributors
  3. Re: connector_ecommerce dependency in v9

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: connector_ecommerce dependency in v9

Re: connector_ecommerce dependency in v9

Avatar

Re: connector_ecommerce dependency in v9

by
Sodexis, Stephane Keller
- 21/03/2016 16:24:12
Eric,

I have not looked in details at the embedded ecommerce platform yet, so can not really comment.
I think we should make sure that  the connector module does not depend on a module that is build for the embedded ecommerce.
The base sale_automatic_workflow module should be usable by the connector and the embedded ecommerce.
So you seem to agree that we should leave on the side for now the creation of the payment on the SO and have separated module if needed later on, right?

So I am suggesting for the main flow for the base code "SO confirmation + invoice creation + invoice validation + register payment on the invoice + SO Done"
I agree with the option to set the SO as done but based on some filter that can be customized, such that it can be executed at other places in the workflow, e.g. just after the SO confirmation such that the SO can not be edited anymore.

I would leave the invoice reconciliation with a payment as a possible extension.  

Thanks for your feedback,
Stephan.



On Fri, Mar 18, 2016 at 8:53 PM, Eric Caudal <eric.caudal@elico-corp.com> wrote:

One of the few advantages of v9 ecommerce is actually the embedded ecommerce platform: generic models are ready and payment acquirers are set up in the SO after the checkout (which was not the case before: paying a SO was not standard). For this reason, a major refactor might be expected for sale_payment_method as by default we dont need to recreate anymore the payment methods just bind them with existing payment acquirers and SO relationship.
For this reason it would make more sense to embed the payment methods in the connector directly.
sale_automatic_workflow should be able to rely on that information to continue the workflow creation.
Another thing is we should add the possibility to set the SO as done with the new 9.0 workflow. Indeed in e-sales, upsells are not usual case and having "SO validation+invoice creation+invoice validation+invoice reconciliation+SO Done" automated might be the most common workflow for ecommerce sales.

--
Eric Caudal [Founder and CEO]
Skype: elico.corp. Phone: + 86 186 2136 1670 (Cell), + 86 21 6211 8017/27/37 (Office)
Elico Shanghai (Hong Kong/Shenzhen/Singapore) Odoo Gold Partner, best Odoo Partner 2014 for APAC
On 03/19/2016 04:37 AM, Stephan Keller wrote:
<blockquote cite="mid:CAJYazoHaF6jZz-uQtf=Mj__Qfp+CL7SmXJY6V=yboTU6fBesgA@mail.gmail.com" type="cite"> 
Another use case IIRC that is used by Akretion is that they don't
confirm sales order until they have a full payment by check, so they
use sale_quick_payment to generate manually the payments before the
validation.
I was wondering where was that register payment button, thanks.

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe




--
Stephan Keller, Ph. D.
CEO Sodexis, Inc.
Orlando/Longwood, FL
www.sodexis.com
Odoo Certified Expert
http://www.linkedin.com/in/stephankellersodexis
Phone: (407) 278-4917
Cell: (407) 202-8998

Reference