Enterprise DNA

Instead of Tourplan

Stop renting Tourplan. Own your tour operations system.

We build your version around your supplier contracts and departure routine, bring your Tourplan records across, and run it for you through Omni by Enterprise DNA.

Tourplan Cloud starts at US$1,000 a month, or US$12,000 for twelve months at that rate. Edition and concurrent users determine your quote.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

A booking file is only the start of the bill

Tourplan prices its editions by functionality and concurrent users. Its published cloud starting price is US$1,000 a month. Compare your actual agreement with the work you need done.

credit_card

The cloud subscription

Tourplan lists a US$1,000 monthly starting point. Your edition and concurrent-user requirement determine the quote.

groups

FIT and group reservations

Tourplan handles individual and group bookings. Your own version holds the departure, traveller count and supplier commitments together.

storage

Supplier contracts and rates

Dated buy and sell rates, currencies and cancellation terms are operational records you can own and change.

event

Room blocks and deadlines

Keep the rooms held, units allocated and release dates visible before a block becomes a cost.

description

Itineraries and vouchers

Turn recorded services into your documents. Requested services stay visibly unconfirmed.

monitoring

Financial reports and connections

Tourplan includes accounting and reporting alongside its booking tools. Scope your accounting and live supplier connections separately when planning your version.

Your own operating records

The questions behind a departure

Supplier desk

Know what still needs a confirmation

Bring supplier commitments, response dates and cancellation deadlines into one review.

  • check Requested services ordered by their confirmation deadline
  • check Supplier name and booking reference beside every chase
  • check Cancellation dates taken from the recorded contract
  • check Low-margin departures with outstanding confirmations singled out

Contract control

Release the rooms you have not sold

See what is held and allocated before the release date passes.

  • check Room blocks grouped by product and service date
  • check Unsold units shown against allocated units
  • check Overbooking rejected when a service is added
  • check Local release preserves the units already allocated

Departure money

Keep currencies and missing costs visible

Review each booking using the supplier costs and exchange rates you recorded.

  • check Cost and selling amounts kept in their stated currencies
  • check Service margin calculated in booking currency
  • check Deposit balances after externally reconciled receipts
  • check Imported Tourplan financial snapshots kept separate from current costing

Traveller paperwork

Produce the documents from the same records

Prepare the departure pack and check its gaps before a person approves it.

  • check Draft itinerary, rooming list, costing and supplier vouchers
  • check Named passenger counts compared with the expected group size
  • check Missing supplier registration evidence flagged for review
  • check Your business name and logo on the paperwork

Make it yours

Design your own Tourplan replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Tourplan. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Tourplan replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Tourplan data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Tour Operator for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Tour Operator for Claude Code

Connected to your own database

Which departures have low margins and still need supplier confirmations?

NZ101

Me cu
Southern Lakes Discovery
Rrency ma
NZD
Rgin_pct aw
15.2
Aiting_confirmation
2

Ask it anything

Questions across your tour records

These questions run on the demo records today. Tourplan also supports custom reporting. Here you own and can change the questions.

chat_bubble Which departures have unconfirmed services and less than twenty percent margin?
chat_bubble Which hotel blocks still have unsold rooms at their release date?
chat_bubble Which confirmed groups have fewer named travellers than expected?
chat_bubble Which agent produces the recorded margin in each currency?
chat_bubble Which supplier holds the largest confirmed commitments in its own currency?
chat_bubble Which departures have unpaid deposits approaching their due date?
chat_bubble Which requested services are near a cancellation deadline?
chat_bubble Which quotes are expired and have gone quiet?
chat_bubble Which adventure supplier records lack registration evidence for the trip date?
chat_bubble How do imported booking totals compare with the services now recorded?

Switching

How to switch from Tourplan

