Glossary of travel, logistics, and transportation software terms

Automated flags that surface when a lane or account turns unprofitable, so a team can renegotiate a rate or reroute before the loss compounds.

A discipline (and tooling, e.g., Stibo Systems, Syndigo) ensures product and location records mean the same thing across every connected system, so a WMS and TMS referencing the same warehouse bay agree it's the same place.

A software architecture requirement for third-party logistics providers who must run each customer's rules, contracts, and reporting separately within one platform.

A software design supporting multiple legal entities, currencies, and jurisdictions within one platform without flattening them into a single ledger - critical for international expense management and logistics operations.

Connecting several systems at once (ERP, TMS, WMS, supplier, and CRM records) so a risk model isn't blind to any one part of the operation.

A platform design giving each client account data isolation, independent configuration, and its own reporting is required for smart-locker or SaaS platforms resold to other businesses.

Architecture that lets a single platform serve many operators under isolated branding, data, and configuration, enabling growth through partners without expanding core support staff.

Tracing exposure not just to a direct vendor but through that vendor's own suppliers and subcontractors, several levels deep.

An IATA-backed standard letting airlines distribute richer, personalized fare offers (branded fares, ancillaries, seat maps) directly, alongside traditional EDIFACT-based GDS content.

Standardizing disparate inputs (aligning timestamps, matching vendor names) into one risk model; skipping this step floods dashboards with false alerts until teams stop trusting the tool.

The vehicle port through which telematics hardware reads engine diagnostics and speed data.

The percentage of available hotel rooms sold during a period, high occupancy through steep discounting, doesn't necessarily mean strong profitability.

Caching routes and critical data locally so tracking and navigation keep working through connectivity dead zones, then syncing automatically once signal returns.

A deployment model requiring upfront hardware and network setup in exchange for full control over every security layer, favored when compliance demands it.

A logistics KPI measuring whether a delivery arrived by the requested date with every item included.

Risk that hits a business's ability to move goods at all, including single-source supplier disruption, logistics bottlenecks, and demand-planning gaps.

Automated notifications that surface cost or efficiency gains (like shipment consolidation) that a team would otherwise miss without reviewing every system manually.

How long it takes to pick, pack, and dispatch a single warehouse order.

Bots that extract order details, validate them against inventory, and confirm to the customer without a person opening a spreadsheet.

Parcel delivery to a locker or pickup point rather than directly to a recipient's door, growing as carriers and consumers seek to reduce failed-delivery costs.

The identifier Travelport onboarding provisions for a travel agency or platform are required on every API call to identify the requester to the GDS.

A logistics KPI counts an order as successful only if it arrived on time, complete, undamaged, and correctly documented - all four conditions at once.

The record a GDS generates once a booking is processed with a supplier, confirming a reservation exists across the airline, hotel, or rail system involved.

A required credential on every Travelport API call identifying the requesting agency; without correct POS configuration, requests authenticate but return no usable content.

The design choice in T&E software between retroactive (flag violations during review) and proactive, card-linked (block violations at the transaction) models is described as the most consequential technical decision in evaluating expense platforms.