* Betr.: " Re: [tryton] New step in sale, purchase workflow" (Thu, 24 Nov 2011 19:11:31 +0100):
> On 24/11/11 18:51 +0100, Mathias Behrle wrote:
> > * Betr.: " [tryton] New step in sale, purchase workflow" (Thu, 24 Nov 2011
> > 17:17:10 +0100):
> >
> > > Hi,
> > >
> > > I'm implementing a module "sale_credit_limit" that prevent validating
> > > sales for a party if he has exceeded his credit limit.
> > > At this stage, I have a problem with the current workflow of sale. After
> > > a lot of thought, I think we have made a design mistake in the
> > > confirmation workflow.
> > > Indeed we have merged the customer validation and the company
> > > validation. And I think it is good to have a separation between those 2
> > > steps. This will allow to generate other documents (shipment, invoice
> > > etc.) in a batch mode.
> >
> > Why is batch mode only possible with an additional step?
>
> Because a sale in quotation doesn't mean that the customer agree on it.
> You need to store this information on it.
Ok. Then I understand now, that this has primarily nothing to do with credit
limit;).
> > > So the idea will be to have an extra step between the quotation and the
> > > confirmation, let's name it "Customer confirmation".
I don't know. it it should be part of the base module.
Example: WebShop with General Terms and Conditions saying, that the purchase
of the customer is automatically his agreement on the trade. You won't need an
explicit customer confirmation in this case.
> > I think, that the needs can differ a lot for different companies. While one
> > will want to prevent even the creation of quotations (i.e. locking down
> > sales with certain defaulting customers),
>
> Quite strange but why not.
>
> > another one will only want to prevent to
> > send out the shipment (s. sharoon).
>
> I think it is really strange to accept sale to someone that you know you
> will not send him the products because he doesn't pay.
>
> > Both are cases of customer validation, but
> > stepping in at a different time.
>
> I don't see where is the customer validation in your example.
I misunderstood first the meaning of customer validation, s. above.
> > I don't see the real difference between customer validation and company
> > validation, finally it is validation.
>
> But a sale is a contract between 2 parties. So you need to have
> validation of both. I think it is not modular nor flexible to make both
> validation merged into one.
> Think about e-commerce website, most of the time, you validate your
> order and you have to wait for the validation of the supplier to be
> sure.
>
> > For me this seems to be the most suitable
> > step to meet most needs.
>
> Which? Having only 1 validation for both side?
>
> > I could very well imagine a warning wizard like for force assign, permitting
> > only users with special permissions to override the credit limitation.
>
> This doesn't work because you will not be able to make the difference
> between sales that are validated but blocked by credit limitation and
> sales that are just waiting for validation.
I see. Where would you want to hook in 'credit limitation check'? After
'customer validation', but before 'Confirm'?
--
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
signature.asc
Description: PGP signature
