Online Store Platform
A complete online store — storefront, dashboard, and everything in between.
Who it is for: A shop, brand or distributor selling its own products — from a few dozen items to a large catalogue with sizes, colours, branches and staff.
27
Guided dashboard screens
Per variant
Own price, stock and photos
Rule-based
Shipping by weight, value or destination
EN + AR
Bilingual, right-to-left included
In one paragraph
Two parts: a storefront your customers shop in, and a dashboard you run the business from. Both are fully bilingual, and both carry your name, your logo and your colours. A new owner signs in, answers a few questions, and is walked through setup step by step. The catalogue, orders, shipping, returns, payments, wallets and staff permissions were built as one system — not a template with a shop bolted on.
The two sides
Storefront
Browse, search, buy, track, return and review — designed for small screens first.
Dashboard
Catalogue, orders, shipping, money, content and staff permissions in one place.
The decisions behind it
Any platform can list features. These are the three choices that shaped this one, and what each cost us.
- 01
Setup is the product
The problem
Store software loses people before they ever sell anything. The owner signs in, finds an empty dashboard and twenty screens with no order to them, and the project quietly dies at the catalogue import.
What we chose
We treated onboarding as a feature, not documentation. A four-step wizard on first sign-in, a guided tour, then a help centre on every screen with a launch checklist in dependency order — attributes before products, shipping before checkout. All 27 screens carry a one-line summary and at most four steps. It is the single largest piece of non-selling work in the product, and the reason an owner can go live without calling us.
- 02
A variant is a product, not a price modifier
The problem
A shirt in three sizes and four colours is twelve different things. Each has its own stock, its own photographs, and often its own price — the XXL costs more, the white one is discontinued. Modelling that as one product with options is where most catalogues start lying about stock.
What we chose
Every combination carries its own price, scheduled sale window, stock count and images. It made the product builder considerably harder to write and to use, and it is why the storefront can tell a customer that this exact shirt, in this exact colour and size, is out of stock — instead of taking the order and apologising later.
- 03
Shipping is rules, not a price list
The problem
Real delivery pricing is never one number per governorate. It changes with weight, with order value, with which courier covers which area, and with whatever promotion is running this month.
What we chose
Base rates per governorate, then conditional rules layered on top in a priority order the owner sets themselves. More to build and more to explain than a flat table, but it means changing your delivery economics is an afternoon in the dashboard rather than a call to us.
How it fits together
The shape of the system, not its wiring. Every application is built on one shared foundation — the same design system, translations, data layer and components — so a fix lands everywhere at once and the interfaces never drift apart.
What it does
Catalogue
- Define shared traits once — colour, size, material — with real colour swatches
- A category tree with images, as deep as you need
- A guided form for simple products; a full builder for products with variants
- Every variant carries its own price, scheduled sale, stock and photos
- A media library showing every image and where it is used
Selling
- Orders with items, customer, totals and history — process, cancel, refund
- Shipments through their full lifecycle: shipped, delivered, refused, lost, failed
- Customer-initiated returns with photos, and the refunds that follow
- A review moderation queue — nothing appears on your site until you allow it
- Coupons: percentage, fixed or free shipping, with conditions and usage limits
- Scheduled promotional banners you can pause or expire
Shipping & payments
- Branches, one of which is the origin every delivery is calculated from
- Base delivery rates per governorate
- Conditional rules on top — by weight, order value or destination, in your priority order
- The couriers you work with, switched on and off
- Which payment methods appear at checkout, with their fees
Money
- A finance ledger of what the store earned and paid out
- A store wallet with its balance and movements
- Customer wallets you can view and adjust by hand — a refund, a goodwill credit
Your site's look
- A home page built from rows of widgets on a 12-column grid, edited in place
- The same builder for your About page, with ready-made section types
- Policy and information pages that also feed the footer
- Five ready palettes or your own colours — live within seconds
Your team
- Accounts for your staff
- 23 areas of the dashboard granted or withheld per role
- A data-entry employee sees the catalogue but not your finances
- 33 dashboard themes and a sidebar or top-menu layout, chosen per user
- Live notifications for new orders as they happen
Why it is built this way
Set up without a phone call
This is where most store software loses people. A four-step wizard on first sign-in, a guided tour, then a help centre on every screen: a launch checklist in the right order, and a guide for all 27 dashboard screens with a one-line summary, at most four steps, and a button that takes you there.
Bilingual to the core
English and Arabic throughout, with the whole interface flipping to right-to-left. Written translations, not a machine pass — because a store your customers can't read in their own language isn't a store.
Permissions enforced twice
A screen someone may not open isn't shown to them, and the server refuses it as well. Hiding a button is not access control.
Type-checked end to end
The codebase is TypeScript throughout and checked before any build is allowed through, so a change that breaks a contract fails at our desk rather than yours.
Settings take effect immediately
Your name, logo, colours, home page and policies update the live site within seconds. No developer, no redeployment, no waiting on us.
One system, many stores
The same build serves every customer, each with their own domain and data. Nothing about your brand is baked into the software — down to the icon in the browser tab.
Built with
Not standard, but available
There is a live version. Ask us for it.
Both platforms run on staging with real data in them. We don't hand out the link publicly — tell us what you sell and we'll open access and walk you through it, so you see the parts that matter to your business rather than a generic tour.
Usually opened within a day.
Want a walkthrough?
We'll show you the real dashboard, end to end, and tell you honestly what setting it up for you would involve.
Book a walkthrough