QGo - Jazeera Packages - QA

B2B2B Workflow

1. New Agency Type – Sub Agent (Under Travel Agent Hierarchy)

Introduce a new agency type titled “Sub Agent”, which operates under a Travel Agent.
Sub Agent hierarchy will inherit the Travel Agent’s configuration while maintaining independent booking and reporting capabilities within permitted boundaries.

2. Markup/Discount Configuration

• Travel Agents can configure markups or discounts specific to each Sub Agent.
• Travel Agents may also apply instant markups or instant discounts for bookings made directly by their Sub Agents.

3. Reporting & Transaction Visibility

Travel Agents should have access to the following reports, reflecting both direct and Sub Agent transactions:

• Transaction Queue Report (TQR)
• Sales Report
• Account Summary Report
• Stock Report
• Manifest

These reports should reflect transaction-level details, including pricing breakdowns. For instance, if a Travel Agent books a ticket via the in-house system with base fare ₹300 and markup ₹50 from in-house, the Travel Agent can present it as ₹350 with zero additional markup.

Sub Agents will also have access to their own reports, displaying their specific sales and financial breakdowns, while showing the received amounts from their parent Travel Agent.

4. Wallet & Balance Handling

• Both Travel Agents and Sub Agents will have wallet-based flows.
• Ticketing by Sub Agents will be subject to combined wallet balance validation:
• A ticket can be issued only if both the parent Travel Agent and the Sub Agent have sufficient balance.
• If the Sub Agent has enough balance but the Travel Agent does not, ticket issuance should be denied.
• This rule applies to both online and offline ticketing flows.

5. Restrictions on Sub Agents

• No outstanding balance support for Sub Agents.
• No Behalf work flow
• No option for direct top-up or bank transfer through the system.
• Instead, a manual adjustment form will be available where the admin or parent Travel Agent can add or deduct balances. This form will include: Amount field, Top-Up button, Deduct button

6. System Modules to Handle Sub Agent Functionality

The following modules need to accommodate Sub Agent configurations:

• Agency Management
• Roles & Permissions
• Transaction Queue Report (TQR)
• Markup/Discount Management
• User Management
• Reporting Module, including:
• Sales Report
• Passenger Sales Report
• Account Summary Report
• Manifest
• Stock Report

New Agency Type – DMC (Destination Management Company)

• A separate agency type called “DMC” will be introduced, similar in structure to a Travel Agent.
• DMC users will have specific permissions to:
• Add, Edit, and View inventories
• View Stock Reports related to those inventories
• View/Edit Transaction Queue Reports (TQR) showing booking details for their managed inventories
• No wallet option for DMCs
• No booking flow, they can be treated as a data entry group in which they will be able to see the bookings of their own inventories.