Food Delivery Software in Morocco — Launch Your Platform
Morocco is a cash-heavy, mobile-first delivery market concentrated in Casablanca, Rabat and Marrakech. The winners are not the platforms with the most features; they are the ones that reconcile cash and get addresses right.
The market shape
Casablanca is the largest market, followed by Rabat and Marrakech. Glovo has strong coverage in the main cities; secondary cities and peripheral neighbourhoods are served unevenly. Start with one dense district and a restaurant mix that already does takeaway.
Cash and payments
Cash on delivery is a large share of orders, so rider cash limits and end-of-shift reconciliation are first-class features. Cards are growing, and CMI or Payzone are the local gateway conversations; neither is in the standard list, so they are paid custom integrations. Confirm merchant-account requirements and settlement timing before promising card payments.
Arabic, French and addresses
Arabic and French are both used commercially. Foodomaa includes Arabic and French language files, but RTL layout, emails and invoices need native review. Addresses are often landmark-based; add a phone confirmation step and a rider note field so the last 200 metres do not fail.
Rider economics
Fuel, scooter maintenance and dense traffic decide the cost per delivery. A 3–4 km radius around a dense district is more realistic than a city-wide map. Plan rider shifts around lunch, dinner and Ramadan.
Launch plan
- Pick one Casablanca or Rabat district with 25–40 takeaway restaurants.
- Set cash limits, delivery fees and a clear refund policy.
- Test Arabic/French checkout, one failed payment and one cash reconciliation.
- Soft-launch with local WhatsApp groups and restaurant social pages.
Costs and compliance
The licence is $299 once, plus a VPS, gateway fees, SMS, maps and custom work. No monthly licence fee and no commission to Foodomaa. Confirm food-safety (ONSSA), local permits and CNDP data-protection obligations with local counsel.
Morocco questions
Is CMI or Payzone included?
No. Both are paid custom integrations. We confirm scope after reviewing the merchant account and API documentation.
Is Arabic supported?
Arabic language files are included, but RTL design and a native review are still required for the storefront, apps and invoices.
Is cash on delivery supported?
Yes, with per-rider cash limits and end-of-shift reconciliation.
Which city should I start in?
One dense Casablanca or Rabat district, or Marrakech if tourism-driven demand matches your restaurant mix.
Is ONSSA or CNDP compliance included?
No. The software can support the processes, but food-safety and data-protection compliance depend on your registrations and contracts. Confirm with local counsel.
What to configure first
- Cash limits: set a per-rider limit and a handover process before the first order.
- Arabic/French: test RTL layout, emails and invoices, not just the storefront strings.
- Zones: one dense district first; a wide map makes cash reconciliation and ETA worse.
- Ramadan: configure special hours and pre-order slots before the season, not during it.
- CMI/Payzone: treat card integration as a paid project with a merchant-account dependency.
Common launch mistakes
- Launching Casablanca-wide instead of one district with 25–40 restaurants.
- Using landmark-only addresses without a phone confirmation step.
- Letting riders carry a full day's cash instead of reconciling per shift.
- Planning Ramadan after the menu and rider shifts are already live.
- Assuming card payments will replace cash on day one.
A 90-day sequence
- Days 1–20: choose the district, sign restaurants and prepare Arabic/French copy.
- Days 21–40: configure cash limits, zones, fees and the card integration.
- Days 41–60: recruit riders, test 30 orders and run a cash reconciliation drill.
- Days 61–75: soft-launch with local WhatsApp groups and restaurant social pages.
- Days 76–90: add a second district only if the first is stable and cash is under control.
Who this fits
- A Casablanca or Rabat marketplace with 25–40 restaurants and a controlled cash process.
- A restaurant group that wants Arabic/French ordering and its own customer list.
- A grocery or pharmacy adding scheduled local delivery.
- An operator preparing for Ramadan demand with pre-orders and adjusted rider shifts.
What to ask before buying
- What is the CMI/Payzone scope, and who owns the merchant account?
- How will cash limits and handover be enforced per rider?
- Who reviews Arabic RTL and French copy before launch?
- Which ONSSA, municipal and CNDP obligations apply?
- How will Ramadan hours and pre-order slots be configured?
Three ways to start
| Model | Best for | What changes |
|---|---|---|
| Single-brand restaurant | A restaurant with repeat customers | One menu, one district, cash and card |
| District marketplace | An operator who can sign 25–40 restaurants | Commission, vendor onboarding, shared riders |
| Grocery or pharmacy | A local retailer adding scheduled delivery | Catalogue, pack sizes, slots and cash limits |
Start with the model that matches the supply you can sign in 30 days, not the model that sounds largest in a pitch.