Air freight forwarding

Before the cargo reaches the airport,
align the records, capacity and responsibility.

Not another cutoff reminder. A clear view of what is missing and who owns it.

NovaPilot connects instructions, actual cargo, bookings and terminal responses into one shipment evidence trail. AI explains changes, digital roles follow milestones and QBot connects authorized systems. People retain important commitments and cost decisions.

AN INDUSTRY SOLUTION IN 95 SECONDS

Cargo is almost at the airport. Are documents, capacity and costs aligned?

Forwarding leaders · Route, operations and settlement teams

Mandarin audio · Chinese / English captions · Full industry solution

The operating problem

Cargo details and flights change while quotes, commitments and cost approvals lag behind. Missing records surface at the cutoff; accountability and costs remain unclear afterwards.

How specialists respond

Document specialists expose version conflicts and gaps. Capacity specialists compare waiting, rerouting and split shipments. Settlement specialists reconcile quotes, bills and customer approvals.

Outputs and business value

Receive a document-readiness checklist, an options comparison and a charge-variance evidence trail, so owners can spot risks earlier, decide and follow through.

An illustrative solution, not a customer performance claim. Data requires authorization and important actions remain owner-approved. Validate outcomes against your systems, evidence and acceptance samples.

Read the full narration

0:05 Cargo is almost at the airport, but documents, capacity and charges still do not line up. Does the busiest moment always turn into firefighting?

0:15 The weight changed, but the quote did not. The flight changed, but the customer commitment stayed the same. Only afterwards do you find that nobody approved the extra charges.

0:26 NovaPilot is the AI expert team for your air freight operation. See risks earlier, prepare options and clarify who owns each decision.

0:35 When instructions are revised repeatedly, first confirm the version and identify conflicts. Before delivery, list what is missing, who must provide it and which documents are needed.

0:46 When flights change, specialists compare waiting, rerouting and splitting shipments. See the cost difference, the delivery impact and what still needs confirmation.

0:59 After departure, settlement specialists keep checking quotes, invoices and customer approvals. Investigate differences and gather missing evidence so each shipment cost can be explained.

1:11 Data use requires authorization. Important actions need your approval. Experience is validated before the team reuses it.

1:21 Bring a recent shipment problem and rehearse the process with us. We deliver a configured solution and validate agreed outcomes. NovaPilot: greater confidence in critical decisions.

START WITH THE OUTCOME YOU OWN

One forwarding company. Multiple services, teams and partners.

Capacity sales and booking

Whether selling your own route capacity or a partner’s, check capacity, cost and client commitments when cargo or flights change.

See the relevant playbook

Documentation and operations

For your own shipments or work entrusted by forwarding partners, establish the document version, operating authority and next approver.

See the relevant playbook

Management and finance

See unresolved charges, blockers and exceptions by shipment without reconstructing them at month end.

See the relevant playbook

ONE CHANGE. MORE THAN ONE CONSEQUENCE.

A warehouse weight changes. What else needs another look?

Actual cargo and source versionDocument, cost and capacity impactPrincipal and capacity-provider confirmationUpdates and actual responses

Each change has an impact scope, required owners and outstanding responses. Client approval is not carrier confirmation; data entry is not cargo acceptance. Closing those gaps is the step from assistance to controlled execution.

OPERATIONAL PLAYBOOKS

Make the issue reviewable, actionable and testable.

Start with the issue you recognize. Expand its inputs, handling, human decisions and exception outcomes. These are evidence-informed solution designs, not customer outcome claims.

01 · Handling team × Documentation owner

Three instruction versions. Which one reaches the next team?

A usable record needs the right shipment, source references and resolved conflicts.

