Skip to content

Custom software development · Jeddah

Custom Software Development Company for Jeddah

We build custom backend systems, trading and logistics platforms, and CRM for companies working through Jeddah, the Kingdom’s commercial gateway on the Red Sea. We work remotely from Ahmedabad, India, on Saudi hours. There is no QalbIT office in Jeddah, and this page explains exactly what that changes.

Jeddah companies buy software to move goods and people: containers off the quay, stock out to branches, travellers from the airport to their hotels. This page covers those systems, and what ZATCA and PDPL change when they are built from outside the Kingdom.

  • 2018

    Building software since

  • 5.0

    Clutch rating

  • 50+

    Clients served

  • 4.9

    Google rating, 18 reviews

Get your free estimate

Three quick questions: scope, approach and a price range back within 48 hours. No sales call required first.

What do you need built?
When do you want to start?
Where should we send the estimate?

Answer all three questions above, then send.

NDA-friendly · IP yours from day one

Definition


What a remote software partner actually does for a Jeddah company

QalbIT builds trading, freight and retail systems for Jeddah companies as a remote engineering partner working from Ahmedabad, India. Two Saudi rules apply to every build. ZATCA Phase 2 e-invoicing reaches taxpayers above SAR 187,500 of VAT-subject revenue by 1 February 2027 under Wave 25, and PDPL Article 29 governs personal data, such as consignee and passenger records, leaving the Kingdom.

Jeddah trades goods, not just software, so the software question usually shows up first inside a warehouse, a customs desk or a booking office rather than an IT department.

A Jeddah systems house can be at your warehouse or your customs broker’s office within the hour, and speaks Arabic with your floor team every day. We sit outside the Kingdom, which changes where consignee and passenger data is processed, how the working week lines up, and who signs for the data-transfer position.

None of that makes a remote build the wrong answer. It makes it a different answer, one that suits a defined system with a clear specification better than an open-ended transformation programme.

We are the second kind of vendor and we say so on the page rather than in the second meeting.

At a glance

  • Core focus

    Trading, logistics and backend systems, CRM, custom APIs

  • Engagements

    Trading platforms · freight tracking · retail CRM · booking tools

  • Delivery

    Remote on Red Sea coast hours, four shared working days a week

  • Saudi position

    No local entity. Processor outside the Kingdom under PDPL

Definition


Local systems house vs global consultancy vs remote engineering partner

The same three options Riyadh buyers weigh, priced and staffed differently for a trading city.

  • Local Jeddah systems house

    Registered in the Kingdom, close to your warehouse or branch network, Arabic-first. Best when the work touches customs brokers, port agents or a floor team daily.

  • Global consultancy

    Large in-Kingdom teams for a trading group moving several companies, brands or ports of entry onto one platform, usually with a board sponsor and a long programme.

  • Remote engineering partner

    A few senior engineers outside the Kingdom building one system you can describe, such as a shipment tracker or a dealer portal, on Jeddah hours. Without a Saudi entity, the transfer of consignee and customer data is settled in the contract.

We are the third. Where a Jeddah systems house is genuinely the better fit, for example a floor rollout across multiple warehouses, we will say so before you sign anything with us.

Fit


When a remote partner is the right call for a Jeddah business

Both sides, so you can place your own project quickly.

  • Hire a remote partner when

    • You can describe the system: a trading ledger, a booking platform, a customs or freight tracker, a dealer portal.
    • Someone in your operations team can answer our questions the same day, so the two-and-a-half-hour gap never stalls a shipment or a release.
    • You need one platform built or rebuilt, such as landed-cost tracking or a branch CRM, rather than a group-wide change programme.
    • You want the code and the product decisions to stay with your company after launch.
    • Consignee, customer and passenger records can be transferred under PDPL’s standard safeguards.
  • Hire locally instead when

    • The system is built around data PDPL treats as sensitive, such as travellers’ health details or biometric check-in. Keep that processing in the Kingdom.
    • You are bidding for government or port-authority work through Etimad, where in-Kingdom delivery is a condition.
    • Delivery has to run in Arabic across your whole warehouse and branch network, not only at the interface layer.
    • You need people on a warehouse floor or a customs desk during a cutover.
    • Your purchasing policy only signs with a company holding a Saudi commercial registration.

Projects in the second list get a polite no from us. A remote build where a Jeddah systems house is the honest answer costs you a season, and with sensitive data it creates a legal problem for both of us.

Next step


Not sure whether to hire locally?

