How to Design a Salla Store That Actually Converts
Salla store design is not a theme choice. It is a sequence of decisions about what a Saudi or Gulf shopper needs to see before they trust you with a payment — and what you delete so that they can actually see it. I have shaped hundreds of Salla storefronts, and the ones that sell are almost never the ones with the most sections on the homepage.
Salla is generous out of the box: a working, hosted, Arabic-first store on day one. The gap between a working store and a selling one is the part nobody hands you.
Where Salla Store Design Starts: What the Platform Already Gives You
Be honest about what you are customising. Salla already handles hosting, the catalogue, local payment methods, shipping, tax invoicing, an Arabic admin panel your client can operate alone, and an app marketplace for the rest. You are not building a store; you are shaping one that already runs.
Which is why the default themes fall short — they are built to be safe, not to be yours.
-
They are made to look acceptable with any catalogue, which means they are tuned for none of them.
-
The starter homepage stacks every available section in the order the theme author listed them, so nothing is prioritised and everything competes.
-
Product templates assume a simple product. Give them six variants and a size chart and they strain.
If you are still choosing a platform rather than customising one, read my comparison of Salla, Zid, Shopify and WordPress first — choosing twice costs more than designing twice.
Salla theme customisation: start by removing
Salla's editor lets you reorder, hide and restyle sections without touching code, and a Twilight theme lets a developer go further. Either way, the first pass should be subtraction: hide every section you cannot justify in one sentence, then rebuild upward with the four or five that earn their place.
The Homepage Sections That Actually Earn Their Place
A homepage is not a brochure. Its only job is to move a visitor into a category or a product page as fast as possible. The sections I keep in almost every store:
-
One hero. One message, one offer, one button. A static banner beats a carousel, because a static banner is always the banner you chose.
-
Category entry points. Four to eight tiles with real names and real photography — not generic icons.
-
Best sellers. Shoppers who don't know what they want will take a recommendation, and this is the cheapest one you can give.
-
A delivery and returns strip. How long shipping takes, what it costs, whether cash on delivery exists, and how to reach a human being.
And the ones merchants keep asking for that nobody scrolls to: the five-slide auto-rotating banner; the "why choose us" grid promising fast shipping, secure payment and high quality (every store online claims all three); a slow social feed that sends traffic away; and a newsletter block placed before the visitor has seen a product.
If the homepage still borrows its colours from the theme demo, the problem sits upstream of layout — start with the identity, which I covered in from logo to packaging.
“A homepage is not a brochure.
It is a signpost — and if it doesn't get
a shopper into a product page in one tap,
it is decoration.”
Category Structure: Design for a Catalogue That Will Triple
Most stores I open launch with twenty products and plan for two hundred. Navigation built for twenty collapses at two hundred, and rebuilding it later means broken links and a returning customer who cannot find what they bought last time.
-
Name categories the way customers speak, not the way your supplier invoices you.
-
Two levels of navigation, maximum. Anything you want to make a third level is a filter, not a category.
-
Give every category a short intro line and an image. An unlabelled grid tells a shopper nothing about where they landed.
-
Build filters before you need them — price, size, colour, brand, availability — and sort by best selling rather than newest.
-
Never ship a catch-all category called "Products" — that is where merchandising dies.
-
Add a second set of collections built on occasions or problems — gifts, Ramadan, sensitive skin — over the same catalogue. People shop by situation more often than by category.
You can see this across the storefronts on my projects page: in the multi-category stores, navigation had to be designed before the homepage was sketched.
The Product Page: What Gulf Shoppers Check Before "Add to Cart"
This is where a Salla store either pays for itself or quietly leaks customers. A buyer arriving from a Snapchat ad runs a short mental checklist, and every unanswered item is a reason to close the tab.
Images
Five to seven per product: a clean pack shot, one in use, one showing scale against something familiar, and — for anything ingested or applied to skin — a readable photo of the back of the pack. Keep crop, background and lighting identical across the catalogue, or the grid reads as a marketplace of strangers.
Variants and sizing
Show colours as swatches and sizes as buttons, not as a dropdown that hides how much choice you offer. Keep sold-out options visible and disabled: absence looks like a bug, a greyed-out size looks like a busy store. And publish a real size table in centimetres, in Arabic. "Standard size" is not a size.
Delivery, price and trust
-
Say how many days delivery takes to the shopper's city. "Fast shipping" is not information.
-
Make it clear whether the price includes VAT and what shipping will add — before the cart, not inside it.
-
Put the return policy in one sentence under the add-to-cart button, not three clicks away in a footer page.
-
Show payment methods as logos — mada, Apple Pay, card, cash on delivery, instalments. Gulf shoppers scan for these the way they scan for a price.
-
Give them a way to ask without leaving: a WhatsApp button on the product page answers the objection your copy missed.
I broke this page down element by element in Product Page Design: 12 Elements That Turn Browsers Into Buyers — it is the one page worth over-investing in.
Checkout: How Few Steps You Can Really Get Away With
Salla owns most of the checkout mechanics, which is a mercy. What you own is how much you ask for — and that is where the damage happens.
Ask for a name, a mobile number, a city and an address with a map pin. That is a complete order. Never ask for, on a first purchase:
-
A registered account before payment. Guest checkout exists for a reason.
-
A national ID, a date of birth, or a second phone number.
-
"How did you hear about us?" as a required field.
-
A coupon box styled as the loudest element on the page. It sends people out to hunt for a code they will not find, and many do not come back.
And on the cart page: let people change quantity without a full reload, and show shipping cost before the last step. A cost that appears at the end is the most reliable way to lose an order you had already won.
Mobile-First Salla Store Design Means Designing for the Thumb
Nearly all the Salla traffic I have watched arrives on a phone, usually from Instagram, Snapchat or TikTok. So the phone frame is the design, and desktop is the adaptation.
-
Put primary actions in the lower half of the screen. On a large phone, the top corners are the hardest place a thumb has to travel.
-
Let a sticky bar carrying the price and the add-to-cart button follow the shopper down the product page.
-
Give tap targets real size and spacing. Swatches placed shoulder to shoulder produce wrong selections, and those become returns.
-
Never bake text into a banner image. It breaks at small widths, it cannot be translated, and search engines cannot read a word of it.
-
Keep search visible in the header, not hidden behind an icon, as soon as the catalogue passes a few dozen items.
Then test the way your customer will: a mid-range Android, one hand, mobile data — not a twenty-seven inch monitor in a dark room.
Arabic Typography and RTL Inside Salla Themes
Salla is Arabic-first, but most themes still inherit a type scale built for Latin text and then pour Arabic into it. The result is technically right-to-left and visually wrong.
-
Give Arabic more line height than you would give English. Arabic body copy breathes at roughly 1.7 to 1.9.
-
Pick one Arabic family that ships with real weights and use those weights. Faux bold thickens the letterforms and damages the joins.
-
Do not letter-space Arabic or apply uppercase styling to it. Neither exists in the script; both break it.
-
Mirror the layout, directional icons, progress steps and carousel arrows. Do not mirror logos, product photography or numerals.
-
Wrap Latin fragments — brand names, SKUs, phone numbers — in their own direction so they stop scrambling.
I collected the ones I meet most often in Arabic RTL Design: 9 UX Mistakes That Cost Gulf Stores Sales, and nearly every one turns up inside a stock Salla theme.
A Pre-Launch Salla Store Design Checklist
This is the list I run before a store goes live; it catches what a customer would otherwise find first.
-
Every product has at least five images at the same crop and background.
-
Every category has a name a customer would say out loud, and none is empty.
-
The homepage has been checked at 360px wide and the hero reads without zooming.
-
Add to cart is reachable with one thumb on every product page.
-
Shipping time and cost are visible before checkout starts.
-
The return policy exists as one sentence on the product page.
-
Every form error is written in Arabic and sits beside the field it belongs to.
-
Search returns something useful for common misspellings and for English brand names typed in Arabic letters.
-
Store contact — WhatsApp number and working hours — is one tap from anywhere.
-
Someone who has never seen the store completes a purchase on their own phone while you watch and say absolutely nothing.
Ship It, Then Watch Somebody Use It
Good Salla store design is mostly restraint: fewer sections, fewer fields, fewer questions between a shopper and the thing they came for. The last item on that checklist teaches you the most.
If your Salla store looks fine but is not converting, send me the link and tell me what you sell — message me on WhatsApp and I will tell you what I would change first. You can also see how I scope a store project or use the contact page.