The Time Zone is the time setting on which most configurations related to time within the account will initially be based.

Additionally, the option Allow schedules to have different time zones enables schedules to be based on a time zone that is either the same as or different from the account's time zone.

You will enter prices one line at a time with a weight and distance range. When searching for prices the algorithm will try to match a record here based on the total weight of all parcels of the same fare type in a shipment and the distance between origin and destination.

Navigate to admin>pricing>parcel zones.

Time: Enter the schedule departure time in 24 hour clock, ex. 18:30 or 02:25. The times are based by default on the account's time zone, but they may also be set according to the time zone of the first station in the itinerary.

Time Zones: Select the time zone on which the schedule will be based. The first option, "Use account time zone," bases the schedule on the time zone configured in the account, while the second option, "Use time zone of first station," applies the time zone of the first station in the itinerary.

Always: The system will automatically send a confirmation email each time a refund is processed.

Busbud does not use shifts so if your price is configured by shift zones you need to update those rules (duplicate them) and make sure that they are not shift zone restricted or Busbud wont have access to them.

Two key updates have been made to the Pay Later configuration:

New Setting – Expiration Time Prior to Trip Departure
A new time-based parameter allows you to expire Pay Later reservations X minutes or hours before departure, whichever is earlier between this setting and the existing Maximum Waiting Time. This helps automatically free up held seats if payment is not initiated in time.

Updated Setting Language – Wait Time Departure Offset

New Name: Wait Time Departure Offset
New Tooltip: To permit payment processing to continue past the departure time of a trip, this setting allows the 'waiting for payment' status to extend beyond departure by the offset time specified.

These updates provide greater flexibility and automation in managing seat holds and payments near departure times.

Also updated:

• Earliest travel date: By date and time.

The Proration Table is used to properly calculate taxes on connecting trips that might go through provinces or zones with different tax rates.

You can manage what trips will be shown to the customer based on the time of purchase and the times of the trips.

The Advance purchase from and Advance purchase to fields are used to define the time window in which ticket purchases are allowed before a trip's departure. These settings ensure that tickets can only be bought within a specific range of hours before the scheduled departure time.

Enter the shift zones, sales channels and shift locations targeted by this rule.

Timezone: Using the drop down menu, select the appropriate timezone in which the station is found. by default, a newly created station will inherit the timezone of the main account.

If you have stations in different timezones, you can adjust the timezone for that particular station so it accurately reflects the local time in that station.

The Enable cross-border taxation (Optional) is for multi country operators that only apply taxes in one jurisdiction, but is considered experimental at this time.

• If checked, this will allow schedules to have different time zones.

Important: All the times showed are in the timezone set in the account.

As we continue the initial configuration of your account, there may be some holidays to identify during which time you have abnormal or enhanced service schedules or cease operations altogether. In this case, you will need to identify these holidays.

Next, the service will look at all of the possible trip departure and arrival times, and eliminate trips that are not desirable.

Each time a transaction is made, a confirmation will be mailed to the customer if an email is available (in many cases, it is mandatory).

In the main screen (if it's the first time) you will have an empty state and you will have to create the first payment terminal.

The next configuration set the expiration time of referenced payments.
By default, and if these parameters are not set, a payment will expire at trip departure time and if it has not a trip departure time the payment will expire after 12 hours.
Sale using this kind of providers after trip departure time could have an unexpected behaviour. If you need sale after trip departure please consider set a maximum waiting time.

Expired tickets should not be changed unless the cutoff time established is negative. Cutoffs time can be managed from the product line properties (Cutoffs)

When moving a ticket, you can only transfer it to a different time, and it has to remain within the same Origin and Destination. Move is more of an admin function (IROPs), since there are less restrictions than with a regular change. Also, there are no fees associated with the Move function.

If you check the reprint option, you have to verify that the /tickets/re-print option is enabled in roles and permissions, also you have to take into account that you will only be able to print a second time but with a watermark indicating reprint.

Enter the email you will assign to the admin user, the password for the email, and confirm the password a second time.

Trip search pull prices from only one Pricing Schema at the same time, it is not possible to combine JP and Fare Tables for a single trip search.