Describe the system and the records it will carry, from bills of lading to passenger lists. We will tell you which list it falls in, even when the right answer is a systems house in Jeddah.

Comparison


Remote partner vs local systems house vs global consultancy

Rates are left out on purpose. Each row is a practical difference for a Jeddah trading or logistics business, and the rows a local firm wins are still here. Share your scope and the data involved, and we will complete this table for your case.

Remote engineering partner compared with a Jeddah systems house and a global consultancy for trading, freight and retail systems
Local Jeddah systems houseGlobal consultancyQalbIT (remote partner)
Physical Jeddah officeYesUsuallyNo
Arabic-first deliveryYesVariesEnglish with your managers, Arabic on screens, labels and invoices
PDPL position on customer dataProcessed inside the KingdomOften processed in-KingdomProcessor outside the Kingdom, safeguards in the contract
Data residencySaudi hosting as standardSaudi hosting offeredSaudi hosting possible, engineering done remotely
ZATCA Fatoora integrationCommonCommonYes, clearance and reporting both
Working-week overlapFullFullFour shared days, 2.5 hours apart
Port and customs system familiarityCommonVariesBuilt from your broker’s and carriers’ documentation
Cover during peak seasonOn siteOn siteRemote, with hours agreed before the peak
Source code ownershipVariesVariesYours, every repository
Team size on your accountVariesLarge, layeredSmall senior team, founder on the thread
  • 01

    The rows a local firm wins stay in.

    Office presence, Arabic-first delivery and peak-season cover favour a Jeddah firm. Better to weigh them now than four months into a build.

  • 02

    A port-facing integration is a spec question, not a location question.

    Whether we have worked with your specific customs or shipping line system before matters less than whether the integration is documented. Send the API documents or file formats your broker and carriers use before the scoping call.

  • 03

    Jeddah mornings are our late mornings.

    Jeddah is on UTC+3 and Ahmedabad on UTC+5:30, so a 9am dispatch meeting in Jeddah is 11:30 for us, on four of your five working days.

  • 04

    Etimad eligibility is binary.

    If your buyer is a government body or a port authority procuring through Etimad with an in-Kingdom registration requirement, that decides the vendor before quality does. Ask us early.

What we build


Custom software we build for Jeddah companies

One reference number should follow a consignment from purchase order to delivery note to invoice, without anyone typing it a second time.

  • Trading

    Trading and import-export platforms

    Purchase orders, letters of credit, shipment status and landed cost in one system, with the declaration your broker files through FASAH and any SABER certificates logged against each shipment. It replaces the spreadsheet only one person understands.

  • Logistics

    Freight, warehouse and fleet systems

    Consignment tracking, warehouse allocation, dispatch planning and proof of delivery for operators moving goods through Jeddah Islamic Port and onward.

  • Portals

    B2B and dealer portals

    Portals where dealers place orders, suppliers confirm shipments and agents check commissions, on top of the system you already run, with permissions an auditor can follow.

  • Hospitality

    Booking and capacity systems

    Seat, room and vehicle capacity for operators moving travellers between the airport, Jeddah hotels and onward transfers, built to absorb the season’s peaks and scale back afterwards.

  • Backend

    Custom backends and APIs

    Laravel, Node.js and NestJS services that link your trading, warehouse and accounting systems, with queues that hold messages when a carrier’s API is slow.

  • CRM

    Custom CRM development

    For retailers and distributors: accounts by branch and route, dealer price lists, van-sales orders and repeat-purchase follow-up, handed over to invoicing without re-keying.

Cost


How much does custom software development cost in Jeddah?

For a Jeddah trading, freight or retail business, the cost of custom software comes from the size of phase one, how many outside systems it has to talk to, and the compliance work built in. Carrier and customs-broker integrations, ZATCA clearance and reporting, and migrating consignment history are separate line items. We scope before we quote, and fix the price of phase one.

You will not find a price list here. A number given before we understand your import flow would be a guess dressed up as a quote.

A two-module CRM for one showroom and a trading platform with landed cost, three carrier feeds and branch invoicing are different jobs, and a range that spans both is no help to you.

So the order is fixed: a scoping call, a written process map, then a fixed-scope price for phase one before you spend beyond discovery. The drivers below move that price; use them to check any quote you receive.

Try the software development cost calculator

