FAQs
Frequently asked questions
What does Walitrix provide?
Walitrix builds travel technology for booking, trade distribution, group operations, back-office servicing, and supplier connectivity. Products can be deployed individually or as a composed stack.
Can we start with one product and expand later?
Yes. Walitrix is modular. Many clients begin with B2B or OTA and add Groups, Back Office, or Connect as their operations grow. Shared data models reduce rework when you expand.
What is the difference between Walitrix OTA and B2B?
OTA is designed for consumer-facing retail: storefront, checkout, and customer accounts. B2B is designed for trade partners: agent hierarchies, credit limits, markups, and partner reporting. Both can share the same supplier connections through Connect.
Which suppliers can Walitrix connect to?
Walitrix Connect supports GDS, NDC, direct airline, hotel, payment, and messaging integrations. Specific connections depend on your commercial agreements and target markets — we scope these during discovery.
Do you replace our existing GDS or airline contracts?
No. Walitrix integrates with suppliers under your existing contracts and credentials. We provide the technology layer; commercial relationships with GDS, airlines, and bedbanks remain yours.
How does implementation typically work?
We start with discovery: channels, markets, supplier mix, and operational requirements. Then we configure products, connect approved suppliers, migrate or parallel-run as needed, and train your teams before go-live.
Can Walitrix integrate with our ERP or CRM?
Yes. Connect exposes APIs and integration points for finance, CRM, and custom systems. Scope and approach depend on your existing architecture and which events need to sync.
What support is available after go-live?
Support covers platform availability, supplier connection issues, and operational guidance. Severity-based response targets are defined in your service agreement. Enhancement work is scoped separately.