New Feature #
Status Flow Update #
We are excited to announce a major system upgrade to the Curfox operational workflow. This update introduces a redesigned First, Middle, and Last Mile model, updated status names, a powerful Sorting & Bagging interface, and important steps to prepare for a smooth transition.
🔑 1. The New Three-Mile Workflow #
The old four-part structure (Main Office, Rider, Warehouse, Return Operation) has been replaced with a three-stage operational flow:
🟢 First Mile #
Activities from merchant to the logistics network:
- Order creation & confirmation
- Assigning pickup rider
- Receiving parcels at Origin Warehouse
- Dispatching parcels to Sorting Warehouse
- Return initiation (sending back to merchant)
🔵 Middle Mile #
The new central Sorting & Transit hub:
- Receiving parcels at the Sorting Warehouse
- Sorting into correct destination buckets
- Dispatching to the right Destination Warehouse
- Handling Invalid Destination (ID) and Failed Delivery (FD) returns
- Options to return to merchant or re-dispatch
🟣 Last Mile #
From Destination Warehouse to the customer:
- Receiving bags/parcels at Destination Warehouse
- Assigning destination rider
- Final delivery (Delivered, Partially Delivered, Failed to Deliver)
- Managing delivery attempts, reschedules, and returns
Benefits:
✔ Enhanced visibility across each stage
✔ Industry-standard logistics alignment
✔ Improved efficiency & exception handling
✔ Fewer errors and faster operations
📝 2. Updated Status Terminology #
To match the new flow, status names have been updated
New Statuses Introduced:
- DISPATCHED TO SORTING WAREHOUSE (First Mile)
- RECEIVED AT SORTING WAREHOUSE (Middle Mile)
🛠 3. Sorting Interface & Bagging System #
A brand-new Sorting Operation UI now ensures error-free and fast parcel processing.
Sorting Trigger #
- Sorting now begins only from Middle Mile → Received at Sorting Warehouse.
- Previous sorting initiation from Received at Origin Warehouse is discontinued.
Guided Sorting Process #
- Scan a parcel → system shows correct bucket (e.g., A1 → Jaffna)
- Operator places parcel in the matching bin
- On-screen counts update in real time
Benefits:
✔ Zero sorting errors
✔ Increased speed (no manual reading)
✔ Real-time dashboard visibility
Bagging & Manifesting #
- Create virtual bags per destination bucket (auto-generated Bag ID)
- Scan parcels into the bag for traceability
- Dispatch bags → Destination Warehouse receives under a single Bag ID
⚙️ 4. Action Required – Migration Steps #
Before release, you must clear all parcels currently in “Received at Origin Warehouse” status.
- These orders will otherwise be “stuck” after the update.
How to clear them:
- Dispatch them to Sorting Warehouse (use Dispatched to Sorting Warehouse)
- Receive them at Sorting Warehouse (use Received at Sorting Warehouse)
🏢 5. Configuring the Sorting Branch #
To enable the new workflow:
- Go to Administration > Demarcation > Branch
- Choose your central sorting hub → Set as Sorting Branch
- Only one sorting branch can be active at a time
🎯 6. Direct Drop-off Simplification #
If merchants deliver directly to the central hub (no pickup process):
- Skip First Mile steps
- Start directly at Middle Mile → Received at Sorting Warehouse
- Scan parcels and begin sorting immediately
✅ Final Summary #
This release brings a complete transformation to Curfox logistics:
- First → Middle → Last Mile model for clarity & accuracy
- Updated statuses for industry-standard workflows
- Interactive sorting & bagging UI for speed and zero errors
- Mandatory step: Clear pending “Received at Origin Warehouse” orders
- Sorting begins only at the Sorting Warehouse
- One Sorting Branch setup required
📌 Important: Please complete the mandatory steps before the end-of-month release to avoid disruptions.
We are confident these changes will empower your team to work faster, smarter, and with full visibility into every parcel’s journey.
Redelivery Flag Attempt Customization #
We are excited to introduce a powerful new enhancement to our delivery management system that gives you precise control over the redelivery process. With this update, you can now set customized limits on redelivery attempts, tailored separately for internal staff and merchants.
This improvement is designed to:
- Boost operational efficiency
- Reduce unnecessary costs from repeated failed deliveries
- Provide a transparent workflow for handling undeliverable orders
🔑 Key Functionality #
1. Customizable Redelivery Limits #
- Define the maximum number of redelivery attempts per order.
- Configure limits independently for:
- Staff actions (via the Office Portal)
- Merchant actions (via the Merchant Portal)
2. Flexible Configuration Options #
- Navigate to Settings → Flags → Manage Setting (Redelivery)
- For both Staff and Merchant, you can:
- Set a specific limit (1–5 attempts)
- Allow unlimited attempts by choosing Any
3. Intelligent Attempt Tracking #
- Each redelivery attempt is automatically tracked.
- Once the configured limit is reached:
- The option to add further redelivery flags is disabled for that user type.
- This prevents orders from being trapped in endless failed cycles.
4. Administrative Override #
- Staff members can reverse an order status when necessary.
- Reversing a status also resets the staff-side redelivery count, enabling manual intervention for exceptional cases.
✅ Benefits #
- Efficiency: Keep delivery workflows streamlined.
- Cost Control: Minimize repeated failed delivery expenses.
- Clarity: Ensure both staff and merchants follow a well-defined process.
- Flexibility: Empower admins with overrides for special cases.
City-Assign for Multiple Agents and Warehouses #
We’re excited to announce a major improvement to Curfox’s delivery routing system: cities can now be linked to multiple warehouses, branches, or agents. This provides operations teams with greater flexibility to route parcels through the most efficient delivery point, eliminating restrictions tied to a single default branch.
🔎 What Problem Does This Solve? #
Previously, each city could only have one default warehouse. If a parcel needed to be routed through a different branch, the system flagged it as an Invalid Destination, causing delays and requiring manual intervention.
With this new feature, you can now predefine multiple valid warehouses per city, enabling smarter, faster routing decisions and reducing delivery errors.
⚙️ How It Works #
- City Setup (Administration > Demarcation > City):
- Default Warehouse → The primary warehouse for new orders in the city.
- Other Warehouses (New!) → A multi-select field to assign additional warehouses/branches/agents that are authorized to serve this city.
- Example Scenario:
- City: Colombo A
- Default Warehouse: Colombo Branch
- Other Warehouses: Colombo Suburbs Branch, Head Office, DHL Express
- Result: Orders default to Colombo Branch, but operations staff can dispatch via any of the other assigned warehouses.
- Dispatch Decision (Middle Mile Operation):
- During sorting or dispatch, your team can select any assigned warehouse (default or additional).
- Example: Dispatch directly to DHL Express instead of Colombo Branch when it’s more efficient.
✅ Benefits #
- Gives operations teams real-time flexibility.
- Reduces manual workarounds and delays.
- Ensures parcels always follow the most efficient path to the customer.
Improvements #
Remember Reason Permission Customization #
We’ve made updating multiple orders quicker and easier!
✨ What’s New #
A new “Remember Reason” checkbox is now available when updating the status of orders (e.g., marking them as Failed to Deliver).
⚙️ How It Works #
- When updating multiple orders with the same reason, simply check the box.
- The system will automatically save your selected reason.
- No need to re-select the reason for every single order — making bulk updates much faster and smoother.
This feature is especially useful for processing large batches of orders efficiently.
🔧 Admin Control #
Administrators can control where this option is available.
Go to Settings > Status to choose which order statuses will have the “Remember Reason” option.
Remove Bulk Option from Partially Delivered Status #
We have removed the Bulk option from the Partially Delivered status.
Impact:
- Users will no longer see or be able to use the Bulk option when updating orders to Partially Delivered.
- This ensures the status is handled only on an individual order basis, improving accuracy and preventing unintended updates.
