Egyptian restaurants rolling out ETA e-invoicing need a POS that issues compliant receipts inside normal service flow, supports Arabic and English outputs, and keeps trading when connectivity drops. Sync includes ETA (Egypt) and ZATCA (Saudi Arabia) e-invoicing in product positioning, with Arabic and English UI and receipts (RTL). Operations should not depend on a manual export after every shift. This page lists requirements your finance team should sign off, how offline-first POS reduces compliance downtime, and questions to ask before go-live. Confirm entity-level setup with PlateForm during onboarding via contact or review Sync compliance features.
What your POS must do for ETA
Receipt and invoice flow
- Generate electronic invoices as part of checkout, not only paper totals
- Preserve sequential integrity finance can audit
- Handle voids and corrections with traceable events
Language and customer experience
- Arabic and English UI and receipts (RTL)
- Staff can explain totals clearly to guests during rollout
Operations under stress
- Continue sales when internet drops; sync compliance data when back online
- Avoid parallel shadow systems finance reconciles by hand
Compliance is operational
If e-invoicing lives only in a back-office tool, the floor will invent workarounds during peak.
ETA readiness checklist
- Legal entity and tax profile configured
- Receipt template approved by finance
- Test void, refund, and discount edge cases
- Arabic customer-facing copy reviewed
- End-of-day report matches tax portal expectations
- Staff SOP for rejected or delayed submissions
- Offline sale test: invoice queue syncs after reconnect
Compliance + offline together
| Scenario | Risk if cloud-only | Offline-first target |
|---|---|---|
| ISP outage during dinner | Stopped checkout | Local queue + sync |
| Printer failure | Manual rewrite | Backup printer map |
| End-of-shift rush | Skipped submissions | Batched sync with audit log |
Sync queues orders and payments locally, syncs on reconnect, zero data loss on reconnect (approved claim). Validate invoice queue behavior on your account.
How Sync fits
Approved product facts:
- ETA electronic invoicing (Egypt)
- ZATCA (Saudi Arabia)
- Arabic and English UI and receipts (RTL)
- Offline-first operations for daily sales
- Cloud Mode for multi-branch reporting and integrations
Do not publish pricing numbers without sales approval.
Questions for finance and IT
- Where is the legal invoice generated (device vs cloud)?
- What is the retry policy for failed submissions?
- Who gets alerted on rejection codes?
- How long are logs retained?
- Does offline mode queue invoices with idempotency?
Related guides
FAQ
Is ETA only available in Cloud Mode?
Confirm scope during onboarding for your entity and mode mix.
What if a receipt is rejected after service?
Define SOP: identify order ID, retry rules, guest communication. Train before go-live.
Does Sync replace my accountant?
No. POS executes operational compliance; finance still owns filings and review.
Explore Sync or book a compliance walkthrough with PlateForm.
