Skip to main content
Logistics

A shipment is managed by evidence not by a phone call

We implement logistics operations systems — from the delivery order through proof of delivery, collection, trip cost and client stock — sized to your operation: last-mile needs evidence before speed, a third-party warehouse bills on actual movement, an own fleet makes every trip a cost centre, and e-commerce fulfilment carries custody of someone else’s stock. This is not an operational luxury here: the Kingdom links three continents, and timing and documentation are a business requirement rather than a choice.

Request an operations assessmentSee the operation types
  • Four operation types, four scopes
  • Proof of delivery before talk of speed
  • Every trip’s cost known
  • Not a freight or customs broker
  • No market figures, no delivery-time promises

Direct answers

The questions asked first

How do you treat last-mile, warehousing, an own fleet and e-commerce fulfilment differently?

By fit rather than price: last-mile suffers from evidence — who received it, when, and against what collection? So it starts with documented proof of delivery and matching collection, and installing advanced route planning before that is waste. A third-party warehouse suffers because what is on the shelf is not its own: it needs storage locations, documented movement and an invoice built on measured space or throughput rather than an estimate. An own fleet suffers because a trip is known by its fuel receipt rather than its cost: it needs the trip as a cost centre, recorded maintenance and consumption per route. E-commerce fulfilment suffers from custody of another merchant’s stock: it needs balance accuracy with clear storage contracts, billing on movement, and returns entered against the same balance. In the assessment we tell you which of these you are.

Do you guarantee delivery times?

We guarantee no time at all, and no system can: timing depends on the road, congestion, weather, customs schedules, vehicle availability and the recipient’s behaviour, none of which we control. What we do commit to is that the promise is measured against the stated time on every shipment, that the cause of any delay is known by its cause rather than by a verbal explanation, and that proof of delivery is complete. Any time commitment or compensation for delay is a service agreement between you and your customer, not a promise from a system.

Do you clear shipments through customs or act as the carrier?

No. We are a systems company: we do not carry goods, do not broker freight, do not clear customs, do not issue transport licences and accept no statutory liability for cargo. What we do is build the system that runs the operation: delivery orders, proof of delivery, collection, trip cost, client stock, service invoicing and on-time reporting — while licensing, clearance and carriage remain the responsibility of the licensed party. We say so at assessment stage, before the contract.

What usually stops logistics projects?

Three things we see repeatedly, none of them technical: undocumented proof of delivery — a signature on paper or a message, which proves nothing in a dispute or a financial claim; collection that does not reconcile — money sitting with drivers, settled late with the details lost; and non-unified master data — addresses, zones, prices and lead times shaped differently for every client, making on-time and cost calculation impossible. That is why we start with addresses, zones, service definitions and proof of delivery, before any promise about an indicator or a report.

Context

Why this sector is different in the Kingdom

Four operational realities impose requirements on the system that do not appear in other markets — with no market figures and no growth estimates.

The sector sits within Vision 2030 priorities

Logistics is one of the strategic sectors in the Kingdom’s Vision 2030, which means a general direction towards more efficient and more local supply chains — and we publish no programme numbers or targets, because they are not ours and we cannot verify them.

Context, not a figure

A link between three continents

The Kingdom’s position makes transit freight and the link between ports and industrial cities part of daily operations, which surfaces the need for accurate timing and documentation that evidences what happened across more than one point.

Documented timing

E-invoicing on every service

Transport, storage and collection invoices fall under e-invoicing requirements, so issuing them from the system with a submission and response log becomes part of operations rather than later administrative work.

Documented compliance

A distributed, mobile workforce

Drivers, couriers and warehouse supervisors work away from the office on a changing connection, so the system needs entry that works offline and syncs later without losing data.

Offline, then synced

We state the context because it explains the requirements — not to sell with it: we publish no market size, no growth rate, no programme target and no expected improvement percentage, because such a figure is either something we cannot verify or something that does not apply to your operation.

Operations

Four operation types — and four different scopes

The same sector does not mean the same project. Read your operation first, then what fits you — and, plainly, what does not.

Last-mile delivery

Hundreds to thousands of shipments daily · couriers and vehicles · often cash on delivery

What it suffers from
Evidence is missing: “delivered” is said by phone, a signature on paper proves nothing in a dispute, and the money collected by the courier is settled late with its detail lost.
What fits it
A documented delivery order per shipment, a courier app that works offline and syncs later, proof of delivery by signature, photo or verification code, and a recorded reason for any failure with an organised second attempt.

What does not fit you: Advanced route planning before documented proof of delivery exists, connecting tracking devices before addresses and zones are unified, and measuring customer satisfaction before knowing who actually received the shipment.

