Custom Software
An online store that fits your catalog, not a template
Off-the-shelf platforms bend your pricing, variants and delivery zones to fit their rules. We build the store around your business instead, with mada and Saudi payment gateways working from day one.
6 to 10
weeks to a launched storefront
2
languages built in from the start
24/7
support once you're live
The direct answer
This is a custom-built online store for businesses whose products, pricing or fulfillment don't fit a generic platform template. If you sell configurable products, run wholesale and retail pricing side by side, or need checkout and invoicing that work correctly for Saudi customers from the first order, this is built for you rather than adapted from someone else's defaults.
What this removes.
Platform checkout doesn't work here
Today
Generic platforms treat mada as an afterthought and fumble VAT-compliant invoicing at checkout.
With the system
Saudi payment methods and ZATCA-ready invoices are built into checkout from the first sale.
Catalog logic doesn't fit the template
Today
Your pricing tiers, bundles or configurable products get forced into a structure that wasn't built for them.
With the system
The catalog model matches how you actually price and sell, not the platform's assumptions.
Arabic is bolted on, not built in
Today
Translation plugins break layout, and RTL pages look like an afterthought to Arabic-speaking customers.
With the system
Arabic and English are both native layouts from the start, checked page by page, not machine-translated.
You're locked into someone else's roadmap
Today
A subscription fee buys you a monthly plan, transaction fees, and no say over what gets built next.
With the system
You own the code and the data. Changes ship on your schedule, not a vendor's release calendar.
What lands in your hands.
Storefront
Arabic and English, built for the products you actually sell.
Checkout and payments
mada, STC Pay and card processing wired to a real gateway.
Invoicing
ZATCA-ready invoice generation on every order, not a bolt-on later.
Admin dashboard
Orders, inventory, pricing and customer data in one place.
Catalog and variants
Product structure built around your actual pricing and options.
Shipping and fulfillment rules
Delivery zones and rates matched to how you ship.
Systems and platforms we work with
- App Store
- Google Play
- Apple
- Android
- iOS
- macOS
- Windows
- Web
Systems and platforms we work with
- React
- Next.js
- TypeScript
- Node.js
- Python
- Flutter
- PostgreSQL
- Supabase
- Tailwind CSS
- Docker
- GitHub
- Google Cloud
- Figma
Five stages. You sign off every one.
Read each stage as a small contract: what we need from you, what lands in your hands, and the sentence that has to be true before we move on.
- Scope and catalog mapping1 to 2 weeks
- Storefront design1 to 2 weeks
- Build3 to 5 weeks
- Testing and launch prep1 to 2 weeks
- Live operation and supportongoing
Scope and catalog mapping
1 to 2 weeks
We map your product catalog, pricing rules and payment requirements before any design work starts.
- Share your product data and pricing rules
- Confirm which payment methods you need
- A scoped feature list
- A catalog data model that fits your products
We move on when the catalog model and scope are signed off in writing.
Storefront design
1 to 2 weeks
We design the Arabic and English storefront together, not one translated from the other after the fact.
- Review layout drafts
- Flag anything specific to how you sell
- Storefront design in both languages
- Checkout flow mapped end to end
We move on when you approve the design for both languages.
Build
3 to 5 weeks
The storefront, checkout, payment integration and admin dashboard get built against the agreed scope.
- Answer questions as they come up
- Test staged builds when asked
- A working storefront on a staging environment
- Payment integration live in test mode
We move on when the store handles a full test order correctly, from browse to invoice.
Testing and launch prep
1 to 2 weeks
We test payments, invoicing, shipping rules and both languages against real order scenarios before going live.
- Run through your own test orders
- Sign off on launch
- A tested store ready for live payments
- A launch checklist
We move on when test orders complete cleanly in both languages with live payment processing.
Live operation and support
ongoing
Once live, we monitor the store and handle fixes, updates and catalog changes as your business needs them.
- Send new requests as they come up
- Flag anything that looks wrong
- 24/7 monitoring
- A direct line for fixes and changes
We move on when we move on when the store is stable and you have a clear channel for ongoing changes.
Asked before signing.
How is pricing calculated for a project like this?
Pricing is scoped against your catalog size, the number of payment methods, and how much custom logic your pricing and fulfillment need. We quote a fixed project price after the scoping stage, not an hourly estimate, so you know the number before build starts.
Can this connect to our existing inventory or accounting system?
Yes, if it has an API or an exportable data format. We've integrated with ERP and inventory tools before, and we'll tell you plainly during scoping if a particular system needs custom middleware and what that adds to the timeline.
Is our customer and payment data handled in line with PDPL?
Yes. Data storage, access controls and retention are built to align with Saudi PDPL requirements, and payment data goes through a licensed gateway rather than being stored on our servers. We'll walk through the data flow with you before launch.
What happens after launch if we need changes?
You own the code, so nothing stops you from taking it elsewhere. Most clients keep us on for ongoing changes and fixes because we already know the system. That's a separate support arrangement, agreed after launch, not bundled automatically into the build price.
Ready to build a store that fits how you sell?
Tell us about your catalog and payment needs. We'll scope the project and give you a fixed price before any code gets written.