Postcodes are not required in Syria, according to the Universal Postal Union. Here is how to build the address form around a map pin and a description, store a Plus Code that works offline, and choose map services after reading what their terms actually say.
Do not make a postcode field required for Syrian addresses. The Universal Postal Union lists Syria among the countries that do not require postal codes, and we found no official Syrian document from 2025 or 2026 that sets up a national postcode or addressing scheme. Ask instead for the governorate and city, the area, a street or landmark description, the building and floor, a mobile number, and a pin the user places on a map.
Save three things for each address: the pin as coordinates, a Plus Code the phone computes from it with no network and no API key, and the text exactly as the user typed it. For the map itself, read each vendor's terms before you build. Google Maps Platform lists Syria as a prohibited territory, several other vendors name no country and refer to export-control or embargo rules instead, and the free public OpenStreetMap servers come with strict usage limits.
We checked what the Universal Postal Union (UPU) publishes and the latest request from the Syrian postal operator. In short: there is no postcode to collect, and there is a phone number you should collect.
| Required? | Why | |
|---|---|---|
| Governorate and city | Yes | A pick list, not free text, so you can filter, report and route orders. |
| Area or neighbourhood | Yes | A pick list with a free-text fallback for areas you have not listed yet. |
| Street, or the nearest landmark | Yes | Free text, Arabic first. Let people describe the place the way they would describe it to a driver. |
| Building, floor, apartment | Recommended | Short separate fields. UPU's sample Syrian address puts them on the line right after the name. |
| Map pin | Yes, for deliveries and rides | The user places or confirms it; the app stores the coordinates and a Plus Code. |
| Mobile number | Yes | The courier calls when the description is not enough. See the postal operator's request above. |
| Postcode | No | Hide it for Syrian addresses, or keep it optional. |
| Notes for the driver | Optional | Gate colour, which entrance, call on arrival. |
Latitude and longitude, plus the accuracy the phone reported, the time, and whether the user dragged the pin by hand. Those extra fields tell you later which pins to trust.
Computed from the pin on the phone itself. It is short enough to read out on a call or paste into a chat, and it decodes back to the same spot without a network.
Street, landmark and building text exactly as typed, in Arabic or English. Put a normalised copy in its own column for search and never show that copy to the courier.
If a geocoding service filled any field, record which one and when. Some vendors limit what you may store, as the storage section below shows.
A full Plus Code is computed from the coordinates alone and converts back to a location offline, with no data tables and no online service. The algorithm is open source (Apache 2.0) and the project says it may be used without restriction, so there is no API key and no account to manage. This JavaScript function turns a pin into a code, and a code back into the centre of its cell:
// Plus Codes (Open Location Code) in plain JavaScript: no library, no network.
// encodePlusCode turns a GPS position into a full code such as "8G5RG864+FJ"; decodePlusCode
// turns a full code back into the centre of its cell. Works the same offline.
const ALPHABET = "23456789CFGHJMPQRVWX";
const LAT_UNITS = 8000 * 3125; // 1/25,000,000 of a degree, the finest grid step
const LNG_UNITS = 8000 * 1024; // 1/8,192,000 of a degree
function encodePlusCode(lat, lng, length = 10) {
if (length !== 10 && length !== 11) throw new Error("length must be 10 or 11");
if (!Number.isFinite(lat) || !Number.isFinite(lng)) throw new Error("not a position");
let y = Math.floor(Math.round((lat + 90) * LAT_UNITS * 1e6) / 1e6);
let x = Math.floor(Math.round((lng + 180) * LNG_UNITS * 1e6) / 1e6);
y = Math.min(Math.max(y, 0), 180 * LAT_UNITS - 1);
x = ((x % (360 * LNG_UNITS)) + 360 * LNG_UNITS) % (360 * LNG_UNITS);
let grid = "";
for (let i = 0; i < 5; i++) { // the 11th+ digits: a 4 x 5 grid inside the cell
grid = ALPHABET[(y % 5) * 4 + (x % 4)] + grid;
y = Math.floor(y / 5); x = Math.floor(x / 4);
}
let pairs = "";
for (let i = 0; i < 5; i++) { // the first 10 digits: latitude/longitude pairs in base 20
pairs = ALPHABET[y % 20] + ALPHABET[x % 20] + pairs;
y = Math.floor(y / 20); x = Math.floor(x / 20);
}
return pairs.slice(0, 8) + "+" + (pairs.slice(8) + grid).slice(0, length - 8);
}
function decodePlusCode(code) {
const c = String(code).trim().toUpperCase();
if (!/^[23456789CFGHJMPQRVWX]{8}\+[23456789CFGHJMPQRVWX]{2,3}$/.test(c)) {
throw new Error("expected a full 10 or 11 digit Plus Code, e.g. 8G5RG864+FJ");
}
const d = c.replace("+", "").split("").map((ch) => ALPHABET.indexOf(ch));
if (d[0] > 8 || d[1] > 17) throw new Error("not a valid Plus Code");
let y = 0, x = 0, yUnits = 8000, xUnits = 8000;
for (let i = 0; i < 10; i += 2) { y = y * 20 + d[i]; x = x * 20 + d[i + 1]; }
if (d.length === 11) { y = y * 5 + Math.floor(d[10] / 4); x = x * 4 + (d[10] % 4); yUnits *= 5; xUnits *= 4; }
return { lat: (y + 0.5) / yUnits - 90, lng: (x + 0.5) / xUnits - 180 };
}
Tested before publishing: on 40,000 random points (20,000 worldwide and 20,000 inside Syria's bounding box) it returns the same 10- and 11-digit codes as the JavaScript implementation from the open-location-code project (Apache 2.0), with the same decoded centres and clean round trips. 33.51123, 36.30654 in Damascus encodes to 8G5RG864+FJ (11 digits: 8G5RG864+FJV). It accepts lower case and spaces and rejects short codes and malformed input. It does not decode short codes such as G864+FJ Damascus, which need a reference location.
G864+FJ Damascus leave out the first four characters and lean on a reference place. The project's documentation says a place-name reference may need a geocoding service to resolve, and two geocoders can put the same town far enough apart to land on the wrong cell. It suggests references at neighbourhood scale rather than city scale. The function above accepts full codes only.| Names Syria? | What the terms say | |
|---|---|---|
| Google Maps Platform | Yes | Its prohibited-territories page lists Syria (checked 15 November 2026). |
| Mapbox | No country named | Product Terms (20 Oct 2026) require compliance with export control laws. The form Master Services Agreement (12 Sep 2025) excludes from the licensed territory any country embargoed or designated as supporting terrorism by the US Government, without a list. |
| HERE | Syria not named | Platform Terms (effective 18 Sep 2023) forbid providing HERE materials to any embargoed destination in violation of US, UK or EU law. |
| MapTiler | No country named | Cloud terms ask you to certify you are not a restricted person under Swiss, US, EU and UK law. MapTiler Satellite adds a warranty that you are not located in a US-embargoed country. |
| TomTom | No country named | Developer portal terms: do not accept the agreement if US or other laws bar you from receiving the products. |
| Esri | Not on its list | Syria is not on Esri's list of prohibited countries and destinations (page last modified 30 Dec 2025). |
| what3words | No country named | Terms (20 Apr 2026) and API licence (26 Oct 2026) bar use by anyone located in a country under a US trade embargo or designated by the US as terrorist-supporting. |
| Apple Maps | No Maps feature listed | The iOS and iPadOS 27 feature-availability page lists Syria under none of its Maps features, and does not say whether maps load there. Test on a device. |
| OpenStreetMap Foundation servers | No country named | Its Terms of Use (last edited 31 Oct 2018) include a sanctions representation for users of its website, tiles and Nominatim. The ODbL data licence has no such clause. |
OpenStreetMap data is open, but the servers the OpenStreetMap Foundation (OSMF) runs are shared by everyone and have rules. These apply in every country:
what3words gives every 3 metre square in the world a three-word name, and its about page names no country it leaves out. Using it in an app means using its licensed API. Business sign-ups go through automated checks that include sanctions-list searches. Its terms and API licence bar use by anyone located in a country under a US trade embargo or designated by the US as supporting terrorism, or listed on EU, UN or US restricted-party lists, and neither document names a country. Coordinates converted from three-word addresses may be stored for 30 days at most.
Plus Codes need none of that. The algorithm is open, the code is computed on the device, and you can keep it with the order forever. Ten characters are harder to remember than three words, so design the flow for sharing with a button rather than typing. For an app that has to work in Syria, not depending on an account or a network is the practical difference.
Aviation authorities document satellite-navigation interference in the region. Their data comes from aircraft, not phones on the ground, and we found no official ground-level measurement for Syria. It is still enough reason to design the pin step carefully.
Turn off postcode validation for Syrian addresses, including any that a checkout library or form builder adds for you. Keep the field optional only if you also ship abroad.
City and area from pick lists, then street or landmark, then building, floor and apartment, then the phone number. Arabic first, English accepted. For marketplace listings the area is often enough, so keep exact pins for deliveries; see building a marketplace.
Open the map on the current position, let the user drag the pin, show the accuracy and ask for a confirmation. Save the coordinates, the Plus Code and how the pin was set.
Check the sanctions or export clause, the storage rules for geocoding results, and the attribution rules. Write down the date of the version you read, and read it again before each major release.
The Nominatim policy says package and vehicle tracking apps must run their own instance, and ride-hailing and delivery apps are exactly that. Build tiles and search from the daily Syria extract and run them where your other servers live.
Compute Plus Codes on the phone, keep map data for the user's area on the device from your own tile server rather than tile.openstreetmap.org, which does not allow offline use, and let an address be saved offline and synced later, as in our offline-first guide.
When the pin is not enough, the number is how the courier finds the door. Normalise it to +963 format and verify it; see SMS codes for Syrian numbers.
Postal codes are not required in Syria: the Universal Postal Union lists it among the countries that do not require them. UPU's Syria sheet from September 2004 said a postcode system was being developed, and we found no newer official document. Make the field optional or hide it.
Checked 16 November 2026 on each publisher's own page (Google Maps Platform on 15 November 2026). Vendor terms change, and some clauses depend on US designations on the day you use a service, which this page does not assess. Confirm with the vendor before you build on it. Nothing here is legal advice.
Tell us what your app needs from the map: deliveries, rides, or just a shop location. We will help you design the address flow and pick a map setup whose terms you have read.