Touring Freight and Production Logistics Software: Why a General Transport System Cannot Model a Truck Pack Ordered by the Stage Build Sequence

Why touring freight is the one logistics problem no transport system was built for

A production is not cargo in the ordinary sense. It is 43 flight cases, 6 dimmer racks, a set of trusses, a wardrobe, a merchandise pallet and a set of instruments, and it has to be unloaded in the exact reverse order of the build so that steel comes off first and the wardrobe comes off last. The load in window at the next venue is four hours. The border between them requires a customs document listing every item with a serial number and a value, and if the list on the document does not match what is in the truck, the truck stops.

A general purpose transport management system models a consignment moving from A to B with a weight, a cube and a delivery window. It has no concept of a truck pack order tied to a stage build sequence, no concept of a case that contains sixty items each of which must appear individually on a customs list, and no concept of a delivery deadline that cannot slip by an hour because 12,000 people already have tickets.

So touring logistics gets run on a case inventory in a spreadsheet, a truck pack diagram in a drawing, a carnet prepared by an agent from a list emailed six weeks ago, and a logistics manager who holds the rest.

Problem 1: the carnet list stops matching reality on about day four

An ATA Carnet is a customs document that lists every item travelling under it, and it works by having the same goods leave a territory as entered it. That is a reasonable assumption for a trade fair exhibit. It is not a reasonable assumption for a tour, where a failed amplifier gets swapped for a rental in Cologne, a broken case is replaced, merchandise is legitimately sold and therefore consumed, and a piece of equipment flies home early with a crew member.

Every one of those events breaks the correspondence between the document and the truck, and the consequence is discovered at a border by a driver who cannot explain it. The usual mitigation is that the logistics manager keeps a mental list of the discrepancies and briefs the driver. That works until it does not.

What a custom build does: the carnet list is generated from the case level inventory rather than typed separately, so there is one source. Substitutions, rentals, early returns and consumed goods are recorded as events against the item, each with a flag for its customs consequence, and the system produces the current position at any moment: what the document says, what is physically in the truck, and where they differ. The remedial action, whether that is a replacement carnet, a temporary import under a different mechanism or a declaration, is your agent's expertise and should stay with them. What software fixes is that the discrepancy is known before the border rather than at it.

Problem 2: the truck pack is a build sequence, not a loading plan

Load out happens in the reverse order of the strike, and load in happens in the order the build needs. Steel and rigging first, then audio and lighting, then backline, then wardrobe and merchandise. That is why a production travels in specific trucks with specific packs, and why swapping two cases between trucks to fit a late addition can cost forty minutes at the next load in.

What a custom build does: the pack plan is a structured object per truck, per leg, tied to the build sequence, with each case placed. When something changes, and something always changes, the effect on the load in is visible rather than being discovered by a crew chief standing at a dock door. Case scanning at load out confirms the plan was followed and, more importantly, catches the case that did not make it onto any truck, which is the failure that ends a show. In our experience the confirmation scan at load out is the single highest value feature in this category because it converts a discovery at the next city into a discovery in the current one, while the case is still ten metres away.

Problem 3: air freight, road freight and crew all move on different clocks

A long haul leg often splits: some gear flies, some goes by sea weeks ahead, some is rented locally, crew fly on different routings and some fly ahead to receive. Each of those has its own booking, its own documentation and its own failure mode, and they only matter as a set, because the show needs all of them in the same room on the same afternoon.

What a custom build does: the leg is the unit. A leg holds every movement of gear, crew and freight required to get from show A to show B, whoever is carrying it. The status of the leg is the worst status of its parts, so a delayed air waybill turns the leg amber even though the trucks are fine. Freight forwarder references, airway bills, booking confirmations and driver contacts hang off the leg rather than living in an inbox. When the tour manager asks whether Tuesday is at risk, there is a single answer instead of four phone calls.

Problem 4: drivers, hours and cabotage are a compliance problem hiding inside a routing

Trucks are driven by people whose hours are regulated, and international road haulage carries rules about how many domestic movements a foreign vehicle may perform within another country. Routings get built around show availability and then handed to a haulier who discovers a problem. A tour that is routed without regard to driver hours produces either an illegal run or a last minute second driver at cost.

What a custom build does: routing checks against driving time and rest requirements at the point the routing is proposed, flags legs that are not achievable with a single driver, and holds the operational rules that apply to your vehicles in the territories you run. It does not attempt to be the legal authority: the haulier and your transport manager own that. What it does is stop an unachievable leg from being confirmed by a booking agent who was thinking about ticket sales rather than tachographs. Catching that at routing rather than at the depot is worth a lot per tour.

What this costs and how long it takes

A first routing, meaning case level inventory with scanning, truck pack plans tied to build sequence, leg based movement tracking with statuses, and carnet list generation from inventory with discrepancy tracking, runs $65,000 to $155,000 and ships in 12 to 18 weeks. A full platform adding air and sea freight bookings, crew movement, driver hours and routing feasibility checks, rental and substitution management, cost capture per leg, and integration with forwarder and haulier systems runs $200,000 to $450,000 phased over 6 to 12 months.

What pushes cost up in touring logistics specifically: the initial inventory build, because getting a production into case and item level detail with serials and values is a warehouse exercise, and the carnet needs values whether or not anyone has ever recorded them. Offline capability, since load outs happen in loading docks and underground service areas with no signal and that is precisely where scanning occurs. Multi tour operation, if you are a specialist freight company rather than a single production, because gear pools shared across tours are a materially harder inventory model. And forwarder integrations, which vary from a proper interface to a portal that has to be checked by a human, so budget for the second case.

Build versus buy, and when buying is the right call

Buy, or more accurately do not build, if you tour domestically with a van and a trailer. A shared inventory list and a competent production manager is proportionate, and software will not repay the effort. Equally, if your gap is genuinely just paperwork preparation and you cross borders twice a year, a good carnet agent solves that more cheaply than any system.

Build when the movement is continuous and international. Specifically: when you run carnets across a routing where gear changes, when the truck pack has to follow the build sequence and getting it wrong costs load in time you do not have, when air, sea and road movements combine on the same leg, or when you are a freight specialist serving several productions from a shared pool. Our position is that the case level inventory is the foundation and everything else hangs off it. A proposal that starts with route optimisation and treats the inventory as a lookup table has misread the problem, because in this business the cargo is the show and its identity matters far more than its cube.

How to choose a developer for touring logistics software

Ask them how the customs item list is produced. If it is a separate document that someone maintains alongside the inventory, you will be back to a discrepancy discovered at a border. It has to be generated from the same case and item records the crew scan.

Ask what happens when the scanner is in a basement loading dock with no signal at 1am. Offline scanning with local storage and later reconciliation is the only workable answer, and the reconciliation has to be able to tell you a case was scanned out and never scanned onto a truck.

Ask how they model a leg that includes a truck, an air waybill and two crew flights. If the model is a shipment rather than a leg, the tour manager will still be making four phone calls to find out whether Tuesday is safe.

Ask who owns the code, the infrastructure and the inventory data, in writing before kickoff. Your case and item register with values and serials is the basis of every carnet, every insurance schedule and every claim you will ever make, and it should not sit on a vendor's account. At Digital Heroes the client owns the repository and the data from the first commit.