TMS add-on

TMS (Transport Management) is a paid add-on on top of your plan: vehicles, drivers, clients, orders and a pallet ledger, as a ready-made project. Buying it in-app is not available yet — contact Quanty to switch it on for your organization.

The TMS section

Once the add-on is on, a TMS group appears in the sidebar, above your workspaces, listing the organization's TMS projects with each one's tables underneath: Pallet events, Vehicles, Drivers, Clients and Orders in a project made by the starter. A Fleet map row sits above them — see Fleet map and Map view. Without the add-on the group draws nothing at all, not even an empty header, so it never gets in the way of an organization that has not bought it.

Before your organization has a TMS project, the group shows a quiet Set up TMS row instead, with two ways in: use a project you already have, or install the starter. Marking or unmarking a project happens from its own menu, Move to TMS / Remove from TMS, and neither one moves anything: "The project stays in its workspace; it is also listed under TMS."

Installing the starter

Install the starter creates a new project with tables for vehicles, drivers, orders, clients and pallets, already linked and configured. Installing costs nothing: no AI runs and no credits are spent, which is also why it works for an organization between plans, when Quanty staff set one up in advance.

The starter creates five tables:

The pallet ledger

Pallet events is the heart of it. Picking the tractor and the client on an event is all a dispatcher has to do: those two fields are linked columns, and Quanty mirrors them onto the vehicle's and the client's own Pallet events column at the same time, in both directions. So a vehicle's basket balance and a client's pallet balance are rollups over exactly the events linked to them, and nothing is ever entered twice:

• Vehicle balance — current basket stock = initial stock + pallets taken − pallets given, checked against the basket's capacity, with an alert for a negative stock, an overfull basket, pallets riding with no basket at all, or damage.
• Client balance — net pallet balance = pallets taken − pallets given across every linked event, with a penalty-risk figure computed from the client's own per-pallet penalty rate.

The dispatcher's own colour legend carries over as the Verification status column's options: yellow for to clarify, red for debt or penalty risk, violet for confirmed, green for settled, magenta for a driver transfer, pink for a base visit. Pallet events has a grid, a calendar (by operation date, coloured by status), a timeline (one lane per vehicle) and a kanban board stacked by status — the dispatcher's ODS calendar and her colour-coded cells, as views over one live table instead of a spreadsheet kept by hand.

The driver form

A public driver report form lets a driver report a pallet movement from their phone in around fifteen seconds: the order number, what happened to the pallets, and a photo of the receipt. A form cannot pick a linked row, so a submission lands as a new event coloured to clarify, with the driver's name and plate as typed; the dispatcher links the vehicle, driver and order afterwards. See Forms for how a form itself works.

Automations

The starter ships three automations on Pallet events, and, like every automation a starter creates, all of them start switched off — an admin turns on the ones the organization wants:

• Pallet settlement deadline reminder — daily, notifies the dispatcher of any open event whose deadline is within 3 days.
• Driver report: to clarify — when the driver form is submitted, sets the new event's status to to clarify and its receipt source to Driver form.
• Driver report: read the receipt (AI) — when the driver form is submitted, runs the AI columns below on the new event. Uses AI credits, which is why it ships off rather than on.

AI columns that read the receipt

Pallet events and Orders together carry twelve AI columns that read the receipt photo or the order document: the operation type, the carrier type, pallets exchanged, the balance stated on the receipt, the settlement clause and its deadline, the penalty per pallet, the client name, whether the receipt is signed and stamped, the document number, a suggested verification status, and — on Orders — whether the order requires a pallet exchange and its settlement terms.

Limits to know

• Only tractor and client are mirrored. Trailer, driver, second driver and order are ordinary one-way links, so there is no per-trailer or per-driver balance out of the box.
• The settlement deadline is typed, not calculated. Formulas cannot add days to a date, so the deadline is a date column the dispatcher fills (the AI column suggests the clause days). The "due in 14 days or overdue" view and the reminder automation work from that date.
• A balance counts the first 1000 linked events. A vehicle or client with more than 1000 pallet events gets a total that leaves the newest ones out. Archive settled events into a new period before that point.
• A receipt is not matched to its order automatically. AI suggests the client name and the order number it reads; linking the event to the order, vehicle and driver is the dispatcher's step.
• Projects installed or marked before two-way links existed are not paired. Pair the link columns in their column settings; existing links on both sides are merged.
• No SMS intake and no connector for cab scanners. Receipts arrive through the driver form, by email or WhatsApp automations, or by hand.

What it costs

Installing the starter is free: it spends no AI and no credits, whatever plan the organization is on. Running the AI columns costs credits the same way any AI column does, at your plan's normal rate — see Billing & credits.

Related pages

• Telematics (GPS): connecting a provider so vehicles show their live position.
• Fleet map and Map view: where those positions are shown.
• Records (CRM): the other plugin project, part of the product rather than an add-on.
• Billing & credits: what installing costs, and what running AI columns costs.