Exception queues
Route schedule changes, cancellations, and sensitive cases.
Back Office
Walitrix Back Office
Servicing, accounting, and operations behind the booking
Post-booking operations — reissues, refunds, queues, invoicing, and supplier reconciliation — in one operational layer.
What it solves
Built for real travel-commerce operations
Retail and trade channels generate volume; back office keeps it profitable. Walitrix Back Office connects booking records to servicing workflows, financial postings, and supplier settlement so teams can resolve exceptions without switching systems.
Who it is for
- Travel businesses with dedicated operations teams
- Consolidators managing high ticket volume
- Enterprises requiring financial controls and auditability
Where does back-office software sit in travel commerce?
Back-office software manages operational follow-through: exceptions, servicing, and controls that keep commercial channels aligned with finance and fulfilment. It is most effective when it shares booking truth with OTA, B2B, and Groups.
What it controls
Capabilities that improve day-to-day operations
Each area is a control surface — not a decorative tile.
PNR servicing
Work bookings after sale without losing channel context.
Financial follow-through
Align invoices, receivables, and supplier payables.
Refund & reissue
Standardise high-impact servicing actions.
Audit & roles
Restrict sensitive actions by role, market, or branch.
Reconciliation
Keep settlement work attached to booking truth.
Problem → system
From after-the-fact reconciliation to controlled operations
Without the right system
- Exceptions handled in email outside the booking system
- Finance and ops working from different truths
- Unclear ownership of refunds and reissues
- No role gates on sensitive actions
With Walitrix in place
- Defined queues tied to booking records
- Servicing and financial alignment in one operational layer
- Standard refund and reissue workflows
- Role-based permissions and audit trails
Product workflow
How Back Office moves work
A scannable operating sequence — not a feature laundry list.
01
Signal
Exception or request arrives
02
Queue
Case routed by type
03
Investigate
Booking context opened
04
Act
Refund / reissue / change
05
Finance
Postings aligned
06
Close
Outcome recorded
07
Audit
Trail retained
System map
Where Back Office sits relative to commerce modules
Back Office is not a replacement for OTA, B2B, or Groups — it is the operational layer that keeps those channels profitable after the sale.
Primary product
Walitrix Back Office
Queues · servicing · controls
Retail
Walitrix OTA
Consumer bookings
Trade
Walitrix B2B
Partner bookings
Programmes
Walitrix Groups
Group departures
Supply
Walitrix Connect
Shared connectivity
- Commerce modules create bookings → Back Office works exceptions and financial follow-through on shared records → Connect remains the supply fabric.
Setup & fit
When Back Office is the right primary module
Use this to separate product intent from adjacent solutions and modules.
| Signal | Strong fit | Usually not primary |
|---|---|---|
| Primary user | Operations and finance teams | Travellers on a public storefront |
| Job to be done | Exceptions, servicing, controls | Consumer conversion UX |
| Composition | Paired with OTA, B2B, and/or Groups | Standalone sales channel |
Experience
Operational insight for faster servicing decisions.
Feature system
Capabilities that matter in production
Exception handling
Route schedule changes, cancellations, and ADM-related cases through defined queues.
Financial alignment
Link bookings to invoices, payments, and supplier payables.
Controlled access
Restrict sensitive actions by role, market, or branch.
FAQ
Common questions about Walitrix Back Office
What does travel back-office software manage?
Walitrix Back Office focuses on operational control after and around bookings — exceptions, servicing workflows, and coordination with the commercial modules that create the bookings.
Does Back Office replace OTA or B2B?
No. It complements sales modules. Most deployments pair Back Office with OTA, B2B, and/or Groups so operations teams work from shared booking truth.
Related solutions
How this product fits operating models
Solutions describe how Walitrix products combine for a specific audience — not separate standalone platforms.
Online travel brands, booking apps, and digital-first retail businesses
Online Travel Agencies (OTA)
Consumer digital retailers must convert visitors through search, fare presentation, checkout, payments, accounts, and post-booking self-service.
Explore solutionWholesalers and consolidators serving agency networks
Consolidators
Consolidators operate on volume, credit, and tight reconciliation — requiring trade tools and robust back-office alignment.
Explore solutionLarge travel businesses and multi-brand operators
Enterprise Travel
Enterprise operators need modular deployment, role governance, auditability, and integration with existing finance and CRM systems.
Explore solutionAlso see technology architecture and integrations.
Ready to evaluate Walitrix Back Office?
Bring the operating model. We will map modules honestly — without inventing capabilities.