Flexible, Fixed and Box pricing

Admin portalRates & financeUpdated today

The rule type decides how the price is built. Choose Flexible, Fixed or Box in the Rule card, then fill in the Price card.

Before you start
  • Your role has the Manage package rules permission.
  • Price fields take numbers only. The unit (SAR, kg, km) sits inside the box.
1

Flexible: a base fare plus extras

A base fare covers a base weight, and every extra kg adds a price. Use it when price should grow with weight or distance.

Rates › Price · FlexibleSample screen
Price
18
3
5
3
2
  1. Base fare. Required. The price of an order up to the base weight, and up to the base distance if you set one.
  2. Base weight. Required, above 0. The weight the base fare includes.
  3. Base distance. Optional. The distance the base fare includes, measured by road from the pickup pin to the drop pin. Without usable pins the base fare applies, and the order is flagged “Bad address”.
  4. Price per extra kg. Required. Added for each kg above the base weight. By default it is counted in proportion, so 0.5 kg extra costs half the price. In Settings you can count every started kg instead.
  5. Price per extra km. Added for each started km above the base distance. Required when you set a base distance.

Example: a base fare of SAR 18 for 3 kg, and SAR 3 for each extra kg. A 5 kg order costs 18 + (2 × 3) = SAR 24.

2

Fixed: price bands

Each band has its own price. Use it when you publish a price list by weight or by distance.

Rates › Price · FixedSample screen
Price
1 Band by2 From3 To4 Price
Weight ▾0 kg10 kgSAR 28✕
Weight ▾10 kg20 kgSAR 40✕
Weight ▾20 kg30 kgSAR 55✕
5+ Weight band + Distance band
  1. Band by. Each row is a Weight band or a Distance band. Changing it refills From.
  2. From. Where the band starts. The first band of a kind starts at 0. Each next band starts where the previous one ends, and Fleetics fills it in for you.
  3. To. Where the band ends. The To value belongs to this band: 10 kg is in 0–10, and 10.01 kg is in 10–20.
  4. Price. The price for orders that fall in this band.
  5. + Weight band and + Distance band add a row of that kind. When a rule has both kinds, the price is the weight band plus the distance band.
3

Choose what happens above the last band

Decide, for each kind of band, what an order beyond the last band costs.

Rates › Price · FixedSample screen
Price
Rule does not apply+ price per kg
3
Rule does not apply+ price per km
  1. Above the last weight band. You choose for each kind. Rule does not apply: a heavier order needs another matching rule, or gets an error. + price per kg: each started kg above the last band is added, and the amount is required.
  2. Above the last distance band. Works the same way, in kilometres.
4

Box: a price by the number of boxes

Box rules price an order by how many boxes it has. They are used for multi-box orders billed by box count, and weight is ignored.

Rates › Price · BoxSample screen
Price
20
1
2
8
  1. Base fare. Required. The price for the boxes included. A Box rule ignores weight.
  2. Boxes included. Required, at least 1. How many boxes the base fare covers.
  3. Box step. Required, at least 1. Extra boxes are charged in steps of this many boxes: 2 means every 2 extra boxes.
  4. Price per box step. Required. Added for each step of extra boxes.

Example: SAR 20 covers 1 box, and every step of 2 extra boxes adds SAR 8. An order of 3 boxes has 2 extra boxes, which is one step, so it costs 20 + 8 = SAR 28.

Screens are simplified drawings with sample data. Your portal may look a little different, but the names and steps are the same.

Common questions

A band error says “Starts where the previous weight band ends”.

Each band of a kind must start where the previous one ends, with no gap. Fleetics fills the From value in for you, so only edit it if you have to.

Why does the first band have to start at 0?

So that every order has a band. “The first weight band starts at 0 kg” appears if it does not.

What does “Use volume weight” do?

On, the higher of the actual and the volume weight is charged. Off, only the actual weight counts. It shows on Flexible and Fixed rules.

What if an order has no usable pin?

A rule with a distance cannot measure it, so the base price applies and the order is flagged “Bad address”. The order is still created.

Can I price by weight and distance together?

Yes, with a Fixed rule that has both weight bands and distance bands. The price is the weight band plus the distance band.

Related guides

Was this helpful?