What moves the number

  • Scope of phase one

    A first phase that gets purchase orders and shipment status right is worth more than one that touches every department lightly. Two connected modules is typical.

  • Integration count and quality

    A carrier with a modern REST API is quick to connect. A broker or shipping line that sends spreadsheets by email needs import jobs and a reconciliation step.

  • ZATCA integration depth

    A trader often needs both paths: B2B invoices to distributors cleared before issue, and simplified invoices from retail branches reported afterwards. Each path needs CSID onboarding, XAdES signing and a hash chain that survives a rejection.

  • Data protection architecture

    Consignee, customer and passenger records each need a decision on where they are stored and what crosses the border. Cheap to decide at design time, costly to change after launch.

  • Arabic in the product

    Arabic and English screens, right-to-left layouts, and invoices, delivery notes and manifests that print correctly in Arabic. Frequently underestimated.

  • Data migration depth

    Moving item masters and opening stock is routine. Moving years of consignment or booking history, reconciled against the ledger, is its own project.

How we work with Jeddah teams


A delivery process built around a 2.5-hour offset

The time difference is minor. Vessel arrivals, month-end stock counts and peak travel seasons are not, so the schedule works around them.

  1. Discovery and process mapping

    Trace how a shipment, an order or a booking moves through your business today, who touches it and where it stalls. Choose the most painful system for phase one and set the data-protection profile for the whole build.

    Mapped process, ordered roadmap, phase-one price and a written position on data transfer.

    1–2 weeks

  2. Architecture and data design

    Design the data model around items, consignments and customers, then the screens and the interfaces to carriers, brokers and your accounting system. Agree what is hosted in Saudi Arabia and what never leaves it.

    Approved data model and screens, an integration plan and a hosting decision.

    2–3 weeks

  3. Build phase one

    Weekly increments, demoed with your real shipments, bookings or accounts, not dummy data, inside your Sunday–Thursday week and clear of your busiest weeks.

    Modules proven against real trading and logistics scenarios.

    6–14 weeks, scope-dependent

  4. Migration, training and parallel run

    Load item masters and opening stock, train branch and warehouse staff, and run the old and new systems together until stock and receivables agree.

    A go-live with reconciled stock and staff who have already used the system.

    2–4 weeks

  5. Stabilise, extend, roll out next

    Fix what the first months of real volume reveal, add the reports your managers ask for, and move to the next system on the roadmap once the first has settled.

    A platform that keeps up with the business rather than a one-time delivery.

    Ongoing, month-to-month

Jeddah works Sunday to Thursday on UTC+3, and our team is on UTC+5:30, so four of your working days overlap ours in full. Thursday afternoons and weekends run on written handovers, and support hours for the peak season are agreed before it starts.

Book a scoping call

Where we fit best


Jeddah projects we take on

Remote delivery works best for the four project types below. Where it does not, the fit lists earlier on this page say so.

  • First build

    Replacing spreadsheets with a real trading system

    Import-export and trading businesses running purchase orders, shipments and landed cost on spreadsheets who need a real system built properly the first time. For trading, distribution and freight-forwarding businesses.

  • Modernisation

    Rebuilding software you have outgrown

    A trading or freight system written years ago, rebuilt for the browser with its consignment and customer history intact, and branches moved over one at a time. For traders on software nobody supports.

  • Compliance

    ZATCA and PDPL retrofit

    Adding Fatoora clearance for distributor invoices and reporting for branch sales to the system you already use, and moving customer data to where PDPL needs it. For traders and retailers in Wave 25.

  • Seasonal scale

    Booking and capacity systems that scale up and back down

    Reservation and transport-capacity systems built for a hospitality or logistics operator whose volume swings hard across the year, without a redesign each time it does. For operators with sharp seasonal demand.

Industries


Sectors we build for in Jeddah

Jeddah’s economy runs through its port, its wholesale trade and its role as the arrival point for travellers heading inland. We know the paperwork and the hand-offs in these four.

  • Trading and import-export

    Purchase orders, letters of credit, landed-cost calculation and supplier reconciliation. The complexity is rarely in one shipment. It is in reconciling dozens of them against contracts written months earlier.

  • Freight, logistics and warehousing

    Multi-warehouse stock, dispatch planning, proof of delivery and consignment tracking through Jeddah Islamic Port and onward inland.

  • Hospitality and transport operators

    Ground transport, hotel blocks and transfer scheduling for operators receiving Umrah and leisure travellers at King Abdulaziz International Airport and moving them on, with demand that rises and falls by season.

  • Retail and distribution

    Branch networks and wholesale distributors across the western region: customer and dealer CRM, branch stock, promotions, and simplified invoices reported to ZATCA from each branch.

Next step


Your process is the reason the off-the-shelf tool doesn’t fit.

Packaged trading and freight tools assume a standard import flow. If yours has its own landed-cost rules, agent commissions or seasonal pricing, tell us, and we will say whether a custom build is worth it.

Saudi compliance


Building software for Jeddah: ZATCA, PDPL and data residency

ZATCA and PDPL work the same way in Jeddah as anywhere else in the Kingdom. The difference is what usually raises them first here: a trading company’s invoicing, or a freight or booking system that holds data on drivers, agents, consignees and passengers.

  1. ZATCA e-invoicing (Fatoora)

    Phase 2 connects your invoicing directly to ZATCA’s Fatoora platform. The rules are national, so a Jeddah trader follows the same ones as any other VAT-registered business; what differs is the mix. Invoices to distributors and other businesses are cleared before they are issued, while simplified invoices from shops are reported after the sale. Both carry UBL 2.1 XML, a UUID, a cryptographic stamp and a QR code. Wave 25, announced on 24 July 2026, applies to taxpayers whose VAT-subject revenue passed SAR 187,500 in any year from 2022 to 2025, half of Wave 24’s threshold, with integration due by 1 February 2027. A trader that also runs freight billing or retail branches usually needs both the clearance and the reporting path, not just one. Integrations most often break at CSID onboarding, at XAdES signature checks, or when a rejected clearance breaks the hash chain and every later invoice fails with it. Sources: Zakat, Tax and Customs Authority (ZATCA), Wave 25 announcement of 24 July 2026, zatca.gov.sa.

    Phase 2 · Wave 25

  2. PDPL and cross-border data

    Saudi Arabia’s Personal Data Protection Law (Royal Decree M/19, amended by M/148) has been fully enforceable since 14 September 2024. It applies to anyone outside the Kingdom who processes personal data about people inside it, and that includes our team. For a Jeddah business that usually means driver, agent and consignee records in a freight system, customer records in a retail CRM, or passenger lists in a booking platform. Article 29 lets that data leave the Kingdom under SDAIA’s approved safeguards, including the Saudi Standard Contractual Clauses, backed by a risk assessment where the regulation calls for one. You remain the controller and we act as processor, so each transfer is justified and written into the contract before it happens. Sources: Saudi Data & AI Authority (SDAIA), Regulation on Personal Data Transfer Outside the Kingdom, v2.0, August 2024, dgp.sdaia.gov.sa.

    Royal Decree M/19

  3. Customs data: FASAH and SABER

    Imports into the Kingdom are declared through FASAH, the national single window for trade run under ZATCA, usually by your customs broker. Regulated products also need conformity certificates issued through SABER, the platform of the Saudi Standards, Metrology and Quality Organization, and SABER is linked to FASAH so the shipment certificate travels with the declaration. We do not file declarations or replace your broker. What we build is the record on your side: each shipment’s declaration reference, certificate status, duty and import VAT, so landed cost is calculated from what customs actually charged rather than from an estimate. Access to FASAH and SABER runs through your company’s and your broker’s own accounts. We work from the documents and exports they provide. Sources: FASAH national single window, fasah.sa · SABER, Saudi Standards, Metrology and Quality Organization, saber.sa.

    Imports

We build compliant invoicing and customs records into the system from day one, not as a module bolted on later. If a Wave 25 notification has set your date, we plan backwards from it.

Working with us


Hiring a vendor outside the Kingdom: the honest version

Four exposures come with any vendor based outside Saudi Arabia. For a Jeddah buyer they look like this.

  • Data transfer

    Before consignee, customer or passenger records reach our engineers, you, as controller, need a lawful basis under Article 29 and documented safeguards. It is settled once, in the contract.

  • Sensitive data

    Travellers’ health details and biometric check-in data are sensitive under PDPL. If a booking or transport system holds them, that part runs in the Kingdom, whoever builds it.

  • Government and port-authority procurement

    Etimad tenders and some port-authority contracts require a Saudi commercial registration from the contracting party. We do not have one.

  • Physical presence

    Nobody from our team will be on your warehouse floor or at a customs desk on Tuesday. If a cutover needs people in the warehouse or at the branches, you need local hands, and we will say so on the first call.

  • Everything else

    Shipping-line and carrier APIs, customs-broker exports, payment gateways, e-invoicing service providers, accounting products, banking APIs and BI tools.

    Integrations

