Hotels & resorts — the supply side
Properties whose inventory, rates and contract terms are captured once as structured data, so what was negotiated is exactly what the system sells.
See the Hotel Partner Portal
Home/Platform
Platform
One record. Every commercial decision reads from it.
TESSMA is organised around the booking, not around departments. Contracting, pricing, finance and operations are views onto the same object — which is why they agree.
Who trades on TESSMA
One contracted marketplace, three kinds of buyer.
TESSMA’s core job is hotel contracting: negotiating and holding a property’s rates, allotments and terms as structured agreements. That contracted supply is then made available, under commercial agreement, to vetted business buyers only — never sold on the open public market. Each buyer below trades on the specific terms it holds, not a rate card everyone sees the same way.
Contracted travel agencies
Digitally connected travel agencies booking against negotiated rates, allotments and credit terms held as live contracts.
Corporate travel accounts
Companies with negotiated corporate programmes, where volume rates and credit terms apply automatically at the point of booking.
Offline & local agent networks
Smaller, community-based travel agents who transact by phone and email rather than through digital channels, onboarded onto the same contracted terms as every other buyer.
Architecture in one idea
Most platforms integrate modules. TESSMA never separated them.
When commercial operations, revenue and finance are separate products, integration becomes a permanent project. Rates drift from contracts. Reports drift from ledgers. Somebody reconciles by hand.
TESSMA holds one commercial record and one set of rules. A module is a way of working with that record, not a copy of it.
CAPTURE
Terms enter as data, not documents
Contracted rates, allotments, credit terms and conditions are captured in structured form during contracting. Nothing has to be re-entered later to make the system sell correctly.
RESOLVE
Every request is priced against who is asking
One inventory position, one rate engine. The rate a buyer sees is resolved from their contract at request time, so there is no separate rate table to keep in sync.
RECORD
The booking carries its own history
Which rule applied, which channel it arrived through, what changed and who changed it. The booking is the audit trail, not a report generated about it.
SETTLE
Finance reads the same object
Commission, adjustments, tax treatment and settlement reference the booking directly. Month-end is a query, not a rebuild.
Modules
What you actually work in.
Each of these is a surface onto the same commercial core. Enable what a property or partner needs; the record underneath does not change.
Commercial Operations
Channel-neutral inventory with per-buyer rate resolution, restrictions and stop-sells applied in a single pass, and an audit record of every published change.
Commercial Marketplace
Commercial partners see supply that is genuinely bookable to them under the terms they hold. Contracted visibility rather than open search results.
Contract Management
Negotiated rates, allotments and conditions are captured as structured data at signature, so the terms in the system are always the terms that were actually agreed.
Connectivity
Certified links to the operational systems a property already runs, keeping commercial terms aligned with what is happening on the floor.
Revenue
Pace, constraints and demand signals in one view, with the rule that produced a recommended rate always visible next to it.
Commercial intelligence
Market position, channel mix and account performance, structured for decisions a commercial team can take the same day.
Finance & payments
Bookings, commissions, adjustments and settlement carrying one reference end to end, with rounding and tax handled centrally.
Operations & automation
Arrivals, exceptions and recurring commercial tasks on schedule, each with a record of what ran, when and why.
Supplier & partner management
Accounts, contracts, credit terms and access managed in one place from first application to ongoing trade.
Applied AI
Assistants that draft, summarise and flag inside the workflow, with the inputs they used shown alongside the output.
Working in it
Designed for the person who has to answer for the number.
Software gets judged on its worst moment: a rate that will not push, a report that disagrees with the ledger, a booking nobody can explain. Those are the moments TESSMA is designed around.
- Every rate shows the rule, contract and constraint behind it
- Every report drills through to the bookings it counted
- Every change names the person or process that made it
- Every failure state says what happened and what to do next
- Design rule
- Explain, then act
Common questions
What people ask before a demo.
No. TESSMA is a commercial layer, not a replacement for on-property operations. It connects to the systems a hotel already runs so commercial operations and reporting reflect operational reality. Which specific systems are certified today is confirmed during scoping.
Yes. Most engagements begin with the single problem that costs the most time — commonly rate consistency or reconciliation. Because every module reads the same record, adding the next one does not require a migration.
Tenant separation is structural rather than a query filter, and access within a tenant is scoped by role at the service layer. The Technology page covers the security model in more detail.
Contract and rate structures are captured first, because everything downstream depends on them being right. Connectivity and finance configuration follow. Typical timelines depend on how many channels and contracts are in scope — we give a written estimate before any commitment.
Commercial model — to confirm Pricing is quoted per engagement based on scope. We do not publish a rate card we would have to negotiate away.
See it against your own rate structure.
Bring a contract, a channel and a reporting question. That is enough for a useful first session.