Quick Answer: Freight forwarding back-office work (document intake, milestone tracking, shipper and consignee updates, invoicing, AR/AP reconciliation) can be automated by 60 to 80 percent using an AI operations layer, without touching the licensed customs filings that stay in your dedicated software. MiOpsAI's Operations chair (LizziAI) plus Finance chair (Mac) handle the automation layer; your licensed customs work stays in CargoWise, DDS+, or your existing customs software.
Freight forwarding is one of the most document-intensive operations in all of logistics. A single ocean shipment can generate 15 to 25 documents (booking confirmation, commercial invoice, packing list, bill of lading, arrival notice, delivery order, customs entry, ISF filing, invoice from the ocean carrier, invoice from the trucking segment, invoice from the drayage, invoice from the warehouse, POD, and so on). Every one of those documents needs to be intaken, filed to the right shipment record, reconciled against the quote, and used to update the client on status.
The typical forwarder handles this with a combination of a specialized platform (CargoWise being the most common), spreadsheets, email, and a lot of operations staff time. The Journal of Commerce has been tracking the labor-intensity of freight forwarding for years; the industry norm is roughly 1 back-office FTE per 800 to 1,200 shipments per month, and that ratio has barely improved in a decade.
This piece walks through what freight forwarding back-office automation actually looks like in 2026, what stays in your customs platform, and how MiOpsAI layers an AI operations desk on top of your existing forwarding tools.
What freight forwarding back-office time goes to
| Activity | Percent of ops FTE time | Automatable? |
|---|---|---|
| Document intake and filing | 25% | Yes (90%+) |
| Client status updates | 20% | Yes (85%+) |
| Milestone tracking / exception flagging | 15% | Yes (80%+) |
| Vendor invoice reconciliation | 15% | Yes (75%+) |
| Client invoicing | 10% | Yes (85%+) |
| Licensed customs work | 10% | No, stays licensed |
| Exception resolution / relationship | 5% | Human owns |
Roughly 85 percent of back-office time is automatable workflow. That is the gap the AI operations layer closes.
Document intake at machine speed
The first big win is document intake. LizziAI reads inbound emails, extracts attached documents (PDF, image, EDI), identifies the document type (commercial invoice, bill of lading, arrival notice, etc.), matches it to the correct shipment record, and files it with the right metadata (issue date, party, reference numbers).
Shipments that used to take 15 minutes of manual filing per document now take under 30 seconds. On a 500-shipment monthly volume with an average of 12 documents per shipment, that is 6,000 documents saved from manual intake per month. At 5 minutes each, that is 500 hours of ops time reclaimed monthly.
Milestone tracking and exception flagging
Every shipment has milestones: booked, cargo received, sailed / flown, arrived, cleared customs, delivered. In a manual back office, ops staff check status pages and update the shipment record. In an automated back office, LizziAI monitors carrier tracking feeds, port status APIs, and customs status feeds, updates the milestone automatically, and flags any exception (missed ETA, customs hold, damaged cargo notice) to the assigned rep.
Client status updates
Consignees and shippers both want status. Historically this meant an ops staffer sending an email every time a milestone hit. LizziAI generates the update automatically, sends via the client's preferred channel (email, portal, EDI 315 status message), and logs it to the shipment record. Ops staff only touch the update if the client asks a follow-up that requires judgment.
Vendor invoice reconciliation
Freight forwarding involves many vendors per shipment (ocean carrier, trucker, drayage, warehouse, customs broker if separately licensed, chassis provider, examination facility). Every one sends an invoice. Every invoice needs to be matched against the shipment, checked against the original quote, disputed if outside tolerance, and pushed to AP.
The Finance chair (Mac) handles the match and dispute workflow. When an invoice arrives, Mac parses it, matches to the shipment, compares against the quote, and either approves for payment or flags for dispute. Ops staff only touch invoices flagged for dispute.
Comparison: manual back office vs automated with MiOpsAI
| Metric | Manual back office | MiOpsAI-automated |
|---|---|---|
| Ops FTEs per 1,000 shipments/month | 1.0 to 1.3 | 0.4 to 0.6 |
| Document intake time per document | 4 to 8 minutes | Under 30 seconds |
| Milestone update lag | 4 to 24 hours | Under 15 minutes |
| Invoice-to-AP cycle time | 5 to 12 days | 1 to 3 days |
| Invoice dispute catch rate | 60 to 75 percent | 95 percent+ |
What stays in your customs software
To be explicit: MiOpsAI does not do customs filings. Your licensed customs brokerage work (7501 entries, ISF filings, ACE filings for U.S. work, or the equivalents in other jurisdictions) stays in CargoWise, DDS+, or whichever customs software you are licensed on. That work requires a licensed broker and specific regulatory software.
What MiOpsAI does is wrap the operational layer around the customs work: intake of pre-filing documents, coordination with the customs broker (whether in-house or third-party), status back to the client, and post-clearance milestones.
How MiOpsAI structures a forwarder back office
- Operations (LizziAI) owns document intake, milestone tracking, exception flagging, and client status updates.
- Projects (Milo) tracks every shipment as a project with all milestones and hand-offs visible.
- Finance (Mac) handles vendor invoice reconciliation, client invoicing, AR/AP, and per-shipment margin.
- Growth (Marcus) manages client development, QBRs, and lane growth conversations.
Frequently asked questions
Do you integrate with CargoWise?
Yes. MiOpsAI reads shipment status and document events from CargoWise and pushes coordination updates back. Documents intaken in MiOpsAI can be pushed to CargoWise where relevant for the licensed work.
What about DDS+?
Same integration pattern as CargoWise. MiOpsAI reads and writes via the DDS+ API.
Can this handle domestic and international shipments in the same platform?
Yes. Domestic and international shipments share the same underlying shipment record structure. International shipments have additional milestones (customs, port, drayage) that appear on the record when the shipment is flagged international.
How does this affect our licensed customs broker workflow?p>It doesn't touch the licensed work. Your customs broker keeps working in CargoWise or DDS+ exactly as they do today. What changes is the pre- and post-clearance workflow around them becomes automated.What about ISF filing deadlines?
Milo (Projects) tracks ISF deadlines as milestones. LizziAI flags shipments where ISF-required documents are still outstanding as the 72-hour window approaches. The actual ISF filing still happens in your licensed software.
Where to start
The best diagnostic for a forwarder is a document flow audit. We look at your inbound email volume, document types, shipment count, and current ops FTE deployment to model where the automation savings are largest. Book time on our request access page. See also the 3PL consolidation playbook for the broader operational context, and our logistics industry page for the full setup.