Software development · Supply chain
Supply chain software development in Riyadh
Supply chain software development is the custom software that sits around the systems a business already runs for ordering, stock, warehousing and transport: the portal a customer orders through, the service that tells the warehouse what to pick, the interface that carries a shipment back to the ERP. Interkey, a software company in Riyadh building custom enterprise applications since 1999, develops this layer for organisations in Saudi Arabia. It builds on your ERP, warehouse and transport systems rather than asking you to replace them, and it scopes each project before quoting it.
In short
- What it is: custom applications, services and interfaces around the ordering, stock, warehouse and transport systems you already run.
- What it is not: a packaged supply chain suite. The work is built to your process and scoped per project.
- Who it is for: retailers and e-commerce businesses, distributors, industrial businesses and logistics operators in Saudi Arabia that have an ERP and operational systems and need software to join them up.
- How it is built: backend and integration, Arabic and English web applications, data engineering, and DevOps, by a team in Riyadh working the Sunday to Thursday week.
- What you keep: the source code, the documentation and the deployment pipeline transfer to you at handover.
- How it is bought: quote only, scoped per engagement, usually after a short paid discovery phase.
Where supply chain software is usually needed
Few organisations need a supply chain system written from nothing. The ERP holds the orders, prices and stock. A warehouse system or a spreadsheet holds the picking. A carrier or a fleet system holds the shipments. The trouble sits between them: an order that is keyed twice, a stock figure that is a day old, a delivery status nobody can see until the customer calls.
That gap is what custom software closes. Interkey's software team lists e-commerce and logistics, and ports and logistics, among the environments it delivers into.
What gets built around your supply chain systems
| Piece of software | What it does | What it connects to |
|---|---|---|
| Ordering portal or app | Lets customers, branches or dealers place and track orders in Arabic and English, with proper right-to-left layouts | The ERP: orders, stock and prices |
| Order and stock interface | Passes orders into the ERP once, and passes stock and price changes back out | ERP and online store or portal |
| Warehouse interface | Sends picking lists and receives shipment and goods-receipt confirmations | ERP and warehouse system |
| Transport and delivery interface | Carries shipment status from carriers or fleet systems back to the order | Logistics systems and the ERP |
| Internal tools | Approvals, exception queues and dashboards for the people who run the flow day to day | Whichever systems hold the data |
| Reporting data feed | Moves supply chain data into a reporting platform on a schedule or continuously | ERP, warehouse and a reporting database |
Which of these a project needs, and in what order, is decided in scoping. We do not assume your warehouse or transport systems offer an API: where they do not, the interface is built through the database, files, screens or a message queue.
Integration comes before screens
In supply chain work most of the risk is in the interfaces, not the user interface. Interkey's approach to integration applies directly:
- One contract per interface, agreed before building: what is sent, how often, what a valid message is, and what happens on an error.
- Duplicates are designed for. An order sent twice must not be booked twice, so every interface recognises a repeat and ignores it.
- Ordering is designed for. Warehouse and shipment messages can arrive out of sequence, so the software must cope rather than assume.
- A named owner for each interface, and monitoring for volume, failures and stale data, so a dropped record is found by an alert and not at month-end.
The patterns behind this, and the reasons ERP interfaces fail, are set out in our guide to ERP integration and on the system integration practice page.
Relatedsystem integration
How a supply chain software project runs
-
Discovery.
A short, paid look at the systems involved: what each allows, who owns it, and what can be changed. It sometimes ends with a recommendation not to build, and that is a useful result.
-
Scope and shape.
The work is defined as a scoped project, a dedicated team, or specialists added to your own team, whichever fits where the domain knowledge sits.
-
Build against the contracts.
Interfaces and applications are tested with realistic data, including malformed records, Arabic text and mixed scripts.
-
Release one flow at a time.
Each interface runs in parallel with what it replaces until the outputs agree, then switches. Nothing changes in one weekend.
-
Hand over and, if wanted, operate.
Source, documentation and the deployment pipeline transfer to you. Interkey can also run and monitor the result as a managed service.
When to buy a product instead
If a configured product already meets the requirement, buying it is usually cheaper than building, and stays cheaper because someone else carries the maintenance. Building is the right answer when your process is what sets you apart, or when no product fits without changing how the business works.
What to ask any supplier before you sign
- Which of your existing systems will the software connect to, and has the supplier read their interface documentation?
- Is there a written contract for every interface, with an owner on both sides?
- How does the software handle a duplicated order or a message that arrives late?
- Do the source code, documentation and deployment pipeline transfer to you, written into the contract?
- Is requirements work done in Arabic with the people who use the system?
- Who monitors the interfaces after go-live, and under what scope?
Questions buyers ask
Do we have to replace our ERP or warehouse system?
No. The work is built around the systems you already run. Replacing one is a separate decision, and where a new ERP is going live Interkey can run the integration workstream beside the vendor implementing it.
Do you sell a ready-made supply chain system?
No. This is custom software and integration, scoped per project. If a configured product fits your need better, we will say so in discovery.
Can the software work in Arabic and English?
Yes. Interfaces are built for Arabic and English with right-to-left support designed in, and requirements sessions can run in Arabic.
Do we own the code?
Yes. Source, documentation and the deployment pipeline transfer to you at handover.
How much does a supply chain build cost?
It is quote only, because the shape of the engagement changes the price: a scoped project, a dedicated team or added specialists. A short paid discovery phase comes first so that the estimate rests on what your systems actually allow.
Who looks after it after go-live?
Either your team or ours. Interkey can monitor and maintain what it builds as a managed service from Riyadh.
Next
Read next
Next step
Scope your supply chain build
Tell us which ERP, warehouse and transport systems you run, and where orders, stock or shipments get stuck today. We will propose the scope of a discovery phase.
Or directly
+966-11-2180999 [email protected]Tawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia