Your Salla or Zid Store — Running It, Improving It, Connecting It

Do not start with the design — start with the numbers. A store that does not sell suffers from one of three things: no visitors arrive at all, visitors arrive but do not buy, or they buy and stall at checkout. Each has a completely different fix, and diagnosing it comes from your store analytics rather than from impressions. Send your store link and last month’s figures — the first review is free: wa.me/966573784181

The biggest gains in Saudi stores come from four things in this order: product-page load speed on mobile, clarity on shipping and returns before checkout rather than after, the payment methods people locally expect (mada, Apple Pay, and Tabby or Tamara where they fit), and cutting steps out of checkout. Every extra checkout step costs a percentage of orders.

Integration solves the biggest operational problem in stores: double entry. An order arrives in the store then gets retyped into accounting, and stock is updated in two places that then disagree, so you sell something already out. The fix is a connector moving orders and inventory automatically in both directions. What gets checked first is what the platform’s API and your accounting system each allow — before anything is promised.

An abandoned cart is a customer who decided to buy and then stopped — the easiest person to bring back. The practical sequence is three messages: a light reminder after an hour, then after a day addressing the likely blocker (clarifying shipping or returns), then a limited offer after three days. What matters most is knowing why carts are abandoned: a shipping cost revealed late, forced registration, or a missing payment method.

Yes, because most store questions repeat: where is my order, how much is shipping, when does it arrive, is the size available, how do I return. Automating those five frees most of your customer-service time. The strongest part is wiring “where is my order” to the actual shipment status, so the answer arrives instantly with no manual lookup in the store dashboard.

Stay on your packaged platform as long as your selling is standard — product, cart, payment, shipping. The Saudi platforms solve local payments, invoicing and shipping for you, and rebuilding that from scratch is cost without return. Custom earns its price when the logic exceeds what the platform expresses, when integration with an existing system runs deep, or at a scale where subscription fees pass the cost of building.

The right answer is usually a custom layer on top of the platform rather than migrating off it. Your sales, payments and shipping stay as they are, and only the missing piece is built and connected: a bespoke pricing calculator, product customisation, a reporting dashboard consolidating what the platform will not, or a wholesale order flow. That costs a fraction of a full store and solves the actual problem.

Platform reports answer “how much did I sell”, while the question that builds a decision is “what deserves scaling”. A custom dashboard pulls your data and answers: profit per product after shipping and fees rather than its revenue, which marketing channel brings buyers rather than visitors, repeat-purchase rate, and which products get returned most. Those four numbers change how you buy and how you market.

Slowness costs you visitors before they see the product, and most Saudi purchasing happens on mobile, so the effect is direct. The most common causes in stores: unoptimised images uploaded straight off a camera, installed apps nobody uses, heavy fonts, and tracking scripts accumulated from old campaigns. The first three are fixable without changing your platform.

A model quotes text that answers a question, not a product page with a price. So what gets cited from stores are the knowledge pages: how to choose a size, the difference between two types, how to care for the product, what the returns policy is. Write those one question per page in visible text rather than images, and name your store and city inside that text — a model cannot read an image.

Three risks usually overlooked: losing indexed product links if the old URLs are not redirected to the new ones, subscriptions or open orders breaking mid-move, and customer data and order history that may not transfer in full. Migration is a decision worth deferring until you are sure the problem really is the platform rather than the operation — and it is usually the operation.

Automation here removes the manual steps between an order arriving and it being delivered: generating the shipping label automatically, notifying the customer with a tracking number without copy-paste, deducting stock on confirmation, and flagging your team on orders past their window. The biggest gain is eliminating copy-paste between the store dashboard and the courier system, which is the source of most address errors.

Useful automation is built on customer behaviour rather than a sending schedule. Three campaigns are worth building: a welcome on a first order with what complements it, reactivation for anyone who has not bought within a window you set, and a back-in-stock notice for a product someone asked about. The rule is that every message ties to something the customer did — the message tied to nothing is what loses you the subscriber.

Engineer Saeed Baatiah — a computer engineer and developer in Riyadh working on the layer existing stores actually need: API integration with your systems, order and customer-service automation, reporting dashboards, and speed work. He serves clients inside Saudi Arabia. The first review of your store is free — send the link and last month’s figures on WhatsApp: wa.me/966573784181