Free 30-minute AI & automation audit with a senior engineer. You keep the notes. Book yours

Use case · Travel & hospitality

Running a B2B hotel-distribution business on one admin, supplier and pricing back end

Admin and supplier services for hotel rates, availability, rate plans, buyer margins, wallets and virtual cards, with queue-based pricing updates on AWS.

Client details are kept confidential. This use case describes the problem and what we built.

The brief

The client runs a B2B hotel-distribution platform that connects hotel suppliers with travel buyers. It sources rates and availability from hotels and distributes them to buyers, each with its own commercial terms.

MultiGenesys engineers worked across the platform’s back office: the admin services that operations staff rely on, the pricing pipeline that keeps rates current, and the supplier-facing services that let hotels manage their own inventory.

The challenge

What needed solving

Thousands of rates moving every day

Hotel availability, rates and inventory change constantly. Updates had to reach the distribution platform quickly without blocking the admin tools that operations staff use all day.

Many buyers, many commercial rules

Each buyer has its own margins, policies, mappings and payment setup. Operations needed one place to manage clients, properties, rate plans and room types.

Hotels needed self-service

Hotel suppliers wanted to manage their own properties, room types, rate plans and promotions, and see how they perform, without going through the operations team.

Hard-to-trace failures

When the admin UI showed server errors, the team could not easily tell whether the cause was a slow query, an external API or the service itself.

The solution

What we built

  1. Central admin service

    A Spring Boot admin API covers client and supplier management, properties, rate plans, room types, policies, day rates, global margins, reservations, reports, scheduled jobs and user management.

  2. Queue-based pricing processor

    A separate service consumes rate and availability updates from Amazon SQS (with S3 for large payloads), maps them to rate plans and writes them to MySQL, keeping heavy pricing work off the admin path.

  3. Supplier portal back end

    A supplier-facing API with Microsoft identity sign-in lets hotels manage properties, room types, rate plans and promo codes, with performance graphs and embedded Power BI reporting.

  4. Payments and wallet controls

    Wallet and virtual-card modules support buyer prepayment and supplier settlement, backed by dedicated test coverage.

  5. Observability and resilience

    AOP-based performance logging with trace IDs and slow-call thresholds, plus Prometheus metrics and Grafana dashboards, make slow queries, external calls and failures visible.

  6. Schema and release discipline

    All database changes run through a Liquibase project, and services ship via Docker, Jenkins and Bitbucket Pipelines, with configuration held in AWS Secrets Manager.

The outcome

What changed

One back office for the business

Operations staff manage buyers, hotels, pricing rules and reservations from a single admin API instead of scattered tools and scripts.

Pricing updates decoupled from admin work

Queue-based processing lets high-volume rate and availability updates run independently of day-to-day admin traffic.

Faster root-cause analysis

Trace-linked logs and metrics show whether an error came from the database, an external API or the service, so fixes target the real cause.

Technology used

  • Java
  • Spring Boot
  • Spring Security
  • MySQL
  • Liquibase
  • Amazon SQS
  • Amazon S3
  • AWS Secrets Manager
  • Prometheus
  • Grafana
  • React
  • Docker
  • Jenkins
  • Bitbucket Pipelines

Have a similar problem to solve?

Share a few lines about your project. A senior engineer — not a salesperson — replies within one business day.

Free AI audit Let’s talk