DLH Aloha POS Agent
Unify Aloha POS BOH data for all stores.
For most multi-unit restaurant operators running Aloha POS, the richest data in lives in classic Aloha POS installations: a Windows Server at each store running Configuration Center, with sales, items, modifiers, voids, and labor punches stored in per-site dated sub-folder files. Getting that data into a modern data warehouse historically meant fragile nightly FTP scripts, hand-rolled parsers, or nasty homegrown code.
The DLH.io Aloha POS Agent is the bridge you've been looking for to solve your Aloha POS data integration issues. It reads each store's Aloha data with read-only access, sends it over outbound-only connections, and lands sales, checks, comps, promos, labor, and gift card detail in a warehouse you own. No more stitching together manual Aloha Insight exports.
Purpose-Built for Multi-Unit Aloha POS Customers
The Aloha POS Agent ships every capability a multi-unit restaurant data pipeline needs - DBF-aware ingestion, open table formats, encrypted credentials, schema evolution, and multi-store consolidation - in a single install you run on the server.
Built for Aloha BOH & Configuration Center
Purpose-built for the classic NCR Aloha back-of-house stack: Configuration Center, TermSrv / RDS sites, and the per-store DBF files where sales, items, modifiers, voids, and labor punches actually live.
Multi-Store Consolidation
Agents collect data from all stores/units - across regions, brands, and Aloha versions - and unify everything into a single normalized schema for analytics and AI use cases.
Data Synchronization
The Agent writes directly to several different output formats that you can easily use for downstream operations. No proprietary storage layer, no vendor lock-in - your restaurant data can be delivered how you need it.
Data Stored Securely
Data is landed securely directly for your access without restriction. Its your data you should have access to it the way you need it.
Firewall-Friendly by Design
Runs inside the BOH network boundary with outbound-only data transfer (via TLS). No inbound ports, no VPN tunnels back into store networks.
Encrypted Credentials & State
The agent is installed by an administrator similar to how your Aloha POS was set up in the first place. The agent provides logging, alerting, and ease of deployment
Schema Evolution Built-In
When a vendor patch or new module adds columns to data structures, the agent absorbs the change and adds the column to the downstream process correctly - no manual intervention needed, no broken reports, no pipeline redeploys.
Beyond Aloha - DLH Syncs Loyalty, Ads, Reviews
Use in combination with core DLH.io to synchronize data from adjacent restaurant systems - loyalty programs, advertising platforms, and review/feedback systems.
Deploy as a Windows Service
Ships as a single signed executable. Install as a Windows Scheduled Task with the bundled PowerShell installer.
Reference Architecture
A single lightweight process with three responsibilities: read data from each Aloha BOH server, provide the data in a consumable format for downstream operations, and track sync state locally so reruns and back-fills are deterministic.
1. Access & Synchronize
The agent captures all necessary data for sales, items, modifiers, voids, labor, gift cards, and more - using a memo-aware, schema-aware reader process. New stores are easily added with a few entries. Run on a scheduled frequency for the synchronization.
2. Review & Analyze
Per-store rows are normalized into a unified schema and synchronized for pickup. Schema evolution is automatic. Partition by store, brand, business date, or any column you choose. Analyze the data and deliver to your downstream processes.
3. Deliver & Query
Query the resulting Aloha POS data as needed through popular data warehouse concepts or lakehouse tables from Snowflake, Databricks, Trino, Athena, DuckDB, is the final result enabling you to continue with further downstream efforts on the data.
The Aloha Data You Actually Report On
Field-level detail straight from Aloha's back-of-house files, not a summarized export. Every transaction row carries the employee ID, store, and business date, so sales, labor, and discounts tie together across every location.
Sales & checks
Check-level sales, revenue by category, and daily sales summaries by store and business date.
GNDSALE · GNDITEM · GNDLINE · GNDREVN · GNDSLSUM
Items & modifiers
Menu items, modifiers, and item groups for product mix and menu engineering.
ITM · MOD · ITMGRP · ITMXMOD
Guest counts
Guest counts recorded with each check, for per-guest spend and covers by daypart.
GNDSALE
Comps, promos & voids
Actual comp and promotion deductions, plus voids with the employee and authorizing manager.
GNDSALE · GNDVOID
Labor, pay & overtime
Clock in and out, hours, pay, rate, and overtime by employee and job code, plus shifts and breaks.
ADJTIME · GNDSHIFT · GNDBREAK
Tenders & gift cards
Payments by tender type, gift card sales and redemptions, tips, and gratuities.
GNDTNDR · GNDGRAT · GNDTPSHR
See every table and column in the Aloha POS data model (ERD).
Reliable Enough to Reconcile
Reporting only replaces your current exports if the numbers tie out. The agent is built around how Aloha actually records a restaurant day.
History on your terms
Load history from any start date your BOH servers still hold, or start from today. Reload any month or date range later with a historical re-sync.
Late corrections & deletes
Every sync re-reads the current month, so edited punches and adjusted checks are picked up after close. Deleted records are captured, not left behind as stale rows.
Aloha business dates
Rows keep Aloha's date of business and store ID, so a check closed after midnight lands on the day the store reported it, matching Aloha's own reports.
Ready before morning
Run daily after end of day, hourly, or near real-time. The closed business day is in your warehouse before the morning's reports go out.
Built for Real Restaurant Operators
Multi-Unit Operators Consolidating Across Stores
Restaurant groups running 10, 50, 200, or 1,000+ Aloha locations get a single, governed view of sales, items, voids, and labor without manually pulling files store-by-store. The agent handles the per-site sync; and if needed the DLH lakehouse handles the consolidation.
Replacing Brittle Nightly Batch Scripts
Decades-old FTP / SMB pulls and homegrown scripts break the moment a vendor patch shifts a column. Replace them with a supported agent that handles schema drift automatically and provides data warehouse-native capabilities.
Replacing Manual Aloha Insight Exports
Operators who rely on scheduled Aloha Insight exports and spreadsheets get the same sales, labor, and discount detail delivered automatically to their own warehouse. Keep Insight for day-to-day store reports while finance and operations report from one consistent source across every location.
Franchise Groups That Pilot Before Rolling Out
Start with one or two locations, reconcile the agent's data against the reports you already trust for the same business dates, then roll out to the rest of your stores. Each additional store is a configuration change, not a new project.
Restaurant Analytics & AI Use Cases
Once Aloha data lands you can use it for downstream processes such as working with forecasting labor, model menu mixes, surfacing void anomalies, calculating prime metrics, etc.
Ideal if Migrating to a Cloud Warehouse
The agent gets the data into your warehouse on your timeline - without re-platforming the BOH or asking each store's IT contact to reconfigure their processes or network.
Read-Only, Outbound-Only
The agent only reads Aloha's data files and opens outbound TLS connections. No inbound ports, no VPN, no remote access into store networks, and no NCR credentials.
SOC 2 Type II, Signed Installer
The agent ships as a signed installer. Request our SOC 2 report from the trust center and review the DPA.
Your Warehouse, Your Region
Data lands in a warehouse you own, in the cloud region you choose, under your retention policy. If you stop the service, your history is already yours.
Questions from Aloha POS operators
Real questions from multi-unit restaurant groups evaluating the agent as a replacement for manual Aloha reporting exports.
Compatibility and installation
Reporting detail
Data reliability
Architecture and security
Pricing, pilots, and contracts
Get the Aloha POS Agent
Start with a pilot on one or two locations and reconcile the data against the Aloha reports you already use. When the numbers tie out, roll out across your store network in a matter of days. Talk to an engineer to scope your pilot.
Read the announcement: DLH.io Introduces Agents for NCR Aloha POS Customers.