Services · Ecommerce development · Queue management subscription sites
Codeeo delivers queue management subscription website development Riyadh software vendors use to turn demos into paying accounts. We build the Arabic first pricing pages, plan builder, checkout, recurring billing and customer account where a hospital group, bank network or government service centre picks its branches and counters, pays by mada or card, receives a ZATCA compliant invoice and sees its queue product switched on, without waiting for a salesperson to email a spreadsheet.
Riyadh is where most national buying decisions for branch networks are made, and our Riyadh team can sit with your product and finance people in person. The site we build sells your existing queue software; it does not replace it.
200+ companies servedFrom a first store to an ADX listed developer
What the subscription site handles
Queue software is rarely bought by a single person. In Riyadh a facilities manager finds you, an IT lead checks security, procurement asks for a quotation and finance wants a tax invoice with the company VAT number on it. A good subscription site serves all four without forcing every deal through a sales call. We build the commercial layer around the product you already run: plans that match how you count value, a checkout that works for a card holder and for a procurement team, billing that copes with branches being added mid term, and a customer account where the client can see what they pay for. Everything feeds your CRM and your accounting system so the same numbers appear everywhere. Small clinics in Al Malaz can buy on a card in minutes, while a ministry or a bank in King Abdullah Financial District can request a quote that converts into the same subscription record once approved. The point is that both routes end in one record, one invoice format and one renewal date.
Buyers choose the number of branches, staffed counters, kiosks and hall screens, then see the monthly or annual total update in Arabic or English. Rules stop impossible combinations, such as more kiosks than your licence tier allows, and add ons like SMS bundles or appointment modules are offered only where they apply. If your sales team prefers to see every lead first, the builder can end in a demo request that carries the configured network into the CRM.
Prospects price their own network before they ever book a call.
Head offices often cannot pay on a card. The site generates a formal quotation with your CR number and VAT details, holds it for approval and converts it into an active subscription once a purchase order arrives, with the agreed terms locked in. Quote validity, discount approval and signatory details are recorded on the account so renewals a year later start from the right figures.
Large Riyadh accounts follow procurement rules without leaving your platform.
Cards and mada are tokenised through a SAMA licensed payment gateway, so renewals charge automatically and your servers never store card numbers. Apple Pay is offered at first checkout where the gateway supports it, and bank transfer remains available for annual invoices.
Renewals collect on schedule with no manual chasing.
When a client opens a new branch in Al Olaya halfway through the term, the system charges only for the remaining days and aligns the new counters to the existing renewal date. Downgrades credit the next invoice rather than refunding by hand. Every adjustment appears as its own line on the next invoice, so a client's finance team can trace why the amount changed.
Expansion is billed fairly and finance does not reconcile by spreadsheet.
Every charge produces a tax invoice in the structure ZATCA requires, with the QR code, buyer VAT number and cryptographic stamp, cleared or reported through the Fatoora platform according to your integration wave. Credit notes follow the same route.
Invoices pass a tax audit without rework.
Failed renewals trigger reminders by email and SMS in the client's language, retries on a schedule you choose and a grace period before features are limited. Queues are never cut off mid service; the account moves to read only after the grace period ends. You decide the message wording, the number of retries and which features pause first.
Fewer lost subscriptions and no hall left without tickets.
Clients add branches, change plans, update payment methods, download invoices and assign billing contacts themselves. Role permissions keep a branch manager from changing the plan that head office approved.
Your support team handles service questions, not admin requests.
A paid subscription calls your product's API to create the tenant, branches and counter licences, and a cancellation or suspension updates them the same way. We agree the contract between the two systems early so neither team guesses.
A client who pays at noon can issue tickets the same afternoon.
Venues and organisers running Riyadh Season attractions or large exhibitions need queues for weeks, not years. Fixed term plans start and end on set dates, can be extended from the account page and close the tenant automatically when the event finishes, with a final invoice issued the same day.
Short engagements become a product line instead of a custom contract.
Monthly recurring revenue, expansion, downgrades, failed payments and cancellations by sector and city, shown in a dashboard or sent to Power BI. Finance sees the same figures as sales.
Decisions about pricing are made on real subscriber data.
Who this is for
The capital concentrates the buyers that matter for queue software: ministries and government service centres, bank and telecom head offices, hospital groups and the venues that run Riyadh Season. The vendors selling to them differ in size and in how much of the sale they want online. These are the situations we see most often, and how the subscription site changes in each. Each one starts from the same question: which part of the sale should a buyer be able to finish alone, and which part needs a person in your team.
You already have customers, but each renewal is a PDF, a bank transfer and a reminder call. We move existing contracts onto recurring billing, import their history and send ZATCA compliant invoices automatically, so the finance person who used to chase payments can spend that time on collections that genuinely need attention. Pilot branches can be priced and billed separately while the full network decides.
Migration of existing subscribers is planned before new sign-ups open.
Your global billing tool may not issue Fatoora invoices, take mada or show Arabic pricing. We build a Saudi storefront and billing layer that sits beside your global stack, keeps Saudi customer data where your compliance team decides and reports revenue back to head office in the format it expects. Head office reporting is mapped during discovery so nobody waits for month end exports.
Data location is decided in discovery with your legal team.
You sell kiosks, ticket printers and screens alongside a software licence. The site handles one off hardware orders and installation scheduling next to the recurring licence, so a client sees a single account and receives separate, correctly classified invoice lines for goods and service. Installation dates are booked from the same account, and the engineer's visit is confirmed by SMS.
Public sector buyers in Riyadh rarely sign up by card. For them the site works as a credible catalogue with clear plans, security documentation and a quotation path, while smaller private clients still buy instantly. One product catalogue feeds both routes. Response documents and certificates sit behind a request form your team approves.
Formal tender submissions stay with your bid team.
How we work together
Most vendors start with a fixed scope build covering the pricing pages, checkout, billing and invoicing, then keep us on a retainer to add plans, payment methods and reports as the business grows. Vendors with a larger roadmap take a dedicated team that also works inside the queue product itself. Because Codeeo has a team in Riyadh, workshops, demos and acceptance testing can happen face to face, with the wider team of 80+ across Dubai, Riyadh and Karachi behind them.
A defined build with a deadline
We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.
A product that keeps evolving
Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.
Something live that needs looking after
A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.
Technology
We usually build the storefront in Next.js or Laravel, run billing on a proven subscription engine or a custom service where your rules demand it, and connect to Saudi payment gateways, the Fatoora platform and your CRM through their APIs. Hosting follows the data location agreed in discovery. Your team receives the documentation and admin access needed to run it without us.
01Web
02Commerce
03Data and cloud
04Marketing and tracking
It depends mostly on billing complexity and your product's API.
A site with card checkout, simple plans and automated invoicing moves faster than one with enterprise quotations, hardware orders and migration of existing contracts. The other variable is your queue platform: if it already exposes an API for creating tenants and licences, provisioning is quick. We agree the order of releases and the dates in writing after discovery, before design begins. Large migrations are usually phased so live subscribers are never billed twice during the switch.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
React
Next.js
TypeScript
Node.js
Laravel
WordPress
Shopify Plus
WooCommerce
BigCommerce
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio