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.
Most vendor pages selling into Jeddah talk about the port and the pilgrim season and stop there. This one covers the two legal questions that actually decide whether you can hire us: ZATCA e-invoicing and PDPL cross-border data.
2018
Building software since
5.0
Clutch rating
50+
Clients served
5.0
Clutch rating
Get your free estimate
Three quick questions: scope, approach and a price range back within 48 hours. No sales call required first.
Definition
What a remote software partner actually does for a Jeddah company
QalbIT builds custom software for Jeddah companies as a remote engineering partner, not a local firm. The same two constraints apply as anywhere in the Kingdom: ZATCA Phase 2 e-invoicing, reaching almost every VAT-registered business by 1 February 2027 under Wave 25, and PDPL Article 29, governing personal data leaving Saudi Arabia. QalbIT designs to both. Delivery is remote from Ahmedabad, India, on Jeddah working hours.
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 local Jeddah systems house sits inside the Kingdom, speaks to your operations team in Arabic day to day, and can walk the warehouse floor. A remote partner sits outside it. That changes how personal data moves, how the working week lines up, and who is contractually on the hook for the compliance 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
First builds · legacy rebuilds · integrations · portals
Delivery
Remote from India on Jeddah hours, Sunday–Thursday overlap
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
Programme-scale delivery with an in-Kingdom presence, usually brought in for a group-wide ERP or a multi-entity transformation with a board sponsor.
Remote engineering partner
A small senior team building a defined system on Jeddah hours from outside the Kingdom. No local entity, so the data-transfer question is real. Best when you already know what the system has to do.
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
Most vendor pages argue one side. Here is the version with both.
Hire a remote partner when
- You can describe the system: a trading ledger, a booking platform, a customs or freight tracker, a dealer portal.
- Your team can own day-to-day decisions, so a two-and-a-half hour offset costs nothing.
- The work is a defined build or rebuild, not an open-ended transformation programme.
- You want the source code and the roadmap in your own hands once it ships.
- Your data-protection position is manageable under PDPL with the standard safeguards in place.
Hire locally instead when
- The system holds PDPL-defined sensitive data, health, biometric or genetic data, criminal records; keep that 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 procurement rules require a Saudi commercial registration from the contracting party.
We turn down the projects that land in the second list. Building remotely where the honest answer is a Jeddah systems house wastes your time and, in the sensitive-data case, creates a legal problem neither of us wants.
Next step
Not sure whether to hire locally?
Tell us what the system needs to do and what data it will hold. We will say plainly which side of that line you are on, including when the honest answer is a systems house in Jeddah.
Comparison
Remote partner vs local systems house vs global consultancy
Rates are deliberately absent. This is not a rate comparison, and every row below, including the ones we lose, is a real difference. We will run this against your actual scope and data profile.
| Local Jeddah systems house | Global consultancy | QalbIT (remote partner) | |
|---|---|---|---|
| Physical Jeddah office | Yes | Usually | No |
| Arabic-first delivery | Yes | Varies | No · English delivery, Arabic in the product |
| PDPL role | Controller or processor, in-Kingdom | Processor, usually in-Kingdom | Processor outside the Kingdom · safeguards required |
| Data residency | In-Kingdom by default | In-Kingdom available | In-Kingdom hosting, remote engineering |
| ZATCA Fatoora integration | Common | Common | Yes |
| Working-week overlap | Full | Full | Sunday–Thursday, 2.5-hour offset from India |
| Port and customs system familiarity | Common | Varies | Built to your integration spec, not assumed |
| Source code ownership | Varies | Varies | Yours, full repository |
| Team size on your account | Varies | Large, layered | Small and senior, founder-accessible |
01
The rows we lose are still on the table.
Three of the rows above are reasons to hire someone else. We would rather a Jeddah buyer read that here than discover it 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. We ask for the spec at the scoping call.
03
The time offset is smaller than it looks.
Jeddah runs UTC+3, we run UTC+5:30. Two and a half hours, with the Saudi Sunday–Thursday week overlapping ours on four of five 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
Systems that talk to each other, so a shipment, an invoice and a booking move through your business without three people re-typing the same reference number.
Trading
Trading and import-export platforms
Purchase orders, letters of credit tracking, shipment status and landed-cost calculation in one system, replacing the spreadsheet that 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
Supplier, agent and customer portals sitting on top of the system you already run, with permissions that hold up under an audit.
Hospitality
Booking and capacity systems
Reservation, transport and capacity-management systems for operators handling seasonal volume spikes, built to scale up and back down without redesign.
Backend
Custom backends and APIs
Laravel, Node.js and NestJS services, integrations, queues and scheduled jobs: the layer that makes the rest possible.
CRM
Custom CRM development
Pipelines built around how your sales and agent network actually works, with clean handoff into invoicing where the CRM touches billing.
Cost
How much does custom software development cost in Jeddah?
Custom software development cost in Jeddah is driven by scope, integration count and compliance requirements, not by headcount or an hourly rate. A ZATCA-integrated invoicing layer, a customs or shipping-line integration and a data migration are each a separate cost driver. We scope before quoting and estimate phase one on a fixed basis.
We don’t publish a price range, and would treat any firm that does with some caution.
Search this and the ranges span $10,000 to $500,000. That spread tells you nothing: a two-module CRM for a Jeddah trading office and a multi-entity ERP with Fatoora clearance and three customs integrations are not the same project.
What we do instead is a scoping call, a process map, and a fixed-scope estimate for phase one before you commit beyond discovery. Below is what actually moves that number, so you can sanity-check any quote, ours included.
Try the software development cost calculatorWhat moves the number
Scope of phase one
The largest single driver. One system built properly beats three built thinly. Most first phases cover two connected modules.
Integration count and quality
A modern REST API with OAuth is straightforward. A shipping line or customs system with no event support needs a middleware and reconciliation layer.
ZATCA integration depth
Reporting simplified invoices is not the same job as clearing standard invoices. Clearance means CSID onboarding, XAdES signing, hash chaining and a failure-handling path.
Data protection architecture
Where personal data lives, what crosses the border, and what gets tokenised at the boundary. Near-free to design at the start, expensive to retrofit.
Arabic in the product
Bilingual interface, right-to-left layout, Arabic-correct invoice and manifest output. Real engineering, frequently underestimated.
Data migration depth
Migrating masters and opening balances is routine. Migrating years of consignment or booking history with reconciliation is a project of its own.
How we work with Jeddah teams
A delivery process built around a 2.5-hour offset
The offset is small. The working week and the operational rhythm of a trading business are not the same as a Riyadh office’s. We plan around both.
Discovery and process mapping
Walk through how a shipment, order or booking moves through your business today, who touches it, and where it breaks. Identify the highest-pain system for phase one and the data-protection profile for the whole build.
Process map, system roadmap, realistic phase-one estimate, written data-transfer position.
1–2 weeks
Architecture and data design
Design the data model, screens and integration contracts, including any port, customs or shipping-line interfaces. Decide what is hosted in-Kingdom and what never leaves.
Approved data model, screen designs, integration plan, hosting and residency decision.
2–3 weeks
Build phase one
Develop in weekly increments, demoing with your real shipments, bookings or accounts, not dummy data. Demos land in your Sunday–Thursday week.
Working modules validated against real operational scenarios.
6–14 weeks, scope-dependent
Migration, training and parallel run
Migrate masters and opening balances, train branch or warehouse staff, and run the new system alongside the old one until the numbers reconcile.
Confident go-live with reconciled data and trained users.
2–4 weeks
Stabilise, extend, roll out next
Tune performance, add reports and automations, then build the next system on the roadmap once adoption settles.
A system that grows with your operation rather than a one-time delivery.
Ongoing, month-to-month
The Saudi working week runs Sunday to Thursday. Jeddah is UTC+3 and our team is UTC+5:30: a two-and-a-half hour offset, with four of your five working days fully overlapping ours. Thursday afternoon and Friday–Saturday run on written updates rather than pretended away.
Book a scoping callWhere we fit best
Jeddah projects we take on
These are the engagements that work well remotely. The ones that don’t are listed higher up the page.
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
Old desktop or early web systems rebuilt as modern web applications, without losing years of consignment or account data or retraining everyone overnight. For companies stuck on unsupported systems.
Compliance
ZATCA and PDPL retrofit
Bringing an existing system to Fatoora clearance and restructuring where personal data sits. Often the deadline is what starts the project. For companies with a Wave 25 notification.
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
Operational software is industry-shaped. These are the sectors where the process knowledge transfers.
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
Reservation systems, fleet and capacity management for operators handling sharp seasonal demand swings across the year.
Retail and distribution
Multi-branch operations, high transaction volume, and simplified-invoice reporting to ZATCA within the required window.
Next step
Your process is the reason the off-the-shelf tool doesn’t fit.
That is usually the actual case for a custom build. Describe the process and we will tell you honestly whether it justifies the project.
Saudi compliance
Building software for Jeddah: ZATCA, PDPL and data residency
The same two regulations decide this everywhere in the Kingdom. What differs in Jeddah is which system usually triggers the question first: an invoicing platform or a customs and freight system carrying personal data on drivers, agents and consignees.
ZATCA e-invoicing (Fatoora)
Phase 2 requires direct integration with ZATCA’s Fatoora platform. Standard B2B and B2G invoices clear before you send them; simplified B2C invoices report afterwards. Invoices carry UBL 2.1 XML, a UUID, a cryptographic stamp and a QR code. Wave 25, announced 24 July 2026, covers taxpayers whose VAT-subject revenue exceeded SAR 187,500 in any of 2022 to 2025, with integration required by 1 February 2027, half of Wave 24’s threshold and effectively the bottom rung. For a Jeddah trading business this usually means invoicing and freight-billing systems both need the integration, not just one. Where integrations fail: CSID onboarding, XAdES signature validity, and the previous-invoice-hash chain breaking after a rejected clearance, which silently invalidates everything downstream. Sources: ZATCA Wave 25 e-invoicing announcement, zatca.gov.sa · Zakat, Tax and Customs Authority.
Phase 2 · Wave 25
PDPL and cross-border data
The Personal Data Protection Law, enacted by Royal Decree M/19 and amended by M/148, became fully enforceable on 14 September 2024, and applies extraterritorially: an organisation outside the Kingdom processing personal data of people inside it is in scope, including us. For a Jeddah logistics or trading business this most often touches driver, agent and consignee records inside a freight or CRM system. Article 29 permits transferring that data outside the Kingdom under SDAIA’s approved safeguards, including Saudi Standard Contractual Clauses, with a risk assessment where those apply. In practice you are the controller and we are the processor. The transfer has to be justified, documented and contracted, not assumed. Sources: Regulation on Personal Data Transfer Outside the Kingdom, v2.0, August 2024, dgp.sdaia.gov.sa · Saudi Data & AI Authority.
Royal Decree M/19
Vision 2030 context
Saudi Arabia’s digital economy reached approximately SAR 495 billion, contributing 15% of national GDP, with the ICT market surpassing SAR 180 billion by 2024. The Kingdom ranked first globally in the ITU’s 2025 ICT Development Index. Sources: Ministry of Communications and Information Technology · Communications, Space and Technology Commission.
We build systems that emit compliant output natively rather than bolting a compliance module onto software that resists it. If a Wave 25 notification is driving your timeline, that date is where we start planning backwards from.
Working with us
Hiring a vendor outside the Kingdom: the honest version
Every foreign vendor selling into Saudi Arabia carries the same four exposures. Here they are, named.
Data transfer
You are the controller. Every transfer of personal data to us needs a lawful basis under Article 29 and documented safeguards. Contract work, done once, before the build.
Sensitive data
Health, biometric, genetic and criminal-record data carries tighter restrictions. If your system holds it, plan for in-Kingdom processing regardless of who writes the code.
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. Floor rollouts and physical cutovers need local hands, and we say so before you sign.
Everything else
Payment gateways, e-invoicing service providers, accounting products, shipping-line and customs systems, banking APIs, BI tools.
Integrations
None of that is a reason to avoid a remote partner. It is a reason to handle the contract properly at the start rather than assume it away.
Tech stack
Technology we use for Jeddah builds
Trading and logistics systems live for a decade. We choose proven technology your future team, internal or external, can maintain.
Backend and business logic
- Laravel (PHP 8.x) for modular business systems with strong audit trails.
- NestJS (TypeScript) where event-driven flows and heavy integrations dominate.
- Queues and schedulers for syncs, alerts and report generation.
Frontend and usability
- Next.js and React with keyboard-first data entry and fast text views.
- Bilingual Arabic and English interfaces with correct right-to-left layout.
- Role-based dashboards for owners, managers and dispatch teams.
Data and integrations
- PostgreSQL and MySQL with strict constraints for financial and consignment integrity.
- ZATCA Fatoora clearance and reporting APIs.
- Integrations with accounting products, payment gateways, shipping-line and customs systems.
Security and residency
- Role- and location-based permissions with full audit logging.
- In-Kingdom hosting options where residency is required.
- Automated backups, staged deployments, monitoring and alerting.
Running an existing ERP, an accounting product, or spreadsheets-plus-email today? We can integrate and extend before we replace: the migration path is part of the plan, not an afterthought.
Outcomes
What the project should actually change
Not projections. These are the operational changes the build is meant to produce, and how you would know whether yours did.
| What changes | How you’d measure it |
|---|---|
| One source of truth across branches, warehouses and agents | Variance between system records and physical or ledger count |
| Compliance output is generated, not assembled | Hours per filing period |
| Invoices clear ZATCA first time | Rejected-clearance rate and hash-chain breaks |
| Approvals are enforced, not remembered | Share of transactions with a complete audit trail |
| Arabic output is correct without manual fixing | Documents requiring rework before sending |
| Owners see position without asking anyone | Time from question to answer |
A note on sourcing
A note on sourcing
We don’t quote a headline failure rate for software projects. The widely circulated figures attributing 55–75% failure to Gartner have no traceable primary source, and we won’t repeat them to make a point. Where we cite a number on this page, the source and date are next to it.
Why QalbIT
Why work with us
Eight years building operational software
120+ engagements delivered across web, mobile and platform work, with 50+ clients. Clutch 5.0, Google 4.9, Upwork Top Rated. We deliver into the GCC today as a white-label engineering partner to a regional agency, and our Saudi-facing work is built on that same operational-software experience.
We say what we are
No Jeddah office, no local entity, no implied presence. The compliance section above exists because we would rather lose a deal at the scoping call than at the audit.
You own the code
Full source ownership, documented, in your repository. No licence, no per-seat fee, no restriction on hiring a different team later.
Senior team, founder-led
A small senior team with direct access to the people writing the code. You won’t be handed to an account manager who relays questions to engineers you never meet.
We’ll tell you to hire locally
When a Jeddah systems house is genuinely the better answer, we say so on the first call. It costs us a project and saves you a year.
QalbIT did a great job turning my idea into a real product. What I really appreciate is how well they understand my requirements, even when I'm not fully sure how to explain or finalize things. They listen patiently, guide me when I'm stuck, and always try to find the right solution. I really enjoy working with their team and I'm definitely looking forward to continuing our work together in the future.
FAQs · Custom software development in Jeddah
Frequently asked questions from Jeddah teams
These are the questions trading, logistics and operations leads actually ask when they compare a remote partner with a local systems house.
Talk to the teamNext step
Let’s scope the first system.
Tell us how goods, bookings or paperwork move through your business today. We will map the process, name the system that earns its place first, and give you an honest, phased estimate. If a Jeddah firm is the better answer, we will say that instead. Typically a reply within 24–48 hours, with questions rather than a brochure.