Order held to avoid capture payment failure

[Jacques Le Roux]

Hi,

I recently wrote a service that runs nighlty to put on hold every outstanding order (backordered or such) payed with a credit card which expiry date is expired or more exactly will be tomorrow. This to avoid picking/packing an order which payment can't be captured. Actually it's a part of a whole where held orders have also order items and OISG held and have also differrent reasons to explain why (some automatic, etc.). This last remark because I did not look closely to OFBiz OOTB code about held orders but it seems that it's not the case (an held order have no order items held, hence I guess no OISG). So I wonder if such things would have an interest to OFBiz OOTB ?

What do you think ?

Thanks

Jacques

[BJ Freeman]

There are a lot of services i have added that deal with fraud, orders
over a certain amount
they are hard coded.
however I think this would be a good place to see if we could start a
conversation about make the statuses more flexible so customer can add
statuses and rules
What do you think?

Jacques Le Roux sent the following on 7/12/2007 4:55 AM:

> Hi,
>
> I recently wrote a service that runs nighlty to put on hold every outstanding order (backordered or such) payed with a credit card which expiry date is expired or more exactly will be tomorrow. This to avoid picking/packing an order which payment can't be captured. Actually it's a part of a whole where held orders have also order items and OISG held and have also differrent reasons to explain why (some automatic, etc.). This last remark because I did not look closely to OFBiz OOTB code about held orders but it seems that it's not the case (an held order have no order items held, hence I guess no OISG). So I wonder if such things would have an interest to OFBiz OOTB ?
>
> What do you think ?
>
> Thanks
>
> Jacques
>

[Jacques Le Roux]

Hi BJ,

This is more ambitious than what I was thinking about. But yes why not think about a generalisation ? Have you already some ideas ?

Jacques


De : "BJ Freeman" <[hidden email]>

> There are a lot of services i have added that deal with fraud, orders
> over a certain amount
> they are hard coded.
> however I think this would be a good place to see if we could start a
> conversation about make the statuses more flexible so customer can add
> statuses and rules
> What do you think?
>
> Jacques Le Roux sent the following on 7/12/2007 4:55 AM:
> > Hi,
> >
> > I recently wrote a service that runs nighlty to put on hold every outstanding order (backordered or such) payed with a credit

card which expiry date is expired or more exactly will be tomorrow. This to avoid picking/packing an order which payment can't be
captured. Actually it's a part of a whole where held orders have also order items and OISG held and have also differrent reasons to
explain why (some automatic, etc.). This last remark because I did not look closely to OFBiz OOTB code about held orders but it
seems that it's not the case (an held order have no order items held, hence I guess no OISG). So I wonder if such things would have
an interest to OFBiz OOTB ?
> >
> > What do you think ?
> >
> > Thanks
> >
> > Jacques
> >

[BJ Freeman]

let me get my thoughts in order and present a draft.
:)
Jacques Le Roux sent the following on 7/13/2007 8:30 AM:

> Hi BJ,
>
> This is more ambitious than what I was thinking about. But yes why not think about a generalisation ? Have you already some ideas ?
>
> Jacques
>
>
> De : "BJ Freeman" <[hidden email]>
>> There are a lot of services i have added that deal with fraud, orders
>> over a certain amount
>> they are hard coded.
>> however I think this would be a good place to see if we could start a
>> conversation about make the statuses more flexible so customer can add
>> statuses and rules
>> What do you think?
>>
>> Jacques Le Roux sent the following on 7/12/2007 4:55 AM:
>>> Hi,
>>>
>>> I recently wrote a service that runs nighlty to put on hold every outstanding order (backordered or such) payed with a credit
> card which expiry date is expired or more exactly will be tomorrow. This to avoid picking/packing an order which payment can't be
> captured. Actually it's a part of a whole where held orders have also order items and OISG held and have also differrent reasons to
> explain why (some automatic, etc.). This last remark because I did not look closely to OFBiz OOTB code about held orders but it
> seems that it's not the case (an held order have no order items held, hence I guess no OISG). So I wonder if such things would have
> an interest to OFBiz OOTB ?
>>> What do you think ?
>>>
>>> Thanks
>>>
>>> Jacques
>>>
>
>
>
>