A move involves exporting the records you need, checking how they map into the new database, and validating the results before you stop using Tourplan.

  1. 1

    Export the records you need

    Ask Tourplan for its documented Tour Summary download, including booking currency and costs. It contains booking details and financial amounts. The import uses booking headers and financial snapshots, not a full operational archive. Supplier contracts, individual services, room blocks and passenger lists need separate exports and mapping. Export what your account allows, usually CSV or Excel, and check with Tourplan about the available options.

  2. 2

    Load a test sample

    Start with a checked sample of your Tour Summary export and use the import's test run first. It rolls back rather than saving records, so you can review the proposed import before loading it. Check that the report headings and dates are understood, and confirm that the booking currency and costs are included. Do not assume the summary contains supplier terms, services or passenger names.

  3. 3

    Review the import results

    Check the import results against Tourplan and resolve anything flagged before loading the full set. Identical records are skipped, while changed records stop the import for reconciliation. Confirm that the booking headers and financial snapshots match your source records. Treat the financial amounts as historical snapshots, not accounting transactions, and map separate exports for records the Tour Summary does not cover.

  4. 4

    Run both systems side by side

    Keep using Tourplan while you check the imported records and run the new database through real booking work. Compare the records and financial snapshots you brought across, and make sure your team understands which information is not included. Live availability, distribution, accounting and phone or web screens need separate implementation and validation, so confirm how you will handle those before relying on the new setup.

  5. 5

    Switch off Tourplan

    Stop using Tourplan only after you have checked the records in scope, resolved import issues and agreed how any separate connections or screens will be handled. Keep the Tourplan records or access you need for reference and any business requirements. The new base is not a reproduction of every Tourplan module, so do not treat the switch as proof that live feeds, accounting or other excluded workflows have moved.

construction

Where the real effort goes

The real work is usually mapping your own fields and operating rules, then deciding how much history to bring. The Tour Summary import covers booking headers and financial snapshots. Supplier contracts, services, allotments and passenger manifests need separate exports and mapping. If you have Enterprise DNA run it, they handle this mapping and migration scope with you.

Not ready for a call?

Get your Tourplan switch plan by email

We will send you the step-by-step plan for moving your business off Tourplan, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose how much you want us to handle

Open source

Do it yourself

Free code. Your hosting and agent costs.

  1. 1 Clone the repo and install its dependencies
  2. 2 Run npm run demo and inspect the fictional tour records
  3. 3 Open it in Claude Code, Codex, OpenCode or Cursor
  4. 4 Read the switch guide, test your Tourplan CSV and reconcile the booking summaries
Get it on GitHub

Built around your business

We customise it

One setup fee, then an agreed retainer

  • check Your supplier fields, booking stages and deposit rules
  • check Your Tourplan records mapped and reconciled
  • check A web front end and different technology where your operation needs them
  • check Your document layouts and agreed supplier connections
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Your records brought across with a checked migration plan
  • check Backups, permissions and agreed connections configured
  • check Your weekly supplier and departure routine maintained as the business changes
Talk to Sam

Questions

Instead of Tourplan, answered

What does Tourplan actually cost? expand_more

Tourplan's <a href="https://www.tourplan.com/resources/frequently-asked-questions/">own pricing FAQ</a> lists cloud subscriptions from US$1,000 a month. That is US$12,000 for twelve months at the starting rate. Pricing depends on edition and concurrent users. Check your agreement for the amount and services your business pays for.

Can we bring our Tourplan history across? expand_more

Yes, with a checked migration scope. Tourplan documents a <a href="https://usermanuals.tourplan.com/V2_5/Content/NX%20Reports/B-Operations%20Reports/B-TourSummary.htm">Tour Summary download</a> containing booking details and financial amounts. The free version imports that summary after its headings and dates are checked. Supplier contracts, individual services, room blocks and passenger lists need separate exports and mapping. We reconcile the records your version needs.

Does this replace our live hotel feeds and accounting? expand_more

Those connections need their own implementation and validation. We scope your live availability, distribution, accounting and any phone or web screens as part of your custom version. The working free base covers the recorded booking and supplier workflows shown here.

Can it check supplier evidence and produce our paperwork? expand_more

It flags missing recorded registration evidence for NZ adventure suppliers, passenger retention reviews and accepted-terms references. A person verifies the source evidence and the applicable rules. It also creates draft itineraries, rooming lists, costings and confirmed-service vouchers in your business identity.

Why change if Tourplan already has reports? expand_more

Tourplan offers standard and custom reporting. The reason to own your version is control over the records, rules and recurring licence decision. Start with the free working base, have us customise it, or have us operate it through Omni by Enterprise DNA. We agree a setup fee and retainer around the work you need.

Show Sam the departure that takes too much chasing

Book a 30-minute call with Sam. Bring your Tourplan bill, one supplier contract and a checked sample of a booking export. We will identify the records, connections and weekly jobs your version needs.

Tour Operator for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Tourplan?

Get your version built