One connection, followed from request to first booking
Five products around a single record: the trading relationship between one buyer and one seller. Each one adds what the next person needs to trust that connection.
Corvane Travel ⇄ Alpine Distribution
Blocked
- Requested
- Commercial review
- Credentials
- Mapping
- Testing
- Approval
- Canary
- Live
Next action
Fix how recheck reports a changed price, then rerun the quote stage
Owner: Priya, Alpine integration
Corvane Travel ⇄ Alpine Distribution
Snapshot v7 approved
Supplier record
The Saltline Hotel Dubai
ALPINE · HT900
Proposed property
The Saltline Hotel
REVO · c100-0001
- Address
- Same after normalising spelling
- Coordinates
- 38 m apart
- Coverage
- 1,204 of 1,260 properties
Corvane Travel ⇄ Alpine Distribution
Not passed
run_014 · alpine-2.3.1 · snapshot v7 · config 12
- Credentials reach the sandboxPassed
- Search, 2 adults + child aged 7Passed
- Quote recheck, price changedFailed
- Book, seller times out mid-bookingInconclusive
- Cancel, non-refundable rateNot run
Corvane Travel ⇄ Alpine Distribution
Sandbox
Trace tr_9f27c1
- 0 msCorvane Travel to TravelRevo quote.recheck
- 19 msTravelRevo to Alpine adapter 2.3.1
- 428 msAlpine to TravelRevo price_changed false
- What failed
- QUOTE-004
- Since
- 09:12 today
- Owner
- Priya, Alpine integration
Corvane Travel ⇄ Alpine Distribution
Suggestion only
AI suggestion
The recheck response has a city_tax line of 13.50 EUR. The original quote has no city_tax line.
- Evidence
- run_014 · tr_9f27c1
- Decision
- Waiting for a reviewer
Approvals, mappings, test results and traces all attach to the connection, and both companies read the same one.
- 5
- products around each connection
- 1
- shared record for buyer and seller
- 8
- stages from request to live
Everything hangs off the connection
Choose a product to see what it attaches. Revo Intelligence has no route here, because it carries no traffic and owns no record. It reads what the others produce.
Mapping snapshot
Supplier codes resolve to one hotel
Each supplier's native code stays intact. A reviewed, versioned snapshot says which property it means, and a correction creates a new version.
What each one adds
One workspace throughout, so nobody has five portals to learn.
Revo Connect
Every buyer and seller connection gets one shared path to live, with an owner and a next action.
The record itself: stage, owner, next action and approvals.
Used by: Business admins and project owners on both sides
- Requested
- Commercial review
- Credentials
- Mapping
- Testing
- Approval
- Canary
- Live
Illustrative. Companies and data are fictional. Revo Map
Supplier property codes resolve to one hotel, backed by evidence a person has reviewed.
A reviewed, versioned mapping snapshot saying which hotel each code means.
Used by: Mapping analysts
- Address
- Same after normalising spelling
- Coordinates
- 38 m apart
- Name
- Similar. Never enough alone
Illustrative. Companies and data are fictional. Revo Verify
Repeatable booking tests, pinned to the exact versions you plan to run.
Test runs pinned to the versions you plan to run.
Used by: Integration engineers on both sides
- Credentials reach the sandboxPassed
- Search, 2 adults + child aged 7Passed
- Quote recheck, price changedFailed
- Book, seller times out mid-bookingInconclusive
- Cancel, non-refundable rateNot run
Illustrative. Companies and data are fictional. Revo Control
When something breaks, see what, where, since when, and who owns the fix.
Traces, errors and an unknown-booking queue once traffic flows.
Used by: Operators and on-call engineers
price_changed must be true when the recheck total differs
expected true
actual false, 197.50 EUR against 184.00 EUR
Illustrative. Companies and data are fictional. Revo Intelligence
Help reading mapping evidence and failed tests. People still make the decisions.
Cited suggestions on top of the others. It adds nothing to the record without a person.
Used by: Anyone reviewing evidence
AI suggestion
These two records share a building with another hotel. Check the chain before approving.
DecisionWaiting for a reviewer
Illustrative. Companies and data are fictional.
Examples are illustrative, with fictional data.
Where they meet the lifecycle
The full walkthrough| Stage | What happens | Product | Who moves it |
|---|---|---|---|
| Requested | What happensA buyer asks to connect to a seller it has agreed to trade with. | ProductConnect | Who moves itBuyer admin |
| Commercial review | What happensBoth sides approve the intent and record the agreement reference. | ProductConnect | Who moves itBusiness admins, both sides |
| Credentials | What happensSandbox access gets checked. Secrets aren't shown again. | ProductConnect | Who moves itIntegration engineers |
| Mapping | What happensSupplier codes resolve to hotels, and a reviewed snapshot is taken. | ProductMap | Who moves itMapping analyst |
| Testing | What happensThe booking flow runs in the sandbox, pinned to those versions. | ProductVerify | Who moves itIntegration engineers |
| Approval | What happensBuyer, seller and operator each approve against the same evidence. | ProductConnect | Who moves itBuyer, seller, operator |
| Canary | What happensA small, capped share of traffic, with booking state checked closely. | ProductControl | Who moves itOperator |
| Live | What happensTraffic ramps within agreed limits. Issues get an owner and a trace. | ProductControl | Who moves itOn-call, both sides |
Hotels first, with direct terms
TravelRevo covers hotels. Buyers and sellers contract and settle with each other directly. TravelRevo isn't a merchant of record and doesn't hold your funds.
Mappings are property identity only
Rooms and rates pass through with the seller's own codes. Every new mapping gets human review, and rooms are never merged automatically.
Deluxe Sea View
Alpine · Non-refundable
Deluxe Room, Sea View
Kestrel · Free cancellation
Tell us where connectivity slows you down
A person reads it and replies.