What is Pavo POS device integration?
If you already have a Pavo POS device, it integrates with Ritapos without replacing hardware. Staff open the check in the POS system; when payment finishes on Pavo a fiscal receipt is cut and the order closes automatically. Double entry and manual receipt risk drop.
All Pavo models use the same Rest, Cloud, UniCloud and P2P types. For other brands see cash-register integrations; for general terms see what cash-register integration is.
Rest, Cloud, UniCloud and P2P compared
Choose the Pavo integration type that matches how you collect payment:
| Type | Connection | Best for | Requirement | Ritapos support |
|---|---|---|---|---|
| Rest | Local network | Counter and self-service | Same LAN as the Ritapos PC | Live |
| Cloud | Cloud (Wi-Fi or SIM) | Tableside, lounger, door payment | Internet | Live |
| UniCloud | Cloud (Wi-Fi or SIM) | Tableside, lounger, door payment | Internet | Live |
| P2P | On-device app | Tableside and mobile collection | Internet or local pairing | Development ongoing |
Rest, Cloud, UniCloud or P2P can all run on one device; pick the type you will actually use to avoid confusion. Step-by-step screenshots are in the Pavo academy lesson.
Rest for counter payment
Rest runs on the same local network as the PC. It is used on self-service and fixed counter lines to send order data to the fiscal device and GİB; after payment the order closes automatically in Ritapos while data is sent to GİB.
Cloud and UniCloud for tableside payment
Cloud does not need a local network. The device only needs internet over Wi-Fi or SIM. For businesses that collect payment at the table, lounger or door, payment links are sent from Ritapos to the chosen device.
P2P for on-device flow
This is the integration type on the Pavo POS device and fits mobile collection. Ritapos P2P support is currently in development; Rest, Cloud or UniCloud should be used for live production. Setup steps for these integrations are covered in detail in the academy lesson.
Recommended Pavo models for integration
Ritapos can integrate with all Pavo models. If you are unsure which Rest, Cloud or P2P type fits you, our support team can help. Pavo works for counter, kiosk and table scenarios. For standard F&B, Ritapos recommends N86 and N96:
| Model | Platform | Store |
|---|---|---|
| Pavo N86 | Android cash-register POS | N86 product page |
| Pavo N96 | Android cash-register POS | N96 product page |
You do not need to replace your Pavo device to integrate with Ritapos; with GMÖ active on any device, remote support pairing is enough.
Setup
Prerequisites
- Pavo cash-register POS with active GMÖ
- Active Ritapos account with admin access
- Same local network as the Ritapos PC for Rest
- Wi-Fi or SIM internet for Cloud, UniCloud or P2P
Step-by-step setup
- Sign in to Pavo Sales. Open the Sales screen with email and password.
- Choose the integration type. Pick Rest, Cloud, UniCloud or P2P and complete Ritapos pairing under Settings > Integrations.
- Prepare the Ritapos account. Sign in as an admin to reach the integrations screen.
- Configure the connection. Ritapos support configures Rest, Cloud, UniCloud or P2P remotely.
- Make a test payment. Verify order and fiscal receipt close-out.
Pavo does not charge a separate integration license; the device side bills annual GMÖ, and Ritapos applies a one-time setup fee for activation. See the Pricing page for details. For step-by-step screenshots, we recommend the Pavo cash-register integration page.
How order and payment connect
The open check stays in Ritapos; the amount is sent to the Pavo device. After payment approval a fiscal receipt is cut and the order closes automatically.
For all brands integrated with Ritapos, see cash-register integrations. Pavo fits sectors such as cafe POS, restaurant POS, bar POS, and beach POS.
VUK 507 and GMÖ with Pavo
Integrated order software and next-gen fiscal devices meet fiscal record obligations under tax law. Ritapos holds the order record; Pavo produces payment and the fiscal receipt; data is sent in line with Turkish Revenue Administration processes.
Under VUK 507 / GMÖ, secure mobile payment must be active on the Pavo device. For e-receipt obligations see e-receipt.
End of day and reporting
The Z report on Pavo and the Ritapos end-of-day report reflect the same collections. Because orders close through the integration, till variance and manual receipt drift drop.
Staff-level collections and multi-branch close-outs are watched in Ritapos; device Z reports stay on Pavo. For stock and cost views see inventory and cost management.
When the receipt limit is exceeded you cannot issue a document in a final consumer's name; through the integration you invoice a real person or a company. You post card and cash refunds on Pavo into the fiscal record and you trigger X and Z reports from Ritapos.
Pavo POS device technical overview
| Capability | Pavo + Ritapos |
|---|---|
| Device | Pavo Android cash-register POS |
| Connection | Rest (local network) / Cloud / UniCloud / P2P |
| Order panel | Ritapos cloud order system |
| Payment | Card, cash, contactless, QR and meal cards with fiscal receipt or invoice |
| Close-out | Automatic order and receipt match |
| Setup | Active GMÖ + remote activation |
| Compliance | Tax-compliant fiscal record; aligned with e-receipt |
Who is it for?
Cafes, restaurants, bars and quick-service teams using or buying a Pavo POS device who want menu, stock and payment on one panel. You do not need to replace existing hardware; a Pavo device with active GMÖ is enough.
Multi-branch teams can watch central reports and device-level close-outs together. Sector flows: cafe POS, restaurant POS, bar POS, beach POS.
Why Ritapos?
The core advantages that set Ritapos apart from competitors.
Easy to Use
Intuitive interface: run daily operations without staff training.
High Speed
Fast checkout screen and instant order routing; a quick start from setup to service.
Transparent Pricing
Clear packages, no hidden costs. Plan without surprise invoices.
Free Integrations
Delivery, cash register, and e-receipt integrations included in the packages.
End-to-End Solution
Orders, inventory, reporting, and integrations on one platform.
KVKK Compliant
Your data stays safe in an encrypted cloud.
Expert Support
24/7 Turkish support line.
Real-Time Reporting
Track revenue, inventory, and branch performance instantly from one panel.
One Platform, Four Smart Solutions
From POS to the owner app, waiter terminal to QR menu: don't split your operations across different systems.
Ritapos POS
Manage the entire flow from order to payment in seconds
Owner App
Track revenue, ticket count, and branch reports in real time
Waiter App
Instant table-side orders, split bills, and fast payments
QR Menu
Reduce staff load with a contactless digital menu
Frequently Asked Questions
What is Pavo?
Pavo is an Android cash-register POS brand that integrates with Ritapos. All Pavo models fit counter, kiosk and table scenarios. For general terms see what cash-register integration is.
What is the difference between Rest, Cloud, UniCloud and P2P?
Rest uses the local network for counter and self-service. Cloud and UniCloud use Wi-Fi or SIM for tableside, lounger or door payment and are live. P2P is the on-device type; Ritapos support is still in development. Prefer Rest, Cloud or UniCloud for live use.
What is required for setup?
You need a Pavo device with active GMÖ, Sales sign-in, and Rest, Cloud, UniCloud or P2P configuration with Ritapos support. Steps are in the academy lesson.
Is there an extra Ritapos integration fee?
Ritapos plans do not charge a separate software integration fee. Pavo does not charge a separate integration license; the device side bills annual GMÖ, and Ritapos applies a one-time setup fee. See Pricing.
Do I need to replace my existing Pavo device?
No. You can integrate an existing N86 or N96 with active GMÖ without replacing hardware.
Will end-of-day till variance appear?
Because orders close through the integration, the Pavo Z report and Ritapos end of day reflect the same collections. Manual receipt and double-entry drift drop.
Which Pavo models are supported?
How are payment and order linked?
Open checks in Ritapos are sent to the Pavo device in full. After the receipt, fiscal data goes to GİB, the order closes and reports update.
Which businesses fit?
Cafes, restaurants, bars and quick-service spots that want compliant order and payment from one panel.
Where do I buy hardware?
How do the receipt limit and refunds work on Pavo?
When the receipt limit is exceeded you cannot issue a document in a final consumer's name; you invoice a real person or a company through the integration. Card and cash refunds post to the fiscal record; you trigger X and Z reports from Ritapos. See the cash-register POS integration hub.
Sign Up Now
Don't wait for a demo. Sign up and try it free for 14 days.
No credit card required. Cancel anytime.