Validated foundation
Demonstrated in development, QA or field testing. Validation does not automatically mean commercial availability.
Independent products. Better together. HalNora One connects purpose-built software for operations, commerce, scheduling, communications, customer relationships, finance, inventory, payroll, payments and workforce management—while preserving clear product ownership.
HalNora communicates what has been demonstrated, what is actively being built, what is planned and what remains long-term vision without presenting roadmap direction as a guarantee.
Demonstrated in development, QA or field testing. Validation does not automatically mean commercial availability.
Currently being built, integrated or tested, with release gates still open.
Approved product direction whose final scope, implementation and timing may evolve.
Strategic direction intended to show platform opportunity, not a commitment to release or timing.
The workspace foundation is now live in development, but it does not pretend every standalone product already shares one production login.
The current workspace can present the HalNora product catalogue, shared business information and permission-aware access. Dispatch, Driver and Merchant links are connected by permission; CRM, Payroll, Pharmacy and other products remain separate until their identity contracts are verified.
The new V20-first Dispatch Entry track broadens the potential customer funnel while V22 continues as the separate multi-vertical HalNora One commercial foundation. V21 and Phase 3C/MS1 remain independent reference/acceptance efforts.
Familiar courier and merchant workflows, stronger ownership controls, merchant drivers, imports and a planned standalone Driver PWA path.
Explore Entry →Broader commercial foundation for courier/delivery, taxi, NEMT and field-service execution.
Explore Dispatch →Separate field-used operational reference that preserves lessons without becoming the Entry or V22 product.
Independent guarded acceptance track with its own validation path.
This section reads from HalNora's public status feed. Core product descriptions stay stable; changing development status, current focus and public milestones can be updated centrally without rebuilding the site.
Courier/delivery, taxi, NEMT and field-service execution models; native Driver/Communications integration; Booking/Marketplace contracts; device, integration and release validation.
Product status →Preserve proven V20 workflows while adding merchant order controls, merchant-owned drivers, permission-controlled CSV imports, auditable ownership isolation and selected standalone V21 enhancements.
Product status →Customer-live storefront operations, vendor/service-provider rollout, Marketplace-owned zones/pricing, supplier API/import review controls and Booking/Dispatch/POS/Inventory contracts.
Product status →KDS/Expo, Inventory consume/reverse safeguards, operational close, first-tenant readiness and provider-neutral terminal integration.
Product status →Provider QA, direct-URL RBAC acceptance, publication/live-email controls and broader authenticated modify/cancel workflows.
Product status →Driver/Dispatch integration, locked-screen hardware-key initiation, Bluetooth/audio routing and broader rugged-device validation.
Product status →Three-proof account linking, signed short-lived authority, PostgreSQL rehearsal, authenticated cross-product testing and production-readiness hardening.
Product status →Durable receipt/idempotency storage, authenticated bank integrations, statutory accuracy, close/recovery controls and production financial E2E.
Product status →Persistent processing, database migration/concurrency validation, live pharmacy connectors, controlled Dispatch callbacks, privacy/compliance review and production authorization.
Product status →Backup/restore proof, provider reconciliation, business release approval and controlled commercial enablement.
Product status →Database-backed authenticated E2E, mandatory MFA, PostgreSQL identity safeguards, statutory calculation validation and later banking/CRA/Accounting integration.
Product status →Canadian Poynt Payment Bridge test path, provider-neutral payment contracts, terminal outcome/reconciliation flows and future Android Tap to Pay investigation.
Product status →Restricted runtime connection, secure workspace/membership bootstrap, verified employee self-service, authenticated two-business testing and later controlled HR→Payroll integration.
Product status →HalNora One is the commercial ecosystem that brings the HalNora product family together. It does not erase product boundaries—it makes those boundaries easier to understand and connect.
The customer-facing umbrella for discovering, adopting and connecting HalNora products.
How HalNora One works →Dispatch, Marketplace, POS, Booking, Communications, CRM, Accounting, Inventory, Payroll, Payments, HR and Pharmacy remain independently scoped products.
Explore products →Identity, permissions, security, integrations, events, fleet, data and communications infrastructure reused where appropriate. Inventory and Payments remain standalone authorities.
Explore the platform →Dispatch, Dispatch Entry, Marketplace, POS, Booking, Communications, CRM, Accounting, Inventory, Payroll, Payments and HR are in development or validation; Pharmacy remains an early regulated prototype. None is presented as generally available until its release gates are complete.
Courier/delivery, taxi, NEMT and field-service execution with routing, resources, tracking, evidence and operational control.
STAGING · ENTRY OPERATIONSStandalone V20-first courier/merchant dispatch preserving proven workflows while adding stronger ownership controls, merchant drivers, imports and selected modern enhancements.
ACTIVE · COMMERCEProducts plus service-provider/contractor discovery with Marketplace-owned pricing and controlled Booking/Dispatch handoffs.
ACTIVE · SELLINGRetail, restaurant, hospitality, production/KDS and field-selling foundations.
ACTIVE · SCHEDULINGAppointments, availability, resources, recurring schedules and service areas.
ACTIVE · FIELD COMMSOperational messaging and PTT now moving into Driver integration after successful native field tests.
ACTIVE · RELATIONSHIPSCustomer 360, pipeline, quotes, tasks, privacy controls, audited exports and security hardening.
ACTIVE · FINANCECanadian accounting foundations spanning ledger, tax, invoices/bills, statements and reconciliation workflows.
QA · INVENTORYPurchasing, receiving, stock movement, transfers, counts, lots/serials, production batches and controlled integrations.
QA · PAYROLLCanadian payroll workflow foundations with privacy controls and gated calculation, payment, filing and Accounting integration.
PROTOTYPE · SPECIALIZEDPrivacy-first pharmacist-release, verified package scan and delivery-handoff prototype.
ACTIVE · PAYMENTSProcessor-neutral payment orchestration for terminals, online/field workflows and future mobile acceptance, subject to provider certification and validation.
EARLY · WORKFORCEEmployee management, onboarding, leave approvals and a controlled future HR→Payroll integration boundary.
Some foundations are shared platform services; others are standalone products that expose controlled capabilities to the rest of HalNora One.
Inventory is a standalone product for stock authority. Approved POS/Marketplace/Accounting integrations can consume its controlled movement and availability contracts.
Explore Inventory →Vehicles, assignments, maintenance, inspections, skills, equipment and requirements that support dispatch and scheduling.
Controlled imports, mapping, validation, reconciliation and audit for businesses moving into HalNora products.
Payments is a standalone processor-neutral product that can expose approved terminal and field-payment capabilities to other HalNora products.
Explore Payments →Dynamic ETA, customer tracking and meaningful alerts built from authoritative operational state.
Pending-state visibility, server-authoritative reconciliation and configurable photos, signatures, scans, OTP and safe-drop evidence.
Barcode/QR workflows, load validation, scan-to-assign, run sheets and chain-of-custody patterns.
Tenant isolation, audit, short-lived authorization, rollback, backup/restore and release validation treated as platform concerns.
A business can begin with Dispatch, POS, Booking—or another HalNora product—without committing to everything else. Connections are added through explicit contracts only when the business case is clear.
See the ecosystem architectureHalNora generalizes architecture underneath while keeping the user experience specific to the job people actually do.
HalNora's long-term hospitality/event direction brings POS, mobile/field payments, Booking, Communications/PTT, staff/resources, incidents and operational command into one coordinated experience while preserving clear product ownership underneath.
Explore the planned workflowHalNora One provides a stable umbrella while individual product roadmaps move at different speeds and pass their own security, device, integration and release gates.
Dispatch, Dispatch Entry, Marketplace, POS, Booking, Communications, CRM, Accounting, Inventory, Payroll, Payments and HR continue in parallel; Pharmacy remains a separate regulated prototype.
Fleet/resources, data migration, notifications, audit, portability and recovery continue as shared foundations; Inventory and Payments remain standalone authorities with controlled cross-product contracts.
Advance the privacy-first pharmacy handoff model only through controlled authorization, device and compliance validation.
Hospitality and Event Operations are planned around venue command, staff/resources, security/production, concessions, payments, parking/transport and medical/first-aid workflows—reusing mature HalNora services without losing purpose-built experiences.
Field validation, production credentials, privacy/security review, device testing, backup/restore, rollback and integration acceptance remain part of the definition of done—not afterthoughts.
Why HalNora is building this way