| Season | Luxury Tent | Family Suite |
|---|---|---|
| Green Jan to Mar | 6 200 | 5 600 |
| Shoulder Apr to Jun, Nov to Dec | 7 400 | 6 750 |
| High Jul to Oct | 9 850 | 8 950 |
- Single occupancy, Luxury Tent only: sharing rate plus 40%.
- Conservation levy: ZAR 320 per person per night.
Contract loading for DMCs and tour operators
RateReady reads every supplier contract twice, asks what it can't prove, waits for your tick, then writes it and proves it landed in your book.
Nothing is written until it's ticked.
Accommodation, transfers, day tours, flights, rail, activities. You name it, it goes in the same way: read, checked, ticked, written, proven.
17,257 of 17,269 figures matched, contract against book2.4 days typical time to close a questionOne live engagement: a boutique luxury DMC in Durban. Service split from the 19 October 2026 read.
The expensive part is being behind
It takes your highest loaded rate and adds ten percent: a number nobody agreed with the supplier, quotable, bookable and invoiced. Tourplan warns on screen. It does not warn through the API, so the first sign is an invoice that doesn't match the confirmation.
In Durban, one re-contract sat unloaded with about ZAR 975 per room-night of already-negotiated margin going unclaimed. Nobody was slow. That's just how much paperwork there is.
An unloaded contract is not a gap in your system. It is a made-up price on an agent's quote.
A made-up lodge with the real checks, running in your browser. Scroll to drive it, from the PDF arriving to every rate proven in the book. At step five, tick it yourself.
| Season | Luxury Tent | Family Suite |
|---|---|---|
| Green Jan to Mar | 6 200 | 5 600 |
| Shoulder Apr to Jun, Nov to Dec | 7 400 | 6 750 |
| High Jul to Oct | 9 850 | 8 950 |
| Option | Green | Shoulder | High |
|---|---|---|---|
| LTENT TWLuxury Tent, sharing | |||
| LTENT SGLuxury Tent, single | |||
| FAMSU TWFamily Suite, sharing | |||
| LEVYConservation, pppn | |||
One question, page 1. Family Suite, High. The print is smudged: read one says 8,950, read two says 8,590. Which is it?
9 rates ready to write. 1 held for your answer.
Keep scrolling and it starts.
Renewals, new rates, new rooms, new specials, changed terms, a levy that moves. RateReady takes the admin out of loading and managing contracts, suppliers and products. Two pages or ninety, the job gets done quickly and properly.
By hand
With RateReady
The job stops being "read this document" and becomes "fill in a form we already have, and prove the answer".
Figure for figure. And every figure has to be found, quoted, in the contract's own text. A number nobody can point to on the page doesn't go in.
Last year's numbers test this year's. A load that would lower a live rate or roll a period back stops and asks.
A system can accept a rate, return success and store nothing. Eighteen single rates once did exactly that. Only the read-back knew.
There is no path from a document to your live rates that doesn't pass a person.
A doubt holds only the figures it's about. Every answer is kept, so nothing is asked twice.
A run can stop halfway and still report success, so the book is asked what it actually holds. On Tourplan it runs over productConnect and holds no licence seat. Not on Tourplan? I'll scope and build your integration at no extra charge.
RateReady's first client: a boutique luxury DMC in Durban, selling lodges and camps across South Africa, Botswana, Zambia and Zimbabwe.
Arrived as they were sent: 278 PDFs, 270 emails, 9 Word files, 6 spreadsheets, 5 zips. Nobody reformatted anything.
81 rate periods in the wrong currency. Three other checks passed it.
18 single rates silently discarded. Every call returned success.
57 options adding VAT twice. Corrected and every one read back.
A run that applied one of five closures. Why every load is rechecked hourly.
An update that would have deleted live child rates. Stopped before writing.
19 loads that would have lowered or re-priced live rates. Somebody has to say so.
163 offers in Tourplan with no contract on file. Now a list to settle.
No. Drop the file in a folder or forward the email. In Durban they came as PDFs, emails, Word files, spreadsheets and zips, some of them scans. That's normal, and it's the point.
No. It can update whatever system you use, Tourplan, Travelogic or anything else. If I haven't built the integration with yours yet, I'll investigate, scope and build it at no additional charge.
No. It runs over productConnect, Tourplan's own documented API, so it holds no licence seat and nobody gets locked out while it loads.
Two independent reads have to agree. Every figure has to be found in the contract's own text. It's checked against your book and last year's numbers. A person ticks it. Then it's read back, and checked again every hour.
What a new contract doesn't restate, like an offer or a supplier's own cancellation terms, is kept. A load that would lower a live rate stops and asks first. In Durban that happened nineteen times.
In Durban the first load landed on 10 September and 179 properties were loaded within fourteen days, and all 381 contracts within 38. Your backlog and your answers set the pace, so I'd rather show you on two of your own contracts than promise a number.
Thirty minutes. A quick background to what I've built and why, a live demo on real contracts, and some food for thought for your own book.