Good day!
There was an old bus ticket booking system.
We are developing a new one at https://infobus24.de/
The website will be in three languages: Russian, Ukrainian, and German.
There are several levels of access with their own functionalities. Each has its own personal account.
In addition, we need to set up the generation and sending of tickets and tax reports according to the template.
At this stage, there are many shortcomings and bugs.
Everything needs to be fixed to make it work and retain all the functionality of the old system (all accesses will be provided).
User types:
1) Super admin - the main consolidator - owner. They can do everything: add consolidators, agents, carriers, input any information and edit it, grant and close any accesses.
2) Consolidator - those to whom we rent the system, including our own (we also sell tickets).
Consolidators can:
- create carrier and agent companies (those who simply sell tickets), add them to their group (Firmengruppe),
- create routes linked to carriers,
- create and input various additional information for creating routes (discounts, luggage, mileage, etc.).
Here, it is also necessary to ensure that duplicate carriers, routes, cities, departure locations, times, etc., are not created again. If they already exist, they should be pulled from the database.
3) Chief - someone who can perform the duties of a consolidator on their behalf, appointed by the consolidator, grants them access, can open or close access for them. They have partially limited access, without the right to delete or add new consolidators, carriers. But they can create or edit agencies, routes, schedules, transport conditions, prices, luggage, discounts, invoices, and tickets.
4) Dispatcher - limited access, allowed to edit orders, issue invoices and tickets, close the return date, access to creating and editing information on bus departures, access to passenger lists. Dispatchers are appointed by the consolidator and access is granted in the same way.
5) Agency (agent) is registered by the consolidator and granted access by them (this is how it currently works).
An agent can change their password themselves if forgotten. However, the consolidator always has the right to revoke the agent's access. The agent has access to booking routes, their work cabinet, information, and booking code (frame) for installation on their website.
6) Carrier - only has direct access to their passenger lists.
What needs to be done.
1. Fix
1. Data on flights, routes, etc., disappear somewhere. The page needs to be constantly refreshed.
2. When searching for a ticket (Flight search), not all available flights are found. For example, there may be 2 flights from Berlin to Kyiv on the same day but at different times.
3. Creating a new flight, it disappears somewhere.
4. When editing a booking with an open return date, there should be an option to add this date.
5. The ticket file should be named Ticket. Rechnung means invoice.
6. When reserving for an agency, the Off.N. field - office number, is required, which is their personal reservation number.
7. Remove our personal phone number from the ticket.
8. Place the agency's phone number on the left side of the ticket.
9. Check the dates on the ticket and in the system, when the bus departs, for example, today, but arrives in different cities tomorrow and the day after tomorrow (as the routes are long).
There may be more bugs and inconsistencies with the old system.
2. Implement
1. Ability to choose a return flight from multiple options (there may be flights at different times on the same day)
2. Add a Delete button at each stage and tab (flight, user, route, etc.)
3. When editing a booking with an open return date, there should be an option to add this date.
4. Add the ability to change the days of the week in the schedule when the flight departs, for example, Fri and Sun. Note that on different days of the week, the bus may depart from different locations in the same city or from different cities.
5. Multiple selection for changes on all tabs: disable cities, change prices, etc. To avoid changing individually.
6. Ability to block the sale of tickets for specific seats on the bus, date, date range, city, boarding location in a specific flight.
7. Provide notifications indicating the specific error (field not filled in or enter a different email...)
8. Passenger list as a template with the option to print (this is currently unfinished).
9. Add booking statuses.
----------
Regarding booking statuses
1. New status - when a new booking is made
2. In progress status - sending a reservation email to the carrier.
The carrier confirms the availability of seats by phone or sends an email confirmation.
3. "Invoice confirmed" status - after the carrier confirms the seat, an invoice is sent to the agency or client via email. The format of these invoices varies.
The agency sends us a payment receipt or we see in the bank that it has been paid.
4. "Ticket confirmed" status - after payment confirmation, the ticket is sent to the agency or client via email and displayed in the system.
5. Paid status
6. Canceled status - the invoice and ticket are deleted, freeing up the seat for booking, and an email is sent to the agency notifying them of the cancellation.
All statuses are manually selected, except for the initial "New" status, which is automatically applied to new bookings.
The emails are theoretically set up, they just need to be sent after all testing to avoid spamming the mailbox.
------------
3. Implement an API from this site and how the booking form works on this site
https://odri-ua.com/
The API is here:
https://odri-ua.com/swagger/index.html
Odri is a similar aggregator site for carriers and agents, like ours, but Ukrainian. We have a personal account there where we manually entered our bookings.
We implemented a booking form on our old site, similar to Odri's site. Through it, all bookings were automatically recorded via the API in Odri's database, our personal account there, and our site's database.
This form is on a separate tab here https://www.avtobus.de/reisezentrum/
It would be preferable to make it differently so that the booking form for Odri and us is the same, making all flights look the same. That would be ideal.
However, all data on Odri's bookings must be displayed on our end (correspondingly in our database) and in our personal account on Odri.
How to visually make this better and easier, I do not know. Perhaps you will suggest a great option :)
All Odri flights are available to all agencies; they can book under their login.
For regular users, there is open access through a booking form (similar to Odri's), and we need to see who made the booking, to whom and where to send the invoice via email for communication. In other words, a section for regular users.
I will provide keys and logins.
------------
4. Create code (script) for embedding a booking form on any website.
Similar to here https://avtobus.kharkov.ua/
-----------
Report every 2 days on progress (list) and screenshots.
