What does a Salla store developer do that the dashboard cannot?
A Salla store developer changes code: the theme files that draw your storefront and the apps that move data in and out of your store. The dashboard lets you configure; a developer lets you change how things work.
Salla already does a lot without code. You can add products, set shipping, switch on payment methods, install apps from the Salla App Store and adjust theme settings. For many new stores that is enough, and paying a developer would be wasted money.
A developer earns their fee when you hit a wall. The product page layout cannot show your size guide where customers need it. The home page cannot be arranged the way your brand designer drew it. Orders have to reach your accounting or warehouse system and no App Store app does it the way you work. You are moving from WooCommerce and have three thousand products and years of Google traffic to protect. Those are developer jobs.
- Twilight theme customisation and custom themes
- Custom apps using OAuth, the Merchant API and store events
- Data migration with URL redirects
- Integrations with accounting, ERP, WhatsApp, sheets and couriers
- Speed, SEO and structured data fixes in theme code
When does a Salla store need a developer, and when is it a waste?
Hire a Salla store developer when the change you want is repeated, visible to customers, or costing you time every day. Skip one when a setting or an existing app does the job.
You probably do not need a developer if
You are launching your first catalogue, your theme's settings cover your layout, and your order volume is small enough that copying orders into accounting takes minutes a day.
A developer pays off if
Staff re-key orders into another system every day, your brand needs a storefront that looks unlike the default themes, or you are moving a large store onto Salla.
Try an app first if
The problem is common: reviews, loyalty, upsells, abandoned cart messages. Search the Salla App Store before paying for custom code.
Our first call often ends with "you do not need us for that; install this app and change that setting". It saves you money and saves us from building something that will be replaced by an app update next month.
How does Twilight theme customisation work?
Twilight is Salla's theme engine. Salla's own starter theme, Raed, is built with the Twig template language and Tailwind CSS, with page templates, reusable components, a master layout and locale files for Arabic and English in separate folders. Developers work through the Salla Partners Portal and the Salla CLI.
Day-to-day, we run salla theme preview, which builds the theme, serves it locally and opens it on a demo store with hot reloading, so each change to a template or stylesheet shows up straight away. When you approve, the theme is published to your store. Theme settings are exposed in your dashboard so your team can still change banners, colours and sections without calling us.
What we customise most: product cards and product page layout, home page sections, category filters, header and mobile menu, trust blocks (returns, delivery times, payment icons), and Arabic typography. What we leave alone: Salla-controlled checkout and payment screens, which the platform manages.
Should you customise an existing Salla theme or build a custom Twilight theme?
Customise when your current theme is close and you need a dozen targeted changes. Build custom when your designer's layouts differ on almost every page, or when you have several brands that need to share one design system.
Customising is faster and cheaper, but it ties you to that theme's structure and its future updates. A custom theme starts from Salla's starter theme, so it follows the platform's conventions, then gets your own components and settings. It costs more up front and is yours to maintain. For most stores with fewer than a few hundred products, a well-customised theme is the better value.
Either way, we keep the code in a Git repository in your name, so every change is tracked and reversible. That matters more than it sounds: the most common Salla support request we hear about is "someone changed the theme and now something is broken, and nobody knows what they changed".
How do Arabic and English work inside a Salla theme?
Theme text lives in locale files, one for Arabic and one for English, while product and category content lives in your Salla dashboard in both languages. A Salla store developer edits the first; your team fills the second.
Getting this split right saves pain. Button labels, section titles, empty-cart messages and trust badges belong in the locale files so they switch cleanly when a shopper changes language. Hard-coding Arabic words straight into a template is a common shortcut in rushed theme work, and it leaves English visitors looking at Arabic buttons, or the reverse.
Layout direction is the other half. Arabic pages read right to left, so arrows, sliders, breadcrumbs, price and discount badges, and icon positions must mirror. Tailwind's direction-aware utilities help, but every custom component still needs checking in both languages on a real phone. We test each changed template in Arabic first, since that is how most of your Saudi shoppers will see it, then in English.
Typography deserves attention too. Arabic fonts render larger or smaller than Latin ones at the same size, and a product title that fits on two lines in English may wrap to four in Arabic. We tune sizes and line heights per language rather than accepting whatever the default theme does.
What can a custom Salla app do through the Merchant API and app events?
A custom Salla app is a small piece of software that a store authorises through OAuth 2.0 to read and change its data. Salla's documentation covers the Merchant API for store data, the Apps API for app settings, subscriptions and events, an Embedded SDK for apps that appear inside the merchant dashboard, and a Shipping and Fulfillment API.
In practice, a custom app listens for store events such as a new order or a status change, then does something your business needs: sends the order to a warehouse system, creates an invoice in your accounting tool, updates stock from a supplier feed, assigns a sales rep, or posts a message to your team. It can also run on a schedule, for example syncing prices from your ERP every night.
Custom apps start from US$900 because they need hosting, secure token storage, retries when the other system is down, and an admin screen or log so your team can see what happened. Simpler one-way integrations built with automation tools can start from US$600. We tell you honestly which one your case needs.
- Order to accounting, ERP or warehouse system
- Supplier stock and price feeds into Salla
- Wholesale or B2B rules that the storefront cannot express
- Internal dashboards combining Salla with other data
- Notifications to staff channels on high-value or flagged orders
How do you migrate from WooCommerce or Shopify to Salla without losing sales?
Move the data, keep the URLs working, and test before the switch. A migration is a project with a checklist, not an export and import.
First we audit the old store: product count, variants, attributes, images, customers, order history, discount codes, reviews and blog posts. Some things move cleanly; others need mapping, because a WooCommerce attribute or Shopify metafield may become a Salla product option or custom field. Customer passwords never transfer between platforms, so customers set new ones; we plan a friendly email or WhatsApp message for that.
Second, search traffic. Every old product and category URL that earns visits gets a redirect to its new Salla address. We crawl the old site, export Search Console data, build the redirect list and check it after launch. Skipping this step is how stores lose months of organic sales after a platform change.
Third, a parallel run: the Salla store is filled and tested on staging while the old store keeps selling. The switch happens on a quiet day, not before a sale or Ramadan.
After the switch, the first fortnight is for watching. We check Search Console for crawl errors and pages that dropped out, compare order numbers with the same weeks before the move, and fix any redirect that points somewhere unhelpful. Reviews are the item merchants most often forget: if your old store showed product reviews, decide early whether they move over through an app import or start fresh, and tell customers either way.
How do Salla accounting and WhatsApp integrations work?
Both start from the same trigger: something happens in your Salla store, and another system needs to know. The difference is what happens next.
For accounting, each paid order becomes a sales invoice or receipt in your cloud accounting system, refunds become credit notes, and payouts from your payment provider are matched to them. Saudi merchants commonly use local tools such as Qoyod or Wafeq, or international ones like Zoho Books; if an App Store app already connects yours well, we will tell you to use it. We build custom sync when your chart of accounts, branch structure or VAT handling needs rules an off-the-shelf app lacks. Your accountant defines the rules; we implement them.
For WhatsApp, the common flows are order confirmation, cash-on-delivery confirmation before shipping, shipping updates with tracking links, and review requests after delivery. These run on the WhatsApp Business Platform with Meta-approved message templates in Arabic and English, and only to customers who agreed to receive them. Details are on our WhatsApp automation page for Saudi Arabia.
How much does a Salla store developer cost?
With BtechWaleTech, Salla store work starts from US$750 for a new store build, redesign or substantial theme customisation. Integrations start from US$600. Custom Salla apps start from US$900. Small one-off fixes are quoted after we look at the store.
What moves a Salla store developer quote: the number of templates changed; whether you need a custom theme or edits to an existing one; catalogue and order volume in a migration; the number of systems an app talks to; and how much admin interface your team needs to manage an integration. We quote in US dollars; because the Saudi riyal is pegged to the dollar, the riyal figure does not drift between quote and invoice.
You pay Salla directly for your plan and the App Store developers for any apps you install. Hosting for a custom app runs on a cloud account in your name. After two free months of maintenance, support starts from US$120/mo.
How long does Salla development take?
Theme customisation takes one to three weeks depending on how many templates change. A full store build or custom theme takes four to eight. A custom app takes six to twelve. A migration usually takes three to six weeks, with most of the time spent on data mapping and redirect testing.
The fastest projects share two things: a single decision-maker on the merchant side, and content ready before design starts. The slowest share one: "we will send the Arabic product descriptions next week", repeated for a month. Tell us your launch date, such as White Friday or a new collection drop, and we plan backwards from it.
- Theme tweaks: 1–3 weeks
- New store or custom theme: 4–8 weeks
- Migration with redirects: 3–6 weeks
- Integrations: 2–4 weeks
- Custom app: 6–12 weeks
Can a Salla store developer improve SEO?
Yes, in the parts code controls. A Salla store developer can make the theme faster, fix heading structure, add structured data for products and breadcrumbs, make category pages carry useful text, and keep images properly sized and labelled. Platform-level behaviour, such as how Salla generates certain URLs, is outside any developer's control.
The biggest SEO wins on Salla stores we review are rarely technical. They are category pages with no text, product titles that are just SKU codes, Arabic and English content that says nothing different from the manufacturer, and no internal links from content to products. We fix the theme side and show your team the content side.
For ongoing work, our SEO services in Saudi Arabia start from US$150/mo. Nobody can guarantee a ranking, on google.com.sa or anywhere else. Clear, well-structured product pages also help AI shopping assistants describe your products accurately.
When should you stay on Salla, and when is Zid, Shopify or custom a better fit?
Stay on Salla when your customers are mostly in the Kingdom, your team is comfortable in an Arabic dashboard, and the local payment and shipping apps cover you. For a large share of Saudi stores that is the right answer, and a developer can stretch Salla much further than people assume.
Consider Zid if you prefer its dashboard or specific features; the platforms are close cousins, and our Zid store developer page covers that side. Consider Shopify when you sell across the GCC and beyond with multiple currencies and need its app ecosystem; see Shopify developer for Saudi stores. Consider a custom build from US$900 only when your business rules (B2B tiers, configurators, complex subscriptions) fight every hosted platform.
Before any move, ask whether a custom app on your current platform would solve the problem for less. Often it does.
How does a Saudi merchant work with a Salla developer in India?
Mostly on WhatsApp and short video calls, inside a working day that overlaps well: India runs two and a half hours ahead, so your 11 am is our 1:30 pm, and your evening order rush lands in our late evening.
Access is the first practical step. You add us as a staff user in your Salla dashboard with only the permissions the job needs; you never share the owner login. Theme code lives in a Git repository you own. For custom apps, the app is registered through a Salla Partners account and hosted on a cloud account in your name, so you keep control if you ever change developers.
Money and paperwork: an itemised USD quote in about two working days, milestones in writing, payment by Wise or bank wire, and invoices from India. Nothing is billed before you approve. In the first two weeks, you can expect a store audit and quote in the first days, then theme changes appearing on a preview store by the end of the second week, with the third of us coordinating, one of us writing the Twig, Tailwind and app code, and another of us on hosting, data and SEO checks.
How do you vet a Salla developer before hiring?
Ask to see how they work, not just what they have made. Screenshots of pretty stores say little about whether the code will survive the next theme update.
- Will you work from a staff account or ask for my owner password? (Staff account is the right answer.)
- Where will the theme code be stored, and will I get the repository?
- Do you edit the live theme directly or preview changes on a demo store first?
- For apps: whose Partners account and whose hosting will it run on?
- How will you handle redirects if we migrate?
- What happens when Salla updates the platform and something changes?
Red flags: asking for owner credentials, editing live without a preview, refusing to hand over code, and bundling an app you cannot run without paying them forever. If you want broader context on vetting remote developers, our guide on how to hire Indian developers covers the general checks.
Example: an abaya brand in Jeddah outgrows its Salla theme
Consider a hypothetical abaya label in Jeddah selling on Salla with around 200 products, each in several sizes and lengths. Sales come mostly from Instagram, and the owner's accountant spends an hour a day copying orders into the accounting system.
Step one is theme customisation, from US$750: a product page that shows a length and size guide next to the size selector, fabric and care details in both languages, and a home page arranged by collection drops instead of generic banners. Everything is previewed on a demo store before going live.
Step two is an integration, from US$600: every paid order creates an invoice in the accounting tool with the right VAT treatment set by the accountant, refunds create credit notes, and cash-on-delivery orders get a WhatsApp confirmation before they are handed to the courier. Step three, only if the brand opens a wholesale channel for boutiques, is a custom Salla app from US$900 for trade pricing and bulk orders.
What do you get at handover, and what happens after launch?
You get the theme source in your repository, app code and deployment notes, admin credentials for any hosting in your name, a list of every setting we changed, and a short screen-recorded walkthrough for your team. Nothing about your store depends on us staying involved.
For two months after go-live, fixes and small adjustments are free. If Salla changes something that affects your theme or app in that time, we handle it. After that, care starts from US$120/mo, or you can hire us for individual tasks when they come up. Some merchants prefer that, especially once the theme is stable and the integrations run quietly in the background.