Stack map for logistics ops (Oct 2026): inventory AI seats across visibility, TMS, forwarding, planning, brokerage, and last mile

What this how-to covers

Logistics teams rarely buy one AI tool on purpose. The visibility platform adds an AI analyst and agents that chase carriers; the TMS adds an in-app assistant and document AI; the forwarder adds booking agents and an MCP connection to your chat assistant; the planning suite adds agents and scenario AI; the broker tools add voice and email agents that can quote and book; the routing tool adds AI route planning; the risk feed adds AI alerts; and every manager already has a chat seat. A year later, four tools can answer the same ETA question with four different answers, and nobody knows which one a coordinator repeated to the customer. This how-to builds one table — Job | Tool | Owner | Cost/mo | Overlap | Decision — for the eight jobs where that overlap is most common.

It is an inventory, not a ranking. Fill Cost/mo from your own contracts and invoices, write overlaps in plain sentences, and add who approves: every booking or tender, every rate offered or accepted, every carrier and customer message, every HTS code and customs entry, every plan or purchase order change, every dock appointment, and every route change on the day. AI drafts and suggests; a named person approves. No customer PII, driver names or phone numbers, live location trails, or full rate files go into a general chat tool.

How to inventory logistics-ops AI seats

Examples at a glance: each feature has a concrete example from a real job plus a short Try this you can run this week.

1. Build the blank table (primary)

What it is: Start with eight rows and six columns, and leave cells blank until you have a source: an admin seat list, a contract, an invoice, or the person who uses the tool. The eight jobs: visibility (project44, FourKites), TMS (Shipwell, Descartes, Uber Freight), forwarder portal (Flexport), planning (Kinaxis, o9, Blue Yonder), brokerage tools (HappyRobot, Parade, Loadsmart), last mile routing (Locus), risk alerts (Everstream, Altana), and the chat assistant (ChatGPT, Claude, or Gemini seats — see ChatGPT for logistics ops and Gemini for logistics ops). Add rows later for warehouse execution (Manhattan), carrier planning (Optimal Dynamics), and ecommerce fulfillment (ShipBob) if you run them.

Concrete example (director of logistics at a mid-size importer) Illustrative: a logistics director fills the table over two afternoons. “Where is my container?” shows up in four rows — the visibility platform's AI analyst, the forwarder's MCP connection, the TMS assistant, and a chat seat the coordinators use — and port-disruption alerts arrive from both the risk feed and the forwarder's map.

Try this

Primary workflow:

Build Job | Tool | Owner | Cost/mo | Overlap | Decision blank for: visibility, TMS, forwarder, planning, brokerage, last mile, risk alerts, chat assistant.

2. Owners and Cost/mo from contracts and invoices

What it is: For each tool, write one owner — the person who can cancel it — and the monthly cost from the contract, invoice, or card statement. If you can't find it, write "Unknown — check bill". Don't fill costs from list prices: in logistics there usually aren't any. Nearly every vendor in today's reviews is quote-only for buyers — project44, FourKites, Manhattan, Blue Yonder, Kinaxis, o9, HappyRobot, Parade, and Locus among them — and others bundle software into freight, customs, or fulfillment quotes (Flexport, ShipBob) or sell outcome-based terms. Several price per shipment, per load, per task, or per outcome, so the monthly number moves with volume.

Concrete example (finance manager gathering costs) Illustrative: a finance manager finds the visibility platform on an annual contract, the forwarder's software folded into freight invoices, and a broker voice agent billed per completed call. She writes "Unknown — check bill" for the AI add-on bundled into the TMS renewal instead of guessing.

Try this

Costs from invoices only:

For each of the eight jobs, name the owner and Cost/mo from contracts and invoices only. If missing, write Unknown — check bill. Do not invent prices, per-load fees, or volume tiers.

3. Mark overlaps in plain language

What it is: For each job with two or more tools, write one sentence about what both do — for example, "The visibility platform's AI analyst and the forwarder's MCP connection both answer ETA questions for the same ocean shipments." Common logistics overlaps: ETA and shipment-status answers from a visibility platform, a forwarder, a TMS assistant, and a chat seat (project44 vs FourKites, What’s new in Flexport); carrier follow-ups from a visibility agent, an exception agent, and a broker voice agent (HappyRobot vs Parade, Loadsmart AI); planning AI in two suites, or in a suite and a spreadsheet (Kinaxis vs o9, Blue Yonder vs Manhattan); disruption alerts from a risk feed and a forwarder map (Everstream AI, Altana AI); and route planning in both the TMS and a last-mile tool (Descartes AI, Locus AI).

Concrete example (logistics coordinator reviewing the table) Illustrative: a coordinator finds the same late container chased by the visibility platform's agent and by a teammate using a chat seat, with two different ETAs sent to the customer. She flags it for a decision first.

Try this

One sentence per overlap:

Wherever two tools share a job, write what both do in one sentence — for example, both answer ETA questions for the same shipments. Ask each tool's owner to confirm it before anyone suggests dropping a seat.

4. Add who approves and the data rules

