Zones
The order
One food order, from a restaurant to a customer.
The batch
One batch of overseas parcels, received at your hub and delivered outward. Routing is hub to zone only.
Enter the batch per governorate. Failed attempts bill at a part of the drop fee; returns bill the reverse-logistics rate.
What it costs, and who pays
Illustrative — not a quotationWhat the platform is billed
Illustrative — not a quotation| Billing event | Qty | Unit | Amount |
|---|
Rates and caps — change any of these
Placeholder figures, kept in this browser only. Nothing you type here is sent anywhere, and clearing your browser data resets it.
Statutory caps (as supplied)
Food delivery costs
B2B billing
Vehicles
The request and result as JSON
The request follows the schema in the architecture document, so the same payload would work against a server later. Paste one back in to reload a scenario.
What this model does not know
- The caps are the figures given to us for Ministerial Decision 109/2026. We have not verified them against an official source, which is why you can change them.
- The rates are illustrative placeholders chosen to make the model readable — they are not Makinzi's commercial rate card, and no output here is a quotation.
- Distances run between the built-up centre of each governorate, not between two addresses, so a single order can differ by several kilometres.
- Zone boundaries are simplified to about 150 metres, so a point close to a border can fall in the neighbouring governorate.
- Nothing is stored or sent. The rate card lives in this browser; only the two send buttons transmit anything, and only when you press one.
- The B2B mode prices hub-to-zone work only. Point-to-point merchant routing is deliberately not offered there, and the food-delivery caps are not applied to it.
- Real pricing depends on volume, service levels, exclusivity, fuel and contract length. Talk to us for a figure you can plan against.