Compliance

Compliance work in freight is mostly about not getting caught out: a shipment held at customs, an insurance policy that lapsed unnoticed, a container racking up port fees, a reefer load that warmed up in transit. Logistall groups nine compliance and quality-tracking areas under this page — customs paperwork, cargo claims, insurance, port demurrage, driver hours-of-service, cold-chain temperature logs, SLA rules and breaches, carrier scorecards, and the audit log. Each has its own page in the app; this page covers what each one records, how it behaves, and when to use it.

Customs declarations

The Customs Declarations page records customs paperwork for shipments that need clearance. To log one, create a declaration and fill in the broker name, HS codes, the customs office, and duties and VAT amounts with currency; each declaration gets an auto-generated reference (e.g. CUS-2026-00001) and can optionally be linked to its shipment. Track progress with the status field — pending while it’s with customs, cleared (with a cleared-at timestamp) once it’s through, or held if customs stops it.

Search and filter work the same as other list pages — see Searching & filtering tables.

Claims

Scenario: a customer reports that three pallets arrived crushed. Open a claim while the evidence is fresh, so the dispute has a reference, an amount, and a paper trail from day one.

The Claims page tracks cargo claims — damage, loss, or other disputes tied to a shipment. Each claim gets an auto-generated reference (e.g. CLM-2026-00001), an optional linked shipment, a free-text claim type, a description, an amount and currency, a status (open, under review, settled, or denied), and opened/resolved dates.

Insurance policies

The Insurance Policies page lists your cargo, fleet, liability, and all-risk coverage. Each policy has a policy number, insurer, type, coverage amount, premium, deductible and currency, start and expiry dates, an optional certificate URL, and notes.

Scenario: a truck’s fleet policy expires next week. You don’t need to remember that — the table highlights a policy’s expiry date in amber once it’s within 30 days of expiring, and in red once it has already expired, so renewals don’t slip through unnoticed.

Demurrage

The Demurrage page records port detention charges — the daily fees a shipping line charges when a container stays at port past its free-day allowance. Each record covers an optional linked shipment, a container number, a port, the number of free days and detained days, a daily rate and currency, and an invoiced yes/no flag for tracking whether the line has billed you yet. If you don’t enter a total amount yourself, Logistall computes it automatically as detained days × daily rate.

Driver hours-of-service

The Driver HOS Logs page holds one daily record per driver: driving minutes, on-duty minutes, off-duty minutes, rest minutes, a cumulative weekly-hours figure, and a violation flag with an optional violation type (daily driving limit exceeded, or weekly hours limit exceeded).

To log a driver’s day, create the day’s record and enter each figure directly on the form. A rolling 7-day summary (total driving/on-duty/rest minutes, days logged, and violation-day count) is available per driver for use on fleet-management dashboards.

Cold-chain temperature logs & breach summary

Scenario: a refrigerated load of pharmaceuticals rides overnight to Tangier. The temperature logs are your proof — to the customer and to yourself — that it stayed within range the whole way.

The Temperature Logs page has two tabs:

Readings is a chronological list of sensor (or manually entered) temperature readings, each optionally linked to a vehicle and shipment, with humidity and a min/max threshold. A reading outside its threshold is automatically flagged as a breach and shown in red.
Summary shows, for the last 30 days, total readings, breach count, and average/min/max temperature grouped by vehicle and shipment, so you can spot which assets have the most cold-chain violations — a reefer unit that keeps breaching is telling you something.

SLA rules & breach events

The SLA Rules & Events page turns “on time” from an opinion into a rule, and has two tabs:

Rules define what counts as on time for a lane. A rule can be scoped by mode, service type, origin city, and destination city (more specific rules take precedence over general ones), with a maximum transit-day threshold and/or a maximum pickup-delay threshold, and an active/inactive toggle.
Events is a read-only log written automatically: Logistall checks active shipments against your rules and records an event when a shipment is running over its threshold (breach) or is within 20% of it (near breach), showing how many hours over or under the shipment is.

Carrier scorecards

When it’s time to decide which carrier gets next quarter’s volume, the Carrier Scorecards page gives you numbers instead of impressions: per carrier per period, it shows total shipments, on-time delivery percentage, damage rate (based on damage/loss claims against delivered shipments), average transit days, and a composite score out of 100 shown as a badge (green ≥ 80, amber 60–79, red below 60).

Scorecards are computed automatically once a month. To compute one on demand (owners and data admins only):

Select a date range.
Select Compute.

Computing again for the same carrier and period overwrites the existing scorecard rather than duplicating it.

Audit log

The Audit Log page answers “who did that, and when?” It’s a read-only, chronological record of significant actions across your account — logins, data changes, admin actions, finance events, fleet events, API/webhook activity, and system events — each showing when it happened, its category, the action, the affected resource, a summary, and who did it.

To investigate something — say, an invoice whose amount changed and nobody claims to have touched it:

Filter by category using the chip row at the top (finance events, in this example).
Narrow further by specific action or resource using the table’s dropdown filters.
Read the matching entries: each one names the actor, the action, and the affected resource.