Weight Tickets¶
Weight tickets are the official record of each weighing transaction. In commercial operations, they serve as the basis for billing, inventory reconciliation, and dispute resolution.
Ticket Types¶
| Type | When Generated | Contains |
|---|---|---|
| Interim ticket | After the first pass of a two-pass transaction | Gross or tare weight only; marked as "INTERIM" |
| Final ticket | After both passes are complete (or single-pass with stored tare) | Gross, tare, net weight, deductions, and final billable weight |
Ticket Sections¶
Weight Summary¶
The weight summary is the primary block on every commercial ticket:
| Field | Description |
|---|---|
| Tare weight | Weight of the empty vehicle (kg) |
| Tare source | Measured, Stored, or Preset |
| Gross weight | Weight of vehicle + cargo (kg) |
| Net weight | Gross minus tare (kg) |
| Quality deduction | Weight deducted for moisture, foreign matter, or grade (kg) — if applicable |
| Adjusted net weight | Net weight minus quality deduction — the billable weight (kg) |
Ticket Status¶
Shows the transaction status badge:
| Status | Meaning |
|---|---|
| Pending | Transaction created; no weight captured yet |
| FirstWeightCaptured | First pass captured; awaiting second pass |
| AwaitingReweigh | A second weight or reweigh was captured but not finalized; the vehicle left to adjust cargo and is expected back for another capture under this same transaction. No invoice yet |
| Complete | Transaction finalized; final ticket available |
| ToleranceExceeded | Weight variance beyond configured tolerance — supervisor approval required |
| Voided | Transaction cancelled (or a tolerance exception was rejected) — recorded with a reason |
A tolerance-exceeded transaction displays a warning and blocks final PDF generation until a supervisor approves (or rejects/voids) the exception.
Vehicle Details¶
| Field | Description |
|---|---|
| Vehicle registration | Plate number |
| Vehicle make | Manufacturer / model |
| Trailer registration | Trailer plate (if applicable) |
| Weighing type | Multideck or Mobile |
Consignment & Cargo¶
| Field | Description |
|---|---|
| Consignment number | Reference number for the load |
| Order reference | Customer purchase order or delivery order number |
| Cargo type | Commodity description (e.g., Maize, Cement) |
| Seal numbers | Container or trailer seal numbers |
| Expected net weight | Declared load weight (kg) — used to compute discrepancy |
| Weight discrepancy | Difference between expected and actual net weight (kg) |
| Tolerance | Configured tolerance applied to this transaction |
Parties & Route¶
| Field | Description |
|---|---|
| Transporter | Registered hauling company |
| Driver | Driver name |
| Origin | Cargo source location |
| Destination | Delivery destination |
| Remarks | Free-text notes added by the operator |
Weighing Passes¶
| Field | Description |
|---|---|
| 1st pass weight | Weight captured on the first pass (kg), with timestamp. Always the very first capture, regardless of how many reweighs followed |
| 1st pass type | Gross or Tare — identifies what was weighed first |
| 2nd pass weight | Weight captured by whichever pass actually finalized the transaction (kg), with timestamp. If the vehicle was reweighed one or more times before finalizing, this holds that later reading, not literally the second capture taken |
| 2nd pass type | The complementary weight type |
If the transaction went through one or more reweighs, the ticket also shows the full capture history: every pass in order, labelled "First Weight", "Second Weight", or "Reweigh #N", each with its own weight, type, timestamp, and (for a pass that didn't finalize) the recorded reweigh reason. See Reweighs and Multiple Capture Passes for how this numbering works and a worked example.
Billing¶
Shown when a weighing fee is configured for the organisation:
| Field | Description |
|---|---|
| Weighing fee | Per-transaction charge in the configured currency (KES or USD) |
Station & Officer¶
| Field | Description |
|---|---|
| Station | Weighbridge station name and code |
| Weighed by | Name of the operator who captured the transaction |
| Weighed at | Timestamp of the final weight capture |
| Capture source | TruConnect (live scale) or Manual |
Enforcement vs. Commercial Ticket Comparison¶
| Aspect | Enforcement Ticket | Commercial Ticket |
|---|---|---|
| Purpose | Regulatory compliance evidence | Billing and inventory record |
| Violation fields | Yes (act, section, excess weight) | No |
| Case reference | Yes (linked to case register) | No |
| Tare source | Always measured on-site | Measured, stored, or preset |
| Quality deductions | Not applicable | Optional per cargo type |
| Billable weight | Not applicable | Yes (adjusted net) |
| Legal watermark | Government agency seal | Company branding |
Printing¶
PDF (A4)¶
Click Print Ticket in the ticket detail drawer to generate a full-page PDF with:
- Company logo and branding
- Weight summary hero (tare / gross / net)
- All consignment and cargo details
- Operator and driver signature lines
An interim PDF is available after the first pass for use as a delivery receipt. The final PDF is generated once the transaction is finalized, whether that happens on the second pass or after one or more reweighs.
Thermal printer¶
Click Print Thermal, next to Print Ticket, in the ticket detail drawer or on the final step of the capture flow. TruLoad generates a raw byte file formatted for an 80mm thermal receipt printer and downloads it to the operator's computer. The same button covers both the interim ticket (available after the first pass) and the final ticket (available once the transaction is finalized), matching the PDF above: a tolerance-exceeded transaction blocks the final thermal ticket the same way it blocks the final PDF, until a supervisor approves or rejects the exception.
The downloaded file contains standard ESC/POS printer commands: initialize, text alignment, bold, double-size, and paper cut, laid out as a compact single-column receipt (48 characters wide) with station name, ticket number, vehicle registration, transporter, the tare/gross/net/ adjusted-net weight summary with tare source, status, timestamp, and the billing line when a weighing fee is configured. This is the same command language used by most 80mm receipt printers, so the file is not tied to a specific printer brand.
TruLoad does not detect or talk to a printer automatically. There is no print-bridge or local agent for this yet, unlike TruConnect for scale readings. Delivering the file to paper is up to the operator's own printer setup: most thermal printers can be installed in Windows as a generic/raw printer, and sending the downloaded file to that printer queue prints it as-is. A station's Printer Configuration field (see Station Configuration) stays metadata only. It documents what printer a station uses but does not select or drive the print job.
The ESC/POS command bytes follow the published spec and were checked by hand against the documented values, but they have not been tested on a physical thermal printer. Treat the output as unverified until someone confirms it prints correctly on real hardware.
Searching and Filtering Tickets¶
The ticket list supports filtering by:
| Filter | Options |
|---|---|
| Date range | From / to date |
| Time range | From / to time (within the date range) |
| Status | All / Pending / First Weight Captured / Complete / Tolerance Exceeded / Voided |
| Station | All stations or a specific station |
| Vehicle registration | Partial match |
| Ticket number | Exact or partial match |
Use the Export button to download filtered results as CSV for reconciliation or reporting.
Field Population and N/A Values¶
Some fields on the weight ticket will show N/A or be blank if they were not captured during the transaction. The table below explains when each optional field is populated.
| Field | Populated when |
|---|---|
| Trailer registration | Operator enters it in the Ticket step |
| Transporter / Driver | Registered in Weighing Metadata and selected during Capture step |
| Cargo type | Selected during Capture step |
| Consignment number | Entered in Ticket step |
| Order reference | Entered in Ticket step |
| Seal numbers | Entered in Ticket step |
| Origin / Destination | Selected during Capture step |
| Expected net weight | Entered in Ticket step — required for discrepancy/tolerance check |
| Weight discrepancy | Only shown if Expected Net Weight was entered |
| Quality deduction | Only shown if a deduction was applied in Ticket step |
| Adjusted net weight | Only shown if Quality Deduction > 0 |
| Deck/axle weights | Only shown for Multideck scale transactions where per-deck weights were captured |
| Billing section | Only shown for third-party weighbridge organisations with a fee configured |
Reducing N/A fields
Pre-register vehicles, transporters, and drivers in Setup > Weighing Metadata so they auto-populate during the Capture step. Require operators to fill all Ticket step fields before printing.
Weighing Scale Types¶
The ticket adapts based on how the weight was captured:
| Scale Type | Ticket behaviour |
|---|---|
| Multideck | Shows per-deck weight breakdown (Deck 1–4) if captured by TruConnect middleware |
| Mobile | No per-deck section — mobile axle-by-axle scale data is not shown on the final ticket |
| Standard (static) | Shows combined weight only |
The scale type is set automatically based on which weighing page was used: /weighing/multideck for
multideck, /weighing/mobile for mobile. /weighing itself is a hub page (Operations + Tickets)
that routes an operator into one of those two capture flows. There is no separate standalone
capture stepper for a plain static scale today. Standard (static) ticket rendering (combined
weight only, no deck breakdown) is the fallback shown whenever a transaction has no multideck/mobile
scale-type tag at all, e.g. one created without going through either dedicated capture flow.
Ticket Lifecycle¶
stateDiagram-v2
[*] --> Pending: Transaction initiated
Pending --> FirstWeightCaptured: First pass captured
FirstWeightCaptured --> Complete: Second pass captured and finalized (net within tolerance)
FirstWeightCaptured --> ToleranceExceeded: Net discrepancy exceeds configured tolerance
FirstWeightCaptured --> AwaitingReweigh: Weight captured, saved without finalizing
AwaitingReweigh --> AwaitingReweigh: Another reweigh captured, still not finalized
AwaitingReweigh --> Complete: Finalized (net within tolerance)
AwaitingReweigh --> ToleranceExceeded: Finalized, net discrepancy exceeds configured tolerance
ToleranceExceeded --> Complete: Supervisor approves tolerance exception
Complete --> [*]Tolerance check timing
Tolerance is evaluated after every capture from the second weight onward, so an operator gets live "still over/under limit" feedback during a reweigh cycle. It only gates ticket generation once the transaction is finalized. The Expected Net Weight must be entered in the Ticket step; if it is not provided before a weight is captured, tolerance is not evaluated for that transaction.