Re: Create return till ...

Hi All, I stumbled upon this thread by chance. Has finally something being done? TIA Jacques Le 11/03/2019 à 12:39, Rishi Solanki a écrit : I agree with the approach what Pierre suggested to go with ProductCategoryAttribute and ProductAttribute. Because for range of products we may need

Re: Create return till ...

I agree with the approach what Pierre suggested to go with ProductCategoryAttribute and ProductAttribute. Because for range of products we may need different default values. Also agree with Scott on the point there must be flexibility at CSR end to override the rule based on the reason of return

Re: Create return till ...

Hello Scott, Thank you so much for your response. Yes, this is the exact way it is been managed currently. Thing is, we need to improve customer experience and reduce customer service reps work. The current approach is working but it totally depends on business to business. Some of them may

Re: Create return till ...

The ability to create a return doesn't necessarily mean that return will be accepted. IMO this is a business process where human intervention is required in order to maintain good customer relations. Approving/declining RMAs depend on a number of factors including: - the reason for return -

Re: Create return till ...

I meant the solution suggested by Arun regarding ProductFacility. Best regards, Pierre Smits *Apache Trafodion , Vice President* *Apache Directory , PMC Member* Apache Incubator , committer *Apache OFBiz

Re: Create return till ...

I don't think that the solution provided by ProductFacility will offer a good solution. I will - again - require a field to be added to the entity. And user would need to propagate the value to field for each product-facility combo. Consider Multiple store, multiple warehouse a big burden on

Re: Create return till ...

Following up on Rishi's posting. I believe we are good entity-wise (meaning: we may be able to avoid using system property setting, with complex prefix/suffix constructs). Product can have Attribute settings. So can ProductCategory, see [1]. We can associate products with different

Re: Create return till ...

Agree with Arun, Just an addon If we are using ProductFacility entity then we should think to move the returnable flag from product to the productFacility entity. Kind Regards, *Vaibhav Jain* | Senior Enterprise Software Engineer HotWax Systems Plot no. 80, Scheme

Re: Create return till ...

We can use ProductFacility entity for storing number of days and can copy to it to OrderItem during order creation. Kind Regards, *Arun Patidar* | Manager, Enterprise Development HotWax Systems Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,

Re: Create return till ...

+1 for having this. The only thing I would like to add go for global setting which should be overridden by product level setting. For example; A site may deal in industry which may require different number of days for the different products. Also agree with Pierre on point we should be aware of

Re: Create return till ...

I am inclined to disagree. At product level this can be solved by setting one or more attributes. So no additional field required to cater for this. At store level we could work with value set in appropriate system properties. Also no entity change required. Best regards, Pierre Smits

Re: Create return till ...

Hello Suraj, *Bottom Line:* We should have a field to manage days to Return at the product and product store level both. *Story:* We have a flag on the product level to manage that product is returnable or not. We can not manage the information on the product store level only because each

Create return till ...

Hello, In OFBiz, we can create a return for order without checking when that order is placed, it might be years long. IMO, we should have a field something like daysToReturn at product store level to allow creating return till after that much days of order completion. I could not find anything