OOMLU Legal
Sign InRegister

OMLU Legal

Service Availability, Printing and Support Policy

Operational guidelines governing cloud uptime, internet dependency, thermal printer setup, and technical support standards.

Effective 7 August 2026Last updated 16 August 2026
  • Terms of Service
  • Privacy Policy
  • Refund & Cancellation
  • Acceptable Use Policy
  • Service & Support Policy
On this page +
  • 1. Cloud Service & Internet Requirement
  • 2. Maintenance Windows & Service Changes
  • 3. Mobile Data Fallback Recommendation
  • 4. Web Browser Printing Mechanics
  • 5. LAN/TCP Thermal Printing & Windows Print Bridge
  • 6. Device-Local Printer Setup
  • 7. Hardware Compatibility Disclaimer
  • 8. Restaurant Infrastructure Responsibility
  • 9. Print Failure & Issued Bill Integrity
  • 10. Manual Operational Fallback
  • 11. Data Consistency & Retry Behavior
  • 12. Support Channels & Hours
  • 13. Incident Communication
  • 14. Beta Features & Experimental Modules

Legal documents

  • Terms of Service
  • Privacy Policy
  • Refund & Cancellation
  • Acceptable Use Policy
  • Service & Support Policy

1. Cloud-Service & Internet Requirement

OMLU is designed as an online cloud service. Internet access is generally required for ordering, kitchen updates, bill issuance, payment recording and account administration.

OMLU relies on real-time API communication and WebSocket event synchronization. Full offline database synchronization and offline bill generation are not currently supported.

2. Maintenance Windows & Service Changes

Nadha Labs performs routine maintenance, security patches, and application deployments to ensure optimal platform performance. Scheduled maintenance is conducted during low-traffic periods where feasible, with advance notice posted on administrative portals. Emergency security updates may occur without prior notice.

3. Mobile-Data / Hotspot Fallback Recommendation

Because restaurant dining operations rely on active network connectivity, Nadha Labs strongly recommends that every Restaurant maintain a backup mobile-data connection or secondary cellular Wi-Fi hotspot to prevent ordering downtime during primary ISP outages.

4. Browser Printing Behaviour

OMLU includes standard same-origin browser printing support. When printing receipts via web browsers (e.g. Google Chrome or Mozilla Firefox), the print preview and physical output depend on local operating system drivers, page margin settings, and browser print dialog configurations.

5. LAN/TCP Thermal Printing & Windows Print Bridge

For direct kitchen and counter thermal printing, OMLU provides the Windows OMLU Print Bridge background tool. The Print Bridge runs locally on a restaurant Windows PC (port 24242) and routes raw ESC/POS command payloads directly over local TCP/IP sockets to compatible network thermal printers.

6. Device-Local Printer Setup

Thermal printers must be assigned a static IPv4 address within the restaurant local area network (LAN). The Restaurant must configure matching printer IP addresses and paper widths (58mm or 80mm) within the OMLU settings portal.

7. Hardware Compatibility Disclaimer

Nadha Labs does not guarantee that every thermal printer model, USB print adapter, or legacy serial printer will be compatible with OMLU. Printing features are tested and supported strictly for standard ESC/POS-compatible LAN/TCP thermal printers. Bluetooth thermal printing is not currently supported.

8. Restaurant Responsibility for Infrastructure

The Restaurant is strictly responsible for procuring, maintaining, and troubleshooting its physical operational hardware, including:

  • Local Wi-Fi routers, LAN switches, and network cabling.
  • Uninterrupted power supplies (UPS) for routers, PCs, and thermal printers.
  • Thermal paper roll replacement and hardware maintenance.
  • Local PC operating system updates and network firewall exceptions.

9. Print Failure and Issued Bill Integrity

A printed output is only as accurate as the restaurant data, prices, tax settings and bill information supplied or confirmed by the Restaurant.

If a thermal receipt fails to print due to paper exhaustion, local network loss, or printer power failure, the bill record remains valid and officially recorded in the database. Staff should verify bill status in the administrative portal and trigger a reprint once hardware is restored.

10. Manual Operational Fallback Recommendation

During prolonged ISP or local network outages, staff should utilize manual pad-and-paper ordering and request counter settlement upon internet restoration.

11. Data Consistency & Safe Retry Behaviour

OMLU implements idempotency keys and transactional guards for order creation and payment recording. In the event of a temporary network drop during submission, staff should refresh the portal status before re-submitting to prevent duplicate orders.

12. Support Channels & Expected Hours

Technical support is provided via email at support@omlu.app. Support is monitored Monday through Saturday, from 9:00 AM to 8:00 PM IST.

13. Incident Communication

Platform service incidents or cloud infrastructure outages are communicated via administrative portal notices or official email broadcasts.

14. Beta Features & Experimental Modules

Modules designated as "Beta", "Preview", or "Experimental" are provided for testing purposes without service level warranties.

On this page

  • 1. Cloud Service & Internet Requirement
  • 2. Maintenance Windows & Service Changes
  • 3. Mobile Data Fallback Recommendation
  • 4. Web Browser Printing Mechanics
  • 5. LAN/TCP Thermal Printing & Windows Print Bridge
  • 6. Device-Local Printer Setup
  • 7. Hardware Compatibility Disclaimer
  • 8. Restaurant Infrastructure Responsibility
  • 9. Print Failure & Issued Bill Integrity
  • 10. Manual Operational Fallback
  • 11. Data Consistency & Retry Behavior
  • 12. Support Channels & Hours
  • 13. Incident Communication
  • 14. Beta Features & Experimental Modules

© 2026 Nadha Labs. All rights reserved.

OMLU is operated by Nadha Labs.

Terms of ServicePrivacy PolicyRefund & CancellationAcceptable Use PolicyService & Support Policy