The problem we solve
The recurring problem is leakage, not looks. Customers reach the cart and disappear at payment. Items sell that were never in stock, because the store has no reliable view of inventory. Staff spend their day re-keying orders into accounting software and courier portals. Layered on top is a stack of plugins added over the years that slows every page, and nobody remembers which of them are still needed. The result is a store that looks finished but costs more to run than it returns, which is why we rebuild the path from order to delivery rather than fitting a better interface over broken operations.
Expected outcomes
- A shorter, clearer checkout that removes the usual reasons for abandoning a cart.
- One trusted stock figure shared by the store, your branches and any other channel.
- Orders reaching shipping and invoicing without anyone re-typing them.
- Product pages that load quickly and can be crawled and indexed properly.
- Your team launching offers, bundles and coupons without a developer in the loop.
- A single view of how products and channels are performing, instead of scattered reports.
Who this is for
- Consumer brands selling across scattered channels that want a store they own.
- Wholesalers who need an ordering portal with account-level pricing and terms.
- Merchants who have hit the customisation or cost ceiling of a closed platform.
- Operators building a platform where several vendors or providers sell side by side.
- Companies with a warehouse and an accounting system that need a store talking to both.
Use cases
- Launching a retail store with variants, sizes, options and bundles.
- Building a multi-vendor marketplace with vendor dashboards and commission settlement.
- A wholesale ordering portal with contract pricing, credit terms and fast entry by product code.
- Migrating from a hosted platform to an owned store, carrying products, customers and order history.
- Adding subscriptions or digital goods alongside physical products.
- Connecting an existing store to inventory and courier systems to end manual entry.
Deliverables
- A live bilingual store or marketplace with a complete admin for your team.
- A published catalogue with products, variants, imagery and pricing.
- Documented payment, shipping and inventory integrations, with credentials handed to you.
- Funnel reporting that shows where orders are being lost.
- Written operating procedures for fulfilment, cancellation and refunds.
- A recorded training session for the people running the store day to day.
- Source files and service accounts in your company name.
Project phases
Discovery and operations mapping
Catalogue audit, pricing, shipping and returns rules, and a map of the order path from receipt to delivery.
Buying-path design
Product, cart and checkout screens designed mobile first, addressing the known points of hesitation.
Store build
Catalogue, search, customer accounts, cart and checkout with full Arabic and English support.
Integrations
Payments, couriers, inventory and invoicing, each verified with a real transaction on staging.
Migration and testing
Products, customers and order history moved across, then performance, device and full-path testing.
Launch and stabilisation
A monitored launch, close attention to the first orders, and fixes during the follow-up window.
- Estimated timeline
- 8 to 16 weeks
- An estimate that depends on scope and how quickly reviews come back — not a contractual commitment in itself.
- Pricing
- After scoping
- Scope depends on catalogue size, the number of integrations required, and whether the platform serves one seller or many. We send a scoped proposal after the discovery session.
Scope and working details
What is in and out of scope, how we work, and what we need from you.
What is included
- Discovery covering your catalogue, pricing rules, shipping and returns as they operate today.
- Buying-path design from landing page to order confirmation, mobile first.
- Catalogue build: categories, attributes, variants, search and filtering.
- Payment integration covering cards, local debit schemes, digital wallets and deferred payment options.
- Courier integration with rate calculation before checkout and shipment tracking.
- Inventory and e-invoicing connected to your systems or to your invoicing provider.
- Tax rules, invoice templates and order notifications in Arabic and English.
- E-commerce event tracking so you can see exactly where the funnel leaks.
- Full order-path testing on staging using real test transactions.
- Data migration from your current platform, launch, and redirects for old URLs.
What is not included
- Product photography and writing the entire catalogue copy — we supply the template and load an agreed sample.
- Negotiating with payment providers or couriers, or opening merchant accounts on your behalf.
- Compliance certificates or tax sign-off — we integrate with the invoicing provider you already use.
- Day-to-day merchandising, fulfilment and customer service after launch.
- Paid media and marketplace advertising management, which is a separate engagement.
How we work
We start with operations rather than screens: how an order reaches you today, who picks it, and where it usually goes wrong. The buying path is designed and tested against real cases from your business before code is written. Delivery is staged — catalogue first, then checkout, then integrations — and you place genuine test orders on staging at every stage. Before launch we walk the whole order path with your operations lead, step by step.
What we need from you
- A catalogue export with product codes, pricing and current stock levels.
- Payment and courier accounts in your company name, or authority to complete registration.
- Your shipping, tax and returns rules as they are actually applied, not as written.
- Product imagery, or approval to launch with what exists while photography catches up.
- An operations owner who will place test orders with us before launch.
Methodology and technology
WordPress with WooCommerce where that architecture suits the catalogue and the way you sell, on a lightweight custom theme rather than a page builder. For large catalogues and multi-vendor platforms we build a separate front end over an API-driven back end, because commission and settlement logic goes past what off-the-shelf extensions handle cleanly. Integrations run through documented APIs using queued, retryable jobs, so an outage at a gateway or courier does not quietly lose an order. For dropshipping stores we connect products and orders to AliExpress through its developer APIs. Measurement through Google Analytics and Google Tag Manager with e-commerce events.
From our work
Lavin Fashion: a complete commerce system, built from scratch
Store, app, AI shopping assistant, automation and supplier links, for a company our owner is a partner in.
How this connects to the rest of our work
A service rarely works alone. These come before it or alongside it, and these are the solutions it forms part of.
Services that work with it
Corporate Website Design & Development
A fast bilingual corporate site that turns visitors into enquiries — and that your team can edit.
APIs and Systems Integration
Documented APIs and an integration layer that keeps your systems in step — and alerts you when it cannot.
Conversion Rate Optimization
Research and testing that find where visitors drop out and turn existing traffic into more revenue.
Part of these solutions
Frequently asked questions
Should I move off my current platform, or stay on it?
Staying is sometimes the right call. We look at what the current setup actually costs: platform fees, the monthly hours lost to manual work, and the things you cannot do because the platform will not let you. If the constraint is customisation or integration with your own systems, moving pays for itself. If the store works and the real problem is content or acquisition, we will tell you that and save you a project.
What happens to my existing orders, customers and history?
We migrate products, customer accounts and order history as far as the current platform allows them to be exported, and we show you what came across and what did not before launch. The old store stays live until reconciliation is complete, and every old product and category URL is redirected so you keep the search visibility you have built.
Can you connect the store to our accounting and warehouse systems?
Yes, provided those systems expose an API or a regular file exchange. We verify that during discovery rather than promising it up front. Where no interface exists, we propose realistic alternatives such as scheduled synchronisation or a middleware layer, and we are explicit about the cost and the limits of each.
How much manual work is left for my team after launch?
The aim is that only judgement stays human: pricing, promotions, exceptions. Passing the order to the courier, adjusting stock, issuing the invoice and notifying the customer are automated within scope. Anything that cannot sensibly be automated is written up as a procedure, so it does not live in one person head.
What tends to break after launch, and how do you handle it?
Most incidents originate outside the store: a gateway timeout, a change at the courier, a conflict after an update. That is why integrations are built as retryable, logged jobs, with alerts that reach us before a customer complains. Every project includes a post-launch window, and after that you can continue on a monthly support package.
Why is there no fixed package price?
Because cost is driven by your commercial rules, not by page count: how prices are calculated, how shipping is split, and how many systems the store has to speak to. A simple catalogue with one gateway is a different engagement from a multi-vendor platform with settlement. We scope it in discovery and then send an itemised proposal.