Explore the work, exceptions and acceptance
Where the work breaks
Multi-client attachments and pages are processed separately, creating shipment or version conflicts. Individually plausible waybills can still have inconsistent totals.
Evidence to bring
Original instructions and revisions, customer/shipment identifiers, master/house relationships, packing and receipt records, and client field templates.
How the product helps
The instruction app associates documents before extraction, retaining raw and normalized values and sources. Deterministic checks test units, totals and requirements; review forms resolve conflicts before a fixed version is exported.
Who makes the important decision
Documentation staff confirm association and version. The principal supplies or corrects facts; the responsible owner approves the handoff.
Branches to rehearse
Clear association: structured output. Mixed/missing pages: request clarification. Total mismatch: locate the difference. Post-review revision: revalidate the affected output.
What the team receives
Source-linked fields, JSON/Excel output, exceptions and the confirmed version. Extraction and system entry are verified separately.
What to measure
Whole-record correctness, review/correction effort, clarification rounds and post-departure amendments—not just OCR field accuracy.
Delivery dependencies and boundaries
Freeze templates, fields and association rules. Deliver valid shipments separately from failed ones; never guess missing or unreadable facts.

Evidence: Carrier notice: master/house AWB inconsistencies

02 · Booking × Sales × Operations

Actual pieces, weight or dimensions changed. Does the original plan still hold?

Do not update the weight while leaving customer approval and capacity planning on an old version.

Explore the work, exceptions and acceptance
Where the work breaks
Actual cargo differs from estimates, changing charging, dimensions and capacity needs. Sales and operations continue from outdated assumptions.
Evidence to bring
Estimated/final pieces, weights and dimensions, measurement records, packaging constraints, quote/rate versions, capacity status and client authority.
How the product helps
Link the changed evidence and calculate charging effects with deterministic rules. Show capacity, cost and document items requiring reconfirmation and prepare alternatives.
Who makes the important decision
The handling team verifies actual cargo; the booking owner checks capacity and cost. The client or authorized sales owner decides repricing, splitting or rerouting.
Branches to rehearse
No material effect: retain evidence. Charging change: reconfirm. Loadability change: request capacity. Rejection: respect the previous authority boundary.
What the team receives
A change-impact list, cost comparison, client approval, system updates and subsequent receipts.
What to measure
Detection lead time, unapproved cost changes, receipt completeness and traceable shipment cost.
Delivery dependencies and boundaries
Model gross, volumetric and chargeable weight separately from allocation constraints. Configure contract rules; AI does not control actual capacity or loading.

Evidence: Carrier conditions: cargo, documents and chargeable weight · Forwarder guide: estimates, final values and pending bookings

03 · Handling team × Principal × Documentation

The cargo cutoff is later. The data may already be late.

Documentation, warehouse delivery, messages and client approvals run on different clocks.

Explore the work, exceptions and acceptance
Where the work breaks
Teams watch departure and cargo cutoffs but miss messaging, evidence or approval dependencies. Cargo arrives before it is ready to be accepted.
Evidence to bring
Versioned rules for carrier, station and commodity; cutoffs and time zones; document states; sending/receiving responses; owners and substitutes.
How the product helps
The digital role works backward from the relevant cutoffs, distinguishing unprepared, sent, rejected and accepted. AI identifies missing items and routes them to owners.
Who makes the important decision
Owners confirm applicable rules; principals supply facts; qualified personnel assess commodity concerns. Authorized people decide delay or rerouting.
Branches to rehearse
Ready: authorized handoff. Vague description: seek facts. Missing evidence: block. Human timeout: escalate, not implied consent. Rejection: correct and verify again.
What the team receives
A dependency-ordered readiness list with sources, owners, deadline risks and receipt states.
What to measure
Readiness before cutoff, overdue decisions, evidence warning lead time and rejection resolution time.
Delivery dependencies and boundaries
There is no hardcoded industry-wide cutoff. Document checks are not customs release, dangerous-goods classification or carriage approval.

Evidence: Carrier messaging guidance: data and acceptance cutoffs · Regulator notice: rejection of insufficient cargo information

04 · Booking × Service × Operations

The client asks “Is it booked?” You only have partial confirmation.

Submission, segment confirmation, carrier receipt and actual departure are not one completed state.

