Availability is a count, not a counter.
A B2B reservation system for operators who sell tours to agencies. The agency browses tours and books through a Spanish storefront; the operator manages availability, pricing, and reservations from a panel available in EN, ES, and TR.
A B2B reservation system built for operators who sell tours to agencies in Spain and Latin America. The agency browses tours and books through a Spanish storefront; the operator manages tours, departures, availability, pricing, and reservations from a panel available in EN, ES, and TR. There is no direct sale to the end traveller: the commercial model is B2B.
Availability is not a counter: occupancy is counted from real reservations every time and held per departure, while the value on the tour is only a default template. Because individual and group reservations pass through the same price function, a pricing rule changes on a single line and no inconsistency reaches the invoice.
A Spanish-language storefront where agencies browse tours and make reservations. The agency works in the target market's language.
Management of tours, departures, availability, pricing, and reservations; the panel comes in EN, ES, and TR. The team works in its own language.
Occupancy is counted from real reservations every time, and availability is held per departure. The risk of overselling and empty seats goes down.
Individual and group reservations go through the same price function; a rule changes on a single line. No inconsistency reaches the invoice.
Reservation and password-reset emails are sent through the system, so the agency can follow the process.
Schema changes are made through version-tracked migrations, and the pricing and availability rules are protected by 17 automated tests. Updates proceed under control.
The pricing rule is governed by a single constant, and both individual and group flows pass through the same calculation function. A rule change is one line — but because it directly affects the invoice, the customer is asked first.
Availability is not stored as a counter; occupancy is computed from real reservations on every query. The quota on a tour is only a default template, and per-departure availability lives on the departure record.
Schema changes are made through version-tracked SQL migrations, and emails (including password reset) go out through the system. Uploaded images are compressed (38.5 → 5.5 MB); the originals are kept as backups.
We'll email you the file covering the module list, screen flows, and integration details.
What people ask us, answered briefly and plainly.
A B2B reservation system for operators who sell tours to agencies. The agency browses tours and books through a Spanish storefront; the operator manages availability, pricing, and reservations from a panel available in EN, ES, and TR.
Agency storefront: A Spanish-language storefront where agencies browse tours and make reservations. Operator panel: Management of tours, departures, availability, pricing, and reservations; the panel comes in EN, ES, and TR. True availability: Occupancy is counted from real reservations every time, and availability is held per departure. One price calculation: Individual and group reservations go through the same price function; a rule changes on a single line. Email notifications: Reservation and password-reset emails are sent through the system, so the agency can follow the process. Versioned schema: Schema changes are made through version-tracked migrations, and the pricing and availability rules are protected by 17 automated tests.
Pricing depends on how many people will use it, which sections are opened, and whether it must connect to other programs. After the conversation we send a written quote with scope, timeline, and a firm price within 48 hours at the latest.
Yes. For one year after delivery, updates, technical support, and server maintenance continue at no extra charge.
Let's begin
How many users, which modules, which integrations — a clear scope and price within 48 hours.
