What problem does it solve?
Smaller courier and merchant-led operations may need dependable dispatch, drivers, order control and portal workflows without the full complexity of a broad multi-vertical platform.
Standalone Dispatch track · V20-first foundation
Active staging / QAEntry-level dispatch & merchant operations
Preserve proven dispatch workflows.
Modernize the foundation deliberately.
HalNora Dispatch Entry is a standalone V20-first product track intended to provide a simpler entry point for courier, delivery and merchant-led dispatch operations. It preserves the proven V20 interface and operating model while selected standalone V21 capabilities are introduced behind those familiar screens.
Designed around
- Proven V20 Dispatch screens and workflows
- Light/Dark themes and configurable branding
- Merchant portal order creation and editing
- Merchant-owned drivers and future mixed assignment pools
- Permission-controlled CSV imports
- Standalone V21 Driver PWA path
Current status
V20-first staging has validated theme and merchant-ownership boundaries plus auditable order controls. The My Drivers foundation/UI is installed and QA-enabled. Two-pool assignment and the standalone V21 Driver PWA path remain planned/disabled; no production deployment is being claimed.
Live development statusActive staging / QA
Current focusPreserve proven V20 workflows while adding merchant order controls, merchant-owned drivers, permission-controlled CSV imports, auditable ownership isolation and selected standalone V21 enhancements.
Last updatedOctober 12, 2026
The live status feed is temporarily unavailable. Showing the last published snapshot.
Investor view
A lower-complexity entry product built from proven workflows.
Dispatch Entry is intended to broaden the commercial funnel without forcing smaller courier or merchant operations into the full scope of the V22 multi-vertical foundation.
What is it being built to do?
Preserve the proven V20 dispatch experience while adding stronger ownership isolation, merchant driver management, discoverable imports, auditable editing and selected modern PWA capabilities.
How does it fit?
It remains a standalone Dispatch product track. Shared HalNora services may be adopted deliberately, but its screens, workflows and release path are independent from V22, V21 and Phase 3C/MS1.
Where is it today?
Active staging and QA. Theme/ownership boundaries and merchant order controls have advanced; My Drivers is installed for QA. Mixed assignment pools, Driver PWA integration and production deployment remain open.
What stays familiar
V20 remains the operating reference.
The intent is not to redesign the entry product into V22. Proven V20 workflows and visual conventions remain the reference while backend controls are strengthened.
Dispatch workflow
Retain familiar order, assignment and operational screens rather than replacing them with a new multi-vertical interface.
Light / Dark themes
Preserve the V20 theme model, URLs/layout principles and configuration-driven business branding.
Merchant portal
Keep the merchant experience recognizable while enforcing authenticated ownership and permission checks behind it.
Rollback-friendly adoption
Introduce enhancements in staged, auditable increments instead of silently replacing the proven operational baseline.
Capabilities being added
Modern controls behind familiar screens.
These capabilities are in different stages of staging, QA and planned integration; they are not all commercially available today.
Merchant-created orders
Merchant users can create delivery orders from their own portal under authenticated merchant ownership.
Flexible merchant editing
The product direction allows an authorized merchant to edit its own orders at any lifecycle stage—including completed—while preserving POD, financial and audit history.
Merchant-owned drivers
Merchants can add and manage drivers belonging to their organization, with a separate central Dispatch fleet remaining distinct.
Two-pool assignment direction
Planned assignment can choose between merchant-owned drivers and eligible central Dispatch drivers without collapsing ownership boundaries.
Discoverable CSV imports
Orders/Tasks, Contacts and Products are being designed as visible, permission-controlled import workflows—not hidden backend handlers.
Standalone Driver PWA path
A V21-derived Driver PWA is planned to sit on V20-backed, permission-checked APIs for tasks, map, history, location, status, POD/evidence and messaging while legacy driver.php can remain available for staged acceptance.
Dispatch portfolio clarity
Four tracks. No implied merge.
HalNora is deliberately keeping the current Dispatch efforts independent so each can be evaluated, validated and commercialized on its own terms.
Dispatch Entry · V20-first
Standalone entry product preserving proven V20 workflows with selected modern controls and enhancements.
V21
Separate field-used/legacy operational reference with its own constraints and lessons. It is not the Entry product and not V22.
Phase 3C / MS1
Independent guarded acceptance/staging effort. It is not grouped into V21 and is not a V22 branch or successor.
V22
Separate HalNora One multi-vertical commercial Dispatch foundation for courier, taxi, NEMT and field-service execution.
Current staging snapshot
What has moved—and what is still gated.
Public wording stays deliberately conservative until each capability passes the appropriate acceptance and deployment gates.
Search themes: entry-level dispatch software, courier dispatch software, merchant delivery portal, driver management, delivery order import, white-label dispatch software and small-business dispatch software.
Product inquiry
Interested in Dispatch Entry?
Talk with HalNora about the entry product, broader Dispatch portfolio, partnerships or investment.