None of this is a reason to avoid a remote team. It is a reason to put the terms in writing before work starts.

Tech stack


Technology we use for Jeddah builds

A trading platform outlives the team that commissioned it. We use proven technology that your future developers, in-house or not, can pick up.

  • Backend and business logic

    • Laravel (PHP 8.x) for trading, stock and invoicing modules with full audit trails.
    • NestJS (TypeScript) for carrier, broker and marketplace integrations that run on events.
    • Queues and schedulers for tracking updates, stock syncs and overnight reports.
  • Frontend and usability

    • Next.js and React screens for fast order entry and stock lookup.
    • Arabic and English interfaces that lay out right-to-left correctly, printed delivery notes included.
    • Role-based dashboards for owners, managers and dispatch teams.
  • Data and integrations

    • PostgreSQL and MySQL with strict constraints, so stock, consignments and receivables reconcile.
    • ZATCA Fatoora clearance and reporting, both paths.
    • Connections to accounting products, payment gateways, carriers and customs brokers.
  • Security and residency

    • Permissions by role and branch, with an audit log behind every change.
    • Hosting in Saudi Arabia for data that has to stay there.
    • Automated backups, staged deployments and monitoring that alerts before customers notice.

Running an accounting product, an older trading system or spreadsheets and email today? We connect to what works first and replace only what has to go, with the migration path in the plan.

Outcomes


What the project should actually change

These are not projections. They are the changes the system should bring to your operation, with the number you would watch to confirm each one.

What the project should actually change: what changes and how you would measure it
What changesHow you’d measure it
One stock and consignment record across branches and warehousesDifference between system stock and the physical count
Landed cost is known before goods are pricedDays from arrival to final landed cost per shipment
Customers see shipment status without callingStatus calls to the operations desk each week
Distributor invoices clear ZATCA first timeRejected clearances and broken hash chains
Discounts and credit limits are enforced by the systemOrders released over limit without sign-off
Peak season runs without manual workaroundsBookings handled outside the system during peak weeks
  • A note on sourcing

    A note on sourcing

    We do not quote failure rates for software projects. The figures often credited to Gartner cannot be traced to a primary source, so they stay off this page. Any number we do cite has its source and date beside it.

Why QalbIT


Why work with us

  1. Eight years building operational software

    We have shipped 120+ engagements for 50+ clients since 2018, across web, mobile and platform work. Clutch 5.0, Google 4.9, Upwork Top Rated. Our current GCC work is white-label engineering for a regional agency, and the trading and logistics systems offered here draw on that experience.

  2. We say what we are

    No Jeddah office, no local entity, no implied presence. We would rather lose a project at the first call than leave you exposed at an audit, which is why the compliance section is so detailed.

  3. You own the code

    The code lives in your repository, documented, from the first commit. You pay no licence or seat fee, and you are free to bring in a different team later.

  4. Senior team, founder-led

    A small senior team works on your account directly. If something matters, you can raise it with the founder.

  5. We’ll tell you to hire locally

    If your project needs people at your warehouses or branches through a rollout, we will recommend a Jeddah systems house on the first call.

The biggest difference has been their flexibility and solution-oriented approach. Rather than pointing out problems, they focus on solving them. I genuinely cannot recall hearing them say, ‘This cannot be done.’ No matter how many changes or updates we send their way, even after long working days, they consistently respond positively and find a way forward. What stands out most is that our relationship has evolved beyond a traditional client-supplier setup and feels more like a partnership. QalbIT takes genuine responsibility for the platform’s functionality, and when bugs are identified, they are addressed without hesitation.
Gabriell Summerland, CEO, Bluecircle

FAQs · Custom software development in Jeddah


Frequently asked questions from Jeddah teams

The questions Jeddah trading, logistics and retail teams raise most, from port and customs integration to code ownership and time zones.

