Skip to Content
  2. Mailing Lists
  3. Contributors
  4. Re: Service definition modules

Archives

Contributors

Re: Service definition modules

Request for new repository sale-terms-conditions

Re: Service definition modules


But the sets of modules we're talking about is more about defining parameters on terms, that can be customized at customer level. So it is more a generic way to deal with terms and parameters linked to customer orders.

Then each of those parameter will probably call some features (distributed across several area: deliveries, invoicing, etc..)

So we're looking to where we should push those set of modules (for the parameters as described here https://github.com/OCA/stock-logistics-warehouse/issues/694).

Can we vote ?

1) include in delivery
2) Include in sale-workflow
3) include in contract
4) or agreed for a new repo sale-term-condition

I vote for 4) as it is not only linked to deliveries or sales nor contract (in the meaning of the current set of modules that mostly deal with contract with customers, not really on the definition of services.

Regards,

Joël


On Thu, Sep 5, 2019 at 1:12 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
Please don't use plurals in the module name for following guidelines. Take also into account https://github.com/OCA/delivery-carrier/tree/11.0/partner_delivery_schedule that already allows to set delivery slots for partners, which is one of the concepts you are defining. If everything is related to delivery, I would put modules in OCA/delivery-carrier.

Regards.

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



--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Department Head
Business Solutions

+41 21 619 10 28


by Joël Grand Guillaume - 09:51 - 5 Sep 2019

Reference

  • Service definition modules 
    Hello all,

In relation with the WMS modules Camptocamp is currently working on, I'm
working on a set of modules to manage service definition.

The idea is to be able to store a set of service levels agreed on with
the customer, with a number of parameters which are specified, and have
default values, but can be customized for a given customer, or a given
sale order.

Typically the parameters could be:

* management of backorders
* days of delivery
* hour of delivery
* invoicing per order (with order reference) or invoicing per delivey
* packaging details in the invoice
* product grouping preference (e.g. a customer could ask for an order of
10 product1, 10 product2, 10 product3 to be packages in 10 parcels
containing each 1 product1, 1 product2, 1 product3 instead of 3 packages
containing a singe product reference)
* constraints on the delivery truck (max dimension, max weight)...

The basic set of user stories is available in
https://github.com/OCA/stock-logistics-warehouse/issues/694 (this issue
will be moved to a better place once we've answerd the question below)

I'm planning to build this as a base module providing the models
required to define the service definitions, and set this on a customer
and on a sale order (+ propagation to invoices and deliveries), +
different smaller modules related to the different aspects (deliveries,
packaging, invoicing...)

I would like to propose these as alpha modules in the OCA but I'm unsure
what repository to target:

* option 1: new repository oca/sale-service-definition, all the addons
go there
* option 2: in repository oca/sale-workflow, at least for the base
module, but then I'm not comfortable in adding cross repository
dependencies, because some of the other modules would probably live in
the WMS repository, others in sale-workflow, others in some maybe in
stock-logistics-*
* option 3: in repository oca/contract because this is related to sale
contract, but I'd like to avoid polluting a self contained module with
lots of cross dependencies
* elsewhere ?

Dear contributors, what would be the best course of action in your opinion?


-- 
Alexandre Fayolle
Chef de Projet
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
    by Alexandre Fayolle - 10:46 - 4 Sep 2019