Dubai · UAE Accepting select growth mandates EN / AR · GCC
Solae Global

Home  /  Field guides  /  Websites & E-commerce

Field guide · Websites & E-commerce

The Field Guide to Building the Store Yourself

The sequence we work in, the decisions that are expensive to reverse, and the five patterns we are most often called in to repair. Written so that a careful owner could follow it without us.

Free to read — no formAbout 4 minutesComplete edition as a PDF

Foreword

Written to be used.

Some readers will finish this document and decide to build and run the store themselves. That is a good outcome, and we would much rather it happened before a fee than after one. The tools have genuinely improved: an attentive owner with a modern platform and a capable assistant can now get further, faster, than a small agency could a few years ago.

What follows is the order we work in and the reasoning underneath it, written plainly. Nothing has been withheld to make the work look harder than it is. Where a decision is genuinely reversible we say so, and where it is not we say that too, because knowing the difference is most of what experience actually buys.

The whole of it

You can generate the work. You cannot delegate the outcome.

Start here

What you can genuinely do yourself.

Decision
Can you run this store yourself?
Yes, run it yourself Small catalogue, single location, single language, card payments
  • A store that looks properly made
  • The content layer, edited into voice
  • Imagery prepared at catalogue scale
Yes, with discipline You enjoy the building; early orders teach most
  • Standard integrations, wired from documentation
  • Your own numbers, read honestly
  • Which decisions are reversible, which are not
Not on your own Catalogue, languages or fulfilment outgrow a single owner
  • A catalogue where one decision changes reporting
  • Arabic built alongside, never fitted over
  • Rules that cannot be quietly reversed
And the honest one

If you sell a small catalogue from one location, in one language, to customers who pay by card, and you enjoy the building, run it yourself. Your first few hundred orders will teach you more than any firm can, and the fee is better spent on stock and photography. Come back when the catalogue, the languages or the fulfilment stop fitting inside one person's head.

The limit

Where the general answer stops being useful.

Not because it is wrong. Because it is general, and this is a contested problem against named competitors who were handed the same advice.

At a glanceWhere a general answer stops
You askWhat comes backWhat the decision turns on Build me a store for the UAETheme, page structure, apps, draft copy, checklistWhether a size is a variant or a separate product Write my descriptions in English and ArabicFluent copy in both, Arabic a native reader acceptsAttribute values translated once as data, never per description How do I improve checkout conversion?Guest checkout, fewer steps, trust signals, faster pagesPayment attempted split from authorised, and where acquiring sits
The prompt

“Build me a Shopify store for a skincare brand selling in the UAE.”

All of it correct and none of it wrong. It is describing a store, rather than yours.

What the decision requires

The first decision is not the theme, it is the product model: whether a 30ml and a 50ml are two variants of one product or two separate products. That single choice propagates into your filters, bundle pricing, shopping feeds, accumulated review counts, returns line-items and every URL you own, and reversing it after launch breaks the links and reviews you have already earned. Decide it against how you intend to discount and how you intend to report margin, not against how the product page happens to look.

The prompt

“Write my product descriptions in English and Arabic.”

Correct as prose. The difficulty is that most of what needs translating is not prose.

What the decision requires

Arabic commerce is an information-architecture problem before it is a language problem. Attribute values — colours, materials, sizes, fragrance families — must be translated once, as data, never per description, or the Arabic filters fragment: ivory rendered three ways becomes three colours, and a customer filtering by it is shown a third of your catalogue. Beyond that, Arabic buyers search in a plainer register than marketing copy is written in, and the words they actually type are usually shorter and more literal than the translation you would be proudest of.

The prompt

“How do I improve my checkout conversion rate?”

Every item true and worth doing. It is also the list your competitors worked through last year.

What the decision requires

In this region the loss usually sits below the interface. Split your funnel between payment attempted and payment authorised: a card declined at the issuer, or a 3-D Secure code that never arrives on a roaming or eSIM number, is invisible in most analytics and looks identical to a customer changing their mind. Authorisation rates also move with where your acquirer and merchant of record are domiciled, since a locally acquired transaction clears more dependably than a foreign-acquired one. That is a commercial arrangement rather than a design change, and it moves more revenue than any button ever will.

The pattern

What a year of doing it alone usually looks like.

ChainHow it goes wrong
The decision takenWhat you see laterWhat it costs to undo
  • Redirects mapped section to sectionEarned addresses resolve to a homepageA complete old-to-new inventory, rebuilt after the fact
  • A translation layer over finished EnglishMirrored layout, English filters, addresses sharedSeparating them properly means going back to the catalogue
  • Every app small and justified separatelyProduct page loaded with third-party scriptsFast on the founder's laptop, slow on customers' phones
  • Store, point of sale and spreadsheet disagreeAn oversell, cancelled by handRefund is the small part; the customer never returns
  • Sale price entered over the originalFeeds report a price movement that never happenedMargin history cannot be reconstructed; evidence gone
The working order

If you run it yourself, run it in this order.

FlowThe working order
  1. Before designWrite the order lifecycle downMost trouble is a state nobody decided, found too late
  2. Early onModel the catalogue before the themeEvery filter, feed and report depends on that vocabulary
  3. Before the buildSettle commercial rules in writingThese are checkout architecture; changing them later rebuilds the flow
  4. During the buildBuild Arabic in parallelFitted afterwards, it means going back to the catalogue
  5. Before launchMigrate, redirect, set a weight limitRedirects are proved against a full inventory of old addresses, never sampled
  6. After launchInstrument, then correctFirst corrections are to data and commercial rules, not design

No one can guarantee AI answers — we improve the signals that earn them.

The architecture

Six workstreams, drawn as one machine.

A store works when six things are true at the same time.

SystemSix workstreams, one machine
iCatalogue architectureModels what is a product and what varies
iiThe order lifecycleEvery state an order reaches, named and instrumented
iiiBilingual by constructionArabic composed alongside English, with its own addresses
A store that holds
ivSpeed on real devicesWeight budget enforced after launch, not only before
vTrust, tax and complianceVAT, invoicing and returns settled before the build
viMachine-readable commerceSame facts reshaped for feeds, engines and assistants
The complete edition

What the PDF adds to this.

  • The six workstreams in full — what each one actually contains, not just what it is called.
  • One line item opened into twelve decisions — the part that decides the result.
  • The shape of a mandate — scope, cadence and what the work honestly asks of you.
  • The written argument behind every diagram on this page, in full.
Complete edition · PDF The Field Guide to Building the Store Yourself Sent to your inbox. We ask who you are because it tells us which brands are working on this — nothing more.
If you would rather not

Run it yourself.
Or hand it to someone whose name is on the result.

The tasks became cheap; who answers for the number at the end of the quarter did not change. We will tell you honestly if you are not a fit.

Request a Growth Audit
Read by the founderReply within 2 working daysPrivate always
Find where your growth is leaking. Request a Growth Audit