Salla Store Development
Build or refresh a Salla store with an approved catalogue, an Arabic mobile journey, tested orders, and merchant handover.
Why?
A store needs more than a refreshed theme. We connect the agreed catalogue, shopping journey, and operating settings, then test the order flow before handing the store over to your team.
-
One Connected Launch Scope
Catalogue, storefront, operating settings, and testing are managed as one agreed store outcome.
-
A Tested Customer Journey
Representative orders and error checks reveal issues before the agreed launch, rather than relying on appearance alone.
-
A Store Your Team Can Manage
Clear access ownership and a practical guide support routine catalogue and order work after handover.
Our process
Check Platform Fit and Launch Scope
We review the store, catalogue, required functions, plan limits, and account ownership, then agree what can be delivered with Salla-supported features.
Prepare the Approved Catalogue
We structure agreed products, variants, categories, and supplied media, checking data completeness and merchant-approved descriptions.
Build the Arabic Shopping Journey
We configure the agreed theme and storefront pages for Arabic, right-to-left layouts, and mobile use, with clear product information and actions.
Configure Approved Store Settings
Within your approved scope and access, we configure supported payment, shipping, notifications, and supplied policies. Purchases and account changes require your approval.
Test Orders and Resolve Issues
We test the agreed product, cart, checkout, and notification paths, including relevant error states. Any live payment or refund test needs your approval.
Approve Launch and Hand Over
After your approval, we complete the agreed launch steps and deliver the test record, operating guide, access handover, and any scoped defect-support arrangements.
Questions?
We scope standard product stores after reviewing platform fit, current setup, catalogue readiness, and required access. Existing-store changes need an agreed publishing plan; migration and custom integrations are assessed separately.
The proposal defines product count, theme and pages, supported payment and shipping setup, order tests, handover, and any defect-support period. Fees and timing follow scope; subscriptions, apps, themes, and provider charges are identified separately.
You own the merchant accounts and approve providers, policies, charges, and account changes. We configure and test within that approval; live payments, purchases, or refunds need explicit approval before execution.
No. Daily stock management, fulfilment, customer service, and campaigns are outside the launch scope. Booking systems and custom features need a separate feasibility check. Sales and conversion gains are not guaranteed.
