Integrations

Integrate Controliza with your current stack without switching systems

Connect ERP, POS, PMS and automations with an API-first architecture built for security, traceability and continuity

Integration with already-deployed ERP, POS and PMS
Documented REST APIs, webhooks and OAuth 2.0
Bidirectional sync with event traceability
No migrations or single-system dependency
Request Technical Session

Compatibility with your technology ecosystem

Controliza connects with your existing stack. It replaces nothing.

ERP

SAP

SAP Business One

ERPAPI + CSV/XML

SAP

SAP ByDesign

Cloud ERPNative cloud API

Business Central

Business Central

ERPREST API + Power Automate

NetSuite

NetSuite

Cloud ERPAPI + middleware

Sage

Sage 200 / X3

ERPAPI + flat file

Odoo

Odoo

ERPAPI XML-RPC/REST

Infor

A3 ERP / A3innuva

ERPExport CSV/XML

Cuadis

Holded

Cloud ERPREST API

Toast

Noray

ERP + PMSAPI + PMS sync

POS

Revo

Revo

POSREST API

Last.app

Last.app

POSREST API

Agora

Agora

POSAPI + webhooks

Camarero10

Camarero10

POSREST API

BDP

BDP

POSAPI + CSV

Prestige

Prestige

POSAPI + sync

Winhotel

Winhotel

POS + PMSAPI + PMS sync

HostelTáctil

HostelTáctil

POSREST API

PMS

Cloudbeds

Cloudbeds

PMSREST API

Mews

Mews

PMSAPI + webhooks

Automation

Webhooks

AutomationHTTP callbacks

Zapier

AutomationTriggers + Actions

Make (Integromat)

AutomationHTTP Scenarios

N8N

AutomationSelf-hosted workflows

Power Automate

AutomationMicrosoft connectors

Protocols and integration methods

Compatibility with standard formats for any system, including legacy.

REST API Webhooks OAuth 2.0 SFTP CSV / XML EDI

Sync model and data governance

Each flow has its cadence, its source of truth and its validation level.

Inbound sync

  • POS sales: automatic daily sync
  • Inventory: updated by count or movement
  • Delivery notes: ingested at reception via OCR
  • PMS occupancy: forecast based on confirmed bookings

Outbound sync

  • Demand forecasts exported to ERP by cost center
  • Suggested orders validated and sent to suppliers
  • Traceability and HACCP records exportable
  • Waste reports for Law 7/2022 compliance

Integration principles

API-first

Architecture designed to connect, not to isolate. Every feature exposed as a documented endpoint.

Auditability

Record of every event, change and sync. Immutable log for compliance and traceability.

Resilience

Automatic retries, persistent queues and alerts on third-party failures. No data loss.

Security by design

OAuth 2.0, TLS encryption in transit, scoped tokens and automatic credential rotation.

Want to see how we connect with your ERP or POS? Schedule a technical session.

Request Technical Session

Frequently asked questions for IT

Who is the source of truth for each data flow?

The POS is the source of truth for sales, the ERP for accounting and suppliers, and the PMS for occupancy. Controliza does not overwrite source data: it consumes, enriches with predictions and returns validated data. Each flow has its source of truth defined and documented.

What happens if a sync fails?

Each sync is queued with automatic retries and exponential backoff. If the target system does not respond, data is retained in a persistent queue until it recovers. Your team receives real-time alerts and can check the event log to diagnose without depending on support.

Does it scale by group and by location?

Yes. The architecture is multi-tenant by design: each location has its own connector configuration, sync cadence and permissions. Adding a new location is a configuration operation, not development. Groups with different POS or ERP by zone operate without conflict.

How much effort does it require from my IT team?

Minimal. For native connectors, your team only provides API access and credentials — we configure and validate. For custom integrations via REST API, we provide OpenAPI 3.0 documentation, sandbox and dedicated technical support during the pilot.

Who maintains the connectors when an API changes?

Controliza. Native connectors are maintained and updated as part of the service. When a vendor updates their API, our team adapts the connector and deploys it without intervention on your side. Custom connectors are also maintained under a support agreement.

What happens if I change ERP or POS?

Controliza does not create dependency. If you change providers, we deactivate the previous connector and activate the new one. Your historical data, forecasts and location configuration remain intact. The change is a reconnection, not a migration.

Results measured in active Controliza clients.

Request a technical session

We review your current stack, integration points and the technical fit of Controliza in your architecture

This site is protected by Google reCAPTCHA. Privacy · Terms

Financiado por Kit Digital y fondos europeos