MXBSDOCS
App →

Standard Pricing Configs

A comprehensive reference for creating and managing commercial pricing configurations that drive bid calculations and instant quotes.

Pricing configs are reusable pricing templates that pre-fill bid forms and power instant quote calculations. Instead of entering rates from scratch on every bid, you build a config once and the system applies it automatically.

You can have multiple configs per vehicle type — for example, one for corporate accounts, one for school district rates, and one for peak season charter work. Exactly one config per vehicle type can be marked as Primary; that config is used by default whenever the system generates an instant quote for that vehicle type.

Create a primary config for every vehicle type you operate. Without a primary config, the system cannot generate instant quotes for that vehicle type, and customers browsing your profile will not see real-time pricing.


Section A — Basics

These fields establish the identity and base rules of the config.

FieldDescription
NameDescriptive label for internal reference. Examples: Full Coach Standard 2024, School District Rate, Corporate Discounted.
Vehicle TypeThe vehicle type this config applies to. One config per vehicle type can be primary.
PrimaryToggle — designates this config as the default for instant quotes for this vehicle type. Only one config per vehicle type can be primary at a time; enabling this will automatically unset any existing primary.
CurrencyUSD or CAD. All values in this config are entered and displayed in the selected currency.
UnitKM or MILE. Distance-based rates (deadhead, mileage tiers) use this unit.
Daily RateMinimum daily charge regardless of actual mileage or hours driven. Applies as a floor even when mileage and hourly charges would otherwise be lower.
Internal NotesFree-text notes visible only to you and your team. Not shown to trip owners or included in bid documents.

Pricing configs are stored internally in USD per km regardless of your display preference. If you later change your currency or unit preference, existing config values update their displayed amounts accordingly — no manual re-entry required.


Section B — Deadhead

Deadhead covers the cost of driving your vehicle from your depot to the trip pickup point (empty, unbillable travel).

FieldDescription
Deadhead RateCost per km (or mile) for empty travel from your depot to the pickup location.
Free Deadhead AllowanceNumber of km included without charge. For example, setting 25 means the first 25 km of deadhead are free and only the distance beyond 25 km is billed.
Deadhead CapMaximum deadhead distance you will charge for. Deadhead beyond this cap is absorbed by you, reducing your exposure on very long depot-to-pickup runs.

Section C — Add-ons

Add-ons are optional charges layered on top of the base rates.

FieldDescription
Fuel SurchargeEnable toggle + type (PERCENT of base fare or PER_DISTANCE) + value. Applied automatically when enabled.
Driver OvertimeEnable toggle + threshold hours (overtime kicks in after N trip hours) + hourly overtime rate.
Overnight Stay RateFlat amount charged per overnight stay when the driver must remain away from the depot.
Gratuity PercentageOptional gratuity percentage added to the subtotal. Displayed as a line item on the bid.
Toll EstimatorEnable to have the system auto-estimate toll costs based on the trip route. When disabled, tolls appear as a manual line item.
Additional Driver ChargeFlat fee added automatically for trips that require a second driver (typically long-distance or extended-duration trips).

Section D — Rates & Tiers

Tiered Mileage

Distance-based rate tiers let you charge different per-km (or per-mile) rates depending on how far the trip goes. Longer trips typically earn a lower per-unit rate.

Example:

FromToRate
0 km100 km$3.50 / km
100 km300 km$3.00 / km
300 km— (open-ended)$2.50 / km

Rules:

  • The last tier is always open-ended (no upper bound).
  • Tiers must be contiguous with no gaps between them. A gap between tiers will produce a validation error on save.

Hourly Tiers

Time-based rate tiers work the same way as mileage tiers but apply to trip duration.

Example:

FromToRate
0 hr4 hr$180 / hr
4 hr8 hr$160 / hr
8 hr— (open-ended)$140 / hr

Trip Type Adjustments

FieldDescription
One-Way AdjustmentPercentage markup added to one-way trips. Compensates for the empty return drive to your depot. Example: 15%.
Round-Trip AdjustmentPercentage discount applied to round trips. Example: -5%.
Round-Trip PreferredFlag that marks your profile as preferring round-trip bookings. Visible to trip owners browsing operators.

Peak Season Multipliers

Date-range-based percentage boosts are configured separately in the Peak Season section of each pricing config. Multipliers apply automatically to any bid submitted for a trip departing within the defined window.

See Peak Season & Multipliers for full configuration details.


Custom Add-ons

Beyond the built-in add-ons, you can define arbitrary charges with:

  • Name — label shown on the bid (e.g., Airport Meet & Greet, ADA Ramp Fee)
  • Amount type — flat dollar amount, percentage of subtotal, or per-distance charge
  • Taxable — toggle whether this add-on is included in the taxable base

Managing Configs

·

Create a new config

Navigate to Fleet → Pricing tab → Add Config (route: /bus-operator/fleet?tab=pricing), or go directly to /bus-operator/fleet/pricing/new. Fill in all sections, then click Publish price list to make it active immediately, or Save draft to save without activating.

·

Set as primary

From the pricing config list, click Set Primary on a config. The system automatically unsets any existing primary for that vehicle type. Only active configs can be set as primary.

·

Deactivate a config

Toggle the active status to inactive. Inactive configs are not used for instant quotes but remain visible in the list.

·

Delete a config

Hard delete from the config list. Blocked if the config is currently marked as primary — set a different primary first. Existing bids that referenced this config are unaffected; bid totals are captured at submission time.