Services · Ecommerce development · Procurement subscription sites

Subscription billing for procurement software sold across the Kingdom.

Codeeo provides procurement subscription website development Saudi Arabia software companies need when they sell purchasing, sourcing or supplier management tools to customers in every region. We build Arabic first pricing pages, checkout with Saudi payment methods, recurring billing that meets ZATCA e-invoicing rules, privacy controls under the Personal Data Protection Law, and the account area customers use to manage plans. One platform serves buyers in Riyadh, Jeddah, the Eastern Province and smaller cities on the same rules.

Selling software by subscription in Saudi Arabia means answering to several national bodies at once: ZATCA for tax and invoicing, SDAIA for personal data, SAMA for payments and the Ministry of Commerce for online selling. We build those obligations into the platform, not a checklist on the side.

Built for
Saudi and international procurement software companies selling subscriptions to buyers throughout the Kingdom.
Typical timeline
Defined in discovery, which runs in person in Riyadh or by video call elsewhere, then fixed in a release plan before design.
What you own
All code, hosting, billing and payment accounts, subscriber records, consent logs and the full invoice archive, in your legal entity's name.
Rated
4.7 / 5 from 23 Google reviews

200+ companies servedFrom a first store to an ADX listed developer

Modon
Majid Al Futtaim
HP
Belkin
Dulsco Group
OneClickDrive
Hanayen
HMS
Clocksprings
Ghezlan

What a national platform needs

Built once for the Kingdom's rules, then rolled out city by city.

A procurement software company growing beyond one city quickly finds that its billing has become the bottleneck. Invoices issued by hand, card payments that do not cover mada, privacy notices copied from a foreign template and sales reps in three cities quoting different prices all slow growth. Procurement SaaS website development Saudi Arabia vendors commission from us addresses this at the national level: one plan catalogue, one billing engine connected to ZATCA, one consent and privacy model aligned with the PDPL, and payment methods that Saudi businesses actually use. Regional detail, such as sales territories, local partners and city specific landing pages, sits on top of that shared base. The list below is where most national builds begin; discovery confirms what your first release must include.

Explain your project
  • Arabic first plan catalogue

    Plans, modules, limits and add-ons stored once and published in Arabic and English, with right to left layouts designed first rather than mirrored at the end. Prices, plan names and comparison tables stay identical across languages, so a buyer in Abha reads the same offer as one in Dammam. Marketing staff can publish a new module page without touching billing settings.

    One source of truth for every price your company publishes.

  • Saudi payment methods

    Card payments through a gateway licensed by SAMA, covering mada, Visa, Mastercard and Apple Pay, with STC Bank (formerly STC Pay) where supported. For larger accounts we add bank transfer reconciliation, and SADAD bill payment if your bank enrols you as a biller. Whether mada cards can be charged automatically on renewal depends on your acquirer, so we confirm it early and fall back to a payment link if needed.

    Customers pay with the method their finance team already uses.

  • Fatoora connected billing

    Every renewal, upgrade and refund produces a tax invoice or credit note that meets ZATCA e-invoicing requirements, with QR codes, Arabic content and the buyer's VAT number. The billing system is integrated for clearance or reporting according to the wave your company falls into. Invoice numbering, retention and cancellation follow the same controlled process across every region.

    Tax invoicing stops being a monthly manual task.

  • VAT data capture and checks

    Checkout and the account area collect the customer's legal name, commercial registration and VAT number, validate the format and lock them onto invoices. Treatment of customers based outside the Kingdom is set with your tax adviser and applied automatically.

    Fewer rejected invoices and fewer reissues.

  • Hijri and Gregorian dates

    Renewal dates, invoice dates and contract periods displayed in both calendars where customers expect it, with billing logic running on one consistent calendar underneath so proration and renewals never drift.

    Public sector and traditional buyers read dates the way they file them.

  • Privacy and consent under the PDPL

    Arabic and English privacy notices, consent records for marketing and analytics, and a request process for access, correction and deletion. Data flows to gateways, billing platforms and analytics tools are documented, including any transfer outside the Kingdom, so your compliance lead can review them against SDAIA guidance. Retention periods for invoices, leads and closed accounts are configured rather than left open.

    Privacy questions from customers get documented answers.

  • Verified sign in for customer admins

    Customer admins who control billing can sign in with single sign on from their employer, and where your company is approved for it, verify identity through Nafath. Sensitive actions such as changing the billing owner require a second step.

    Billing control stays with the right person at the customer.

  • Regional sales territories

    Accounts are assigned to territories such as the Central, Western and Eastern regions, with quotes, discounts and commission tracked per rep. Approved discount ranges are enforced in the quote tool, so pricing stays consistent wherever a deal is closed. Partners and resellers can be added as their own territories with separate commission rules.

    National growth without a different price list in every city.

  • Public sector buyer path

    Government entities usually purchase through Etimad and formal procurement procedures rather than online checkout. A dedicated section explains how they can buy from you, offers tender documents for download and routes enquiries to your bid team. Where your product is listed with the Local Content and Government Procurement Authority or holds local content certification, that information can be shown here once you confirm it.

    Public sector interest reaches the people who can respond to it.

  • Renewal and recovery automation

    Advance renewal notices, card retry schedules, overdue reminders for transfer customers and a grace period you control, sent in the customer's chosen language through email and WhatsApp Business messaging. Each reminder links straight to the invoice and a secure payment page.

    Revenue is protected without staff chasing every overdue account.