Third-party warehousing (3PL)

Storage for several clients · inbound and outbound · billing by space or movement

What it suffers from
What is on the shelf is not yours: it is unclear which item belongs to which client at which location, invoices rest on estimated space, and the difference surfaces when the client claims rather than before.
What fits it
Separating each client’s stock into dedicated locations, inbound and outbound on documented orders, invoicing built on measured space or throughput with published rules, and periodic balance reports per client.

What does not fit you: Onboarding all clients before locations are separated, relying on an external spreadsheet for billing, and building client stock reports from a file separate from the warehouse so the numbers disagree at the first claim.

Own fleet and transport

Owned vehicles and drivers · trips and routes · maintenance and fuel

What it suffers from
A trip is known by its fuel receipt rather than its cost: route is not compared with route, it is unknown which client or lane consumes more, and maintenance is handled at breakdown rather than before it.
What fits it
The trip as a cost centre gathering fuel, maintenance, driver and violations; plan against actual per route; a maintenance log with inspection cycles alerted before they fall due; and known consumption per vehicle.

What does not fit you: Relying on fuel cards alone as the cost source, managing maintenance in a file separate from the system, and connecting new tracking devices before trip and driver data are unified.

E-commerce fulfilment

Stock for several merchants · picking and shipping · returns and per-merchant rates

What it suffers from
Custody of someone else’s stock: you are held to balance accuracy, a return from the end customer is not entered against the balance, and the service rate per merchant is unknown so it is negotiated by estimate.
What fits it
Accurate stock per merchant in separate locations, documented picking and shipping per order, returns entered against the balance with a recorded reason, per-merchant service pricing on published rules, and per-merchant performance reports built from the operation rather than a file.

What does not fit you: Accepting new merchants before their locations are separated, promising a service rate before the real operation is measured, and managing returns by hand outside the system so differences swell every season.

The bands here are indicative guidance rather than an official classification, and the criterion is the nature of the obligation: a promise to an end customer, custody of someone else’s stock, running your own vehicles, or holding merchants’ goods in trust. Two of them can coexist in one company, and each has a different starting point.

Symptoms

What usually shows up in logistics operations

Eight recurring symptoms, each with a different root cause — which is why the treatment differs even when the complaint sounds the same.

Proof of delivery said by phone

“I delivered yesterday” proves nothing in a client dispute or a financial claim, and does not establish who received it or when.

Cause: no documented evidence

Collection that does not reconcile

Money held by couriers is settled at week or month end, so small differences disappear and accumulate into an amount nobody can explain.

Cause: deferred reconciliation

Addresses and zones not unified

The same address appears in different forms per client and the zone is judged by eye, making punctuality or lane cost impossible to compute consistently.

Cause: scattered master data

A trip with no known cost

Fuel comes from an invoice, maintenance from a workshop, the driver from payroll — and no single figure says whether this lane earns or loses.

Cause: no cost centre

Maintenance at breakdown rather than before

No fault history and no known inspection cycles, so a vehicle stops on a peak day and shipments are rescheduled with no view of how often the fault recurs.

Cause: maintenance without a log

Client stock not separated

Items for several clients sit in one location without clear separation, so one client’s item is issued in place of another and the error surfaces at count or claim time.

Cause: locations not separated

Storage invoiced by estimate

The invoice rests on remembered space or an approximate pallet count, so you under-bill the large client and over-bill the small one.

Cause: unmeasured billing

Dispatch that cannot be compared

Each supervisor dispatches their own way, and whether yesterday’s dispatch was better than today’s is never measured, so the operation improves by luck or not at all.

Cause: dispatch not measured

Components

What we implement in the operation

Eight components built in order according to your operation; we do not implement all of them for an operation that does not need them all.

Addresses, zones and service definitions

Unifying addresses and zones, and defining each service (delivery, pickup, return, storage) with its time, price and rules — the base everything else is computed on.

The base

Delivery orders and dispatch

A documented order per shipment, assignment to a courier or vehicle, and organised delivery attempts with a declared reason for each failure.

A shipment with an order

A field app that works offline

An app for the driver and courier that works without a connection and syncs later: the shipment list, navigation, proof of delivery and collection capture.

Offline, then synced

Proof of delivery and collection

A signature, photo or verification code per delivery, the collected amount recorded and tied to the shipment and client, and a daily settlement per courier.

Evidence and reconciliation

The trip as a cost centre

Gathering fuel, maintenance, driver and violations into one trip cost, and comparing plan against actual per route and client.

Does the lane earn?

