Cancellations & Refund Policy

Effective Date: 18th June,2025

At Bee2Bees, we strive to offer flexible and transparent service policies to our valued travel partners. As we work on a B2B model, cancellations and refunds are subject to the terms agreed upon at the time of booking and the policies of the hotels and vendors involved.

1. Booking Cancellation
  • Cancellations must be requested in writing via email or WhatsApp with a clear reference to the booking.

  • All cancellation requests will be acknowledged with a confirmation receipt.

  • Cancellation timelines vary based on the hotel, season, and vendor terms. These will be communicated at the time of quotation or invoice.

2. Refunds
  • Refund eligibility is determined by the cancellation policy of the respective service provider (e.g., hotel, transport vendor).

  • If a booking qualifies for a refund, the amount (after applicable deductions) will be processed within 7–14 working days to the original payment mode.

  • No refunds will be provided for:

    • No-shows or late arrivals.

    • Early checkouts or unused services once the package has started.

    • Bookings canceled outside the permissible window.

3. Force Majeure

Bee2Bees is not liable for cancellations due to circumstances beyond our control, including but not limited to natural disasters, political unrest, strikes, or government-imposed restrictions. In such cases, we will coordinate with vendors for rescheduling or partial refunds where possible.

4. Modifications

Date or service modifications are subject to availability and may attract additional charges. Any changes must be communicated at least 72 hours before the scheduled service.

5. Dispute Resolution

In case of any dispute regarding cancellations or refunds, we request our partners to reach out to our support team at info@bee2bees.com or call us on +91 8595450349. We aim to resolve concerns fairly and quickly.

Note: All services are provided to registered travel agents or corporate clients under commercial terms. Consumers should route all queries through their respective travel partners.