Around 80% of MENA e-commerce traffic is mobile. Around 30% of mobile carts complete checkout. The gap between those two numbers is where most stores leave money on the table — and most of it comes down to five fixable mistakes.
Mobile checkout conversion rate isn't a mystery. It's a thumb on a small screen, a half-charged battery, an unstable connection, and a shopper who'll bail the moment something feels off. Every extra tap, every unnecessary field, every confusing payment screen costs you orders.
Mistake 1: Asking for too much, too early
The classic Salla and Shopify checkout asks for full name, email, phone, country, city, district, street, building, postal code — before the shopper has even seen the shipping cost. By field five, attention drops. By field eight, you've lost a real percentage of carts.
The fix is sequencing. Show shipping cost as early as possible, ideally based on phone number or city alone. Group the address into one screen, payment into another, and never put both on the same long scroll. Test removing the postal code field entirely — in Saudi Arabia and the UAE, most couriers don't need it for delivery, and shoppers don't know theirs.
Every field on a mobile checkout costs you 1–3% of carts. Audit your form. If a field doesn't directly enable shipping or payment, kill it.
Mistake 2: Breaking autofill
Modern phones autofill names, addresses, and card numbers — if your form fields use the right HTML attributes. Custom checkouts often break this. The shopper taps the field, expects their saved address to appear, sees nothing, and starts typing manually. Half of them don't finish.
The signs: when you tap a field on iPhone or Android and no suggestion bar appears above the keyboard. The fix is technical but quick. Make sure each input has the correct autocomplete attribute (name, tel, street-address, postal-code, cc-number). For your Shopify and Salla store, this is especially important on the address block — it's the longest form and the one autofill helps most.
Mistake 3: Wrong payment order
The order of payment methods on the checkout screen matters more than people think. The first method shoppers see is the one they're most likely to choose, even if it's not the best for them.
For Saudi Arabian and UAE traffic, this usually means putting Mada and Apple Pay at the top. Stripe-style credit card forms convert lower than tokenized one-tap methods. Cash on delivery (COD) is interesting — it converts well but creates fulfillment headaches. Some stores hide it lower in the list to nudge shoppers toward prepaid.
- Default order to test: Apple Pay → Mada → Visa/Mastercard → STC Pay → Cash on Delivery
- For higher-AOV stores: Apple Pay → Tabby/Tamara → Mada → Card → COD
- If you sell to UAE primarily: Apple Pay → Card → Tabby → COD
None of these are universal. The right order is whatever your shoppers actually convert best on, and the only way to know is to test two variants over two full weeks.
Mistake 4: No sticky CTA on long forms
If your checkout form is longer than one screen — and almost all are — the shopper has to scroll back to the bottom every time they want to continue. On a phone with a thumb, that's annoying. After two scrolls, frustration builds.
A sticky "Continue" or "Place Order" button at the bottom of the screen, visible while scrolling, removes that friction entirely. It's also one of the easiest mobile checkout conversion rate tests to run — same form, same fields, just one CSS change. We've seen it lift completed checkouts by 6–11% on stores with multi-step flows.
Watch out for two pitfalls. First, make sure the sticky button doesn't cover field labels on smaller phones. Second, keep the button disabled (visually grayed) until the current step is complete — otherwise shoppers tap it, get an error, and lose trust.
Mistake 5: Address fields that don't match how people think
Western e-commerce checkouts assume a structured address: street name, house number, postal code. In Saudi Arabia and most of MENA, people often navigate by district, landmark, or building name, not by street. A form that demands "Street Number" gets blank stares.
The fix is two-part. Make most address fields optional except for what the courier actually needs (city, district, phone). Add a free-text "Delivery notes" field at the end where shoppers can write "behind the Panda, white building, second floor" — which is how the driver will actually find them. We've seen this single change reduce delivery failures by 15–25% on local stores.
Test the fixes — don't just ship them
All five of these fixes are easy to ship. They're also easy to ship badly. The autofill fix can break a form on a specific browser. The sticky CTA can cover a field on iPhone SE. The new address layout can confuse shoppers used to the old one.
Before rolling any of these to 100%, run them as A/B tests. Watch a handful of recordings of real shoppers using both versions — that combination of behavior data is what separates a guess from a real test. The decision framework for which tool fits which question is in heatmaps vs session recordings vs A/B tests.
Next steps
Pick the one mistake from this list that sounds most like your store, and fix it as a test, not a permanent change. Run for two weeks. Measure completed orders, not just checkout starts. Then move to the next one. Five fixes done properly over a quarter usually beats fifty changes shipped on gut feel.