Explore the work, exceptions and acceptance
Where the work breaks
First-leg confirmation becomes an all-route promise. After acceptance, teams continue watching booking screens rather than shipment events.
Evidence to bring
AWB/segments, booking responses, refresh timestamps, acceptance/tracking events and the milestones the client needs.
How the product helps
Display each segment with source and time, separating planned and actual events. Missing or stale responses create verification tasks and factual customer-update drafts.
Who makes the important decision
The booking owner confirms pending legs with the carrier or forwarding partner; service approves external communication; operations follows the mandate.
Branches to rehearse
All legs confirmed: continue tracking. Partial: identify pending legs. Stale data: verify. After RCS: use tracking. Unknown result: do not report success.
What the team receives
Segment states, verification tasks, a customer-update draft and source timestamps.
What to measure
Misreported states, overdue confirmations and time from exception detection to owner response.
Delivery dependencies and boundaries
Map each carrier’s status codes. Missing responses or unavailable accounts remain explicitly unknown.

Evidence: Booking guide: partial confirmation and carrier receipt · Cargo-terminal online services announcement

05 · Booking × Sales × Client owner

The flight changed. More than a flight number needs updating.

Rerouting can change cost, timing, onward handling and the commitment the client accepted.

Explore the work, exceptions and acceptance
Where the work breaks
After an offload or payload change, teams seek alternatives separately. The flight changes but prices, arrival promises and destination arrangements do not.
Evidence to bring
The actual change notice, booking and client agreement, candidate routes and valid quotes, spending limits and downstream dependencies.
How the product helps
AI summarizes impacts and compares waiting, rerouting or splitting by cost, timing and unresolved conditions. The digital role follows approvals and responses.
Who makes the important decision
The client or authorized sales owner accepts revised timing/cost. The booking owner confirms capacity; operations amends within the approved scope.
Branches to rehearse
Approved extra cost: request capacity. Wait: update the risk. Rejected: stop new commitments. Client approval without carrier confirmation: pending. Timeout: reconcile the original request.
What the team receives
Conditional options, approvals, amendment tasks, customer updates and confirmed rerouting responses.
What to measure
Time to a decision-ready option, approval completeness and missed downstream updates.
Delivery dependencies and boundaries
Do not promise capacity, compensation or arrival from model estimates. Recheck approval when cost or timing changes.

Evidence: Carrier sales terms: cancellation, payload reduction and offload

06 · Finance × Sales × Operations

The cargo has departed. Who approved this charge?

Bring the cost basis and delegated responsibility back to the shipment—not just another spreadsheet.

Explore the work, exceptions and acceptance
Where the work breaks
Measurement changes, extra services and approvals live in different records. A handling team may prepare a dispute without authority to file it.
Evidence to bring
Quote revisions, charging basis, service receipts, client approvals, carrier/terminal bills, dispute history and the applicable correction calendar.
How the product helps
The settlement specialist matches normal charges and separates charging, service, version and missing-evidence differences, routing a supported package to the authorized party.
Who makes the important decision
Sales verifies client agreements. Finance decides acceptance, recovery or dispute. Formal submissions and accounting adjustments follow account and contract authority.
Branches to rehearse
Supported amount: review and match. No client approval: sales task. Missing receipt: collect evidence. Supplier mismatch: authorized dispute. Existing case: follow it.
What the team receives
Shipment cost evidence, unapproved charges, dispute packages, handoffs and outcomes.
What to measure
Unapproved charges, resolution cycle, missed submission windows and disputed receivable age. Potential differences are not additional profit.
Delivery dependencies and boundaries
Separate preparation, approval, submission and payment authority. Never borrow another party’s account to bypass it.

Evidence: Carrier billing disputes: evidence and submission authority

FROM A FOCUSED APP TO INDUSTRY COORDINATION

Assemble around the outcome you own.

Capacity sales and booking coordination

Combine cargo-change review, segment states, rerouting options and shipment-charge review around bookings and quotes. Retain the authority and responses behind capacity and commitments.

Entrusted operations and documentation

Combine instruction association, document review, cutoff readiness and receipt handoff around one mandate. Establish whose version is being used and who receives the result.

