The Q1 2026 Release is the largest scope expansion the platform has shipped in recent quarters. Air freight booking is now a first-class capability alongside ocean. A dedicated Dangerous Goods (IMO/DGD) module replaces the previous boolean hazmat flag. The yard model moves from free-text location strings to a five-level hierarchical location system, and the damage management foundation gets standards, cross-company visibility, and a richer mobile capture flow.
Air Freight Booking
The platform now supports air freight alongside ocean. A new Flight entity and UI module sit parallel to the existing Voyage model, with their own scheduling, routing, and document workflow. A dedicated Airline party role mirrors the existing sea-carrier (Line) role across booking parties, customs configuration, stock transport intake, and checkout validation, so air-side counterparties can be modelled and integrated without being shoe-horned into the ocean schema.
Supporting changes include:
- Booking forms now accept airline-side counterparties and airport-coded routing.
- Customs declaration flows recognise air shipments and apply the appropriate party-role validation at checkout.
- Stock transport intake captures airline carrier and source type for downstream reporting.
Dangerous Goods (IMO/DGD) Module
The platform previously stored only a boolean "has hazardous material" flag. Q1 2026 introduces a full Dangerous Goods module per booking unit: UN number, proper shipping name, hazard class and sub-risk, packing group, packaging instructions, and quantity per inner/outer packaging. The data feeds into both customs declarations and shipping documentation, including the dedicated DGD form, so operators no longer keep dangerous goods information in spreadsheets alongside the platform.
Five-Level Hierarchical Yard Location System
Yard locations now live in a structured, yard-scoped hierarchy up to five levels deep, replacing the free-text location field that previously sat on each inventory unit. The hierarchy is configurable per yard and enforced consistently across the desktop, scanner, and reporting layers.
- Leaf-Level Location Type: Each leaf can be configured as single-unit or multi-unit, and the system warns when an assignment would conflict with the configured occupancy rule.
- Inspection-Triggered Check-In: Inspection templates can be configured to trigger automatic yard check-in on completion, so a completed receiving inspection moves the unit into stock and assigns its location in one step.
- Truck Out Experience Revamping: The Truck Out workflow has been redesigned around the new hierarchy, supporting cleaner VIN scanning, location confirmation, and outgoing-unit handoff.
- Camera Barcode Scanning: The scanner app now supports camera-based barcode scanning in addition to physical scanner hardware, useful for occasional users and field operators without dedicated scanners.
Damage Management Foundation
Q1 establishes the structural foundation for the damage management capabilities that ship as a dedicated module later in the year.
- Damage Standards: A configurable Damage Standards catalogue defines damage types, severity scales, and capture rules. Standards are reusable across inspection templates and activity definitions, so damage data is consistent regardless of where it is recorded.
- Cross-Company Damage Visibility (Alliance Groups): A new Alliance Group entity links multiple parties so that damage records captured by one member are visible to others under the agreed sharing rules. Useful for OEM-carrier-terminal alliances that need a shared damage history per VIN.
- Four-Side Outcome Type: A new activity outcome type captures four ordered values (left front, right front, right back, left back), simplifying inspection forms that need to record per-side data.
- Mobile Quick Actions: Selected activity types and inspection templates can be flagged as Quick Actions, surfacing as one-tap buttons on the related mobile form for high-volume capture work.
- Signature Capture: Inspectors can now attach a person-signature image directly to an inspection sheet when liability is confirmed, removing the need for a separate paper signature step.
- Locale-Friendly Outcome Parsing: Numeric outcomes such as "1,25" now parse correctly in locales using a comma as the decimal separator, removing a long-standing irritation for European mobile users.
Multi-Currency Pricing and Quotation Depth
Pricing gets significantly richer this quarter, particularly for multi-leg routes and multi-currency operations.
- Source-Currency Pricing: Quotation charges now persist the original source price, source currency, and source rate alongside the converted main-currency value, preserving full pricing traceability.
- Daily ECB FX Rate Import: An automated daily import of ECB reference exchange rates keeps accounting and reporting current without manual intervention. Storage is idempotent and the import runs on its own scheduling.
- Route-Segmented Charges: When a quotation includes an intermediate port, charges are now grouped into pre-intermediate, post-intermediate, and full-route segments, with the route segment captured on each charge line.
- Multi-Line Quotation Charges API: A new external API endpoint returns quotation charges grouped by shipping line, so integration partners can compare carrier pricing without specifying a line up front.
- POD Region in Charging Rules: Charging rules can now match on POD region in addition to specific port, country, and continent, supporting regional pricing that doesn't map cleanly to political boundaries.
Peppol Maturation
Building on the three-phase Peppol rollout completed in Q4, this quarter focuses on operational depth:
- Peppol Invoice list filter enhancements.
- A Peppol Identifier automatic resolver that looks up counterparty Peppol IDs from existing party data.
- Direct download of Peppol invoice attachments from the invoice record.
- Comprehensive unit-test coverage of the Peppol pipeline.
Vessel, Voyage, and Manifest Enhancements
- Vessel Merge with Usage Statistics: Duplicate vessel records can be merged using the same pattern as the transport address and party merge features, with usage statistics shown during the merge to make the right choice obvious.
- Vessel Message Deduplication: Duplicate vessel-message requests within a 90-day window are now prevented, and a dedicated request management view exposes status and not-found filtering.
- Port Stay with Bidirectional Sync: Voyage modelling now uses Port Stay as the primary port-time field, with Idle Days kept as a secondary view and both kept bidirectionally in sync across single-voyage and bulk-voyage editing.
- Manifest Type from Charge Class: The Manifest module and its Word and Excel exports now load the unit type from the charge classification, falling back to the booked type when absent.
- Country Flags on POL and POD Columns: Port of loading and port of discharge columns in list views now display country flag icons for fast visual scanning.
Customs and AES Modernization
- Legacy AES Mode Removal: The platform now operates exclusively against the modernized ACE Portal, removing the legacy Web and Embedded AES modes.
- Manual Customs Release Override: When customs system data is delayed or incorrect, operations staff can now manually override the customs release status on a stock unit, removing the need to wait for a re-sync or reach out to the customs broker.
Activity Billing, Accounting, and Reporting
- Activity Outcome on Billing Grid: A conditional Activity Outcome column on the Activity Billing grid surfaces the measured outcome alongside the charge, so operators can see why a charge fired without leaving the billing view.
- Pending Collections List: A new Pending Collections module tracks shipped units that have outstanding balances, supporting proactive collection workflows on units that have already left origin.
- NVOCC Charge Target and Agent Filtering: A dedicated NVOCC charge target supports NVOCC-specific billing flows, with agent-based filtering on the NVOCC role so users can scope shipments by their NVOCC counterparty.
- Invoice Prefix Configuration: Invoice types now support a configurable prefix with multiple format options, including period-based and year-based numbering schemes.
- Warehouse Receipt Document Type: Warehouse Receipt is now a selectable document type on bookings and dock-receipt messaging jobs, generated from booking data using the standard document template pipeline.
- Send Mail from Invoice List: The Invoice List now supports direct mail dispatch through the messaging job pipeline, in addition to the existing export-by-messaging-job action.
External API Coverage
The external API continues to broaden:
- Forecasts Export: A new GET endpoint for forecast exports follows the same incremental-sync, cursor-based design as the existing booking-items endpoint.
- Stock Items Export: Inventory units are now exposed through a dedicated incremental export endpoint, with rate limiting and token authentication consistent with the rest of the export API.
- New Yard Filter on Export: The export API supports filtering by yard and includes vehicle physics properties on the response.
- VIN-Decode in Import Stock: VIN decoding is now available in import stock forms (previously available only in transport orders), populating make, model, year, and other vehicle attributes from the VIN.
Closing
Q1 2026 widens the platform's modal footprint to include air freight, gives dangerous goods their own first-class data model, and replaces a long-standing free-text yard convention with a structured hierarchy. The damage management foundation is now in place, multi-currency pricing matches how operators actually quote, and the external API surface continues to grow. The release positions the platform for the larger themes of 2026: deeper damage workflows, multi-yard operations, and platform-wide validation discipline.
