Throughput is the terminal's volume report: how much product went into and out of your storage tanks, per month, per client and per product, with the number...
Throughput
Throughput is the terminal's volume report: how much product went into and out of your storage tanks, per month, per client and per product, with the number of loads handled, the dip corrections booked and the net kilograms from weighbridge tickets. A terminal manager uses it to follow volumes per client and product, to check what a client is about to be billed for tank throughput, and to spot tanks whose book and physical stock keep drifting apart.
Where to find it: Workspace → Logistics → Warehouse → Throughput. The menu entry only appears when the Terminal module (Terminal fixed storage tanks) is switched on in Warehouse settings.
Who can use it
Anyone with a Warehouse permission (View sites, the live yard, units, tanks and movements). The screen is read only: it adds up what was booked under Storage tanks with Product in / out and Record a dip. To change a figure, book the missing operation or a correction there; nothing is typed on this screen.
Where it sits in the operation
Every receipt, delivery, transfer and dip correction is one line in the movement ledger. Throughput reads only the tank lines of that ledger and rolls them up by month, client and product. The same ledger lines are what Bill a month prices as Tank throughput per m³, so the report is the volume side of the terminal invoice.
Figure 1 Receipts and deliveries are throughput and are billed; corrections are reported but never billed; transfers are neither, because the product never crossed the terminal boundary.
What you see
Two rows of filter tabs above the list:
The period: This month, Last month, This year (the default), Last 12 months and All. Periods are days in the workspace's own time.
The site: All or one site. This row only appears when you have more than one site.
One row per month, client and product, newest month first:
Column
What it shows
Month
The month, for example "May 2026". Sorting on it sorts by date.
Client
The client of the movements: the one chosen in Product in / out, otherwise the tank's renter. A dash when neither was set.
Product
The product moved.
Received
Litres received into tanks (from road tankers and from units on site).
Delivered
Litres delivered from tanks (into road tankers and into units on site).
Loads
Number of receipts plus deliveries: the trucks and units handled at the tanks.
Dip corrections
The signed total of book corrections from dips, with + (gain) or − (loss). A dash means none (or less than half a litre).
Weighed (net)
Net kilograms of the operations booked with a weighbridge ticket (gross − tare). A dash when none was weighed.
Volumes follow Volume unit in settings (litres, m³, or automatic from 100 000 L). The list has the usual search, sort and export menu (Excel, print). On a phone each row shows the client, the month and the litres received.
Transfers between your own tanks are not counted: product that only moved inside the terminal did not come in or go out. A month with only a correction for a client and product still appears, with zeros for received and delivered.
Check a client's volumes before billing
Open Throughput and click Last month; pick the site if you run several.
Type the client's name in the search box, or click the Client column header to sort.
Add Received and Delivered per product: divided by 1000, that is the m³ that Bill a month will charge as Tank throughput.
Look at Dip corrections. A large one is worth a look before you bill: it often means a receipt or delivery that was never booked. Book the missing operation on Storage tanks instead of leaving it inside a correction, so it is billed.
Compare Weighed (net) with the litres: net kg ÷ litres should be close to the product's density.
Use the export menu to save the month to Excel for the client or your controller.
Who a movement is counted for
Every receipt and delivery is booked for one client, chosen at the moment of the operation. That choice decides the client row here and the invoice it is billed on.
Figure 2 Fill in Rented to (client) on every rented tank and choose the client on operations for third-party product in a shared tank; otherwise volumes land on the wrong client or on none.
Controls and exceptions
Read only, from the ledger. There is no edit on this screen and no separate throughput table: the figures are recalculated from the movements every time you open it, so they always match Movements and the tank cards.
Wrong client or product on a booking. Movements cannot be edited. Book the reverse operation (a delivery against a wrong receipt, or the other way round) with a note, then book it correctly. Both lines stay in the history and both appear here, netting out.
Client changed on a tank. Changing Rented to (client) only affects operations booked after the change; earlier movements keep the client they were booked for.
Month boundaries. The period tabs use days in the workspace's time, while rows are grouped by the month of the stored (UTC) timestamp. An operation booked in the first hours of the 1st, in a workspace east of UTC, can be listed under the previous month. Bill a month uses the workspace's local month.
Weighed (net) with typed litres. When the operator typed the litres and also the weights, the litres booked are the typed ones and the net kilograms are kept beside them, so this column can be used as a cross-check.
No standard-volume conversion. Litres are reported as observed at the time of the operation; there is no VCF or 15 °C correction.
For the manager
Monthly, before billing: last month per client. The Tank throughput line on Bill a month (on the client's Equipment & stock tab) is exactly received + delivered in m³ for that client, priced from the Tank throughput rate in Rates (a client-specific rate wins over the general one). With no rate, the preview warns "No rate for Tank throughput: not billed." Tank rent is a separate line per rented tank.
Turns: received + delivered over a period, against the capacity rented to the client, is the number of tank turns: a rented tank that never turns is rent only, a tank that turns often earns throughput.
Losses: the Dip corrections column per product and month. A steady negative trend is product loss (evaporation, meters, leaks); a positive one usually means receipts booked short.
Trend: the dashboard tile Throughput this month shows the m³ received + delivered so far this month with the change against last month.
Further analysis: AI Reports → "All business data" → Yard and tank movements (Warehouse) has litres received, litres delivered and dip correction litres by client, product, site and source over time. Through MCP, report.warehouse_throughput returns the same rows as this screen.
Glossary
Throughput
Product received into plus delivered from the storage tanks in a period; tank-to-tank transfers excluded.
Receipt
A Tank received movement: product into a tank from a road tanker or a unit on site.
Delivery
A Tank delivered movement: product out of a tank into a road tanker or a unit on site.
Transfer
A Tank transfer movement between two tanks of the same site. Not throughput.
Load
One receipt or one delivery: one truck or unit handled at the tanks.
Dip correction
A signed Correction movement that set a tank's book level to a dip. Reported, never billed.
Net weight
Gross weight minus tare from the weighbridge ticket, in kilograms.
Tank throughput rate
The price per m³ in Rates applied to received + delivered.
Tank rent
The monthly rate per tank rented to a client, billed separately from throughput.
Tank turn
One fill-and-empty cycle of a tank's capacity; throughput divided by capacity.
Related screens
Storage tanks: where receipts, deliveries, transfers and dips are recorded.
