fix(order): standardize initial order status across admin and frontend - #401
Merged
Nsanjayboruds merged 1 commit intoJul 25, 2026
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
Summary
Standardize the initial order status across the admin and user frontends by using
Placedconsistently, while maintaining backward compatibility for existingOrder Placedrecords.Description
This PR fixes the inconsistency between the backend and frontend regarding the initial order status.
The backend creates new orders with the status
Placed, whereas parts of the admin dashboard and user order tracking expectedOrder Placed. This mismatch caused incorrect status display, filtering, badge rendering, and dropdown behavior.Changes Made
Placedas the canonical initial order status.Order PlacedtoPlaced.Order Placedrecords continue to display and function correctly without requiring any database migration or backend API changes.Testing
Placed → Packing → Shipped → Out for delivery → Delivered) continue to work as expected.Related Issue
Fixes #398
Type of Change
Checklist