What it is: Add two columns: Who approves and Data rules. Many logistics tools can now act, not just draft — book or tender a load, counter a rate, email a carrier, draft an HTS code, change a plan, move a dock appointment, re-route a driver. For every tool, name the person who approves each action it can take: the transportation manager for bookings and booking rules, the carrier sales lead for rate ceilings, the logistics coordinator for carrier and customer messages, the customs or compliance lead (or licensed broker) for every code and entry, the planner for plan and purchase order changes, the warehouse manager for appointments, and the dispatch lead for routes on the day. Driver safety and hours-of-service rules stay with the carrier and dispatcher. Write what data may go in: sanitized exports and approved procedures, yes; customer PII, driver details, or rate files in a general chat tool, no. September changelogs show why this matters — see What's new in Flexport (Sep 2026) and What's new in o9 Solutions (Sep 2026).

Concrete example (carrier sales lead tightening approvals) Illustrative: she finds a voice agent allowed to counter rates up to a ceiling nobody had reviewed in months. She lowers the ceiling, turns auto-booking off for 30 days, and names herself as approver for every ceiling change.

Try this

Who approves, what goes in:

For each tool, write who approves bookings, rates, carrier and customer messages, customs codes, plan changes, appointments, and route changes, and one line on what data may go in.

5. Write one-sentence decisions

What it is: For each overlap, write one decision: keep both (with a reason), consolidate into one, or pause one for 30 days. Name who owns the follow-up and the renewal date. Start with the three rows where overlap costs the most attention: visibility, brokerage, and the chat assistant — the places where two answers to one question reach a carrier or customer.

Concrete example (VP of supply chain at a building-products manufacturer) Illustrative: he makes the visibility platform the only source of ETAs given to customers, pauses ETA questions in chat seats for 30 days with the lead coordinator as owner, and keeps one broker tool as the only one allowed to book.

Try this

One sentence, one owner:

For the visibility, brokerage, and chat assistant rows only, write a Decision in one sentence each (keep both, consolidate, or pause). Name who owns the follow-up date and note any renewal date.

Pricing context (October 2026)

This how-to does not quote vendor prices. Fill Cost/mo from your contracts and invoices only; use Unknown — check bill when missing. Today's logistics reviews note which vendors are quote-only — nearly all of them for buyers (Oct 2026).

Our soft offers stay $9 for the toolkit spreadsheet and $19 for the audit — links on /stack and /audit.

Uncertainty: Logistics software is mostly sold on custom contracts, often bundled with freight, customs, fulfillment, or per-load and per-outcome fees, so a list price would not be your bill even where one exists. This page invents none. Vendor AI features and the actions they can take change with each release — re-check each tool's settings after major updates.

When it’s useful (honest take)

Useful when you suspect three tools answer the same ETA question or chase the same carrier.

Less useful when you only need a single-product review — start from project44 AI or Flexport AI instead.

Related options (educational)

FAQ

What columns does the table need?

Job, Tool, Owner, Cost/mo, Overlap, and Decision — plus Who approves and Data rules once you are ready.

What if I cannot find a price?

Write Unknown — check bill. Do not invent amounts from directories, a vendor's sales deck, or a freight quote.

Which eight jobs?

Visibility, TMS, forwarder, planning, brokerage, last mile, risk alerts, and chat assistant — the inventory order for this page.

Can AI book loads or accept rates on its own in this inventory?

No. The inventory assumes a named person approves bookings, rates, carrier and customer messages, customs codes, plan changes, appointments, and route changes — and owns any auto-booking or rate-ceiling setting a tool offers.

Where do custom GPTs fit?

On the chat-assistant row. OpenAI says custom GPTs are scheduled to retire on December 11, 2026 — move freight SOP work into a project; see ChatGPT for logistics ops.

Optional next step (if seats overlap)

If logistics ops pays for a visibility platform with an AI analyst, a TMS assistant, a forwarder's MCP connection, broker agents, and chat seats that all answer the same ETA question, finish this inventory before the next renewal. Map the overlap with the $19 AI toolkit audit or the $9 AI toolkit spreadsheet. Email Audit $19 or Toolkit spreadsheet $9.

Checkout is live via Stripe. After you pay, we email delivery (spreadsheet) or intake next steps (audit).

Related: Stack map for ecommerce ops · ChatGPT for logistics ops · Gemini for logistics ops · What’s new in Flexport (Sep 2026) · What’s new in o9 Solutions (Sep 2026) · project44 AI · FourKites AI · Flexport AI · Manhattan Active AI · Blue Yonder AI · Kinaxis AI · o9 Solutions AI · project44 vs FourKites · Uber Freight AI · HappyRobot AI · Parade AI · Blue Yonder vs Manhattan · Loadsmart AI · Shipwell AI · Optimal Dynamics AI · Descartes AI · ShipBob AI · Locus AI · Altana AI · Everstream AI · Kinaxis vs o9 · HappyRobot vs Parade · Stack map for field service ops · Samsara AI · Motive AI · Samsara vs Motive · Cin7 AI · AfterShip AI · ChatGPT for ecommerce ops · Gemini for ecommerce ops · Claude · Three checks before another AI seat · ops hub