# How do TMS and WMS vendors sell to shippers, 3PLs and freight forwarders?

> **The short answer:** TMS, WMS and forwarding-system vendors sell to logistics buyers (shippers, 3PLs and freight forwarders), mostly by replacing a system that still works. Deals open on dated triggers: ERP support dates, new sites, mergers and incumbent price changes. Larger buyers run an RFP and scripted demos. By Panelhop’s estimate, enterprise replacements take about 12 months and 3PL deals about 6 months.

- Page: https://panelhop.com/industries/logistics/tms-wms-forwarding-systems
- Section: Home › Industries › Logistics › TMS, WMS and forwarding systems
- Updated 5 October 2026 · Based on Panelhop research, October 2026
- Written for: Vendors of TMS, WMS and forwarding systems selling to shippers, 3PLs and forwarders
- Publisher: Panelhop (https://panelhop.com/)

**Your best demo loses to a system that still works.** You sell a TMS, WMS or forwarding system to shippers, 3PLs or Speditionen. The RFP often arrives written around a rival or the ERP’s own warehouse module, and strong evaluations end in no decision. Deals move when a dated event raises the cost of staying.

- Mid-market TMS deal: €27–107k a year (Illustrative)
- Mid-market SaaS WMS: €21–107k a year (Illustrative)
- Enterprise replacement: Typically 12 months (Illustrative)

## TMS, WMS and forwarding systems · How a deal really moves

**The RFP was written around someone else. Then the old system stays, and finance won’t buy your ROI.** (Illustrative)

With Panelhop: The same deal, found before the requirements. ERP dates and loss reasons tracked; finance in before demos end.

One shipper or 3PL, 6–13 people, and by our estimate about 12 months for an enterprise replacement, about 6 months at a 3PL.

What opens a deal:

- **ERP warehouse support ends** (Technology)
- **Incumbent price change** (Contract)
- **New DC or won 3PL contract** (Contract)
- **Merger and consolidation** (Consolidation)
- **eFTI digital freight rules** (Regulation · EU)
- **Routing-guide failure** (Contract)

The buyer: **A shipper, 3PL or Spedition**. Running an old TMS, WMS or ERP module.

Who decides:

| Seat | What worries them | Can veto |
|---|---|---|
| VP Logistics or COO | A failed go-live in front of customers. | Yes |
| CIO and ERP owner | A TMS or WMS migration on top of an ERP migration. | Yes |
| CFO or controller | Services overruns and modules nobody uses. | Yes |
| CISO or IT risk | A hosted-system outage that halts warehouses. | Yes |
| Disponent or DC manager | Training and parallel running during peak. | No |
| Procurement | Lock-in and price changes at renewal. | No |
| Selection consultant | Vendors who go around the selection process. | No |
| The 3PL’s own client | Service problems while the 3PL switches systems. | No |

How the deal moves:

| Stage | Typical time | Where it stalls today | With Panelhop | Service |
|---|---|---|---|---|
| Trigger | 1–2 months | The requirements were written without you | Weekly: accounts with an ERP support date or new site, scored and mapped | Signal Desk (In-market accounts, weekly): https://panelhop.com/services#signal |
| Requirements | 4–8 weeks | – | – | – |
| RFP | 6–12 weeks | – | – | – |
| Scripted demos | 3–6 weeks | The old system wins by still working | Loss reason and the reopening event become required fields | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Business case | 1–3 months | Finance won’t sign another customer’s ROI | Finance on the deal before demos end; the case uses the buyer’s data | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Contract | 1–3 months | – | – | – |
| Implementation | 4–24 months | Sign late and go-live waits for next year | The go-live window is a deal field; close dates work back from it | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Next site | – | – | – | – |

With Panelhop across the deal: Signal Desk · weekly on what opens a deal (in-market accounts, scored and mapped); Panel Check on the buyer (coverage baselined); Panel Ops · monthly from the last stage back to the next trigger (scores and plays tuned against the baseline).

*Source: Stages, seats, triggers and stalls from Panelhop research, October 2026; the services as described on the Services page.*
*Note: Durations, panel sizes and cycle lengths are Panelhop estimates from our research, not measurements.*

## At a glance

| Fact | Value |
|---|---|
| Mid-market TMS deal | €27–107k a year (Illustrative) |
| Mid-market SaaS WMS | €21–107k a year (Illustrative) |
| Enterprise replacement | Typically 12 months (Illustrative) |
| Go-live | 4–8 months for mid-market WMS, 12–24 months for enterprise (Illustrative) |

*Source: Panelhop research, October 2026.*
*Note: Values marked Illustrative are Panelhop estimates from our research, not measurements.*

## Why do TMS and WMS deals stall?

**Replacement pipelines leak before the RFP is written.**

TMS and WMS deals stall when the vendor arrives after the requirements are written, loses to the incumbent as no decision or meets integration scope at contract. The accounts running an ageing ERP warehouse module or an old TMS are already in your CRM.

**Exhibit 1: Where the pipeline leaks: 4 points across 8 stages.**

1. **The ERP support date reaches you as an RFP** (stage: Trigger). What you see: RFPs arrive written around an ERP’s own warehouse module or a competitor’s system. Why it happens: Nobody tracks which accounts run an ageing ERP warehouse module or an old TMS, or when its support ends.
2. **The Lastenheft is written before you arrive** (stage: Requirements). What you see: You are missing from longlists that consultants and functional databases produce. Why it happens: Engagement starts at the RFP instead of at requirements, so the Lastenheft is written around the systems the buyer already knows.
3. **Strong evaluations end in ‘no decision’** (stage: Scripted demos). What you see: Closed-lost reasons read timing, and the same accounts evaluate every few years. Why it happens: Nobody records the loss reason or the event that would reopen the deal. In Modern Materials Handling’s 2026 software survey, 14% of respondents ran a WMS installed 15 or more years ago.
4. **IT joins at contract and the services estimate grows** (stage: Contract). What you see: IT joins at contract stage and the services estimate grows. Why it happens: The ERP, EDI and carrier-API owners are not on the opportunity. We flagged integration scope as a likely stall for all 3 operational-system vendors we analysed.

*Source: Panelhop research, October 2026; [Modern Materials Handling](https://www.mmh.com/article/2026_software_survey_software_stays_at_the_center_of_the_automated_warehouse).*

## What triggers a shipper or 3PL to replace its TMS or WMS?

**Support dates, new sites and price changes open replacements.**

ERP support dates, incumbent price changes, new sites, mergers, routing-guide failure and the EU’s eFTI rule open TMS and WMS deals. Most of these events are dated before the RFP is written. The windows are Panelhop estimates from the research.

**Exhibit 2: The 6 events that open or close the window for a deal.** (Illustrative)

- **ERP warehouse module support ends** (Technology). What happens: Older ERP releases, and the warehouse modules built into them, are reaching the end of mainstream maintenance as ERP vendors move customers to successor platforms. Where to spot it: Job posts for ERP and warehouse migration roles, the account’s IT roadmap and user-group news. Window: Opens 12–24 months before the support date.
- **Incumbent price or licence change** (Contract). What happens: An incumbent TMS, WMS or forwarding system changes its pricing model or licence terms, and renewal costs rise. Where to spot it: Trade press, user forums and renewal conversations. Window: Opens in the 1–6 months around the renewal.
- **New DC or won 3PL contract** (Contract). What happens: A new distribution centre or client contract needs a WMS by a fixed start date. Where to spot it: Press releases, planning permissions, property news and 3PL contract announcements. Window: The WMS is chosen 3–9 months before the site opens.
- **Merger and platform consolidation** (Consolidation). What happens: An acquirer picks one TMS, WMS or forwarding system per division and retires the rest. Where to spot it: Closing announcements and investor-day integration plans. Window: A displacement window for challengers, often 6–36 months after closing.
- **eFTI digital freight rules** (Regulation). What happens: From 9 July 2027, EU authorities must accept freight information that operators share electronically through certified eFTI platforms. Where to spot it: European Commission eFTI pages, national transport ministries and road haulage associations. Window: Opens 6–18 months before the date for TMS and forwarding systems that issue transport documents such as e-CMR.
- **Routing-guide failure and the freight bid** (Contract). What happens: Tender rejections rise and shippers rebid outside the annual freight RFP, which tests the tendering and rate tools in their TMS. Where to spot it: Tender rejection indices, shipper mini-bid announcements and each account’s RFP calendar. Window: Weeks after rejections spike; tools that feed the bid need to be live before data collection starts, often in September.

*Source: Panelhop research, October 2026; [European Commission, DG MOVE](https://transport.ec.europa.eu/transport-themes/logistics-and-multimodal-transport/efti-regulation_en).*
*Note: Timings are Panelhop estimates from our research, not measurements.*

## Who signs off on a TMS or WMS deal?

**IT and finance decide whether the old system goes.**

The VP of logistics, COO or owner signs a TMS or WMS deal, but IT and finance decide whether the incumbent goes. The transport, warehouse or dispatch manager champions it, while procurement, security and an outside selection adviser shape the shortlist. At a small Spedition, the panel can be 2–4 people, by Panelhop’s estimate.

**Exhibit 3: At a mid-size shipper or multi-site 3PL, 6–13 people sit on the panel and 4 seats can stop the deal.** (Illustrative)

At a mid-size shipper or multi-site 3PL: 6–13 people.

| Seat | Typical titles | Cares about | Worries about | Can veto |
|---|---|---|---|---|
| Economic buyer | VP Logistics, COO, Geschäftsführer | Lower cost per shipment or order without a risky go-live. | A failed go-live in front of customers, inside a multi-year contract. | Yes |
| Operational champion | Transportation Manager, Warehouse Manager, Disponent | Fewer spreadsheets and less rekeying between systems. | Training and parallel running during peak. | No |
| IT and ERP owner | CIO, Head of Enterprise Applications, ERP lead | Fit with the ERP roadmap, EDI partners and carrier APIs. | Running a TMS or WMS migration alongside an ERP migration. | Yes |
| Finance | CFO, Financial Controller, Kaufmännischer Leiter | Total cost including services, and savings on the company’s own volumes. | Services overruns and paying for modules nobody uses. | Yes |
| Procurement | Category Manager IT, Leiter Einkauf | A weighted RFP with references from similar operations. | Lock-in and price changes at renewal. | No |
| Information security | CISO, IT Risk Manager | SOC 2 Type II or ISO 27001 evidence, hosting location and backups. | A hosted-system outage that halts warehouses. | Yes |
| Selection adviser | Supply Chain Technology Consultant, Systems Integrator Project Lead | A defensible, criteria-based selection from a Lastenheft. | Vendors who go around the selection process. | No |
| The 3PL’s own client | Shipper Logistics Director | The technology the 3PL commits to in its bid. | Service problems while the 3PL switches systems. | No |

*Source: Panelhop research, October 2026.*
*Note: The panel size is a Panelhop estimate from our research, not a measurement.*

## What do TMS, WMS and forwarding-system vendors sell, and to whom?

**Each deal replaces a system the buyer knows well.**

TMS, WMS and forwarding-system vendors sell the operational system a shipper, 3PL or forwarder runs every day. Mid-market deals are SaaS subscriptions; enterprise deals add implementation and integration work that finance counts alongside the licence. Deal sizes are Panelhop estimates converted from US dollar price guides.

**What vendors of this type sell**

- Shipper TMS for planning, carrier selection, tendering and freight settlement
- WMS for distribution centres, 3PL warehouses and fulfilment, priced per user or per site
- Forwarding systems covering quotes, bookings, customs filing and accounting
- Implementation, integration and data migration services

**Which shippers, 3PLs and forwarders buy it**

- Enterprise and mid-market shippers
- 3PLs and contract logistics providers
- Freight forwarders and Speditionen

## How does a TMS or WMS deal move from trigger to go-live?

**Replacement deals stall before the RFP and after the demo.**

A TMS or WMS deal moves from a dated trigger through requirements, an RFP, scripted demos and a business case to an implementation planned around peak. Small Speditionen decide quickly, while enterprise shippers run formal selections. The durations show the buyer’s side and are Panelhop estimates from the research.

**Exhibit 4: Stage by stage: what you do, what the shipper does, and what changes at the 4 stages where deals stall.** (Illustrative)

| Stage | Typical time | What you do | What the shipper does | Today | With Panelhop | Service |
|---|---|---|---|---|---|---|
| Trigger | 1–2 months | Waits for the RFP, with no view of ERP support dates, new sites or incumbents. | An ERP support date, merger, new site or incumbent price change forces a decision. | The first sign of a project is the RFP. Stalls: Arriving after the requirements. In DACH and large enterprise selections, a requirements catalogue (Lastenheft), consultants or functional databases often fix the longlist before a vendor’s sales team engages. | Each week, accounts with an ERP support date, new site, merger or incumbent price change arrive in your CRM, scored, with the buying group mapped and a brief. | Signal Desk (In-market accounts, weekly): https://panelhop.com/services#signal |
| Requirements | 4–8 weeks | Learns of the project when the RFI or Lastenheft arrives. | Writes a requirements catalogue and filters the market to 5–8 candidates. | Nobody knows how many won deals started before the Lastenheft. | A Panel Check rebuilds your funnel from raw CRM records and shows how many won and lost deals first entered at the RFP stage. | Panel Check (GTM audit · 2–3 weeks): https://panelhop.com/services#audit |
| RFP | 6–12 weeks | Answers functional, technical, implementation and pricing questions. | Scores bids with weights and picks 2–3 finalists. | The RFP response goes out with only operations on the deal. | Stage exit criteria require IT, finance and procurement contacts before the RFP response is submitted. | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Scripted demos | 3–6 weeks | Demos on the buyer’s own scenarios and data, then lines up references. | Scores the finalists, calls references and visits live sites. | A lost evaluation goes quiet for years, with timing as the only reason on record. Stalls: The incumbent wins by standing still. Replacing a working system feels riskier than living with it, so strong evaluations end in no decision. | A closed-lost reason and the event that would reopen the deal become required fields at the stage change, so your team knows which event to watch for. | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Business case | 1–3 months | Hands over an ROI built on other customers’ numbers. | Finance tests the savings against the company’s own freight and labour data. | Finance meets the ROI after the demo. Stalls: Finance rejects borrowed ROI. Savings modelled on another customer’s baseline do not survive a CFO review. | Finance becomes a required role before demos end, so the business case is built with the buyer’s own data. | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Contract | 1–3 months, security often in parallel | Answers security questionnaires and negotiates terms and the statement of work. | Security, legal and procurement review, then executives sign a multi-year contract. | Security and integration questions arrive after the verbal yes. | Security and the ERP owner are named roles, and the evidence request is an exit criterion before terms. | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Implementation | 4–8 months for mid-market WMS | Hands over to delivery once the contract is signed. | Plans go-live outside peak and runs the old and new systems in parallel. | Go-live dates are set without the peak freeze. Stalls: Go-live collides with peak. A mid-market WMS needs 4–8 months after signature to land outside the peak freeze, so a deal that misses its signature date waits for next year’s window. | Each account’s go-live window and peak freeze become deal fields, close dates work back from them, and a handoff document records the integrations promised. | Leak Fix (We build the fixes): https://panelhop.com/services#build |
| Next site | – | Treats the first site or division as done. | Runs each site or division with its own budget, so the next site is a new sale. | Nobody holds a map of the customer’s other sites. | Panel Ops operates the next-site plays Leak Fix builds with your team, re-tiers accounts each quarter and reports against the baseline every month. | Panel Ops (We run it monthly): https://panelhop.com/services#run |

*Source: Panelhop research, October 2026.*
*Note: Illustrative figures here are Panelhop estimates from our research, not measurements.*

## How does Panelhop change the way a TMS or WMS deal moves?

**Panelhop flags trigger accounts to your reps before the RFP.**

Panelhop changes how a TMS or WMS deal moves by flagging trigger accounts before the RFP is written and putting IT and finance on the deal. A Panel Check (GTM audit) first baselines each stage of your TMS or WMS pipeline from your own CRM data. Signal Desk (in-market accounts, weekly), Leak Fix (we build the fixes) and Panel Ops (we run it monthly) then work the stages that leak, measured against that baseline.

What we baseline and report:

1. Share of new deals entered before the RFP or Lastenheft, against the baseline
2. Days a deal spends in business case, against the baseline
3. Expansion deals as a share of pipeline, reported apart from new logos, against the baseline

## What other vendors sell to shippers, 3PLs and forwarders?

**Other vendor types in logistics.**

The same shippers, 3PLs and forwarders buy from these vendor types too, through different panels and pipelines.

- [Visibility, network and orchestration platforms](https://panelhop.com/industries/logistics/visibility-orchestration-platforms): Carrier networks, transportation visibility and orchestration layers sold above the TMS, WMS and ERP to shippers and logistics providers.
- [Customs and trade compliance software](https://panelhop.com/industries/logistics/customs-trade-compliance-software): Declaration, classification and trade compliance software sold to customs brokers, freight forwarders and cross-border shippers.
- [Freight audit, payment and billing](https://panelhop.com/industries/logistics/freight-audit-payment): Freight invoice audit, carrier payment and freight billing software sold to shippers’ finance and logistics teams, brokers and 3PLs.
- [Yard management and yard automation](https://panelhop.com/industries/logistics/yard-automation): Yard management and computer-vision yard automation sold to multi-site shippers, 3PLs and distribution networks, site by site.

[The whole logistics market: segments, panel and pipeline →](https://panelhop.com/industries/logistics/)

## What do terms like “TMS” and “WMS” mean?

**The words your buyers use, defined.**

Plain definitions of the terms that come up when you sell TMS, WMS and forwarding systems to shippers, 3PLs and forwarders.

- **TMS**: A transportation management system: software a shipper, 3PL or broker uses to plan loads, choose carriers and tender loads to them, track shipments and settle freight bills.
- **WMS**: A warehouse management system: software that runs receiving, storage, picking and shipping in a distribution centre or 3PL warehouse.
- **Forwarding system**: The core operating system of a freight forwarder, covering quotes, bookings, shipment files, customs filing and accounting in one platform. Switching it touches every department.
- **Lastenheft**: A German requirements catalogue a buyer writes before a tender. A vendor whose strengths are missing from the Lastenheft rarely reaches the shortlist.
- **Scripted demo**: A demo run on the buyer’s own scenarios and data and scored against weighted requirements. Scripted demos expose trade-offs but can flatten finalists into a price comparison.
- **Go-live window**: The months in which a shipper or 3PL will accept a cutover, outside the peak freeze. Buyers also avoid parallel running, old and new systems side by side, near peak.

## What do vendors of TMS, WMS and forwarding systems ask about selling to shippers, 3PLs and forwarders?

**Answers before your next shipper deal.**

### How long does a TMS or WMS selection take?

A TMS or WMS selection at an enterprise shipper takes about 12 months from trigger to signature and can run to 24 months, by Panelhop’s estimate. On the same estimate, mid-market shippers take about 5 months and 3PLs about 6 months. A structured evaluation alone runs an estimated 8–16 weeks. Implementation then takes an estimated 4–8 months for mid-market WMS and 12–24 months for enterprise projects.

### How do you sell a WMS against an ERP’s own warehouse module?

To sell a WMS against an ERP’s own warehouse module at a shipper or 3PL, arrive before IT has chosen. Track the accounts whose ERP release, and the warehouse module inside it, is nearing the end of mainstream maintenance. Put the ERP lead and finance on the opportunity by the second meeting, and show a deployment that runs before and after the ERP migration. Buyers who know few providers beyond their ERP vendor write requirements around the ERP’s own module, so reach them before the requirements catalogue is written.

### Who buys a WMS at a 3PL?

At a 3PL, the managing director or COO usually signs a WMS deal, with finance, IT and the warehouse or operations lead in the room. The 3PL’s own client matters too: 3PLs often commit to technology in open-book contract logistics bids, so a won tender or a new site sets a hard go-live date. Map the client and the site before you demo features.

### When do shippers and 3PLs go live with a new TMS or WMS?

Shippers and 3PLs with a seasonal peak go live outside the peak season and usually freeze system changes from early November. Work back from that window when you forecast. A mid-market WMS takes an estimated 4–8 months to go live, so the signature has to come 4–8 months before the planned go-live. A deal that misses that date waits for the next year’s window, so give it a dated next step instead of a new close date.

### Why do freight forwarders hesitate to switch forwarding software?

Freight forwarders hesitate because one forwarding system runs bookings, customs filing and accounting, and a switch at a large forwarder can take years. Forwarders tend to move only when an incumbent’s pricing change, a merger or a customs rule raises the cost of staying. Small Speditionen decide quickly. Track those events by account so your rep arrives before the shortlist forms.

### Do logistics software vendors need SOC 2 to sell to enterprise shippers?

Logistics software vendors usually need a SOC 2 Type II report to sell to US enterprise shippers and 3PLs, whose RFPs often ask a TMS or WMS vendor for one by name. European and regulated buyers ask for ISO 27001, and automotive logistics buyers for TISAX. In the EU, NIS2 adds supplier clauses to the contract. Only 5 of 18 logistics vendors in Panelhop’s research publish any security evidence, so a ready evidence pack can shorten the review.

## Sources

**Where the numbers come from.**

Sourced figures link to their source below. Figures marked Illustrative, and figures given as estimates, are inferred from Panelhop research. Vendors appear only as types, never by name.

1. [Modern Materials Handling, 2026 Software Survey: Software stays at the center of the automated warehouse (2026)](https://www.mmh.com/article/2026_software_survey_software_stays_at_the_center_of_the_automated_warehouse)
2. [European Commission, DG MOVE, eFTI Regulation (2026)](https://transport.ec.europa.eu/transport-themes/logistics-and-multimodal-transport/efti-regulation_en)
- Panelhop research, October 2026: our analysis of the vendors, buying panels, pipelines and triggers for TMS, WMS and forwarding systems in logistics, from public sources. Vendor names are not published.

## Next step

Find where your pipeline to shippers, 3PLs and forwarders leaks.

[Book a GTM audit](https://panelhop.com/book) · [What the Panel Check covers](https://panelhop.com/services#audit)