We build D2C platforms, loyalty engines and omnichannel commerce software for retail, FMCG, beauty, F&B and hospitality brands across the UAE. Our Dubai-based engineers ship Arabic-first storefronts, integrate Tabby and Tamara correctly, and have launched products that survive White Friday and Ramadan traffic.
Commerce software has two audiences: the customer at checkout who needs it fast, and the ops team who needs every order, return and refund traced. We build for both from sprint one.
Most engagements pair one platform build with two or three add-on services.
Arabic-first storefronts on Shopify, Medusa or Saleor, wired to your POS, ERP and delivery partners.
Points, tiers, referrals and member-only pricing with real-time balances your stores trust.
Two-way sync between web, app and store. Stock, prices and orders never drift apart.
One unified profile across web, app, store and call centre. Built on Segment, BigQuery and Postgres with consent and audit tracking.
Stock, shipments and supplier data in one view. Replenishment alerts before shelves run empty.
Algolia-backed search, Arabic-aware ranking and recommendations that lift basket size honestly.
These are ranges from real engagements. We measure them because retainers depend on them.
Default target for the storefronts we ship, on standard cloud (AWS Bahrain or Dublin).
Web, app and store see the same stock within seconds, not the next morning. Oversells drop to near zero.
From kickoff to a live storefront with payments, BNPL, delivery and Arabic content for a new GCC country.
Where the program rebuild ships properly. Members earn, redeem and care, not just sign up at the till.
We pick stacks proven on real storefronts. Fast where it matters at checkout, low-overhead everywhere else.
Next.js and React for web, React Native for app. Arabic-first layouts, image CDN, and Core Web Vitals measured in CI.
Shopify for speed-to-market, Medusa or Saleor where you need full control. Stripe, Tabby and Tamara wired with retries and idempotency.
Postgres for orders and customers, BigQuery for analytics, Algolia for search. Segment for events, dbt for the models marketing actually reads.
POS, ERP, WMS and delivery (Talabat, Careem, Aramex) on a normalised internal protocol so swapping partners is not a rewrite.
AWS Bahrain or Dublin for UAE-region work. Terraform, Datadog and PagerDuty for the operational layer.
Pricing shared openly during scoping. Smallest engagement starts around the cost of one senior in-house hire.
A two-week review of your storefront, data flows and integrations before peak season or a market launch.
Brands preparing for White Friday, Ramadan, or a new GCC market entry
A senior pod shipping storefront, loyalty and integration features alongside your team each sprint.
Retail and FMCG brands launching D2C, new markets, or rebuilding loyalty
We own your storefront, integrations and data pipelines on a monthly retainer.
Live brands past launch who want one steady partner for commerce engineering
Commerce platforms live or die by a few decisions made in the first quarter. We focus there and leave clever for the recommendations layer.
Checkout webhooks, payment callbacks and delivery confirmations can arrive twice. Our pipelines treat re-delivery as normal, so customers never get double-charged or double-shipped.
Stock is held the moment a customer adds to cart, with a short timeout. Oversells during a flash sale stop being a daily ops fire.
One profile per shopper across web, app, store and call centre. Email, phone and loyalty ID resolved to a single record before marketing or ops touch it.
-- Row-level tenant isolation.
-- One schema, many tenants, zero "where did this data leak from" tickets.
ALTER TABLE invoices ENABLE ROW LEVEL SECURITY;
CREATE POLICY tenant_isolation ON invoices
USING (tenant_id = current_setting('app.tenant_id')::uuid);
-- Application sets the tenant for every connection.
-- If we forget, the query returns zero rows, not someone else's.
SET LOCAL app.tenant_id = '8f3a-...-c1';
SELECT id, amount_cents, status
FROM invoices
WHERE status = 'pending'
ORDER BY created_at DESC
LIMIT 25;
An example of tenant isolation we apply to per-brand and per-market storefronts. The same principle underpins our segregated customer data pipelines.
Walk the store and the warehouse (literally or remotely), read the orders and returns logs, talk to merchants, ops, marketing and CX. We listen for the breaks that always happen during peak hours.
Milestones, risks, and what we would do first. Including the work we would recommend you do not do before peak season.
Our senior pod is in your repos shipping production features. Your team owns the merges, we own the cadence.
Measured against the outcomes we agreed on. The people who start with you are the same people in month six.
SKIMBOX rebuilt our D2C checkout and loyalty engine in one quarter. Our White Friday stopped being a fire drill, and active loyalty members more than doubled within six months.
Manual reconciliation replaced by real-time inventory sync.
Customers now finish payment in a single attempt.
Across two peak seasons since we rebuilt the inventory layer.
Yes. We build invoicing and tax flows that handle UAE VAT, e-invoicing readiness and cross-border GCC sales. We work alongside your finance team, build the audit trails inspectors actually look for, and rehearse the reg-change motions before they happen.
Tell us what is slipping at checkout, what is breaking in ops, and what your trading team is bracing for next peak. Written plan in two weeks, or an honest 'we are not the right team'.