Part of HalNora One · Independent product
In development
Point of sale

A standalone POS system for retail, hospitality and mobile selling.

HalNora POS is being developed as its own commercial product for reliable checkout, registers, tenders, returns, restaurant production and mobile selling—with clean ownership boundaries from the beginning.

Designed around
  • Retail businesses
  • Restaurants and hospitality
  • Concessions and event vendors
  • Table-side/mobile selling
  • Flexible POS hardware
  • Marketplace-connected production
Current status

Catalog, variants, pricing, discounts, split tenders, returns, register controls and Marketplace/KDS boundaries are established in development. No first live tenant has been accepted yet.

Live development statusActive development
Current focusKDS/Expo, Inventory consume/reverse safeguards, operational close, first-tenant readiness and provider-neutral terminal integration.
Last updatedOctober 12, 2026
The live status feed is temporarily unavailable. Showing the last published snapshot.
Investor view

Problem, capability, connection and current stage.

HalNora separates demonstrated development progress from future product direction so scope can be understood without treating roadmap items as commitments.

01 · PROBLEM

What problem does it solve?

Retail, restaurant and mobile selling need reliable transactions without forcing every merchant into one processor or operational system.

02 · CAPABILITY

What is it being built to do?

Server-authoritative checkout, catalogs, registers, tenders, returns, KDS/Expo, operational close and device foundations.

03 · HALNORA ONE

How does it connect?

Connects to Inventory for stock movement, Accounting for financial events, Marketplace for production context and Payments for certified terminal/mobile payment orchestration.

04 · STAGE

Where is it today?

Development and field QA. Core transaction foundations exist; first-live-tenant acceptance, hardware/provider validation and production certification remain gates.

Current direction

What this product is being built to do.

Public descriptions reflect current development direction and do not imply general availability or production certification.

01

Server-authoritative checkout

Keep totals, tender outcomes and final transaction state authoritative on the server rather than trusting device calculations alone.

02

Catalogs & variants

Model categories, products, variants, SKUs, multiple barcodes, units of measure and commercial product details.

03

Pricing & manager controls

Support price books, discounts and controlled manager overrides with auditable state.

04

Registers & cash sessions

Track register sessions, cash movement and accountable cashier operations.

05

Split & mixed tenders

Support multiple tender types and split-payment workflows with explicit transaction state.

06

Returns & refunds

Treat returns and refunds as explicit transactions rather than editing completed sales.

07

Device foundations

Model terminals, printers, scanners and peripherals without hard-coding a single hardware ecosystem.

08

Mobile & field payments

Reuse secure provider-supported/tokenized payment capability for authorized workers, including Tap to Pay where supported and validated.

09

Restaurant production

Support KDS/Expo, table-side direction, modifiers, split checks and hospitality workflows without merging POS with Marketplace or Booking.

10

Close readiness

Warn or block closure when open tills, unresolved payments/checks or active production still require attention.

Payments & terminals

POS requests the payment. HalNora Payments orchestrates approved providers.

HalNora POS remains authoritative for the sale. HalNora Payments is the standalone processor-neutral layer intended to coordinate approved terminal/mobile payment workflows while certified processors remain authoritative for card processing.

01

Poynt Payment Bridge

Availability in Canada has been confirmed for semi-integrated payment requests from external software to GoDaddy/Poynt terminals.

02

Test before live

The first Poynt adapter is planned against a separate test account before any production rollout or reconciliation claim.

03

Provider-neutral adapters

HalNora does not assume GoDaddy provides every POS SDK or Tap-to-Pay path; other certified providers can be integrated where required.

04

Reconciliation boundary

POS/Dispatch can request and record payment outcomes while the certified processor remains authoritative for card processing.

Explore HalNora Payments
Product boundary

POS owns the sale.

POS owns POS sales, sale snapshots, tender intent and register operations. Marketplace owns Marketplace commercial orders; Inventory owns product movement; Accounting owns the books; Dispatch owns fulfillment execution.

HALNORA ONE ARCHITECTURE

Connected, not coupled.

Cross-product workflows use explicit contracts, authenticated events and clear authority so one product does not silently take over another product’s records.

How the HalNora platform works →
Restaurant & production operations

Production can connect without blurring transaction ownership.

Current integration work supports Marketplace-originated production through POS/KDS while preserving Marketplace as the commercial-order owner and Inventory as the product-movement owner.

01

KDS & Expo lifecycle

Production tickets can move through kitchen/display and expo states without creating a fake POS sale.

02

Marketplace source awareness

Production analytics and system health can distinguish Marketplace-originated work from native POS transactions.

03

Inventory safeguards

Availability checks, consume/reverse events and ownership controls are designed to prevent POS and Inventory from both deducting the same stock.

04

Operational close

Open tills, unresolved payments/checks and active production are surfaced before a location closes operations.

What comes next

Development priorities.

HalNora prioritizes reliability, security, recoverability and real-world validation over feature count alone.

01

Continue payment-provider integration and certification without weakening server-authoritative transaction rules.

02

Expand KDS/Expo and restaurant/table-side flows with broader device QA.

03

Complete Inventory ownership cutover and reconciliation so duplicate stock deductions remain blocked.

04

Advance hardware/peripheral abstractions, offline recovery and operational-close validation.

05

Add approved CRM and Accounting integrations through explicit events rather than shared tables.

Search themes: POS software, retail point of sale, restaurant POS, kitchen display system, mobile point of sale, field payments, register software, table-side POS.

Product inquiry

Interested in POS?

Talk with HalNora about product direction, commercial use cases, partnerships or investment.

Contact HalNora