labs@atheron:~/industries/tours-attractions/integrations$ connect --systems --automate

Reseller integrations

Every channel selling from the same seats.

Every reseller with its own login and spreadsheet is a chance to oversell a departure or miss a commission. A hub that gives resellers one documented interface, and brings agency bookings into your own system, keeps every channel selling from the same seats.

Start a project See the example projects

// what matters here

What is different in this industry.

One interface for resellers

Live availability and booking for resellers through one documented interface, with a key each.

Agency bookings arrive on their own

Bookings from online agencies are written to your booking system as they happen.

Commissions with each sale

Each sale is recorded with its channel and commission, ready for month end.

You see every message

Each exchange is logged, and a failure raises an alert at once.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectAPI

Channel and reseller hub

Hypothetical. Not a client, not a result.

// The problem

An attraction sells through online travel agencies, hotel desks and local resellers, each with its own login and spreadsheet, and staff move bookings between them by hand.

// What we would build

An integration hub that gives resellers live availability and booking through a documented interface, receives bookings from the online agencies, and keeps the operator's booking system and accounting in step.

// What is in it

Live availability and booking for resellers through one interface
Bookings from online agencies written to your booking system
Commissions recorded with each sale
Sales posted to your accounting system
Every message logged, with alerts when one fails

// Stack

Node.js
PostgreSQL
OpenAPI
Online agency interfaces
DigitalOcean

// estimate

Build: ≈ US$56,700 to US$86,700, delivered within 14 weeksCAD 80,700 to 123,400
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

API contract agreed: 2.9 to 3.9 weeks
Core resources built: 2.9 to 4.4 weeks
Security, gateway and connections: 1.9 to 2.9 weeks
Docs, SDKs and load tests: 1.4 to 1.9 weeks
Launch and first callers: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

Interface access from your resellers and agencies: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 16,140 to 24,680
API contract agreed 8.7%: CAD 7,020.90 to 10,735.80
Core resources built 26.2%: CAD 21,143.40 to 32,330.80
Security, gateway and connections 17.5%: CAD 14,122.50 to 21,595.00
Docs, SDKs and load tests 8.7%: CAD 7,020.90 to 10,735.80
Launch and first callers 8.9%: CAD 7,182.30 to 10,982.60
Holdback, 30 days after launch (10%): CAD 8,070 to 12,340

Start from this example

Example projectWeb app

Bookings and demand dashboard

Hypothetical. Not a client, not a result.

// The problem

A museum and a family of attractions see ticket sales in one system and reseller sales in emails, so pricing and staffing are set on last year's guesses.

// What we would build

A dashboard that reads the booking system, resellers and the till into one model, so managers see demand by day, product and channel, how far ahead guests book, and which channels pay for themselves.

// What is in it

Bookings by day, product and channel
How far ahead guests book, by season
Channel costs set against what each brings in
Capacity used against capacity offered
Exports for finance and the board

// Stack

Next.js
PostgreSQL
dbt
Booking and till interfaces
DigitalOcean

// estimate

Build: ≈ US$36,200 to US$55,300, delivered within 14 weeksCAD 51,600 to 78,800
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 2.4 to 3.4 weeks
Core features: 1.4 to 2.4 weeks
Full build: 0.9 to 1.9 weeks
Testing and fixes: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

Interface access from your resellers and agencies: 1 to 4 weeks

How it is paid

Deposit 30%: CAD 15,480 to 23,640
Discovery 6.6%: CAD 3,405.60 to 5,200.80
Design approved 6.6%: CAD 3,405.60 to 5,200.80
Core features 20%: CAD 10,320 to 15,760
Full build 13.3%: CAD 6,862.80 to 10,480.40
Testing and fixes 6.6%: CAD 3,405.60 to 5,200.80
Launch 6.9%: CAD 3,560.40 to 5,437.20
Holdback, 30 days after launch (10%): CAD 5,160 to 7,880

Start from this example

// questions

Questions we get about this.

Which online travel agencies can the reseller hub connect to?

Those with an interface open to operators, directly or through a connectivity partner. We confirm yours before we quote.

Can small local resellers use the hub without building anything?

Yes. They can use a simple reseller portal on top of the same interface.

What happens when a reseller booking fails to arrive?

It is retried and flagged to your staff, so a guest is never missing from a manifest without warning.

Back to the industry: Tour operators and attractions About the service: Integrations and automation

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call