Route optimization for Riyadh — Wasel addressing, prayer-time pauses, and ring-road logistics, handled.
Riyadh is the GCC's largest delivery market by parcel volume but its grid-and-ring topology — five concentric ring roads connected by spoke arterials — punishes naive route ordering more than almost any other GCC city. Add five mandatory daily prayer pauses, a Saudi Post Wasel address standard most international tools don't recognize, and a regulator (the Public Transport Authority, PTA) that is actively tightening commercial-vehicle rules in 2025–2026, and a generic US route planner will routinely cost a Riyadh fleet 18–25% more kilometres than a Riyadh-aware one.
Riyadh's road network is dominated by five ring roads — King Fahd, King Salman, Eastern Ring, Southern Ring, and the Second Ring — connected by major arterials like Olaya Street, Tahlia, King Abdullah, and Northern Ring. The pattern means almost every cross-city route has at least two viable paths (inner ring vs outer ring), and the difference between a good and bad ordering is often 8–15 km. SortDrops uses live road distances from OpenStreetMap, so the optimizer evaluates both routings and picks the actual shortest, not a heuristic guess.
Riyadh enforces five mandatory prayer pauses per day during which most retail and many commercial premises briefly close. Dhuhr (around midday), Asr (mid-afternoon), and Maghrib (sunset) overlap with peak delivery windows. A driver who arrives at a stop at the start of a 25-minute prayer pause is stuck or has to re-circle. SortDrops does not natively schedule around prayer times today, but our Pro tier per-stop service-time field lets dispatchers add a 25-minute buffer to any stop expected to land mid-prayer, and the optimizer respects that when ordering.
Third: distances in Riyadh are long. The official metro area spans over 1,900 km², and a single 'cross-city' run from Diriyah in the northwest to King Khalid International Airport in the northeast is 45–55 km one way. Optimizing 15 stops across an area that big with a poor solver leaves easy wins on the table — typically 20–30% of total kilometres.
A common Riyadh same-day courier loop: depot in Sulaymaniyah → Olaya office stops (3–4) → King Abdullah Road retail (2 stops) → Hittin residential (3 stops) → King Khalid Airport area (1–2 cargo) → return via Northern Ring. Unoptimized, this path will typically cross the Second Ring three times and clock 78–84 km. Through SortDrops the same stops chain: depot → Olaya → KAR → King Khalid → Hittin → home, crossing the Second Ring once and clocking 58–63 km.
For grocery delivery into the dense Al Yasmin / Al Malqa / Hittin corridor in north Riyadh, the constraint is the compound. Many of those neighbourhoods are private compounds with controlled gates, and the geocoded "address" lands at the compound gate rather than the villa. SortDrops respects whatever gate-level pin you geocode — we will not "improve" an address by moving it 400 metres into the compound, because the driver still has to physically enter at the gate.
Saudi Post's Wasel system is the national addressing standard. SortDrops' geocoder accepts Wasel-format addresses (e.g., 'Building 6829, Street King Abdullah, Al Olaya District, 12235, Riyadh') and resolves them to the building gate rather than the plot centre. For dispatchers paste a Wasel string verbatim and we will pin it correctly. If you have an internal CRM that stores both Wasel and a free-text fallback, paste Wasel — it's about 2–3 minutes more accurate per stop on average.
Arabic and English are both first-class. Drivers can navigate the SortDrops driver-link in Arabic (RTL layout fully supported), and dispatchers can paste mixed Arabic/English address strings. The Public Transport Authority of Saudi Arabia (PTA) is the relevant regulator for commercial fleet operation; PTA permits are a separate workflow from route optimization but our dispatch session log produces a CSV record per stop suitable for PTA-style audit trails.
Yes. The geocoder reads Wasel-format strings (4-digit building, district, postcode) and resolves them to the registered building gate. This is consistently more precise than free-text address lookup in Riyadh. If your CRM stores both, prefer Wasel.
Not natively today. The workaround we recommend: dispatchers add a 25-minute service-time buffer (Pro feature) to any stop expected to land mid-prayer. The optimizer respects that buffer when ordering and the driver-link respects it on arrival ETAs. Native prayer-time-aware scheduling is on our 2026 roadmap.
Yes. The driver-link UI renders RTL when Arabic is the chosen language, and the dispatcher app accepts Arabic-script address input. Auto-detection is by character set, not by user toggle.
Mrsool and HungerStation are end-customer marketplaces with proprietary routing built into their merchant operations. SortDrops is a self-service route optimizer for fleets that don't want to rebuild a marketplace engine internally — couriers, pharmacies, B2B parts distribution, etc. We're complementary, not competitive.