New MENA market? Why your address database starts at zero.
An in-house coordinate database is a record of where a carrier has already delivered. Cross a border into a market with a different addressing system and that record stops predicting anything.
Two years of delivery history. Two ways the next market can go.
A carrier operating in Saudi Arabia has two years of delivery history, a coordinate database built from it, and a failed-delivery rate it is comfortable with across Riyadh and Jeddah. The decision is made to expand into Egypt. On the first day in Cairo, that database is inert — not degraded, not partially useful, but empty for the addresses it is being asked to resolve.
The reason is structural rather than technical. In-house coordinate databases are built from delivery history in markets already served. They do not transfer across MENA because Saudi Arabia and Egypt describe location in structurally different ways — and no volume of KSA data covers an informal Cairo neighbourhood.
A KSA address database is a KSA-only asset
Each delivery attempt adds a data point. Over time an operator accumulates coordinates for the addresses its customers actually use: apartment compounds in Riyadh, residential zones in Jeddah's northern districts, industrial parks in Dammam. That database is valuable. It is also entirely local.
Saudi Arabia's National Address system — administered by Saudi Post and widely referred to as Wasel — gives every registered building a structured record: building number, street, district, city, postal code, plus a four-letter, four-digit short address. Informal place names still dominate delivery culture, but a formal grid exists underneath them.
Egypt operates on a different logic. Formal addresses exist in older city cores, while a large share of the Greater Cairo metro is made up of informal areas — estimates of the share of residents living in them range from roughly 40% to about two thirds, depending on the definition and source used. In those zones, location is described by landmarks, district names and directional guidance. A geocoder populated with KSA delivery history produces no useful output for that input.
Every new MENA market entry starts at zero
Market entry follows the same arc for every operator running an in-house database. Coverage in the new market begins at zero. Early deliveries fail or require intervention — a driver call, a customer callback, a human-assisted routing decision. As those attempts are processed, successful coordinates accumulate, and after several months of volume, coverage builds in the areas served most frequently.
The problem is the ramp. Through that period the operator pays the full cost of cold-start failures while competitors with pre-built coverage do not.
Coverage that has to be earned is coverage you don't have yet.
The ramp carries strategic cost because the regional market is not standing still. MENA e-commerce is growing at double digits, and logistics capacity in Saudi Arabia is being built out to match — which means a new entrant's first quarter is measured against operators that already deliver reliably.
What day-one coverage actually requires
The alternative to the cold-start model is address intelligence built from structured data pipelines rather than from delivery history. Blassa's coverage for KSA and Egypt is mapped ahead of an operator's first shipment in either market, which changes what is possible on day one.
The difference is not operational sophistication. It is whether the coverage model requires an operator to have already been somewhere before it can reliably deliver there.
Expansion is the moment in-house databases break
Operators who have built in-house databases know their strengths: high accuracy in mature markets, calibration to a specific fleet and routing logic, low marginal cost once coverage is established. None of that is in question.
In-house databases record where a fleet has been. Expansion asks where it can go.
The failure mode is expansion-specific. In MENA, where Saudi Arabia and Egypt describe location through incompatible systems, that gap is not a minor operational nuance. It is the difference between a market entry that delivers reliably from week one and one that spends its first quarter recovering from its own cold start.
It geocodes well in Saudi Arabia's formal address zones. In dense Egyptian areas where formal addressing is incomplete or absent, coverage is materially weaker. A provider that cannot resolve a meaningful share of a new market's addresses does not remove the cold-start problem — it trades one gap for another.
It depends on delivery volume and geographic density. Operators typically need several months of consistent volume in a specific area before an in-house database reaches useful coverage. Where informal settlements are dense, the timeline extends, because drivers work from verbal directions that never become stored coordinates.
Yes. Blassa's address database covers Saudi Arabia and Egypt, with structured coordinate data available via API before the first delivery in either market.
Geocoding APIs convert a structured written address into coordinates. Blassa's API first parses unstructured address text — informal descriptions, mixed Arabic and English, landmark references — into a structured address, then geocodes it. That parsing step is where a MENA-specific database outperforms a generic geocoder.
Expanding into a new MENA market without pre-built address coverage means paying for every address the database has not seen yet. Most operators do not model that cost when planning entry. They pay it in the first quarter instead.