Automate carrier workflows without buying a TMS first

No-TMS overview

"No-TMS" describes forwarders running operations on spreadsheets (Excel, Google Sheets, Airtable), email threads with carriers and shippers, document libraries (Drive, Dropbox, similar), and lightweight tools (Notion, basic CRM systems, occasionally project-management tools). This pattern is common across small-to-mid forwarders, specialty operators handling specific commodity or trade-lane workflows that don't fit a standard TMS template, and forwarders who haven't yet adopted a TMS or have made a deliberate operational choice to stay off one.

Per Expedion's positioning: "you don't need to buy a TMS first." Adopting a TMS is a meaningful operational decision; it requires evaluation, training, data migration, and ongoing licensing, and many forwarders run sustainable operations without one. The no-TMS path is for forwarders who haven't made that purchase yet, or who have decided their operational stack works without a TMS today.

All 7 Tier 1 carrier integration tables include "No TMS" with an "Email + spreadsheet workflow" mechanism as a fully-supported Expedion integration mode, with Full coverage on SI, BL, Booking, and Tracking workflows. This is not a fallback or a degraded version of the TMS-integrated experience; it is a distinct integration architecture that connects forwarder-maintained tools (spreadsheets, email) directly to carrier portals through Expedion's agent layer.

What this spoke is, and isn't: this is the canonical reference for forwarders running without a TMS. It is not a recommendation against TMS adoption; Expedion works equally well across multiple operational maturity levels. The other 6 integration spokes describe Expedion working with specific TMSs; this one describes Expedion working without a TMS layer. Spreadsheets plus Expedion do not deliver TMS functionality. Specific TMS features (multi-tenant accounting, customs-filing depth, inventory management, multi-tenant CRM) are not replaced by this integration mode; they remain real TMS capabilities for forwarders who need them.

Operational integration patterns

Without a TMS in the picture, the integration surface shifts from a TMS API to the forwarder's existing tools. Three integration surfaces replace what a TMS API would otherwise provide.

Layer 1: Forwarder spreadsheets and shipment tracking files. The forwarder's existing operational files become the system of record. Excel workbooks, Google Sheets, Airtable bases, or similar tools. Common patterns: a master shipment-tracking spreadsheet with one row per shipment (booking ref, carrier, vessel, container details, milestones, customer info, freight rate); separate spreadsheets for rate cards, customer contact lists, and document tracking; Drive or Dropbox folders for BL drafts, customs paperwork, and pre-alerts. Agents read shipment data directly from these files and write events back to the same source. Milestones get logged to the tracking spreadsheet, completed BL events flag the relevant row, and customer-facing updates pull from the same data the forwarder's team already uses.

Layer 2: Email integration. Forwarders without a TMS run carrier coordination through email. Booking confirmations, BL drafts, milestone notifications, customs notifications, rate quotes all flow through the forwarder's email inbox. Agents parse incoming carrier emails to extract structured data (booking refs, milestone events, BL fields) and update the spreadsheet layer. Outbound coordination (email to shippers, consignees, customs brokers, internal team) also runs through email; agents draft routine messages that the forwarder reviews before sending. Email access uses the forwarder's authentication with explicit authorization; no credential sharing across forwarder accounts.

Layer 3: Direct carrier portal automation. Without a TMS to mediate, all carrier-side execution runs through portal automation. Maersk.com, myMSC, My CMA CGM, Online Business Suite, ONE eCommerce, SynCon Hub, and ShipmentLink: agents drive each carrier's portal directly to submit SIs, request BL amendments, execute bookings, file customs documentation, and pull tracking data. This is the same portal-automation mechanism that fills carrier-integration gaps in the TMS spokes; here it is the universal carrier-execution surface rather than a per-carrier fill-in.

For ops automation, this three-layer architecture means there is no TMS API in the picture. The forwarder's existing tools become the system of record (Layer 1 plus Layer 2), and Expedion bridges between them and each carrier's portal (Layer 3). Forwarder-side data exchange runs through direct file and email surfaces; carrier-side execution runs through portal automation universally.

How Expedion integrates

Expedion agents read shipment state from the forwarder's existing tools. From spreadsheets: booking refs, container details, customer info, freight rates, milestone tracking. From email: carrier-sent booking confirmations, BL drafts, milestone notifications, customs notifications, rate quotes. The forwarder's existing files and email threads are the system of record; agents pull from the same data the forwarder's team uses daily.

