RevenuePilotby Foxes TechnologyRevenuePilot reconciles and reads back. It does not take silent ownership of your catalogue, your bookings or your prices. Everything is built on versioned APIs with explicit scopes—and every connector states exactly what it can do today rather than what it might do later.
Capability claims age badly, so this table states the current status of each connector in plain words. Certification-ready means preview reads exist—it does not mean a governed write path is available.
| Connector | Capability | Status |
|---|---|---|
| Generic API and CSV | Read-only canonical ingestion: push canonical catalogue, bookings and pricing from any system | Available now |
| Egypt Excursions Online | Read, controlled write and read-back | Controlled pilot |
| Foxes Booking Engine | Catalogue and booking reads | Read connector |
| Rezdy | Catalogue, advertised pricing and bookings | Certification-ready |
| Bókun | Catalogue, default pricing and bookings | Certification-ready |
Generic API and CSV are available now and take canonical data out of any system. They are the path most operators begin on, and they carry the same canonical contracts as a named connector.
Read-only canonical ingestion over a versioned API that advertises its scopes truthfully: catalog_read, departure_read, booking_read and price_read. Inbound keys are organization-scoped and stored as hashes.
Files are encrypted in the browser with AES-256-GCM before upload and land in signed private object storage. Canonical templates keep the shape predictable, and raw uploaded objects are deleted after seven days.
Whichever path you use, the same seven contracts are reconciled: products, options, departures, bookings, cancellations, costs and commissions. Rows are validated asynchronously with partial-row reporting.
Connecting is not the milestone. Reconciled data you can defend is the milestone—and the sequence below is what turns one into the other.
An organization declares one canonical source connector. That declaration is the reference point everything else is checked against, so there is never an unspoken question about which system is authoritative.
Products, options, departures, bookings, cancellations, costs and commissions arrive through the connector, the Generic API or CSV. Ingestion must match the configured source; a second or mismatched source is rejected rather than merged.
CSV rows are validated asynchronously with partial-row reporting, so a file with problems tells you which rows failed and why instead of disappearing into a single success or failure.
Reconciliation compares what RevenuePilot holds against your source, and read-back confirms what your source actually shows. Reading back is how a claim about your data becomes a verified statement rather than an assumption.
A channel RevenuePilot cannot safely reach is shown as not connected rather than simulated. A website with no secure booking or pricing API can receive insights, but its prices cannot be changed safely—so they are not.
Connector offboarding is TOTP-protected. It blocks non-terminal work, removes credential and certification authority, revokes Generic API keys and invalidates sync, while preserving canonical and audit evidence.
Most integration pain comes from ambiguity: two sources disagreeing, a scope that promises more than it delivers, or a system that quietly becomes the owner of your data. Each of these is closed deliberately.
RevenuePilot v1 permits a single canonical source connector per organization. CSV and Generic API ingestion must match that configured source; a second or mismatched source is rejected rather than blended into an ambiguous truth nobody can audit later.
The Generic API advertises catalog_read, departure_read, booking_read and price_read—and nothing beyond them. Inbound keys are organization-scoped and stored as hashes, so a key is bound to one tenant and is not recoverable from our side.
Your booking or reservation system remains the source of truth throughout. RevenuePilot reconciles what it reads and reads back what exists; it never assumes ownership of your catalogue or your prices as a side effect of being connected.
Customer-configured source webhooks, outbound event webhooks and multi-brand administration are not part of RevenuePilot v1. Naming that plainly is more useful than an integrations page that implies a capability you would only discover was absent after signing.
A pricing system connected to your reservations deserves an explicit answer about what it can change. This is ours.
Yes. Generic API and CSV are available now and are the universal path: you push canonical catalogue, bookings and pricing from any system as read-only canonical ingestion, using the same seven contracts a named connector uses.
No. External price writes are disabled by default. Live price execution requires a certified connector plus shadow qualification, policy review and operator approval. Connecting a source grants reads, reconciliation and read-back—nothing more.
Not in v1. RevenuePilot permits one canonical source connector per organization, and CSV or Generic API ingestion must match that configured source. A second or mismatched source is rejected rather than silently merged into an unauditable picture.
Connector offboarding is TOTP-protected. It blocks non-terminal work, removes credential and certification authority, revokes Generic API keys and invalidates sync, while preserving canonical and audit evidence so your history remains defensible.
Generic API and CSV take canonical data out of any system, with read-only ingestion and explicit scopes. No live price writes are required to evaluate what RevenuePilot sees in your portfolio.