Delivery software that ships with a fixed city list fails the moment you add a second country — or even a second coverage model inside one country. Networks across Morocco, Algeria, Tunisia, Egypt, KSA, UAE and beyond need to upload their own cities and zones and still run one platform.
Speedliv is multi-country by design: clients upload city/zone lists for every country they operate in. Maghreb & MENA are the go-to-market focus, not a technical ceiling. Demo environments may show Morocco (MAD) as sample data only.
Why vendor-locked cities break networks
- Your partner already priced 180 communes your vendor never heard of
- Spelling variants (Arabic / French / English) break matching
- Franchise boundaries ≠ administrative boundaries
- Cross-border expansion means a second tariff and telephony setup — not a second product
- Confirmation teams and drivers need the same zone names finance uses for settlements
What “city upload” must include
- Bulk import of cities / areas / zones per country
- Mapping to tariffs and partner rules
- Use in confirmation (out of zone), hub routing, and driver assignment
- Updates without rebuilding the whole tenant
- Clear ownership: who may edit the geographic master data
Zones are operational objects, not a pretty map widget.
Recommended rollout
- Export your current coverage from Excel / partner contracts
- Normalize names (pick a canonical spelling per language you operate)
- Upload country A, validate confirmation + tariff + driver assignment
- Upload country B on the same tenant
- Configure per-country telephony for confirmation if you use it
- Train agents on out-of-zone and reassign paths
Checklist
- Per-country city/zone upload
- Tariffs by zone / partner
- Out-of-zone status in confirmation
- Driver / hub assignment uses the same lists
- Settlements can aggregate by zone
- Second country does not require a second product
- COD optional regardless of country
- Sample demo currency not mistaken for product limit
Product truth (Speedliv)
- Shipping ops platform by Storeino (white-label)
- Parcels, slips, finance settlements, call-center confirmation, inventory, driver app
- Multi-country city/zone upload
- In-app languages include EN, AR, FR (and ZH)
- COD optional
FAQ
Is Speedliv Morocco-only?
No. Morocco may appear in demo samples. Upload your countries’ cities and zones.
Do we need separate instances per country?
The product is built so multi-country runs on one platform — evaluate tenancy with sales for your governance needs.
How does this relate to Storeino?
Speedliv is made by Storeino for shipping / courier companies, confirmation centers, and warehouse / 3PL teams.
CTA
Book a meeting on speedliv.com with your zone files ready. Demo: https://demo.speedliv.com/en/auth/login · WhatsApp +212 661-962932
Data model tips for bilingual city lists
Many Maghreb networks need Arabic and French names for the same zone. Practical approach:
- Canonical code per zone (stable ID)
- Display labels per language
- Import mapping table from legacy spellings
- Forbid free-text city on confirmed parcels when a zone match exists
Confirmation “out of zone” must reference the same IDs tariffs use.
Tariffs and partners across borders
Multi-country is not only geography:
- Currency per country
- Partner share rules
- Tax display (keep statutory tools in accounting — do not invent tax engine claims)
- Telephony and SMS sender behavior per country
Speedliv’s positioning: one shipping platform with uploadable cities/zones and per-country operational settings (including confirmation telephony configuration).
Governance
Decide:
- Who approves new cities
- How often lists sync from partners
- How retirees/obsolete zones are deactivated (not deleted if history exists)
Expansion playbook (example)
- Stabilize country A with clean zones + settlements
- Pilot country B with one partner and one confirmation team
- Compare confirmation rate and settlement close time before scaling
- Only then open merchant acquisition hard in country B
Extended FAQ
Can we start with one country?
Yes. Multi-country readiness means you *can* upload the next list without migrating platforms.
What about Gulf expansion from Maghreb HQ?
Same pattern: upload cities/zones, configure teams and telephony, keep parcel truth unified.
Is MENA a hard-coded limit?
No. GTM focus ≠ technical lock. Evaluate your countries with sales using your zone files.
City file template (practical columns)
Suggested columns for upload workshops:
- country_code
- zone_code (stable)
- name_fr / name_ar / name_en (as needed)
- parent_city (optional)
- active (true/false)
- default_partner (optional)
- notes
Validate duplicates before import. Deactivate rather than delete zones with history.
Telephony and SMS per country
Confirmation teams dialing Algeria from a Morocco-only trunk waste attempts. Configure telephony by country in the shipping/confirmation platform settings. Keep carrier contracts explicit.
Sample executive one-pager
Share monthly:
- Countries live
- Zones active vs inactive
- Confirmation rate by country
- Settlement close time by country
- Top out-of-zone reasons
This keeps multi-country expansion honest instead of vanity map screenshots.
Naming conflicts across borders
“Saint-Louis”, “New Cairo”, or shared commune names need country_code in every join. Never unique-key on name alone.
Training kit
- 1-pager zone search for agents
- Driver app zone display examples
- Finance settlement filter by country
- Out-of-zone playbook with reassign partners
CTA reminder
Bring zone files to a meeting on speedliv.com. Demo https://demo.speedliv.com/en/auth/login · WhatsApp +212 661-962932.
Half-day upload workshop
Morning: clean file + stable codes. Afternoon: upload country A, test out-of-zone in confirmation, test driver assignment, test settlement filter. Close: rejected spellings to map.
Vanity map risk
A colored map without settlements and confirmation tied to the same zones is theater. Demand zone→tariff→out-of-zone→settlement in the demo.