Cross-party authority

Share only authorized shipment facts. Control quotes, customer information and submission rights separately. Preparing material does not grant approval or commitment authority.

CHOOSE THE FIRST DELIVERY SCOPE

Validate an outcome before widening execution.

Start: evidence and review

Choose one instruction type and client schema. Deliver source-linked records before external writes. Samples, association and definitions are the main dependencies.

Extend: cross-role follow-up

Add a second source, owners, waiting, escalation and handoffs. Establish who owns each state; a delivered notification does not close the work.

Deepen: controlled execution

Validate permission, duplicate handling and result checks for each API or RPA action. Routine actions operate within authority; cost, price, publishing and external commitments remain owner decisions.

MORE THAN ANOTHER CHAT WINDOW

Ground the interpretation, decision and action.

AI applications: interpret the change

Interpret documents and context, expose sources, gaps and conflicts, and prepare reviewable outputs. Do not invent missing business facts.

Explore AI applications

Data and low-code: align facts and ownership

Align identifiers, timestamps and metric definitions with the data layer. Use configured forms and existing approvals for missing data, reviews and exception handoffs.

Explore the platform

QBotRPA and workers: follow through

Use authorized APIs where available, or validated RPA paths for interface-only systems. Digital roles follow receipts and pending tasks; reconcile unknown outcomes before retrying.

Explore QBotRPA

FROM THE BUSINESS ISSUE TO A DELIVERY PLAN

Rehearse the difficult handoff before committing to delivery.

Bring a matched set of records

Choose a recent exception. Bring the source documents, revisions, system states and human handling record together, with sensitive information redacted.

Test different outcomes

Vary data completeness, external confirmation and the owner’s approval or rejection. Agree when to proceed, wait, change the plan or stop.

Retain a deliverable scope

Freeze field definitions, responsibilities, API and RPA dependencies, human decisions and acceptance cases. Keep unresolved conditions visible.

Compare comparable samples for hands-on time, whole-record correctness, exception resolution and actual running cost. Include failures, waiting and rework; model extraction scores and generation counts are not business outcomes.

CHECKABLE OPERATING EVIDENCE

Evidence for the scenario. Your samples for the result.

View public evidence and its limits

Official guidance establishes operating constraints. Practitioner reports establish reported events, not industry prevalence. These sources imply no endorsement or partnership. Validate applicability by marketplace, route, contract and effective version.

Carrier notice: master/house AWB inconsistencies
A 21 July 2017 notice records penalties or delays associated with house-waybill errors, weight mismatches and post-departure changes. Not current prevalence.
Carrier conditions: cargo, documents and chargeable weight
The conditions distinguish gross, volumetric and chargeable weight and address inconsistent documents. They do not establish universal carrier rates.
Forwarder guide: estimates, final values and pending bookings
The guide distinguishes estimates from final values. Changes may require carrier review; saving a quote does not reserve capacity.
Carrier messaging guidance: data and acceptance cutoffs
The 2024 guidance specifies advance messaging for its stated route scope. Its timing is not a universal cutoff.
Regulator notice: rejection of insufficient cargo information
The September 2025 notice describes ACE rejection of insufficient cargo and party information. Technical submission is not regulatory acceptance.
Booking guide: partial confirmation and carrier receipt
The 25 March 2025 guide distinguishes partial confirmation and other booking states. Its booking view freezes at RCS; subsequent events use tracking.
Cargo-terminal online services announcement
The 27 June 2024 announcement describes existing online status and charge services. The solution connects systems rather than assuming the industry is undigitized.
Carrier sales terms: cancellation, payload reduction and offload
The April 2025 terms allow operational changes under stated conditions. A booking agreement is not an absolute no-offload guarantee.
Carrier billing disputes: evidence and submission authority
The FAQ describes supporting evidence and limits who can file billing disputes. Preparing evidence does not grant another party’s submission authority.

Research checked on 24 October 2026. Validate priorities with the business owner using recent redacted samples.