Services · Ecommerce development · Customer loyalty subscription sites

Billing sites for loyalty software that fit how Jeddah merchants trade through the year.

Codeeo works on customer loyalty subscription website development in Jeddah for companies that sell rewards, stamp card and member retention software to the city's restaurants, cafés, perfume shops, abaya boutiques and hotel outlets. We build the plan pages, sign up, recurring billing on mada and cards, Arabic tax invoices and the merchant portal. Jeddah trade rises and falls with Umrah traffic, summer, Ramadan and Jeddah Season, so your subscriptions need to flex with those cycles instead of losing merchants every quiet month.

Our team works from Dubai, Riyadh and Karachi, so discovery, design reviews and sprint demos for Jeddah clients run by video call, with shared prototypes your sales and finance staff can test between sessions.

Built for
Loyalty and rewards software vendors based in Jeddah, and vendors elsewhere whose merchants are concentrated along the Red Sea coast.
Typical timeline
Set in writing after discovery calls, when plan structure, gateway choice and the number of merchants to migrate are clear.
What you own
Source code, plan catalogue, payment gateway account, Fatoora credentials, merchant data and invoice archive, all in accounts registered to your company.
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 we put into the site

Billing that bends with the season and still invoices correctly.

A loyalty vendor selling to merchants in Al Rawdah, Al Zahra or the historic Al Balad district faces a pattern most global billing tools were never designed for. A café near the Corniche may run its loyalty campaigns hard through winter and Ramadan, then want to scale down when families travel in summer. A perfume retailer near the airport may serve pilgrims passing through and need extra message credits for a few weeks. If the only choices are pay in full or cancel, many of them cancel.

We design the subscription model around those rhythms: pauses, seasonal add ons, prepaid credit packs and plan changes that take effect cleanly. All of it still feeds one billing record, one ZATCA invoice trail and one set of entitlements inside your loyalty product, so finance and support work from facts rather than exceptions noted in a spreadsheet. Each item below is scoped against your own plans and merchant mix during discovery.

Explain your project
  • Pause and resume plans

    Merchants can pause a subscription for a set period from their portal, keeping their member data and settings but stopping campaign sends. You choose the rules: how long, how often, whether a reduced holding fee applies, and what happens automatically when the pause ends.

    Seasonal merchants stay on your books instead of churning in summer.

  • Campaign credit packs

    SMS, WhatsApp and push message credits sold as one off packs on top of a plan, bought in the portal and paid instantly. Credits appear in your loyalty platform as soon as payment clears, with usage visible to the merchant.

    Busy weeks earn extra revenue without a plan change.

  • Plan pages in Arabic and English

    Clear comparison tables written for owners of small and mid sized businesses, Arabic first with right to left layout, plus an English version for the many Jeddah businesses run by managers from other countries. Every plan names its limits plainly: branches, members, credits, integrations.

    Owners pick the right plan without a call.

  • Reseller and POS dealer accounts

    Many Jeddah merchants buy software through the dealer who installed their tills. We add partner accounts that can sign up merchants, see their status and earn commission, while billing and invoices still come from your company.

    Dealers sell your product without you losing the billing relationship.

  • Card, mada and Apple Pay collection

    Payments run through a SAMA licensed gateway, with mada and international cards, and Apple Pay where enabled. We test stored card renewals on mada with your gateway early, because support for merchant initiated charges varies between providers.

    Renewals succeed on the cards local merchants actually carry.

  • Fatoora invoices and credit notes

    Pauses, credit pack purchases, prorated changes and refunds each generate the correct Arabic tax document, reported or cleared through ZATCA. Merchants download them from the portal at any time.

    Unusual billing events still produce clean tax records.

  • Smart retry and reminders

    Failed payments retry on a schedule that avoids weekends and month end pressure, with reminders by email and WhatsApp. During a grace period the merchant's members keep earning points, so their customers never notice a billing problem.

    Recovered revenue without damaging the merchant's own customers.

  • Group accounts for multi outlet owners

    Many Jeddah families own several restaurant or retail brands under one holding company. A group account lets the owner manage every brand from one login, choose whether each brand is billed separately or together, and move branches between brands without cancelling anything. Invoices still show the correct legal entity and VAT number for each brand.

    Family groups manage every brand in one place and see one clear bill.

  • Usage dashboard for merchants

    A clear view of members enrolled, credits left, branches active and next renewal, so the merchant can see what they are getting for the subscription before renewal day arrives. Monthly summaries by email, in Arabic or English, remind owners how many repeat visits the programme drove, which is the strongest argument you have against cancelling.

    Merchants who see value renew more readily.

  • Entitlement sync and reconciliation

    Every billing event updates your loyalty platform through its API, and a nightly job compares both systems and flags mismatches for your support team before a merchant complains. Support staff see the full billing history next to the platform record, so most queries are answered in one screen.

    No merchant runs on features they stopped paying for, or loses ones they paid for.

