By Brian Carlson, Founder, Cornerstone Edge | Supply chain consultant specializing in WMS selection, implementation, and technology roadmap strategy
This post is based on our recent LinkedIn Live, “Aligning WMS & TMS Roadmaps for Strategic Success,” featuring Brian Carlson and Tony Wayda of JBF Consulting. Watch the recording here.
Most companies approach Warehouse Management System (WMS) and Transportation Management System (TMS) selection backwards. They open vendor demos before they’ve defined what they need, treat analyst rankings as a shortlist, and discover the gaps after they’ve signed a contract.
After years of leading WMS implementations and selections across retail, apparel, appliance, and food and beverage operations, I’ve seen the same failures repeat. They almost always trace back to the same root cause: the pre-work didn’t happen.
These are the seven questions every organization should be able to answer before spending a dollar on either system.
1. Have you documented your requirements at the detail level—not just the high level
Detailed requirements are what separate a successful WMS or TMS selection from an expensive mistake.
Every vendor can meet your high-level requirements. The real gaps show up in the details. As JBF Consulting’s Tony Wayda shared, one client had purchase orders so large the vendor portal couldn’t load them during testing—something a high-level requirement would never catch. By the time it surfaced, the contract was already signed.
The question isn’t whether your TMS can handle inbound routing requests. It’s whether it can handle your routing requests—your volumes, your PO structure, your vendor behavior. Define your specifics before you talk to a single vendor.
2. Have you aligned with your external partners, not just your internal team?
A WMS or TMS integration gap is just as likely to live outside your organization as inside it.
I worked with an apparel company that executed the internal selection process well. Detailed requirements, scripted demos, proper EDI mapping, pallet and case-level ASNs—all accounted for. What they discovered post-selection: an external vendor was willing to enter data into one system but not two. That wasn’t a technology problem, it was a change management problem nobody had surfaced. If you haven’t had direct conversations with your upstream and downstream partners before you select, you have a blind spot that no RFP will catch.
3. Do you understand what data needs to move between your WMS and TMS—and when?
WMS and TMS integration isn’t a yes-or-no question—it’s a timing and data question.
Tony flags a scenario that comes up more often than you’d expect: a carrier is running late, and the TMS has that visibility. In theory, the DC can pivot—pull a drop trailer and keep labor productive. But if that signal hits the warehouse floor too late, you’re left with a dock crew standing around with no warning and no work. The integration was there. The timing wasn’t.
On the outbound side, retail flow loading creates the same problem in reverse. You need to tender a load to a carrier before you know exactly what’s on the truck—which means your WMS and TMS need to handle a live two-way update as the load fills. Tony built custom integrations to solve this exact problem during a Manhattan WMS implementation at a major retailer. It wasn’t a workaround. It was a requirement that should have been in the RFP.
4. Have you independently validated the vendor’s integration claims?
“It’s integrated” is one of the most misleading phrases in enterprise software—and one of the most common.
I’ve seen this fail two ways. In the first, a company selected a TMS because they were told it integrated with their existing WMS. When we got under the hood, the integration was partial—not deep enough to meet their requirements. They ended up building a significant custom interface. In the second, a client assumed that selecting the WMS and TMS from the same vendor meant the two products were integrated. They weren’t. The competing TMS vendor had a better-tested integration with that WMS than the vendor’s own product did.
The same parent company does not mean integrated products. Validate independently, every time.
5. Do you know which product the vendor is actually selling you?
Many major WMS and TMS vendors have grown by acquisition—which means multiple products at different maturity levels under a single brand name.
When you’re evaluating Körber for WMS, you need to know which product is actually being proposed. If you are looking at the WMS and the TMS, you’ll want to ask whether the integration is live and mature—not on a roadmap. With Oracle, understand which version of their WMS is on the table and how it connects to OTM today. Blue Yonder’s WMS and TMS story similarly requires independent validation. Manhattan’s unified platform concept—a common data model beneath both systems—is gaining traction, but implementations are still early. Ask every vendor: what platform, what version, what does the integration look like today?
6. Have you done scripted demos using your own data?
A scripted demo with your own data is the single most effective tool for exposing gaps before you commit.
Standard vendor demos show you what the software can do in ideal conditions with clean, generic data. A scripted demo—built around a day in the life of your operation, with your actual data, your real exceptions, your edge cases—shows you whether it works for you. Score it. Grade it. Make the decision data-driven.
Vendors don’t love scripted demos. Do them anyway. This is where most selections go wrong: the software looks capable in the demo room and struggles in production because nobody asked the hard questions before signing.
7. Is your strategy defined before you start looking at software?
Technology should support your operation. If you let the software define your strategy, you’ve already made a mistake.
Know your workflows, your integration non-negotiables, and your unique operational requirements before you issue a single RFP. Plan your WMS and TMS together even if you’re implementing them separately—the decisions you make on one will directly constrain the other. And don’t solely rely on analyst rankings to create your shortlist. The vendor in the top right corner of the Magic Quadrant may miss every one of your “secret sauce” requirements. A vendor not mentioned might meet them all.
Do the work upfront. It costs far less than correcting a bad selection on the back end. Curious for more details? Watch the full recording, here.
Brian Carlson is the founder of Cornerstone Edge, an independent supply chain consulting firm. He has led WMS selections and implementations across retail, apparel, appliance, and food and beverage operations. Cornerstone Edge helps supply chain organizations define requirements, evaluate technology, and implement systems that fit how they actually operate. This post draws on a conversation with Tony Wayda, Principal at JBF Consulting.