Talk to the team
No. QalbIT has no office or legal entity anywhere in Saudi Arabia. Delivery runs remotely from Ahmedabad, India, on Jeddah working hours. We say this plainly because implying a local presence creates a problem for both of us the first time it is checked.
Yes, with the data-protection position handled properly. Under PDPL you are the controller and we are the processor. Transferring personal data outside the Kingdom is permitted under Article 29 with approved safeguards, including Saudi Standard Contractual Clauses. That is contract work done once, before the build starts.
Yes. Phase 2 requires direct integration with the Fatoora platform: UBL 2.1 XML, UUID, cryptographic stamp and QR code, with standard invoices cleared before sending and simplified invoices reported afterwards.
Wave 25 covers VAT-subject revenue above SAR 187,500 in any of 2022 to 2025, with integration required by 1 February 2027. Treat the notification you received from ZATCA as authoritative for your own date, and confirm your status directly rather than relying on any article, this one included.
Jeddah is UTC+3 and we are UTC+5:30: a two and a half hour offset. Your Sunday to Thursday week overlaps ours on four days out of five. Demos and decision calls are scheduled in your hours; Thursday afternoon through Saturday runs on written updates.
Your organisation, in full, in your own repository, once project payments are complete. No licence, no per-seat fee, no restriction on hiring another team afterwards.
Yes, where the system’s interface is documented, and our being remote changes nothing about that. Import declarations go through FASAH on your broker’s account, so we build from the exports and documents your broker and carriers already produce, never by logging in on their behalf. Shipping-line and port-side feeds are scoped the same way. Bring the interface specifications or sample files to the scoping call. Prior experience with that exact platform matters less than having its interface written down.
Yes. Consignment tracking, purchase orders and landed-cost calculation, freight, duty, insurance and the exchange rate on the day, are common first releases for Jeddah trading companies replacing a spreadsheet that stopped being reliable once the volume grew.
Yes. A B2B or dealer portal on top of the system you already run, with role-based permissions that separate what a supplier, a dealer and your own staff can see and change, is straightforward to add without touching the core system underneath.
Yes, provided the first release is scoped tightly rather than broadly. We define one platform and the core journey, give you a clickable prototype in week one and a working demo every two weeks after that, so the pace of the build matches the pace of the business it serves.
Yes. Invoices, manifests and reporting can be fully bilingual with correct right-to-left layout, Arabic invoice and manifest output, and Arabic sorting. Project delivery itself, calls, documentation, written updates, runs in English. If your stakeholder group needs Arabic-language delivery throughout, a local systems house is the better fit and we will say so.
Jeddah systems houses, global consultancies running group-wide programmes, and remote partners such as QalbIT. We build shipment tracking, yard and warehouse allocation, delivery runs and proof-of-delivery apps for freight operators working out of Jeddah Islamic Port. We do it from Ahmedabad, India, on Saudi hours, with no office in Jeddah. A local house is the better pick when the cutover needs people in your warehouse. Where the work is a defined system with documented carrier and broker feeds, distance matters far less.
There is no honest single figure. The price follows what phase one covers, such as purchase orders, letters of credit and landed cost, how many carriers, brokers and banks it connects to, and whether your invoices need ZATCA clearance, reporting or both. Phase one gets a fixed price once we have scoped it together. Migrating several years of shipment and supplier history is quoted as a separate line, so you can see what it adds.
Local agencies, resellers who configure a packaged CRM, and custom builders like QalbIT. We build CRM for Jeddah retailers and distributors: accounts organised by branch and sales route, dealer-specific price lists, van-sales orders and reminders for repeat buyers, with every sale reaching invoicing without re-entry. If a packaged CRM fits how your branches sell, we will tell you to buy it. A custom build earns its place when route sales, dealer pricing or per-branch ZATCA reporting do not fit the product.
Hire locally if the work needs people on a warehouse floor, at a customs desk or in your branches during cutover, if you need Arabic-first delivery, or if an Etimad tender requires a Saudi registration. Hire remotely when the system can be written down as a specification and your own managers make the daily calls. We are the remote option, two and a half hours ahead of Jeddah, and on the first call we say which side of that line your project falls on.
No. ZATCA’s Phase 2 rules are the same across the Kingdom, whichever city you invoice from. What changes for a trader is the path each invoice takes: sales to distributors and wholesalers are cleared by the Fatoora platform before the buyer receives them, and simplified invoices from your shops are reported afterwards. A business selling both wholesale and retail needs both paths working in one system. Duty and import VAT paid at customs are recorded separately, against each shipment, so landed cost reflects what was actually charged.
Our current GCC delivery is a white-label engagement, so we cannot name the end client. We can share detailed case studies from comparable trading and logistics builds in Europe and India, and we would rather tell you that than manufacture a Jeddah reference.

Next step


Let’s scope the first system.

Walk us through how a container, an order or a booking moves through your business today. We will map it, choose the system that should come first and send a phased estimate you can check line by line. If a Jeddah firm is the better answer, we will say that instead. Expect a reply within 24–48 hours, usually with questions about how your goods or bookings flow.