Journey pricing is a pricing schema used to set special prices for specific O&D’s, that require dynamism using the different parameters that the configuration offers.

Journey pricing is a pricing schema used to set special prices for specific O&D’s, that require dynamism using the different parameters that the configuration offers.

-Any product (market pricing and journey pricing)

In this scenario, we have Market Pricing product that works with modifiers and fare tables according to seat class

To create and/or update rules of journey pricing, you have two different ways of doing it:

To create and/or update rules of journey pricing, you have two different ways of doing it:

Journey pricing

Navigate to admin>pricing.

Given a selected trip, we will try to find a Journey pricing record that matches the trip. If found it will applied following the same rules as with JP pricing.

Navigate to admin>Pricing Schemas>market-pricing.

En este escenario, tenemos el producto Market Pricing que funciona con modificadores y tablas de tarifas según la clase de asiento

Betterez offers three possible pricing schemas for products of the reservation family, Point to point, Journey and Market pricing.

Betterez offers three possible pricing schemas for products of the reservation family, Point to point, Journey and Market pricing.

The Journeys report is aimed to show information related to Journey statistics, without considering pricing.

The Journeys report is aimed to show information related to Journey statistics, without considering pricing.

Accumulating and redeeming loyalty points is something that is managed at the level of Pricing records. For every journey pricing rule/Market pricing modifier that is entered, there are two parameters related to loyalty.

Accumulating and redeeming loyalty points is something that is managed at the level of Pricing records. For every journey pricing rule/Market pricing modifier that is entered, there are two parameters related to loyalty.

Journey pricing schema involves the use of individual pricing rules for each origin and direction. This pricing rules can be tweaked and controlled using a number of different exceptions which include:

The Betterez platform offers three distinct types of pricing schema for the that can be applied to a (reservation) product:

The use of fare classes are a feature only available for accounts with products that are using the Journey Pricing pricing schema. Customers using this pricing type must declare at least on fare class in order to show results in the trip search. Accounts with products using the Point to Point pricing type can not use fare classes.

The use of fare classes are a feature only available for accounts with products that are using the Journey Pricing pricing schema. Customers using this pricing type must declare at least on fare class in order to show results in the trip search. Accounts with products using the Point to Point pricing type can not use fare classes.

If you are using Journey Pricing pricing method and assuming you have *uploaded your Journey Pricing CSV, your schedule is now ready for selling!

Finally, your schedule will not be found in the trip results if there is no price in the Fare Table. If you are going to use _Point to Point pricing method, you can set pricing right here in the Fare table section.

In the case of Journey pricing, you need to make sure that there are rules that apply to what Busbud has access to. Example: Price rules restricted by fare type, channels or shift zone.

It is important to always take into consideration if your current pricing applies to Busbud. The same should be consider for future price modifications.

Loyalty can only be used with products that use Journey Pricing. Accummulating and redeeming points are set in columns of the Journey Pricing csv. Click to learn about Loyalty accumutating and redeeming points

Loyalty can only be used with products that use Journey Pricing. Accummulating and redeeming points are set in columns of the Journey Pricing csv. Click to learn about Loyalty accumutating and redeeming points

La fidelidad solo se puede utilizar con productos que utilicen Journey Pricing. La acumulación y el canje de puntos se establecen en las columnas del csv Journey Pricing. Haga clic para obtener más información sobre Acumulación y canje de puntos de fidelidad

La fidelidad solo se puede utilizar con productos que utilicen Journey Pricing. La acumulación y el canje de puntos se establecen en las columnas del csv Journey Pricing. Haga clic para obtener más información sobre Acumulación y canje de puntos de fidelidad

Loyalty can only be used with products that use Journey Pricing or Market Pricing. Accummulating and redeeming points are set in columns of the Journey Pricing csv. Click to learn about Loyalty accumutating and redeeming points

Loyalty can only be used with products that use Journey Pricing or Market Pricing. Accummulating and redeeming points are set in columns of the Journey Pricing csv. Click to learn about Loyalty accumutating and redeeming points

You can only enable open return when the pricing schema is one of Journey or Market pricing

Remove pricing from all fare tables that include the station you want to remove.

• To configure multicurrency pricing using Journey Pricing, click Here.

• To configure multicurrency pricing using Journey Pricing, click Here.

If your route is linked to a product that has Journey Pricing, you will see a section for Proration Table.

If your route is linked to a product that has Journey Pricing, you will see a section for Proration Table.

• Para configurar precios en múltiples monedas usando Journey Pricing, haga clic en Aquí.

• Para configurar precios en múltiples monedas usando Journey Pricing, haga clic en Aquí.

Si está utilizando el método de fijación de precios de Journey Pricing y supone que ha *subido su archivo CSV de Journey Pricing, ¡su programación ya está lista para venderse!

Si está utilizando el método de fijación de precios de Journey Pricing y supone que ha *subido su archivo CSV de Journey Pricing, ¡su programación ya está lista para venderse!

For Journey pricing:

For Market pricing:

La fidelidad solo se puede utilizar con productos que utilicen precios de viaje o precios de mercado. La acumulación y el canje de puntos se establecen en las columnas del csv Journey Pricing. Haga clic para obtener más información sobre Acumulación y canje de puntos de fidelidad

La fidelidad solo se puede utilizar con productos que utilicen precios de viaje o precios de mercado. La acumulación y el canje de puntos se establecen en las columnas del csv Journey Pricing. Haga clic para obtener más información sobre Acumulación y canje de puntos de fidelidad

• Our promo code setup is designed to respect the lowest hierarchy rule (i.e. Product -> Type -> Route) first within the list of constraints. For example: if a customer configures the promo to be of type 'Roundtrip', but also to apply for a specific route, then the discount will only apply to the leg of the journey that is within the designated route (when choosing a round-trip transaction) rather than applying to both legs. This is because the return leg is part of a different route, and therefore a new promo rule needs to be created to discount both legs.

• Promos are recalculated for ticket changes. This means that when doing a ticket change, the current price will be pulled, and the promo will be applied over this new price. (Keep this in mind for Dynamic Pricing).

Zone: Enter any free text name, number or identified to group stations by zone. This value can be used in the journey pricing schema.

To remove a station from trips searches you need to make sure is not used in any pricing schema.

The fares mapping allows you to select the fares that will be equivalent between the consumer and the provider when both accounts use journey pricing. It is possible to select more than one.

The fares mapping allows you to select the fares that will be equivalent between the consumer and the provider when both accounts use journey pricing. It is possible to select more than one.

When changing the prices and calculating taxes backwards, the account’s rounding policy is applied and this can cause some rounding errors in connecting trips. This rounding errors will be fixed in the last ticket of each journey. Any transaction fees will be added to to the price after taxes.

El proceso para agregar registros JP está documentado en este enlace: Journey Pricing Create

El proceso para agregar registros JP está documentado en este enlace: Journey Pricing Create