Who this is for

Four national situations we plan for.

Procurement subscription platform development Saudi Arabia companies ask for depends a great deal on where they start. A Saudi founder scaling beyond the home city, an international vendor opening a Saudi entity and a company selling to both government and private buyers each face a different first problem. These are the four starting points we see most. Whichever applies, the national base described above stays the same.

01

A Saudi vendor moving from one city to several

You built your customer base in one region and now have reps or partners in others. Pricing has drifted, invoices are issued by different people and nobody has a single view of renewals. We centralise plans, billing and reporting, then add territory views so regional managers see their own numbers without seeing everyone else's. Sales leaders also get one renewal calendar for the whole Kingdom.

Centralise first, then add regions.

02

An international procurement SaaS entering the Kingdom

Your global billing platform was not set up for mada, Fatoora invoicing or Arabic documents. We build a Saudi storefront and billing configuration for your local entity, connected to your global systems for reporting, and adapt privacy notices and consent to the PDPL. Your legal and tax advisers confirm the registration side; we build what they decide. Pricing can still be shown in Saudi riyals while your group reports in its own currency.

03

A vendor serving both government and private buyers

Private companies want to buy online; public entities buy through Etimad and tenders. One site has to serve both without confusing either. We split the paths clearly, keep card checkout for private customers and give public sector visitors the information and contact route they need. Reporting shows public and private pipeline separately, which helps when planning bid resources.

04

A company replacing manual billing before an investment round

Investors and auditors want recurring revenue they can verify. If your subscriptions live in spreadsheets, we migrate them into a proper billing engine with invoices, payment records and reports that reconcile, so revenue figures come from the system rather than a slide. Churn, expansion and failed payment reports are ready for due diligence.

Migration with reconciliation reports.

Six stages from national requirements to a platform live in every region.

  1. 01Requirements and obligationsDiscovery covering plans, sales channels and regions, plus the tax, privacy, payment and e-commerce obligations that apply to your entity, reviewed with your own advisers where legal judgement is needed.
  2. 02Commercial modelPlans, add-ons, proration, discounts, territories, payment methods and invoice content agreed in writing, with ZATCA treatment confirmed by your tax adviser.
  3. 03Arabic first designPricing, checkout, account and public sector pages designed right to left first, tested with Arabic readers, then mirrored into English with the same structure.
  4. 04Platform buildSite, billing engine, gateway, ZATCA integration, CRM and accounting connections built in short releases, each demonstrated on staging and signed off by your team.
  5. 05Compliance and billing testsFull subscription lifecycles tested, from signup to refund, with invoices validated, consent records checked, data flows documented and security controls reviewed before launch.
  6. 06Phased regional rolloutLaunch in your strongest region first, migrate subscribers in batches, then open further regions and partners once the first renewal cycle has run cleanly.

Technology

What we build this with.

We select a billing platform when your plans fit its model and write custom billing logic when they do not. Front ends use fast, bilingual frameworks such as Next.js. Hosting is chosen with the PDPL, NCA controls your customers require and their data residency questions in mind.

01Web

  • React
  • Next.js
  • TypeScript
  • Node.js
  • Laravel
  • WordPress

02Commerce

  • Shopify Plus
  • WooCommerce
  • BigCommerce
  • Headless storefronts

03Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

04Marketing and tracking

  • GA4
  • Google Tag Manager
  • Search Console
  • Meta Pixel
  • Looker Studio

National questions about subscription sites for procurement software.

Tax, personal data, payments and e-commerce rules all apply.

ZATCA sets VAT and e-invoicing requirements, including the Fatoora integration phases. The Personal Data Protection Law, overseen by SDAIA, governs how you collect and use personal data. Payments run through providers licensed by SAMA. The e-commerce law and Ministry of Commerce rules cover selling online, and many customers ask suppliers to meet NCA cybersecurity controls. We design the platform with all of these in view and ask your advisers to confirm anything that needs a legal opinion. Rules change over time, so the platform is built to make updates to invoice content, notices and consent text a configuration task rather than a rebuild.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews