Projects, assets and movement

You are billing for work nobody recorded.

Rate cardsMulti-client stockGate and dock

Where the standard system leaves the cost in place.

Third-party logistics is a service business billed on events: a pallet stored for eleven days, a case picked, a label applied, a vehicle detained for four hours. Almost all of those events happen on the floor, and most of them never reach an invoice. Meanwhile the client wants service level reporting, the transporter wants a settlement, and the documentation trail has to survive a check at a state border. This sector leaks revenue quietly, in small increments, all day.

Value-added services are performed on request and billed only when someone remembers to raise them.
Storage billing is calculated from a month-end snapshot rather than from actual occupancy over the period.
Client stock is segregated physically but not systemically, so a stock report per client is assembled by hand.
Trip cost for market vehicles is settled from paperwork weeks later, so route profitability is never actually known.
Vehicle and driver documentation expiry is tracked on a wall chart, and a lapse is found at a checkpoint.

What we build

Built for logistics and warehousing.

Built on the same core our products run on, extended with the records and rules this sector is actually judged against. These are scopes we build and integrate, not shelf modules with a licence key.

Contract rate cards and billing

Client-specific rates for storage, handling, and value-added services applied to recorded events, so the invoice is generated from what happened rather than from what was remembered.

Multi-client inventory

Stock held and reported per client with ownership, segregation, and location discipline, so a client statement is a query rather than a reconstruction.

Gate, dock and yard control

Vehicle in and out, dock allocation, turnaround and detention time recorded at the gate, which is both an operational metric and a billable one.

Trip planning and costing

Own and market vehicle trips with freight, advance, fuel, toll, and driver settlement captured against the trip, so route and lane profitability is real.

Consignment document lifecycle

Consignment note, statutory transport documentation, and proof of delivery tracked as a lifecycle with ageing, so an unreturned proof of delivery is chased before it blocks a payment.

Claims, shortage and service levels

Shortage, damage, and claim settlement recorded against the consignment, with service level performance reported per client from the same data the billing uses.

What it has to be able to prove.

Compliance fails when it is a parallel activity. These obligations are carried by the system that runs the operation, so the evidence exists because of how work was recorded rather than because someone assembled it afterwards.

Transport documentation validity

Statutory transport documents generated and tracked against the consignment and the vehicle, including validity windows, so a movement is not exposed at a check post.

Vehicle and driver document control

Fitness, permit, insurance, pollution, and licence expiry monitored against the asset, with the vehicle blocked from allocation once a document has lapsed.

Proof of delivery retention

Delivery evidence captured, indexed against the consignment and invoice, and retained, which is what a payment dispute or an audit will ask for.

What it runs on.

The sector layer is built. The operational core underneath it is not a proposal: it is running in production with clients today.

ERPMachERPLiveContract billing, receivables, trip and vehicle cost, and finance, extended with the rate card and event structures a service business bills from.See what it does

SIMSMach SIMSLive with clientsMulti-client, multi-location stock with movement-level discipline, cycle counting, and client-wise reporting.See what it does

What it returns.

Billable events reach the invoice

Handling and value-added work is recorded where it happens, so revenue stops depending on recall.

Route profitability becomes knowable

Trip cost is captured against the trip, so lane and vehicle economics can be compared rather than assumed.

Client reporting produced automatically

Stock, service level, and activity statements come from the operational record instead of a monthly assembly exercise.

Where this normally starts.

Which of these applies depends on how well the constraint is already understood. A review that finds the real one usually turns into a build.

Automate

Process automation

Removing the approvals, handoffs, follow-ups, and reconciliation that quietly consume your team's week.

How it works

See

Data and reporting

Turning scattered records into dependable, current reporting that leaders can act on rather than argue about.

How it works

Questions we actually get asked.

Our rate cards are complicated and different for every client. Is that a problem?

It is the reason to build rather than buy here. Slabs, minimums, free periods, handling tiers, and value-added rates are configured per contract, so complexity lives in configuration instead of in a monthly spreadsheet that only one person can operate.

Can you integrate with our clients' systems?

Frequently, and it is worth doing where volumes justify it. Order and dispatch instructions arriving directly, and stock and status flowing back, removes the double entry that both sides currently pay for. Where a client has no interface, we automate the file exchange instead.

Our drivers and floor staff will not use a complicated app.

Then they should not have to. Capture at these points is designed to be a few taps, a scan, or a message, and where a smartphone is genuinely unrealistic we put the capture at a supervisor or gate station instead. A system nobody uses records nothing.