Skip to content

Rate card settings

Per-customer global-card fallback, plus tenant-wide pricing defaults — the default cubic factor and default oversize pallet constraints.

Rate Card Settings groups three pricing controls under Settings → Rate Card Settings:

  1. the per-customer global fallback switch,
  2. the tenant default cubic factor, and
  3. the tenant default oversize constraints.

When the engine can’t find a matching assigned card for a lane, this setting decides what happens:

SettingBehaviour
ONThe booking is priced off a global rate card.
OFFNo price — the quote returns “no rate found”.

Turn it OFF for customers who must only ever be priced on their own negotiated cards (so a missing lane surfaces as an error rather than silently using a general rate). Turn it ON for customers where a sensible default rate is better than no quote. For where this toggle sits in the pricing order, see Rates hierarchy.

The Assigned cards count shows how many rate cards each customer has. Fallback only comes into play when a requested lane isn’t covered by those cards — a well-covered customer rarely hits it.

For rolling a policy out across many customers:

  1. Use the search box to filter the list.
  2. Tick the customers you want, then Set selected ON/OFF.
  3. Or use Set ALL ON/OFF to change every customer at once.

The tenant-wide cubic factor (kg/m³) converts volume into chargeable weight (m³ × factor = kg). It is the middle link in the pricing engine’s resolution chain:

PrioritySource
1The rate card’s own cubic-factor override
2This tenant default
3No factor — charge on the actual (dead) weight only

Industry reference points: road general freight 333, express 250, air freight 167.

The tenant maximum “standard” pallet dimensions — Length / Width / Height in mm plus Weight in kg. Current values: 1200 × 1200 × 1500 mm / 575 kg.

  • An item exceeding any limit is treated as oversize and repriced on chargeable weight (see the oversize strategies on Rate cards & pricing).
  • A rate card can override each field individually.
  • The booking widget uses these defaults too.
  • A field left blank falls back to the per-pallet-type limits.