Freight transport software in Algeria (2027): trips, consignment note, driver advances, proof of delivery, empty returns and margin per trip

“The truck came back empty from Ouargla, the driver returned twenty-five thousand dinars of expenses without a single receipt, the shipper disputes thirty hours of waiting, and the invoice went out three weeks later because the signed note had stayed in the cab.” Freight transport software is not a dot moving on a map: it is a trip kept as an object, an order, a truck, a driver, a consignment note, milestones, timestamped waiting, a proof of delivery; an advance settled on return; an invoice issued that same evening; a backhaul looked for before the truck leaves empty; and a margin computed trip by trip. This guide describes what gets built, for a six-truck carrier as for one chartering sixty.

Symloop13 min read
Freight transport software in Algeria: trips, empty returns, marginWhat gets built for a carrier: shipper order, trip, consignment note, driver advance, proof of delivery, invoice that evening, margin per tripFREIGHT TRANSPORT SOFTWARE · ALGERIA · 2027Freight transport softwarein Algeria: trips, empty returns, marginWhat gets built for a carrier: shipper order, trip,consignment note, driver advance, proof of delivery, invoiceA TRUCK BACK EMPTYand an invoice sent three weeks laterA TRIP COUNTED ON RETURNbackhaul looked for, invoice that eveningsymloop.com

Short answer. Freight transport software in Algeria in 2027 holds five things. Orders and a rate grid: shippers, lanes, the price per trip, per tonne or per kilometre, waiting free time, the payment term; the order arrives through a portal, WhatsApp or an API, and its price is written before loading. A trip: an order, a truck, a driver, a consignment note, milestones, timestamped waiting, a proof of delivery, and if possible a backhaul; it is the object everything else reads. A driver app that works without network: milestones, photos of the load and of the signed note, expense receipts, fill-ups; the advance is handed over against signature and settled on return. An invoice issued on return on the signed note, waiting billed per the grid, receivables tracked per shipper against the written term. And a management view that reads margin per trip, per truck and per lane, empty kilometres against a threshold, and everything still open: unsettled advances, trips without a note, orders without a consignment note.

This guide is for the road carrier with five to fifty trucks, the manufacturer or distributor running its own long-haul fleet, the one chartering other carriers, and the founder living in France who wants to build for Algeria what online freight exchanges do there: find a load for the way back. In the common description, a consignment note is the document issued by the carrier giving the details and instructions of the shipment, in principle the transport contract itself, with the names of the sender and the consignee, the point of departure and the destination. This guide builds the application around that document and the trip it describes. It does not repeat how a vehicle’s consumption and cost per kilometre are measured, described in the fleet management guide, nor how thirty urban stops are ordered, described in the delivery rounds guide; here the truck leaves full for a single destination, and the question is what it brings back. Transport contract rules, documents required on the road, driving times and tax are for the manager and counsel: the application produces the documents and applies the grid they write. And this guide gives no national empty-run statistic: the empty share is measured at your company, truck by truck.

One trip, from the shipper’s order to the evening invoice: empty return or backhaul

The figure follows a four-day trip, Algiers–Ouargla and back, and counts what it earns depending on whether the truck returns empty or loaded.

Figure 1 · A four-day trip followed from the shipper’s order to the evening invoice: truck and driver assigned with a signed advance, consignment note and photo at loading, timestamped waiting at unloading, delivery proven by a signed and photographed note, backhaul found at three in the afternoon, road expenses settled on return. The same trip earns sixty thousand seven hundred and twenty dinars if it comes back empty and one hundred and fifty-one thousand seven hundred with the backhaul. Figures, distances and names are a constructed example.

Order and assignment: Monday at 6:00, shipper A places an order on its portal, twenty-four tonnes of building materials for Ouargla; the price comes from the grid, one hundred and eighty thousand dinars per trip, with twenty-four hours of waiting free time. At 7:30 the dispatcher assigns truck T4 and Rachid; the expense advance, twenty-five thousand dinars, is handed over against signature in the application. Loading: at 9:10 consignment note LV-0612 is produced from the order, the load is photographed, the weight noted; at 9:40 the truck leaves, and the driver’s phone records milestones without network per the offline application guide. Waiting: Tuesday at 6:20 arrival is timestamped and geolocated, the waiting clock starts; unloading only begins Wednesday at 12:20, thirty hours later; six hours exceed the free time, and the grid bills them, twelve thousand dinars, beyond argument because both timestamps come from the phone, not from a statement.

The proof: at 12:40 the signed delivery note is photographed, timestamped and geolocated per the trustworthy photos guide; the consignee’s reservations, if any, are entered with their photos. The return: from delivery, the application looks for a backhaul, open orders from known shippers around Ouargla heading north, and tells by WhatsApp those who usually ship on that lane; at 15:00 shipper C confirms eighteen tonnes for ninety-five thousand dinars, with a sixty-kilometre detour. The account: Thursday at 20:00 Rachid hands back twenty-one thousand four hundred dinars of photographed receipts and three thousand six hundred in cash, the advance is settled, and shipper A’s invoice goes out that same evening. Empty, the trip would have earned sixty thousand seven hundred and twenty dinars, thirty-two percent; with the backhaul, one hundred and fifty-one thousand seven hundred, fifty-three percent. Figures, distances and names are a constructed example.

«The trip is an object: an order, a truck, a driver, a consignment note, milestones, a proof of delivery; its margin is computed on return, and the backhaul is looked for before the truck leaves empty.»
01

Six real situations, and what the application does

Each row is a sentence heard at a carrier, and the answer is a trip kept as an object, not a more honest driver.

Figure 2 · The first three rows are settled by the backhaul, the settled advance and the photographed note; the next three by timestamped waiting, margin per trip and the tracking link. None is settled by a more honest driver or a more present manager.

The truck comes back empty: the backhaul is looked for from delivery, sometimes from assignment; shippers in the arrival region are told, the dispatcher sees candidates ranked by detour and revenue, and the share of empty kilometres is tracked per truck against a written threshold. Expenses returned without receipts: the advance is signed at departure, each expense is a receipt photographed on the phone with its category, and settlement happens on return; an unsettled advance stays an open line in the driver’s name. Invoice sent three weeks later: the signed note is photographed at delivery, the invoice is issued on return from the trip; no note, no invoice, and the trip without a note shows in the evening list.

The shipper disputes the waiting: arrival and start of unloading are timestamped and geolocated; the free time and the hourly price are in the grid they accepted; the invoice shows the computation. Nobody knows which trip makes money: every trip has its margin, grid revenue minus measured fuel, justified expenses and fixed cost per kilometre; the manager reads it per truck, lane and shipper. “Where is my truck?”: the shipper has a tracking link per trip with milestones, and the agent of the WhatsApp agent guide answers from the trip status; the dispatcher no longer picks up three times per load.

02

Freight transport software, in five layers

The trip is the accented layer: the grid sets its price, and everything else only writes or reads it.

Figure 3 · The accented layer is the trip: an order, a truck, a driver, a consignment note, milestones and a proof of delivery gathered in one object. The grid above sets its price; the driver, the invoice and management below only write and read it.

Orders and rate grid. Shippers, their lanes, the price per trip, per tonne or per kilometre, waiting free time and the hourly price beyond it, the payment term and the credit ceiling per the customer credit guide; the order arrives through the shipper portal, WhatsApp, or the partner API for an equipped manufacturer; the price is computed by the grid and accepted before loading. Trip. An order, a truck, a driver, a consignment note produced from the order, milestones, timestamped waiting, a proof of delivery with reservations, a backhaul attached to the same trip; a trip entrusted to another carrier follows the rules of the subcontracting guide, accepted order, required proof, computed settlement. Driver. An app on their phone, offline first: milestones, photos, expense receipts by category, fill-ups with the odometer; every entry says who and when, per the roles guide.

Invoice and collection. The invoice is produced from the trip on return: flat rate or tonnage, waiting per the grid, the backhaul invoiced to its own shipper; receivables are tracked per shipper against the written term, reminders go out per the notifications guide, and the export goes to the accountant per the integration guide. Management. The board of the dashboard guide: margin per trip, truck, lane and shipper; empty kilometres against the threshold; fixed cost per kilometre taken from the fleet; open advances, notes and consignment notes. A passenger carrier has other objects, tickets, seats, conductor, described in the passenger transport guide.

03

The month’s board: six trucks, empty kilometres, margin, receivables

The figure is what the manager reads at month end: six rows, one per truck, and two panels for what is owed and what is still open.

Figure 4 · The board the manager reads at month end: per truck, trips, kilometres, the share driven empty against the threshold they wrote, revenue and margin, fixed cost per kilometre included; per shipper, receivables against the contract term; and what is still open, unsettled advances, trips without a signed note, an order without a consignment note. Trucks, shippers and figures are a constructed example.

The trucks: sixty trips and ninety-six thousand kilometres in the month, thirty-six percent of them driven empty; T4, twenty-two percent empty, makes the best margin, one million fifty thousand dinars; T3, forty-nine percent empty, makes the weakest, two hundred and ten thousand, with almost as many kilometres; T3 and T1 exceed the forty-percent threshold the manager wrote, and their lanes are where the backhaul is looked for first. The margin: three million six hundred and forty thousand dinars on twelve million two hundred thousand of revenue, thirty percent, fixed cost per kilometre included; T1 and T6 have almost the same turnover, not the same margin.

Receivables: three million two hundred and twenty thousand dinars across three shippers; shipper B owes eight hundred and sixty thousand for seventy-two days, beyond the sixty-day term written in the contract, and the application blocks or flags a new order per the manager’s rule. What is still open: three unsettled driver advances for sixty-four thousand dinars; four trips without a signed note, therefore not invoiced; one order that left without a consignment note. Each line has a name and a date, and the list reaches the manager every evening. Trucks, shippers and figures are a constructed example.

«Two trucks make almost the same turnover and not the same margin; the difference is in the empty kilometres, and the board shows it truck by truck.»
04

One trip, in six beats

Delivery is the accented beat: the photographed signed note and the timestamped waiting are what make invoicing that same evening possible.

Figure 5 · The accented beat is delivery: the photographed signed note and the timestamped waiting are what make it possible to invoice that same evening and to bill waiting without argument. Before it, the order, assignment and loading; after it, the return, the invoice and the margin are only readings of the trip.

Receive the order: portal, WhatsApp or API; lane, tonnage, date; grid price accepted. Assign: available truck per the fleet, driver, the lane’s standard advance handed over against signature. Load: consignment note produced from the order, photo of the load, weight; the shipper receives their tracking link.

Deliver: timestamped arrival, waiting clock, unloading, signed note photographed, reservations with photos. Return: backhaul proposed and attached, expense receipts, fill-ups, advance settled at the depot. Invoice and count: invoice issued by a background job per the background jobs guide as soon as the note is there, trip margin computed, the truck’s and the lane’s board updated.

05

Freight transport software in 2027, in weeks

Six weeks, the first without code, and two for orders and trips, because the invoice, receivables and margin are only readings of the trip.

  • What the manager sees: every evening, trips delivered and invoiced, those without a note, open advances; every week, empty kilometres per truck; every month, margin per lane and shipper and receivables against their term.
  • What the carrier stops doing: finding out at the depot that a truck came back empty, accepting expenses without a receipt, invoicing three weeks later, arguing about waiting from memory, answering “where is my truck” three times.
  • What is measured: margin per trip, truck, lane and shipper; share of empty kilometres; waiting hours billed; time between delivery and invoice; open advances; receivables beyond term.
Figure 6 · Six weeks, the first without code: the grid, waiting free time, term and empty-km threshold are the manager’s decisions. The two accented weeks are orders and trips, because the invoice, receivables and margin are only readings of the trip.

Week 1, grid and rules: shippers, lanes, grid, waiting free time, term, standard advance per lane, empty-kilometre threshold, fixed cost per kilometre; with the manager, without code, and with counsel for the documents. Weeks 2 and 3, orders and trips: order by portal or WhatsApp, assignment, consignment note, milestones, waiting, proof of delivery, attached backhaul. Week 4, driver app: offline, photos, receipts, fill-ups, settled advance; tracking link for the shipper.

Week 5, invoice and receivables: invoice on signed note, waiting per the grid, receivables against the term, reminders, accounting export. Week 6, management and returns: margin per trip and per truck, empty kilometres, backhaul proposal per lane, Saturday review. A carrier whose fleet is already equipped per the matching guide reuses the cost per kilometre as is; one that charters adds entrusted trips and their settlement.

Does freight transport software start with GPS?
No, with the trip. A dot on a map says neither what the trip earns, nor whether it is invoiced, nor whether the advance is settled. The trip, order, truck, driver, consignment note, milestones, proof of delivery, is the first thing built; positions come from the driver’s phone at milestones, and a GPS unit already installed is plugged in afterwards through integration.
How does the application find a backhaul?
It does not invent one: it looks at open orders from your shippers whose loading point is close to the delivery and whose destination is on the way back, ranks them by detour and revenue, and tells by WhatsApp the shippers who usually ship on that lane that a truck will be empty on such a day at such a place. The dispatcher decides. Over the months, the board shows the lanes where the return is almost always empty, and that is where an agreement with a regular shipper is negotiated.
How is waiting billed?
By the grid accepted with the order: a free time, twenty-four hours in the example, then a price per hour. Arrival and start of unloading are timestamped and geolocated on the driver’s phone; the invoice shows both times and the computation. The free time and the price are the ones the carrier and the shipper write; this guide sets none.
How are driver advances kept?
The lane’s standard advance is handed over against signature in the application at departure. Each expense is a photographed receipt with its category, meals, parking, handling, small repair; fuel is recorded separately, fill-up by fill-up, as in the fleet guide. On return the balance is computed, handed back or topped up, and signed; an unsettled advance stays open in the driver’s name and shows every evening.
And when the driver has no network on the road?
The app records anyway: milestones, photos, receipts and timestamps are kept on the phone with a unique id and go out when the network returns, without duplicate. A milestone’s time and position are the phone’s at the moment of the tap, not at the moment of sending. The shipper sees the last milestone received and its time.
Can a trip be entrusted to another carrier?
Yes: the chartered trip carries an order accepted by the partner, the same link to photograph the load and the signed note, and a settlement computed from the proof of delivery, as in the subcontracting guide. The trip margin becomes the difference between the shipper’s price and the partner’s price, and the board separates trips done by your trucks from entrusted ones.
How long to put this in place?
Six weeks in the standard calendar, the first without code and two for orders and trips. A carrier with a few trucks and three regular shippers takes less; one with dozens of lanes, different grids per shipper and chartered trips takes more, the time to write each grid and take over current receivables.
Send us one month of trips, signed notes and invoices, and we show the margin per trip and the empty share per truck

Road carrier, manufacturer with its own fleet, charterer or founder in France: we build the order and the grid, the trip and its consignment note, the offline driver app, the evening invoice and the margin board

A dry-run take-over on your own trips, the grid, waiting free time and empty-kilometre threshold written with the manager, and a calendar in weeks. We work from Algiers and Sétif, in French, Arabic and English.