Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please add Return and exchange function #16491

Open
alibler opened this issue Mar 1, 2021 · 8 comments
Open

Please add Return and exchange function #16491

alibler opened this issue Mar 1, 2021 · 8 comments
Labels
Feature request This is a feature request

Comments

@alibler
Copy link

alibler commented Mar 1, 2021

Instructions

Feature Request

As a mature ERP system, The return and exchange function should be built in the completed sales order or purchase order.

Use case

Replacmet-Order-or-Return-Order

@alibler alibler added the Feature request This is a feature request label Mar 1, 2021
@dolibarr95
Copy link
Contributor

Hi :)
Is it the same request ?
#12200

@alibler
Copy link
Author

alibler commented Mar 10, 2021

It's a similar request, but why hasn't dolibarr officially provided this basic function for so many years? Axel dev development of the return module is very simple! His return module doesn't have the function of tracking the order in the regular ERP system at all.

How do you realize the process management of sales return or purchase return?

@atm-maxime
Copy link
Member

Hi. Dolibarr is developed by an open-source community and made to be used by most companies and organization. The fact that the "return" function isn't existing yet is just that no one started to work on it. Everyone wants Dolibarr to already have its most favorite function, but developments are made by volunteers or financed by users. And there are not many requests about returns. In the meantime, using an external module such as the one you mention is a possibility. Doing manual stock movements and credit note is also possible.

If the feature request is already fully explained in #12200v, please close this duplicate one.

@BebZ
Copy link

BebZ commented May 18, 2021

Yes, it may look "simple" for integrators that are always wondering why Dolibarr doens't make coffee...
For developpers they will not make a a "simple" module (as existing on dolisotre maybe).

It has to be considered as a new Object, like propal/order/invoice/etc...
and not only linked to a "stock movement" and "credit note"...
else it can never be complete and linked to all convenient objects like projects, accounting, banks, permissions, etc...
and it will never be accepted in the "core" I think if it is not a very clean and complete object. Am I wrong ?

@aljawaid
Copy link
Contributor

I had the Product Returns module made by @AXeL-dev to solve my small business problem as mentioned in the intial post by @alibler so I do agree that Dolibarr needs this in the core.

I do also agree with @atm-maxime on the Dolibarr explanation.

In support of the module, I must say if it helps before purchasing, the reason i made this module was for my small business (physical store). I wanted a simple product return system where i could log my products with returns on a custom reference number. I could also add notes and statuses to the returned product and have an 'exchanged' status too for auditing purposes. The lists works fine and the returned product entries can be linked to supplier invoices. Yes, you need to go to the product returns section to see the module in action (meaning it doesnt link the supplier invoice > return both ways) but I found this easier to manage. Stock can also be moved using stock movement.

Create Return

image

Completed Return

image

@DATUC
Copy link
Contributor

DATUC commented Jan 20, 2022

Hi @ll This module need to e added in the core this is neded since more than 4years allready and to be honest is true the Axel modul is ther but lake many functions and @aljawaid wil note be on stage 7/7 to manage products returns and this is not cool

@github-actions github-actions bot added the Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open label Jan 21, 2023
@DATUC
Copy link
Contributor

DATUC commented Jan 22, 2023

Hi @ll any news about this ???!!!...

@github-actions github-actions bot removed the Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open label Jan 22, 2023
@github-actions github-actions bot added the Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open label Jan 22, 2024
@dolibarr95
Copy link
Contributor

Hi!
still relevant

@github-actions github-actions bot removed the Issue Stale (automatic label) This issue is stale because it has been open 1 year with no activity. Remove this label to keep open label Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature request This is a feature request
Projects
None yet
Development

No branches or pull requests

6 participants