Who this is for

The Jeddah vendors this approach suits.

Jeddah has a dense mix of independent food and beverage brands, family owned retail groups, hospitality outlets and import traders, and loyalty software companies serving them tend to share the same billing problems: lumpy demand, dealer led sales and merchants who need convincing at every renewal. These four situations come up most often. If your product is still finding its first paying merchants, we would usually suggest a simpler setup first and build the full platform once pricing settles.

01

A vendor losing merchants every summer

Your churn spikes when school holidays empty the city and merchants cut costs. A pause option, cheaper off season tier or credit based plan can keep those accounts alive. We design the rules with you, model what they do to revenue, and build them so merchants can act on their own from the portal rather than asking your team for a favour. Once the rules are live, the revenue report shows how many paused accounts came back, so you can judge whether the option is doing its job.

We test any pause rule against last year's churn before building it.

02

A company selling mostly through POS dealers

Installers and dealers across the city recommend your product when they set up a new restaurant. Right now commissions are tracked by hand and dealers cannot see which merchants they signed. A partner area with referral links, merchant status and commission statements gives dealers a reason to keep recommending you, and gives you clean data on which channel performs. Dealers can also be given limited support views, so they handle first line questions from merchants they installed without seeing billing details.

03

A hospitality technology firm adding paid loyalty

You already sell guest management or ordering software to hotels and restaurants around the Corniche and Obhur, and loyalty is a new paid module. We add the module to your existing customer accounts with its own plan options, so hotel groups can switch it on for some outlets and not others, and see it on one invoice. Hotel finance teams often need cost centres per outlet, so we add those fields to invoices and to the portal's export.

04

A vendor whose merchants serve pilgrims and visitors

Merchants near the airport, in Al Balad and on the routes towards Makkah see heavy visitor traffic in Ramadan and the Umrah months. They want larger message volumes and multilingual campaign templates for a few weeks. Short term add ons, billed and invoiced correctly, turn that demand into revenue for you. Campaign templates in Arabic, English, Urdu or Bahasa Indonesia can be sold as part of the add on, if your platform supports them, so merchants reach visitors in a language they read.

Add ons expire automatically, so nobody is billed for them by mistake.

Six stages from first call to a live Jeddah billing site.

  1. 01Discovery by video callSeveral focused calls with your founders, finance and sales to map plans, seasonal patterns, dealer arrangements and how merchants pay today, with notes shared after each session.
  2. 02Pricing and rules modelWe write the billing rules in plain language, including pauses, credit packs and dealer commission, and agree them with your accountant before design.
  3. 03Prototype with real merchantsClickable plan pages and portal screens in Arabic and English, tested remotely with a handful of your existing Jeddah merchants.
  4. 04Build in reviewed sprintsSite, billing, gateway, ZATCA reporting and platform sync built in short cycles, each shown live on a staging site you can click through yourself.
  5. 05Merchant migrationExisting accounts imported with their plan history, then invited to save a payment method, with a support script for your team. Merchants who never respond are flagged for a phone follow up rather than cut off on renewal day.
  6. 06First season reviewAfter the first busy period and the first quiet one, we review pauses, credit sales and churn, then adjust plans, pause rules and messaging using what both periods showed.

Technology

What we build this with.

Stack choices follow your product and team. A typical setup pairs a Next.js or WordPress front end with a subscription billing engine, a SAMA licensed gateway, a Fatoora integration and APIs into your loyalty platform and CRM.

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

What Jeddah loyalty software companies ask us.

It is set after discovery, based on billing rules and integrations.

Simple monthly and annual plans with one gateway take less time than a model with pauses, credit packs and a dealer channel. Gateway onboarding and the ZATCA integration route also affect the schedule. We send a written plan with stages after discovery, and the plan pages can often go live before the full portal is complete, so marketing can start collecting sign ups. Planning the launch around your merchants' calendar also helps: going live just before Ramadan, when restaurants are busiest, is rarely a good idea.

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