How an order gets its rule and its price
Understand why an order was priced the way it was: which rule was chosen, how the weight was counted and what the price is made of.
- Nothing to set up. This guide explains what Fleetics does with the rules you made.
See which rule an order gets
On Create Order the matching rules are listed, best first, and the first one is chosen for you.
Summary
- The best match is chosen for you. Rules that name the merchant come first, then the most specific rule (zone, then city, then same or other city, then box type and client type), then the cheapest.
- The other matching rules follow in the same order. Changing the rule needs the “Change package rule on order” permission.
Know when a rule qualifies
A rule is a candidate for an order only when all of these are true.
- The rule is Active.
- Its shipment type is the order’s: Forward or Reverse.
- The order’s service is in its Service types.
- Its client type fits the merchant.
- Its conditions match the order.
See how the charged weight is counted
The charged weight is the higher of the actual weight and the volume weight, rounded up by your rounding step. With several boxes it is worked out for each box, then added up. Without dimensions, the actual weight is used.
| Step | Example |
|---|---|
| Actual weight | 5.0 kg |
| Volume weight (40 × 30 × 30 cm ÷ 5000) | 7.2 kg |
| The higher of the two | 7.2 kg |
| Rounded up to 0.5 kg | 7.5 kg charged |
See what the price is made of
The price is a set of lines, and VAT is worked out on each line.
- Delivery, then Extra weight, Extra distance or Extra boxes, depending on the rule type.
- Your additional charges that apply to every order, and the ones picked on the order.
- Charges that the recipient bears are added together into the COD to collect.
- The merchant’s COD fee is not part of Rates. It is set on each merchant.
Know what happens when no rule matches
In the portal, Create Order shows an error. Orders from the API, a store or an import wait in Order Issues.
| Type | Merchant · source | Reference | 1 Reason |
|---|---|---|---|
| API order rejected | Al Noor Electronics · API | AN-10077 | No price rule for Riyadh → Dammam, Next Day, 12 kg |
- No price rule. The reason names the route, the service and the weight. Create or widen a package rule that covers it, then retry the order from Order Issues.
API and import orders send a package rule ID, or a service ID that uses the merchant’s default rule. If the rule does not fit the order, the message reads “Package rule PR-xxx doesn’t apply to this order”. Store orders get the first matching rule for the service of their store tile, and you can change it on the order.
Screens are simplified drawings with sample data. Your portal may look a little different, but the names and steps are the same.
Common questions
Why was a more expensive rule chosen?
Rules that name the merchant come first, then the most specific rule, and only then the cheapest. A rule for one zone beats a rule for a whole city.
Who can change the rule on an order?
Users with the “Change package rule on order” permission.
Does editing a rule change old orders?
No. Each order keeps its price, the rule used and the conditions it matched.
What does “Bad address” mean?
The order has a valid city but no usable pin. Distance cannot be measured, so the base price applies.