A store owner may receive an attractive interface only to discover missing images, incomplete products or an inactive payment service. A Salla design proposal needs a clear work description: what the company delivers, what you provide and what depends on the platform or another provider.
Start with a readiness file connecting each part to content, configuration or a test, rather than an undefined “complete store”. This reveals what the agency offer purchases and what remains necessary for actual operation.
Before design: is your store ready to proceed?
Identify the store-account owner, merchant's country of activity, verification status and requirements of desired services. The agency's country does not determine merchant eligibility. Hiring an Egyptian provider, for example, does not establish that every requirement for your entity's store is available or approved.
Salla provides guidance for selling from outside Saudi Arabia and directs merchants to support for suitable options. Check your actual case before tying launch to an unfinished process. Avoid old articles with country-availability lists or an agency promise of guaranteed acceptance.
A readiness file shared with the provider
| Area | Merchant input to approve | Provider output |
|---|---|---|
| Identity and interface | Logo, colors and assets available for use. | Agreed brand settings, pages, elements and preview. |
| Products | Accurate names, descriptions, images, prices and options. | Sample and catalogue preparation or entry within defined quantities and scope. |
| Content | Approved contact details, policies and copy. | Formatted pages and entered text without invented details or terms. |
| Configuration and services | Accounts, documents and operational decisions. | Included settings and any pending external activation. |
| Operation and handover | A responsible employee participating in tests and training. | Order test, subscription register and guidance for the delivered scope. |
For each input, identify its owner and timing; for each output, define review. If the provider writes descriptions or prepares images, record this explicitly rather than assuming it is included in “upload products”. If content already exists, avoid buying duplicate work.
A fictional gift store
The store sells a gift box in two sizes with a buyer-written message and preparation instructions. A product image and occasion banner may look sufficient in a design presentation. Scope acceptance requires a configured product whose options and message reach the responsible employee.
Ask what the chosen store settings, theme and plan support, and what requires an app or additional work. A field in a reference image does not prove it is available in the actual flow. Choose a size, enter a message and review what reaches the order under the approved configuration.
Explain the boundaries of visual customization
Salla documents identity customization through store settings such as logo, color and font. Ask what the provider configures through available options, what it adds beyond them and what you can edit afterward. “Custom” does not establish ownership of an unspecified design, code or licence.
Review homepage, category, product and cart on mobile rather than only the first-page image. If two languages or particular elements are included, identify the content and states to inspect. Clarify image, font and icon sources and permitted use without treating another store's assets as available to copy.
Agency fees and continuing costs
Separate setup, design, content, integration and training fees from the Salla plan, theme, apps and other services. Identify each subscription, purpose, frequency and renewal owner. You need the actual offer and plan covering your requirements when chosen, rather than prices estimated in an article.
Salla documents administration of plans, extra subscriptions and invoices. Review it during handover: what is active, its current cost and terms, and what stops if a subscription ends? Agency fees do not automatically include every renewal, and purchasing a theme does not automatically include every future change.
External activation needs its own status
For payment, shipping, a domain or system integration, identify accounts, inputs and agency responsibilities. Technical configuration differs from merchant-account acceptance, completed verification or provider approval. Record what is ready, pending or awaiting your decision.
Agree what is delivered when design finishes while external activation remains pending, and how the flow is tested once available. This makes status understandable instead of declaring a store ready to sell before an essential step has been exercised.
Acceptance with the person who will run the store
- The responsible employee edits the sample product and agreed content through appropriate access.
- They open the store on mobile and follow product selection and ordering through an arranged test method.
- They review options and information reaching operations and identify manual handling.
- They inspect the plan/subscription register and service owners.
- They record gaps, resolution timing and exclusions from agreed support.
For the broader order cycle, use the e-commerce scope checklist. For platform selection, read the platform comparison. Discuss Salla store design and implementation with the readiness file so the proposal starts with work you actually need.
Sources and verification date
Salla's documentation on store identity, plans and subscriptions and selling from outside Saudi Arabia was opened on 3 November 2026. It is used as platform guidance without guaranteeing eligibility, prices or agency accreditation. The example and readiness file are original illustrations. The text was prepared with AI assistance and review of its content and sources.
