Delivery carriers only accept city names they recognize — each one has a fixed list of the cities it serves, spelled a particular way. But real customers type their city however they like: kech, mrkech, marra kech instead of Marrakech. When an order's city doesn't match what the carrier expects, the parcel gets rejected or delayed — a direct hit to your delivery rate. City Corrections solve this by teaching eGrow to automatically rewrite those wrong spellings into the exact name each carrier wants, before the parcel is created. Manage them at https://v2.egrow.com/settings/geography/corrections.
Why corrections are per shipping company
This is the most important thing to understand: corrections apply only to orders sent to the shipping company you select. Two carriers can serve the same town under different official spellings (or one may not serve it at all), so eGrow keeps a separate correction list for each. At the top of the page you first select a shipping company — everything you then add applies only to that carrier.
Anatomy of a correction
Each correction is a simple mapping of many wrong spellings to one right one. Click Add Correction and fill in:
- Correct City — the exact spelling the shipping company expects, for example
Marrakech. You pick this from the carrier's own list of served cities, so it's guaranteed to be a name the carrier accepts. (This is why connecting the carrier as a city source first is helpful — it fills that list.) - Wrong Spellings — every misspelling or variant that should map to that city, for example
kech, mrkech, marra kech. Separate them with commas or new lines. Add as many as you see in the wild.
Save it, and from then on any order heading to that carrier whose city matches one of those wrong spellings is silently rewritten to Marrakech when the parcel is created — so the carrier recognizes it and the parcel goes out.
Catching new spellings automatically: Auto-flag
You can't predict every way a customer will type a city. That's what Auto-flag new cities is for. Turn on this switch for a shipping company and eGrow will automatically flag any order city that isn't in your corrections yet, so you can complete it instead of letting a bad city slip through to the carrier. It turns your correction list into a living thing that grows from your real orders.
The “Needs correction” list
Flagged cities collect in a pending list — a badge shows “{n} cities need a correction” with the note “These cities arrived on orders but aren't in your corrections yet.” For each pending city you make one decision:
- Correct — the city is misspelled; map it to the right Correct City. From now on it's auto-fixed.
- It's correct — the spelling is already fine (the carrier accepts it as-is); mark it so it stops being flagged.
Clearing this list regularly is the whole maintenance routine — a minute here keeps parcels from bouncing later.
Finding your way around the list
The corrections table has filter tabs so you can focus:
- All — every city eGrow has seen for this carrier, corrected or not.
- Corrected — cities you've already mapped.
- Not corrected — the pending ones still waiting on your decision.
Each correction can be edited (add more wrong spellings, or fix the target city) or deleted at any time.
A worked example
Say you ship with Ozon Express, and its city list spells the city Marrakech. Over a week your orders arrive with kech, marrakch, and marra kech. You:
- Select Ozon Express as the shipping company.
- Turn on Auto-flag new cities so nothing unfamiliar gets through.
- Add a correction: Correct City
Marrakech, Wrong Spellingskech, marrakch, marra kech.
Now every future order with any of those spellings ships to Ozon as Marrakech automatically. When a brand-new variant like merakech appears, it lands in Needs correction, you tap Correct and add it to the same mapping — done.
When you should use City Corrections
- You run cash-on-delivery and ship through carriers that require exact city names (very common across Morocco and the wider region).
- You see parcels rejected, delayed, or returned because of unrecognized or misspelled cities.
- Customers enter their own address (from a landing page, a form, or WhatsApp) where typos are frequent.
Set it up once per carrier, keep the “Needs correction” list clear, and a whole category of failed deliveries simply disappears.
Related
City Corrections is one part of eGrow's Geography settings, alongside City Sources (pulling a carrier's served-cities list) and Shipping Rates. Fewer bad cities also means better numbers in your delivery analytics — watch your return rate by city to see the impact.