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

Product based order statuses? #229

Open
monecchi opened this issue Mar 3, 2024 · 0 comments
Open

Product based order statuses? #229

monecchi opened this issue Mar 3, 2024 · 0 comments

Comments

@monecchi
Copy link

monecchi commented Mar 3, 2024

Hi there! First thing first, thanks for your project! It has helped me a lot with a personal project.

Regarding the order statuses and the way they are now implemented, depending on the business model, a "shop" might prefer to apply statuses only to the order itself instead of individual order items.

Also regarding the "cancellation action" customers can perform, a shop might not want customers to be able to cancel individual order items, but preferably the whole order itself.

As of now, all cancelled orders are deleted from database, but a shop might want them stored for later control, filtering, customer order history etc. Perhaps, it'd be a good idea to bring some logic with an option for storing them for 30 days or indefinetly if it comes to it.

Perhaps a better approach for the "cancellation action" would be to provide a separate mongoose model and api on the server side defined as "Cancellation Request". The Cancellation Request model would contain the order and order items as also a "reason" text posted by customers.

Every time customers cancel an order & order item(s), Admins and Merchants would be able to check "cancellation requests" by filtering orders by order.status so they could analyze and then approve or decline those cancelled orders.

Best regards!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant