β¨ Overview #
Weβre excited to introduce the Status Customization Feature, designed to provide advanced control over the systemβs order status flow. Due to the critical nature of status transitions and workflow integrity, access to this feature is strictly limited to Super Admins and the Parallax Team.
π 1. Restricted Access Control #
To ensure secure system management:
- Access to βAdd Newβ and βManageβ status functions is protected by strict security protocols.
- The system validates the logged-in userβs email against a secure whitelist configured in the
.envfile. - Only authorized administrators can view and use status configuration controls.
π 2. Custom Status Creation #
Authorized users can now create fully customized statuses with powerful configuration options:
π Basic Information #
- Add a Status Name
- Add a Detailed Description
π Status Categorization #
Assign statuses to specific logistics phases:
- π First Mile
- π Middle Mile
- π¦ Last Mile
- πͺ Merchant
π¨ Visual Customization #
Improve UI visibility with:
- Custom Status Colors (Success, Info, Warning, Danger, etc.)
- Custom Icons for better recognition
π Status Logic (Transitions) #
Define workflow rules clearly:
- Set Before Statuses (which statuses can come before)
- Set After Statuses (which statuses can come after)
βοΈ Activation Controls #
- Mark status as Active / Inactive
- Set a Default Status for new entries
π οΈ 3. Advanced Status Management #
Existing statuses can now be enhanced and updated through the Manage Settings Modal:
π·οΈ Custom Display Names #
- Update the Custom Name shown to users without affecting backend logic
β System Validation Rules #
Configure critical workflow validations such as:
- Allow / Restrict Branch Updates
- Bypass selected Status Flow Rules when needed
π Required Action Settings #
Make data mandatory when a status is triggered:
- π Require a Reason
- βοΈ Capture Weight
- π΅ Assign a Rider / Delivery Rider
- π Specify Origin / Destination Cities
- π¬ Select Origin / Destination Warehouses
β οΈ Important Technical Note #
To maintain a smooth and functional status workflow, Before / After statuses must always be cross-linked correctly:
- If Status B follows Status A:
- Status A must be listed in the Before Statuses of Status B
- Status B must be listed in the After Statuses of Status A
β Proper cross-linking is essential to avoid broken workflow loops and ensure system stability.
π₯ Target Audience #
- π‘οΈ Super Administrators
- π§βπ» Technical Support / Parallax Backend Team
π Location #
Administration > Settings > Status