Carrier-side workflows execute through direct portal automation across all 7 Tier 1 carriers. Where carrier-side execution requires portal-specific knowledge (Maersk's HS-code enforcement at SI submission, MSC's character validation and ICS2 filing modes on myMSC, COSCO's portal-only flows for Chinese-origin documentation), Expedion agents handle the variance per workflow against each carrier's portal directly. Same mechanism the TMS spokes use to fill TMS-integration gaps; here it is the universal pattern rather than a per-carrier fill-in.

Completed events write back to the forwarder's spreadsheets and email. Milestones logged to tracking files, BL events flagged on the shipment row, customer updates drafted as email replies for forwarder approval. The forwarder's tools stay the system of record through the full workflow.

Authorization is forwarder-provided: agents use forwarder-supplied spreadsheet access (file-share permissions on Google Sheets, Drive folder access for Excel, similar), email account access with explicit authorization, and carrier-portal credentials with explicit authorization per carrier. No credential sharing across forwarder accounts.

Workflows automated without a TMS

Five Phase 1 workflows on the no-TMS integration mode. Each row is a workflow; the integration mechanism describes how Expedion agents bridge between the forwarder's spreadsheets and email and each carrier's execution channel. The forwarder-side integration uses spreadsheet read/write and email parsing; the carrier-execution integration uses direct portal automation across all 7 Tier 1 carriers. Same end-to-end coverage as the TMS-integrated spokes, with the system of record sitting in the forwarder's existing tools rather than a TMS database.

Onboarding timeline

Expedion onboarding for no-TMS forwarders runs the same five to seven business days as the TMS-integrated paths. The variance vs TMS-integrated onboarding is operational scope, not a structurally faster engagement: spreadsheet and email surfaces need to be wired up (file-share permissions, email account access with explicit authorization, file structure mapping), and carrier portal credentials need to be set up for each carrier the forwarder uses. This typically takes the same calendar time as TMS-integration onboarding.

No-TMS-specific onboarding steps: forwarder shares spreadsheet templates (master shipment-tracking file, rate cards, customer contact lists, similar) and grants email access with explicit authorization. Agent file-mapping configuration translates the forwarder's existing column structure into the agent's data model, with no requirement to migrate to a different spreadsheet template. Forwarder reviews every agent output during the supervised validation period before production handover, same as the TMS-integrated paths.

Operational maturity floor: Expedion's automation ROI is most visible above a meaningful shipment-volume threshold; below that threshold, manual ops remains the right operational call for some forwarders. The exact threshold varies by carrier mix and workflow complexity; the todo block flags the operational verification.

Where it fits

Three forwarder profiles fit the no-TMS integration mode.

Small operators starting out. Just launched the business; haven't picked a TMS yet; processing a meaningful but limited shipment volume on spreadsheets and email. Expedion is the first automation layer they would add. Carrier-side execution automation provides immediate operational value; TMS adoption remains a separate operational decision the forwarder can make on their own timeline.

Specialty and niche forwarders. Established operators handling specific commodity or trade-lane workflows that don't fit a standard TMS template. Some have deliberately stayed off TMS because their workflow is too specific to map cleanly onto general-purpose TMS data models. Expedion automates the carrier-side execution without forcing the forwarder into a TMS template.

Forwarders evaluating TMS adoption. Some forwarders process shipments on spreadsheets while researching, evaluating, or implementing a TMS. Expedion can run during the evaluation period (proving automation value on the carrier-side) and continue running after TMS adoption (re-pointing the agent layer to the new TMS via the same agent-on-portals pattern plus the new TMS API; carrier-side automation does not need to be rebuilt). This makes Expedion compatible with later TMS adoption without forcing it.

What this integration mode is, and isn't: this is carrier-side execution automation on top of the forwarder's existing spreadsheets and email. It is not a TMS replacement. Multi-tenant accounting, customs-filing depth (US ACE/AES, ICEGATE-grade compliance, EU customs filings), inventory management, multi-tenant CRM, rate management at scale, and audit trails for regulatory compliance regimes that require TMS-grade audit logging remain real TMS capabilities for forwarders who need them. The no-TMS spoke serves forwarders whose operational stack works without these specific TMS features today.

Operational maturity flexibility: Expedion works at multiple operational maturity levels (no-TMS, mid-market TMS, enterprise TMS). The choice of operational stack is the forwarder's; the agent layer is independent.

Related pages

Carriers Expedion supports without a TMS: Maersk, MSC, CMA CGM, Hapag-Lloyd, ONE, COSCO, and Evergreen.

Hubs: Carriers hub · Solutions hub · Integrations hub

Solutions: Bill of Lading · Shipping Instructions · Booking · Documentation · Tracking

TMS integrations: CargoWise · GoFreight · Magaya · Logi-Sys · Descartes · ShipThis

Frequently asked questions