Fleet, maintenance and inspection cycles

A record per vehicle, preventive maintenance and inspection cycles alerted before they fall due, and a fault log showing recurrence and operational impact.

Before the breakdown

Client stock in separated locations

A location or area per client, inbound and outbound on documented orders, and periodic per-client balance reports that stand up to a claim.

Documented custody

Service invoicing, reporting and compliance

A transport or storage invoice on published rules through the statutory integration with a submission and response log, plus punctuality, evidence and cost reporting decisions can be read from.

A documented invoice and report

Method

The method: from master data to operation

Eight stages, each with a published output, starting with addresses, zones and service definitions rather than with configuration — because computing punctuality on non-unified data produces a false number.

  1. 01

    Assessment and operation type

    A visit covering operations, the warehouse and trips, establishing the real operation type, what runs on spreadsheets today, and where the largest financial or contractual risk sits.

    Output: an assessment naming your type
  2. 02

    Master data

    Unifying addresses, zones, prices, lead times, service definitions and clients — because computing punctuality on non-unified data yields a false number.

    Output: unified master data
  3. 03

    Configuration and testing

    Configuring delivery orders, collection and pricing, and running a full cycle on real data: order, delivery, proof, collection, settlement, invoice.

    Output: one complete tested cycle
  4. 04

    Field app and training

    Training drivers and couriers on the offline app, proof of delivery and collection capture, with illustrated guides left with you.

    Output: a guide per role
  5. 05

    Phased go-live

    Going live on one lane, branch or client first, then expanding — not switching the whole operation in a single day.

    Output: one lane running, then expansion
  6. 06

    Fleet and maintenance

    Vehicle records, inspection cycles and preventive maintenance, and tying fuel and maintenance cost to the trip so lane cost becomes known.

    Output: a known trip cost
  7. 07

    Integration and reconciliation

    Connecting clients, payments, e-invoicing and tracking devices where an interface exists, reconciling collections and balances with accounting, and closing a first period.

    Output: a documented close with its differences
  8. 08

    Periodic improvement

    A periodic review: which lane consumes more, where delivery failure recurs, which client’s times are missed most, and which report nobody uses and should be dropped.

    Output: a periodic improvement report

The durations shown are planning ranges to help you build your schedule, not contractual commitments: the actual duration depends on how clean your data is, how ready your addresses are and how quickly adjustments are approved, and can be affected by peak season.

Measurement

What we measure in a logistics project

Indicators read from the operation itself, not promises about market numbers.

Punctuality against the stated time

The share of shipments delivered within the agreed time per service and client, because a promise that is not measured can neither be improved nor defended.

Proof-of-delivery completeness

The share of deliveries with documented evidence (signature, photo or code), because a delivery without evidence does not count in a financial claim.

Collection reconciliation

The gap between collected and expected per courier and shift, and how much settlement is late — because lateness is what erases the trail.

Trip-cost coverage

The share of trips whose full cost is known (fuel, maintenance, driver), because a trip without cost turns lane pricing into guesswork.

Client-stock accuracy

The count-versus-balance gap per client separately, because you are held to the accuracy of goods held in trust rather than owned.

We announce no improvement or saving percentage, no capacity increase, no time commitment, and no figures about market size or programme targets. What we measure is punctuality against the stated time, proof-of-delivery completeness, collection reconciliation, trip-cost coverage and client-stock accuracy — figures read from your system about your operation.

Integration

Where the system lives in your operation

We connect what you have instead of forcing its replacement, and we inspect every interface before promising it.

Odoo (sales, stock and accounting)

The shipment, collection and invoice on the same stock and accounting entries, so the work is not run in two systems.

The primary integration

Maps and addresses

Connecting maps to capture coordinates and measure actual distance, after addresses and zones are unified — not before.

After addresses are unified

Tracking devices — where an interface exists

We read from tracking devices only if they export data through an available interface, and after inspecting it; we neither supply nor install devices nor program their units.

An explicit boundary

E-invoicing

Connecting transport and storage invoices to the statutory integration with a log of every submission and response, and reports for anything failed or rejected.

With a documented log

Client systems

Receiving delivery orders from the client’s system and returning delivery status to it, after inspecting its interface; if it has none we say so.

After the interface check

Boundaries

Where our scope stops — written before you ask

In logistics, a management system gets conflated with licensing, carriage, clearance and devices, so the separation is written out plainly.

Carriage, freight and customs clearance

We are not a carrier, a freight broker or a customs broker, and accept no statutory liability for cargo or customs transit times; we run the system that documents the operation.

Transport licences and permits

