Report Types

Report Types Visible to Users

These reports are available for selection by regular users.

Tour List

Purpose: Overview of planned tours.
Provides a summary of routes, transport points and logistics data for a selection of tours. Used by dispatchers for the daily planning overview or as a contingency plan for the drivers.

For designing in the Report Designer, the tour custom fields 1–6 and the tour's cargo area consumption are also available.

Delivery Note

Purpose: Pickup / delivery note.
Accompanies a shipment to the recipient. It is usually signed upon receipt and sent off. Based on the shipment with pickup/dropoff POIs, contacts, cargo data, time windows, status and reference IDs.

For designing in the Report Designer, the total required quantity and the cargo area consumption are also available in the shipment dimensions. This also applies to the other shipment-based reports such as Pickup Note, "Flushing" Report and Parent Shipment Report.

If a shipment was divided by a way split or quantity split, the report of the parent shipment additionally contains the list SplitChildren in the Report Designer, with all associated partial shipments. Each partial shipment offers the same fields as the shipment itself, including SplitSortOrder with its position within the split. This lets you design a single document for the entire parent shipment. The partial shipments only appear on the document if the template uses this list. Reports for individual partial shipments remain unchanged.

Incident

Purpose: Documentation of events and incidents.
Serves to record and report special events (e.g. accidents, damages, delays) that have occurred at a transport point or during a tour.

Standard Site Document

Purpose: Site document template.
(Optional module) A document assigned to a specific site (e.g. a customer location). Used for site-specific instructions or access notes.

Package Report

Purpose: Container / load carrier report.
(Optional module) Creates printable labels for containers or load units, including barcodes, addresses and content descriptions.

Trade Offers

Purpose: Freight exchange offers.
(Optional module) Lists transport capacity offers that have been entered on the trade page.

Trade Demands

Purpose: Freight exchange demands.
(Optional module) Lists transport capacity requests that have been entered on the trade page.

Pickup Note

Purpose: Pickup receipt.
(deprecated, now covered by the delivery note) The counterpart to the delivery note on the pickup side. Documents what was taken along at a pickup point.

Transport Points Evaluation

Purpose: Transport point evaluation.
Detailed report on a specific transport point and all shipments processed there.

Weekly Framework Tour Evaluation

Purpose: Weekly framework tour evaluation.
Weekly overview of planned or performed framework tours for medium-term logistics planning.

Invoice Template

Purpose: Invoice template.
(Optional module) Invoice document per order for billing to customers.

Invoice Positions

Purpose: Position invoice (itemised proof). (Optional module) Detailed breakdown of all billable positions within an order or an order group.

Tour Positions Evaluation

Purpose: Driver task sheet. Lists all tasks a driver has to complete for their tour: transport points, actions, products, quantities.

Standing Order Evaluation

Purpose: Standing orders overview. Summary report on standing orders and their current execution status.

"Flushing" Report

Purpose: Flushing protocol. (Optional module) Used in mineral oil or tank logistics to document flushing operations.

Quotation / Offer Report

Purpose: Customer quotation. (Optional module) Creates a formal quotation document for a customer based on planned transport services.

Load Carrier Report

Purpose: Load carrier tracking. Overview of load carriers (pallets, containers) and their distribution across transport points and tours.

Parent Shipment Report

Purpose: Consolidated / split shipment report. Report on parent shipments together with all associated child shipments – for grouped or split delivery and billing scenarios.

KPI Report Types (Superadministrators only)

These reports are hidden from regular users and can only be created by Xplanis employees. They primarily serve operational analysis as well as performance monitoring.

KpiTourReport

Purpose: Performance analysis per tour. Key fields:

• CountStops, CountTP, CountShipments, CountPositions
• PerformedTime: planned vs. actual tour duration
• PerformedDistance: planned vs. actual distance
• TotalCargo: kg, m³, litres, pallets
• StopTimesActual: total time/min./max./average of stop times
• Costs: per km, per hour, HVF, total
• TourCosts, TourEarnings
• Violation: complete breakdown of rule violations (capacity, time windows, qualifications, overtime, working radius)
• OrdersTotal: number of orders, positions and cargo quantities

KpiVehicleReport

Purpose: Utilisation analysis per vehicle. Key fields:

• CountTours: by status (completed, in execution, released, planned, other)
• PerformedTime: planned vs. actual
• PerformedDistance: planned vs. actual
• CapacityUtilizationMaxInPercent: maximum utilisation in % for kg, m³, litres, pallets

KpiDriverReport

Purpose: Performance and punctuality analysis per driver. Key fields:

• CountTours: by status (completed, in execution, released, other)
• CountTransportPoints: completed, in progress, not started
• PerformedTourTime / PerformedDrivingTime: planned vs. actual
• CountPlanedTourStartTime / CountPlanedTourEndTime: delay distribution (0–15, 15–30, 30–60, >60 min.)
• MonitoringDrivingTime: tour time, driving time, manual driving time, break time

KpiQualityReport

Purpose: Service quality and compliance monitoring. Key fields:

• CountDeliveryRatioOrderTours: delivery success rate by tour status
• CountComplianceDeliveryTimeWindow: compliance with time windows vs. delay (by time buckets)
• CountComplianceDeliveryDay: delivery on the correct day (on time, 1 day deviation, >1 day deviation)

KpiResourcePlanningReport

Purpose: Working time planning for drivers. Key fields:

• Name: driver name
• TotalDays, TotalHours, TotalHoursOverall
• DaysTemplate: list of days with summed hours of all drivers per day
• Days: list of working days and hours worked per driver

KpiPositionReport

Purpose: Detailed tracking at product/position level. Key fields:

• DriverTaskId, PositionId
• TimeStart, TimeEnd, TimeDurationMin
• Driver: first name, last name, username
• Product: name, type, code, unit, reference ID, barcode
• QuantityPlaned, QuantityActual, QuantityReturn, QuantityMeasured
• PoiName, PoiLocation
• IsDropoff, IsAdhoc
• ShipmentCreationSource

KpiGroupReport

Purpose: Logistics summary at group level. Key fields:

• CountShipments, CountUnallocatedShipments, CountSplits
• CountTours: by status (planned, in planning, fully planned, released, other)
• DateRange, GroupFilterString

KpiTsg

Purpose: TSG transaction reconciliation (tank/weighbridge gate). Links measurement data of a TSG terminal with tours, shipments, drivers, products and POIs. Key fields:

• TSG data: transaction no., distributor, vehicle reference, transport company, terminal timestamp
• Product: description, meter no., uncompensated/compensated volume, mean/base temperature, rejection status
• Linked to: TourId, ShipmentId, DriverTaskId, TransportPointId, PoiId
• Planned, actual and measured quantities per driver task

KpiExamGroupReport

Purpose: Group examination with full tour detail. Aggregates KpiTourReport entries per group for an in-depth group analysis for a training evaluation. Key fields:

• CountUnallocatedShipments
• OrdersTotal: order/position count and cargo quantities
• Tours: complete list of embedded KpiTourReport objects
• DateRange, GroupFilterString

Export Formats

Reports can be exported in the following formats:

Automatic Report Generation

Reports can be created automatically via report generation settings. Key options:

• Trigger: after completion of a transport point or after completion of a tour
• Distribution recipients: own dispatch, main group dispatch, e-mail (order, customer, buyer, recipient, invoice, POI), SFTP
• Suppression: do not create / do not send for empty transport points
• Fallback: fallback e-mail address if the configured recipients are empty