Drop Shipment Rules blueprint

[Nicolas Évrard]

Hello,

I have started a new blueprint that define how we could handle
different rules wrt the drop shipment process.

https://code.google.com/p/tryton/wiki/DropShipmentRules

There is a pending question related to the place where the
drop_shipment_rule object should be stored.

Initially I though about the warehouse because I find it logical that
different warehouses might use different policies.

Cédric has raised concerns about this choice.

Another option that might be logical would be to add a property in the
sale.config object in order to define company-wide default for this
value.

Does anybody have an opinion on this matter? If so please make
yourself heard that would help us decide what is the best course of
action.

--
Nicolas Évrard

B2CK SPRL
4, rue de Rotterdam
4000 Liège
Belgium
Tel: +32 472 54 46 59
E-mail/Jabber: nicolas...@b2ck.com
Website: http://www.b2ck.com/

[Cédric Krier]

On 24/09/13 15:29 +0200, Nicolas Évrard wrote:
> Hello,
>
> I have started a new blueprint that define how we could handle
> different rules wrt the drop shipment process.
>
> https://code.google.com/p/tryton/wiki/DropShipmentRules
>
> There is a pending question related to the place where the
> drop_shipment_rule object should be stored.
>
> Initially I though about the warehouse because I find it logical that
> different warehouses might use different policies.
>
> Cédric has raised concerns about this choice.
>
> Another option that might be logical would be to add a property in the
> sale.config object in order to define company-wide default for this
> value.

I think there is no need to get a Model with a one2many because such
rules apply on all the company.
If different behavior is expected to be based on location then a new
matching field for location would be added to the rules.

The question could be more is a rule matching pattern the right solution
for this feature.
An other possible solution will be to just improve
sale_supply_drop_shipment to allow a computation of the property
"drop_shipment" on the ProductSupplier instead of fixed value.

--
Cédric Krier

B2CK SPRL
Rue de Rotterdam, 4

4000 Liège
Belgium
Tel: +32 472 54 46 59

Email/Jabber: cedric...@b2ck.com
Website: http://www.b2ck.com/

[Cédric Krier]

On 24/09/13 16:11 +0200, Cédric Krier wrote:
> On 24/09/13 15:29 +0200, Nicolas Évrard wrote:
> > Hello,
> >
> > I have started a new blueprint that define how we could handle
> > different rules wrt the drop shipment process.
> >
> > https://code.google.com/p/tryton/wiki/DropShipmentRules
> >
> > There is a pending question related to the place where the
> > drop_shipment_rule object should be stored.
> >
> > Initially I though about the warehouse because I find it logical that
> > different warehouses might use different policies.
> >
> > Cédric has raised concerns about this choice.
> >
> > Another option that might be logical would be to add a property in the
> > sale.config object in order to define company-wide default for this
> > value.
>
> I think there is no need to get a Model with a one2many because such
> rules apply on all the company.
> If different behavior is expected to be based on location then a new
> matching field for location would be added to the rules.
>
> The question could be more is a rule matching pattern the right solution
> for this feature.
> An other possible solution will be to just improve
> sale_supply_drop_shipment to allow a computation of the property
> "drop_shipment" on the ProductSupplier instead of fixed value.

Finally, I don't think any of those are good solution.
When I think about this subject, I see two kind of way:

- static value (current implementation) where the company don't want
to receive product at all (because it can not manage it).

- non-static value where the company wants to optimise the shipment
and warehouse cost. But this one can not be managed correctly by
static rules because such optimisation will depend on many
parameters like: sale frequency, quantities, stock quantities,
supplier delivery cost etc.
So this are too much parameter to be computed on the fly which
means this optimisation should be done by a background process
which will update the static value for the period until the next
run.

[Mathias Behrle]

* Cédric Krier: " Re: [tryton] Drop Shipment Rules blueprint" (Wed, 25 Sep 2013
13:12:21 +0200):

Couldn't nevertheless a rule object be a good extensible base for the control
of the delivery process (used by such background process)?

However I see this rule object not specially on drop shipment, but on the
delivery process at all. Should be on the company, and warehouse should be in
the rule.


--

Mathias Behrle
MBSolutions
Gilgenmatten 10 A
D-79114 Freiburg

Tel: +49(761)471023
Fax: +49(761)4770816
http://m9s.biz
UStIdNr: DE 142009020
PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6

[Axel Braun]

Schöne Grüße,
Axel
--
Written from my Google Nexus with K-9 Mail. Apologies for typos and swypos.



"Nicolas Évrard" <nicolas...@b2ck.com> schrieb:

>Hello,
>
>I have started a new blueprint that define how we could handle
>different rules wrt the drop shipment process.
>
> https://code.google.com/p/tryton/wiki/DropShipmentRules
>
>There is a pending question related to the place where the
>drop_shipment_rule object should be stored.
>
>Initially I though about the warehouse because I find it logical that
>different warehouses might use different policies.
>
>Cédric has raised concerns about this choice.
>
>Another option that might be logical would be to add a property in the
>sale.config object in order to define company-wide default for this
>value.
>
>Does anybody have an opinion on this matter? If so please make
>yourself heard that would help us decide what is the best course of
>action.

I could only give you an idea on the functional triggers. Most companies tie this to a certain product, customer, pack respective sales size ( e.g. full pallets as drop ship, single units out of stock), or decide even on sales line level, e.g. by setting an appropriate flag.

Hth
Axel