We issue no licences, run no permit procedures and represent no regulator; the assessment notes which licences the system operation needs, and nothing more.

Tracking devices and sensors

We supply no tracking devices or sensors, do not install them and do not calibrate them; where an existing device exposes an interface we read from it after inspection.

Time guarantees, compensation and insurance

We guarantee no delivery time, decide no compensation for delay and provide no cargo insurance; those are obligations written into the service agreement between you and your customer.

When what is needed falls outside our scope we say so in the assessment and refer a licensed specialist instead of accepting it and learning at your operation’s expense. That is written in the contract, not left to courtesy.

FAQ

Questions specific to logistics

Direct answers on operation types, scope, responsibilities and what we do not guarantee.

How do you treat last-mile, warehousing, an own fleet and e-commerce fulfilment differently?

By fit rather than price: last-mile suffers from evidence — who received it, when, and against what collection? So it starts with documented proof of delivery and matching collection, and installing advanced route planning before that is waste. A third-party warehouse suffers because what is on the shelf is not its own: it needs storage locations, documented movement and an invoice built on measured space or throughput rather than an estimate. An own fleet suffers because a trip is known by its fuel receipt rather than its cost: it needs the trip as a cost centre, recorded maintenance and consumption per route. E-commerce fulfilment suffers from custody of another merchant’s stock: it needs balance accuracy with clear storage contracts, billing on movement, and returns entered against the same balance. In the assessment we tell you which of these you are.

Do you guarantee delivery times?

We guarantee no time at all, and no system can: timing depends on the road, congestion, weather, customs schedules, vehicle availability and the recipient’s behaviour, none of which we control. What we do commit to is that the promise is measured against the stated time on every shipment, that the cause of any delay is known by its cause rather than by a verbal explanation, and that proof of delivery is complete. Any time commitment or compensation for delay is a service agreement between you and your customer, not a promise from a system.

Do you clear shipments through customs or act as the carrier?

No. We are a systems company: we do not carry goods, do not broker freight, do not clear customs, do not issue transport licences and accept no statutory liability for cargo. What we do is build the system that runs the operation: delivery orders, proof of delivery, collection, trip cost, client stock, service invoicing and on-time reporting — while licensing, clearance and carriage remain the responsibility of the licensed party. We say so at assessment stage, before the contract.

What usually stops logistics projects?

Three things we see repeatedly, none of them technical: undocumented proof of delivery — a signature on paper or a message, which proves nothing in a dispute or a financial claim; collection that does not reconcile — money sitting with drivers, settled late with the details lost; and non-unified master data — addresses, zones, prices and lead times shaped differently for every client, making on-time and cost calculation impossible. That is why we start with addresses, zones, service definitions and proof of delivery, before any promise about an indicator or a report.

Does a small logistics company need a full system?

No. It needs three things done well: unified master data for addresses, zones and prices; a delivery order with documented proof of delivery; and a collection settled daily. Advanced route planning, connecting tracking devices and complex dashboards add setup and entry a small team cannot carry and get abandoned after months. An abandoned project is worse than a small successful one — and we say so at assessment stage even when it means a smaller scope for us.

Do you integrate with our tracking devices?

Yes, if it exports data through an available interface: we inspect the interface first (a file, a protocol or an API) and say plainly if the device does not provide one. We neither sell nor install devices and do not program their units — that is device-specialist work, and separating responsibility helps you when something fails. The data we read is tied to the shipment and the trip so reports can be built from it, not merely displayed as a map.

What is out of scope?

Carriage, customs clearance, transport licences and permits; tracking devices, sensors and their supply and installation; cargo insurance; delay compensation; guaranteed delivery times or a punctuality improvement percentage; running the warehouse or fleet on your behalf; system and cloud licences (contracted in your name); and publishing market-size figures or national programme targets. We say all of this at assessment stage, before the contract.

Which operation type are you?

Tell us your daily shipments, vehicles and warehouses, and whether you collect on delivery, and we will come back with an assessment naming your type, the fitting scope — and what does not fit you.

  • An assessment that names your operation type
  • A written scope before any commitment
  • A plain statement of what is outside our scope
Request a proposal

Related topics

We are a systems implementation and integration company, not a carrier, a freight broker or a customs broker: we do not carry goods, do not clear customs, do not issue transport licences and accept no statutory liability for cargo or for customs transit times, and we supply and install no tracking devices or sensors. We guarantee no delivery time, no punctuality improvement percentage and no fuel or capacity saving, and we publish no figures about market size or national programme targets. Durations shown are planning ranges rather than commitments, and the scope of work is written into the contract.