Food delivery app development Saudi Arabia projects are bigger than they look: a food delivery app for Saudi Arabia is three apps and one control room, not one app. Customers order, restaurants accept and prepare, drivers collect and deliver, and an operations team keeps all of it moving. The part that decides whether it works is not the code. It is whether you can pay people reliably through mada, speak to customers in Arabic that feels natural, and open one city at a time with enough drivers and restaurants to make the first order arrive hot.
This guide explains how apps in the style of Jahez and HungerStation work, what you need to build, how mada and the other local payment methods fit in, what the transport rules mean for your drivers, and how to plan a rollout from Riyadh to the next city. Our team uses those two names only as examples of a model, and in our experience the first questions founders ask are about payments and drivers, not features. We say what apps of this type typically include, not private facts about either company. A fact sheet with outside sources is at the end.
Planning a food delivery app for the Kingdom? Tell us your city, your cuisine focus and your launch date and we'll reply with a scoped plan. Share your idea on the contact page or see our mobile app development in Saudi Arabia.
Our take: Start with one district, not one country. A hundred orders a day in a single neighbourhood teaches you more than ten orders a day in five cities, and it's the only way to find out whether your drivers, restaurants and delivery times actually work.
The market you are walking into
Food delivery in Saudi Arabia is large, crowded and watched closely by regulators. Some numbers help set expectations, though you should treat all of them as snapshots.
- Jahez's chief financial officer said in 2025 that licensed delivery platforms processed about 290 million orders in 2024, with Jahez handling 91 million of them, which he put at roughly 32% of the market by the Transport General Authority's data.
- For the first nine months of 2025, Jahez reported about 68.7 million orders at an average order value of around SAR 63.
- Keeta, a newer entrant, began operating in Saudi Arabia in September 2024. Press reports say it passed 150 million orders in 2025, though that figure comes from secondary coverage.
- HungerStation, owned by Delivery Hero, does not publish detailed Saudi operating data. Reports say its HungerStation Plus subscription passed 10 million subscribers, which shows how far loyalty programmes have gone.
What this tells a newcomer is simple. The big names have scale, subscription programmes and restaurant relationships built over years. You will not beat them on breadth. You win, if you win, on focus: a city or region they serve thinly, a cuisine or occasion they handle badly, a group of restaurants that want a fairer commission, or a business model such as group orders for offices or catering for events. Pick your wedge before you pick your features.
How this kind of app works
An order flows through four parties.
- The customer browses restaurants nearby, builds a basket, pays and tracks the order.
- The restaurant receives the order on a tablet or app, accepts it, sets a preparation time and marks it ready.
- The driver gets a job, goes to the restaurant, collects, delivers and confirms.
- The operator (you) sets up restaurants and menus, watches live orders, handles problems and settles money.
The platform earns mainly from commission on each order, plus delivery fees and, in time, advertising and subscriptions. The trick is that every party must be happy at once. A customer who waits forty minutes blames the app. A restaurant that loses money on commission leaves. A driver who waits twenty minutes at a counter stops accepting jobs. A good product design reduces those waits and makes them visible.
If you want the same model explained for the UAE, read our guide on how to develop a food delivery app in the UAE. Many of the foundations are shared. This article covers what is different in Saudi Arabia.
Choose your model before you build
There are three common ways to run a delivery business, and the choice changes your costs, your rules and your software.
Marketplace with its own drivers
You list restaurants, you take orders and you also supply the riders, either employed or through a licensed logistics partner. You control the experience and the delivery time, and you carry the cost and the regulation.
Marketplace with restaurant drivers
Restaurants deliver with their own staff. You provide the ordering and payment layer. This is cheaper to start and lighter on licensing, but you have less control over speed, and quality varies by restaurant.
Hybrid with a third-party fleet
You hand deliveries to a licensed logistics company through an API. This is faster to launch than building a fleet and keeps you within the rules if the partner is licensed. Dispatch quality depends on the partner.
Many successful operators start hybrid in one city, learn the economics, then bring delivery in-house where the volume justifies it. Whatever you choose, the transport rules below apply to who may carry the food.
Source: Arka Softwares delivery process.
Saudi Arabia: the rules that shape your product
We are developers, not lawyers, so take advice from a Saudi lawyer and confirm current rules with the regulators. Here is what we understand from public sources.
Delivery licensing and drivers
The Transport General Authority (TGA) regulates delivery through apps. Its executive regulations bar delivery activity without a licence and, as reported, limit it to establishments licensed for goods transport and to Saudi individuals who operate their own vehicles. Affiliated drivers need a valid driver card, and individual Saudi drivers need a driving licence and a certificate of no criminal record. Reports also describe a phased requirement for non-Saudi drivers to work through licensed light-transport companies, a required uniform and a face-verification feature linked to the TGA system. In October 2024 the TGA paused new licences for app-based motorcycle delivery while new rules were prepared, and we could not confirm when that pause ended.
What this means for your software:
- Your driver app needs identity and document capture, with a way to check licence validity and expiry.
- You need to record which licensed entity each driver works under.
- You may need face verification at sign-in and at the start of shifts.
- Your admin panel needs a compliance view: who is active, whose documents are expiring, and an audit trail.
- If you use a third-party fleet, you need proof that the partner holds the right licence.
Personal data
The Personal Data Protection Law (PDPL) became fully enforceable in September 2024, with implementing regulations issued by SDAIA in 2023. A food delivery app collects names, phone numbers, addresses and live locations, so it is squarely in scope. Plan for clear consent and privacy notices in Arabic, purpose limits, retention rules, a way to honour access and deletion requests, and a breach process. Reported rules include notifying SDAIA within 72 hours of certain breaches. Our guide to mobile app security and data protection covers the engineering side, and the same principles apply in the Kingdom.
VAT and e-invoicing
Saudi VAT is 15%. ZATCA's e-invoicing programme (Fatoora) has a generation phase and an integration phase rolled out in waves, with taxpayers notified in advance of their integration date. A delivery platform issues invoices, commission statements and often tax invoices on behalf of restaurants, so ask your accountant which phase applies to you and which entity issues which document. Build your order and payout data so that invoices can be produced and stored in the required format.
Consumer rules and food safety
Restaurants need their own municipal and food-safety permits, and your terms should require them to keep those valid. Expect rules on price display, refunds and complaint handling too. Put the restaurant's licence number and expiry in its profile in your admin, and flag expiries.
Payments: mada first, then everything else
In Saudi Arabia, a payment screen without mada is a broken payment screen. Mada is the national debit network, and its online use has grown fast: mada e-commerce transactions reached a record SAR 27.55 billion in March 2025, up 73% on a year earlier, according to SAMA data reported in the press. SAMA has also pushed to raise the share of electronic payments towards 70% of all payments by 2025.
The methods your customers expect
- Mada cards, with 3-D Secure authentication.
- Apple Pay, which many iPhone users treat as their default, often running over the mada network for local cards.
- STC Pay and other wallets, which use their own integration path.
- Credit cards (Visa and Mastercard).
- Buy now, pay later from providers such as Tabby and Tamara, mainly for larger baskets. We cover the model in buy now pay later app development in Saudi Arabia and the UAE.
- Cash on delivery, still common, and a real operational cost.
How to connect them
You rarely integrate with mada directly. You use a licensed payment gateway that supports it. Local and regional gateways such as HyperPay, Moyasar and PayTabs offer mada, Apple Pay, wallets and cards through a single integration, each with its own fees, onboarding process and settlement times. Compare them on:
- Which methods they support, including Apple Pay and STC Pay
- Per-transaction and monthly fees
- Settlement time (when money reaches your account)
- Marketplace and split-payment support, which matters for paying restaurants
- Refund and partial-refund tools
- Quality of Arabic checkout and the developer documentation
- Onboarding requirements for your company type
Onboarding can take weeks and may need your commercial registration and bank details, so start it in month one, not week twelve. We discuss the wider landscape in mobile app payment options, and the cost side in app development cost in Saudi Arabia.
Money flows on a delivery platform
A single order moves money between several parties. A typical split: the customer pays the full amount to the platform; the platform keeps its commission and delivery fee, pays the restaurant its share and pays the driver or fleet partner. Design a ledger from day one that records every movement: charge, commission, payout, refund and adjustment. Reconcile it against your gateway reports daily. Many early delivery apps run on spreadsheets for this and regret it.
Think through the awkward cases:
- A restaurant cancels after the customer has paid.
- An item is out of stock and the order is partially refunded.
- The driver is delayed and the customer receives a voucher.
- Cash on delivery: the driver holds your money until they remit it.
- A chargeback arrives weeks later.
Each needs a defined rule and a trace in the ledger.
Arabic that feels native
Customers in Saudi Arabia expect Arabic first and English second. Translating the English screens is not enough.
- Right-to-left layout. Every screen must mirror correctly, including progress bars, back arrows, carousels and the order tracker.
- Numbers and currency. Decide how to show riyal amounts and be consistent. Many apps show Western numerals with Arabic text, which most users prefer, but test with your audience.
- Menus in both languages. Restaurants must be able to enter dish names, descriptions and categories in Arabic and English. Machine-translated menus read badly and put people off.
- Tone and dialect. Use clear Modern Standard Arabic for interface text, with a friendly tone. Keep promotional copy short and natural.
- Search. Arabic search needs to handle spelling variants, optional diacritics and different forms of the same letter. Customers type "برجر" and "برغر" for the same dish.
- Address entry. Many Saudi addresses rely on the national short address and landmarks. Support pin-drop on the map, the short address, and free-text notes in Arabic.
- Notifications and SMS. Write templates in Arabic, and check that they render correctly on both iOS and Android.
Our guide on Arabic app localisation and right-to-left design goes through the details and the common mistakes.
What the customer app needs
- Sign-in with phone number and a one-time code, plus Apple sign-in where required by the store.
- Location and address book with map pin, short address, saved places and delivery notes.
- Restaurant discovery: search, categories, cuisine filters, ratings, open/closed status, delivery time and fee estimates.
- Menus with photos, options, add-ons, allergen notes and special requests.
- Basket and checkout with promo codes, tip, scheduled orders and payment choice.
- Live tracking: status steps, driver location on the map, estimated arrival and a way to contact the driver without sharing the real phone number.
- Order history and reorder in one tap.
- Ratings and feedback for the restaurant and the delivery separately.
- Help inside the order: report a missing item, cold food or late arrival, with quick refunds for clear cases.
- Loyalty: points, subscriptions with free delivery, or a simple stamp card.
- Notifications for order stages and offers, with clear controls.
What the restaurant side needs
Restaurants judge you on how little work you add to their kitchen.
- Order receiving by tablet app with loud, reliable alerts, printer support and an easy accept/reject flow.
- Preparation time control and a "busy" mode that slows incoming orders.
- Menu management: items, prices, photos, options, availability toggles and scheduled menus (breakfast, lunch, dinner).
- Opening hours and holiday schedules, including prayer-time closures where relevant.
- Reports: sales, popular items, payout statements, commission breakdown and disputes.
- Integration with point-of-sale systems where possible, so menu and stock changes sync. This is often the hardest and most valuable feature.
- Multi-branch support for chains.
What the driver app needs
- Onboarding and compliance: document upload, licence checks, vehicle details, face verification and approval status.
- Availability toggle and shift or zone selection.
- Job offers with pickup, drop-off, distance, estimated earnings and a short accept window.
- Navigation deep links to a maps app, with clear pickup and drop-off steps.
- Proof of delivery: one-time code, photo or both.
- Earnings: per-order breakdown, daily and weekly totals, tips and payout history.
- Cash handling for cash-on-delivery orders, with balance and remittance reminders.
- Support and incident reporting, such as accidents or unreachable customers.
- Battery and data care: background location is expensive, so tune update frequency and test on mid-range Android phones.
The admin panel: your control room
Operators spend their day here, so it deserves real attention.
- Live order board with filters by city, restaurant and status, plus alerts for late or stuck orders.
- Dispatch tools: manual assignment, reassign, batch orders and see driver locations.
- Restaurant onboarding: licence capture, menu import, commission settings and contract status.
- Driver management: approvals, document expiry, performance and blocks.
- Pricing and zones: delivery fees by distance, surge and free-delivery thresholds, zones by city and neighbourhood.
- Marketing: promo codes, banners, push campaigns and referral rules.
- Finance: ledger, payouts, refunds, cash-on-delivery reconciliation and exports for your accountant.
- Support: a ticket view tied to each order with a record of what happened.
- Analytics: orders, average delivery time, acceptance rates, cancellations, repeat customers and cost per order.
- Compliance: licence and permit tracker, audit logs and data-request handling.
Want a feature list that matches your first-city budget? We'll split the scope into a launch version and a second phase so you can open sooner. Book a call and we'll walk through it.
The hard problems under the hood
Dispatch
Matching drivers to orders is the heart of the system. A simple version offers the order to the nearest available driver and widens the circle if nobody accepts in 30 seconds. A better version considers the restaurant's preparation time so the driver arrives when the food is ready, not ten minutes before. Add batching later, where one driver takes two nearby orders, but only after the basics work.
Delivery time estimates
Customers judge you by the promised time. Combine preparation time (from the restaurant), driver travel time (from a maps API) and a buffer learned from past orders per restaurant and per hour. An estimate that is honest and slightly long beats one that is optimistic and wrong.
Live location at scale
Thousands of drivers sending a location every few seconds is a lot of traffic. Use a real-time channel such as WebSockets, throttle updates when a driver is stationary, store only what you need and keep location history on a short retention schedule for privacy.
Peak times
Lunch, dinner, Ramadan evenings, weekends and national days produce spikes. Load test for ten times your normal traffic, scale the order and dispatch services independently and keep a plain "we're busy" mode for restaurants. See mobile app backend architecture explained for how we structure this.
Maps and geocoding
Map quality drives delivery time and driver trust. Test your chosen provider on real Saudi addresses, including new districts and compounds. Budget for map usage fees, which grow with your order count, and check them against your per-order margin.
Fraud and abuse
Expect promo abuse, fake accounts, refund abuse and collusion between drivers and customers. Start with simple rules (one promo per device and phone, limits on refunds per user) and add risk scoring when you have data.
Technology choices
A cross-platform framework such as Flutter or React Native suits the customer, restaurant and driver apps, because it keeps costs down and keeps the apps consistent. Driver apps with heavy background location may need extra native work. Our comparison Flutter vs React Native helps you choose. The backend should be cloud-hosted with an in-Kingdom or nearby region where possible, keeping PDPL and data-transfer rules in mind.
A worked example: one order, start to finish
To make this concrete, here is a made-up order in Riyadh, with illustrative numbers.
- At 8:10 pm, a customer in Al Olaya opens the app in Arabic, picks a grill restaurant 2.5 km away and adds two meals and a drink for SAR 96. The delivery fee is SAR 9 and a tip option is offered.
- She pays with Apple Pay over her mada card. The gateway authorises SAR 105 and the platform records the charge in the ledger.
- The restaurant's tablet rings. The cook accepts and sets 18 minutes. The platform now knows when the food will be ready.
- Dispatch waits until about four minutes before readiness, then offers the job to the nearest of three available drivers. The first driver accepts in 12 seconds.
- The driver arrives as the food is bagged, scans the pickup code and heads out. The customer sees the driver's position and a 14-minute estimate.
- At the door, the driver shows a four-digit code. The customer reads it out, and the order is marked delivered at 8:51 pm.
- The system closes the ledger entries: commission to the platform, the restaurant's share into its next payout, the driver's fee and tip into the driver's earnings.
- The customer rates the food four stars and the delivery five. One missing sauce is reported and a small automatic refund is issued.
Every step is a screen, a rule or a record that has to be designed. Notice how many depend on timing information from the restaurant. That is why the restaurant app and the preparation-time flow matter as much as the pretty customer screens.
City rollout: opening one city at a time
A delivery marketplace is local. Ten orders a day in each of five cities is a worse business than a hundred orders a day in one. Plan your launch in stages.
Stage 1: choose the first zone
Pick a dense area with many restaurants, high evening demand and a population that matches your offer, for example a district in Riyadh with offices and apartments close together, or a university area in Jeddah or Dammam. Define a delivery radius small enough that most orders arrive within 30 minutes.
Stage 2: sign restaurants before you launch
Aim for a full choice in the zone: a healthy mix of cuisines and price points, including a few well-known names that bring customers. Offer a fair commission or an introductory rate, free onboarding and help with menu photos. Take time to handle Arabic menu entry yourself at first, because good menus sell.
Stage 3: recruit drivers through licensed channels
Work through licensed entities and make onboarding quick. Guarantee earnings for the first weeks if you must, because empty roads in the first month hurt more than a subsidy does. Check every document against the current TGA requirements.
Stage 4: soft launch
Open to a limited group, such as a few thousand invited users or a single neighbourhood. Watch delivery times, cancellations and support tickets daily. Fix what breaks. Our testing checklist and launch checklist apply here.
Stage 5: grow demand
Use first-order offers, referrals, restaurant co-marketing and local partnerships with offices, universities and residential compounds. Plan the details with our guide on getting your first 1,000 users and app store optimisation, and make sure Arabic keywords appear in your store listing.
Stage 6: replicate the playbook
When the first zone hits stable delivery times and healthy margins, copy the process into the next zone and then the next city. Keep a checklist: restaurant count, driver count, support staff, marketing budget, local partners and a licence check. Different cities have different customs and busy hours: Jeddah's evenings differ from Riyadh's, the Eastern Province has its own rhythm and the holy cities see surges around pilgrimage seasons. Review each city's data separately.
Numbers to watch during rollout
| Metric | Why it matters |
|---|---|
| Average delivery time | The biggest driver of satisfaction and repeat orders |
| Orders per active driver per hour | Shows driver earnings and fleet efficiency |
| Restaurant acceptance and preparation accuracy | Late kitchens spoil deliveries |
| Order cancellation rate | Signals stock, price or timing issues |
| Repeat rate at 30 days | Tells you whether people come back |
| Cost per order (support, delivery, payment fees) | Shows whether the unit economics work |
| Customer acquisition cost | Compare with the lifetime margin per customer |
| Refund rate | A quality and fraud signal |
How the business makes money
Revenue usually comes from a mix:
- Commission on each order from the restaurant.
- Delivery fees from the customer, sometimes tiered by distance.
- Service fee in addition to the delivery fee.
- Subscriptions that bundle free delivery for a monthly price.
- Advertising: restaurants paying for placement.
- Quick-commerce and groceries as an add-on category, where the basket sizes are different.
The economics depend on volume and density. Work them out for a single order before you scale: commission income minus driver cost, payment fees, support, discounts and a share of overheads. If a typical order loses money, volume will not fix it. Our monetization guide compares the models, and the errand and courier marketplace article shows a neighbouring model in the Kingdom.
What it costs and how long it takes
A food delivery platform is not a small project: it includes a customer app, a restaurant app, a driver app and an admin panel, with payments, live tracking and dispatch. By our indicative pricing, a single-platform build at advanced complexity starts from about USD 14,400 (SAR 54,000), and a full multi-app platform with dispatch, a restaurant tablet app, finance tools and compliance features will usually sit above that starting point depending on scope. Typical timelines for advanced builds run five months or more. These figures are indicative, exclude VAT and depend on scope, so please treat them as a starting conversation, not a quote.
The recurring costs matter as much:
- Payment gateway fees on every order
- Maps, SMS and push-notification usage
- Cloud hosting and monitoring
- Driver and restaurant onboarding and support staff
- Marketing and customer incentives
- Maintenance, typically 15 to 20% of the build cost each year; see mobile app maintenance cost
For a Saudi-wide view of budgets read app development cost in Saudi Arabia, and for how a project is staged see our mobile app development process.
A sensible phased plan
- Phase 1 (launch): customer app, restaurant tablet app, driver app, admin panel with live orders, mada, Apple Pay and cards, basic dispatch, Arabic and English.
- Phase 2 (grow): promo engine, loyalty and subscriptions, STC Pay and BNPL, POS integrations, scheduled orders and richer reports.
- Phase 3 (scale): batching and smarter dispatch, advertising for restaurants, grocery and quick-commerce, multi-city tooling and analytics.
Writing a clear brief makes quotes comparable; use our requirements document guide, and read the contract checklist before you sign with anyone.
How we'd build it
- Discovery. We define the city, the wedge, the model (own fleet, restaurant drivers or hybrid), the payment gateway and the compliance plan. You get a written scope.
- Design. Arabic-first wireframes for all four surfaces, tested with a few restaurants and drivers, not only customers. See our UI and UX guide.
- Build the risky parts first. Orders, payments and ledger, then dispatch and live tracking, then the polish.
- Test with real conditions. Replay busy-hour traffic, test mada flows, bad networks, wrong addresses and cancelled orders.
- Soft launch in one zone, then fix and widen.
- Support and iterate. Ongoing improvements guided by delivery times and repeat rates.
Ready to scope your delivery platform? Send us the city, the model and a rough budget, and we'll reply with an honest view of what's realistic. Start the conversation or book a call.
Common mistakes
- Launching in several cities at once. Density beats breadth. Win a zone first.
- Treating mada as an afterthought. Test payments with real local cards early and plan gateway onboarding time.
- Ignoring the driver rules. Using unlicensed drivers risks suspension. Build compliance into onboarding.
- Weak restaurant tools. If the kitchen tablet is clumsy, orders get missed and restaurants leave.
- Machine-translated Arabic. It undermines trust. Have native speakers review the text and the menus.
- No ledger. Spreadsheets break at a few hundred orders a day.
- Underestimating support. Real people must handle late and wrong orders quickly, at night and on weekends.
- Buying growth before fixing delivery times. Discounts bring customers who leave after one bad order.
- Skipping the unit economics. Know what one order earns before you scale.
- Copying a giant's features. Start with the few things that make your wedge work.
Source: Arka Softwares indicative pricing. Single platform, excluding VAT.
Related on-demand work we've delivered
We haven't published a food delivery case study, so we won't pretend to one. Two projects touch the same building blocks. Dial Usafi is an on-demand services app (laundry, cleaning, babysitting and chef services) that also lets providers promote their work, built over four months by a six-person team on Android, Java and Laravel. Its listed challenges were an audience unfamiliar with the idea, simpler navigation and reliable performance, all things a delivery app faces on day one. Pearl Cab is a cab-booking app with live tracking, ETA calculation, in-app maps and navigation, multiple payment options, an SOS button and local-language support, built over six months by a five-person team. Live tracking, ETAs and payments are the same components a delivery app needs. The case studies report no usage numbers, so treat them as evidence of capability, not of results.
Wrapping up
An app in the style of Jahez or HungerStation is a logistics business with an app on top. The software has to be dependable, in Arabic and built for mada, but the outcome depends on local density, fair terms for restaurants, decent earnings for licensed drivers and a delivery time you can keep. Pick a wedge, open one zone, learn from real orders and expand only when the numbers hold.
If you're planning a food delivery platform for the Kingdom, tell us about it on the contact page, or explore our mobile app development in Saudi Arabia. We'll reply with a suggested scope, timeline and a clear quote.
Fact sheet and sources
Facts from outside sources are linked and were checked on the dates we researched them. Market figures are snapshots and some come from secondary coverage, so please confirm them before quoting. Prices marked "Arka" are our own indicative rates. Rules change; confirm with the regulators and a Saudi lawyer.
| Fact | Source |
|---|---|
| Jahez's CFO said licensed platforms processed about 290 million orders in 2024, with Jahez handling 91 million, about 32% by TGA data. | Argaam: Jahez holds 32% share of delivery orders |
| Keeta began operating in Saudi Arabia in September 2024 and was reported to pass 150 million orders in 2025. | Argaam: Keeta hits over 150M orders in Saudi Arabia in 2025 (secondary reporting) |
| HungerStation Plus was reported to exceed 10 million subscribers and 100 million orders. | Sharikat Mubasher (secondary reporting) |
| The TGA's executive regulations require a licence for delivery activity and limit it to licensed goods-transport establishments and Saudi individuals with their own vehicles; drivers need a driver card or licence plus a clear record. | Gulf News: new rules for delivery services take effect |
| The TGA froze new licences for app-based motorcycle delivery in October 2024 pending new regulations. We could not confirm whether the freeze has ended. | Gulf News; Argaam |
| Mada e-commerce transactions reached a record SAR 27.55 billion in March 2025, up 73.4% year on year. | MEA Tech Watch, citing SAMA data |
| SAMA's target was to raise the share of electronic payments to 70% by 2025. | SAMA: e-payments share exceeds FSDP's 2022 target |
| SDAIA issued the PDPL Implementing Regulations on 7 September 2023; the law became fully enforceable in September 2024; the regulations include a 72-hour breach notification requirement. | Clyde & Co; CMS |
| ZATCA's e-invoicing has a generation phase (from December 2021) and an integration phase rolled out in waves with advance notice to taxpayers. | ZATCA: e-invoicing roll-out phases |
| Advanced single-platform app: from USD 14,400 (SAR 54,000), typically 5 months or more; maintenance 15 to 20% of build per year. Indicative, excluding VAT. | Arka Softwares pricing, October 2026 |



