Logistics runs on paperwork and phone calls. Melrose, a startup founded in 2024, is betting that a simple, unified directory of port terminals and a modern EDI platform can automate enough of that manual labor to justify a $39 million seed round [PitchBook, 2026]. The company's public footprint is minimal, centered on a blog and a functional website, but the capital signals a serious attempt to build foundational infrastructure for US freight movement.
The wedge is terminal data
Melrose's most tangible product is a public directory of US container terminals. The site lists facilities in ports from Long Beach, California to Savannah, Georgia, providing gate hours, UN/LOCODEs, firm codes, and contact details [getmelrose.com/terminals, 2025]. For dispatchers and truckers, this is baseline operational data often scattered across PDFs and legacy portals. By aggregating it, Melrose creates a natural entry point into a logistics workflow. The company claims this grew from a sketch to a nationwide platform in 2024 [Melrose Blog, 2024]. The directory is a classic wedge: a free, useful tool that positions the company as a source of truth before pitching paid automation.
Automating the paperwork layer
The larger bet is on Electronic Data Interchange (EDI), the decades-old standard for business documents like load tenders and invoices. Melrose's blog details integrations between its EDI platform and Transportation Management Systems (TMS), arguing that automation cuts costly human errors in shipping documents [Melrose Blog, 2025]. The product is described as a purpose-built AI for drayage and trucking operations [getmelrose.com/signup, 2025]. In practice, this likely means using rules engines and natural language processing to parse and generate EDI transaction sets (like the 990 Response to Load Tender), reducing manual data entry between shippers, brokers, and carriers.
Funding and opacity
The $39 million seed, backed by three investors, is a substantial sum for a company with no disclosed customers or founding team [PitchBook, 2026] [f4.fund, 2026]. The only named individual linked to Melrose is Khalid Karim, who authors the company blog [Melrose Blog, April 2025]. External databases list a co-founder role and prior stints at Uber and Amazon, but Melrose itself does not publish a team page [LinkedIn, 2026]. This level of opacity is unusual for a seed-stage company with this level of funding. The capital likely aims to fund rapid product development and customer acquisition in a market where trust and reliability are paramount.
| Aspect | Status | Source |
|---|---|---|
| Funding Raised | $39M (Seed) | [PitchBook, 2026] |
| Investor Count | 3 | [f4.fund, 2026] |
| Key Product Surface | US Terminal Directory & EDI Platform | [getmelrose.com, 2025] |
| Public Traction Signal | Nationwide platform claim in 2024 | [Melrose Blog, 2024] |
| Team Disclosure | Limited; blog author Khalid Karim identified | [Melrose Blog, April 2025] |
The integration challenge
The technical premise is straightforward: replace manual processes with automated data flows. The execution is where complexity lives. A successful logistics automation platform must achieve depth in three areas.
- Data accuracy and latency. Terminal hours change, gates close, contacts rotate. A directory's value decays without constant upkeep. An error here causes real physical delays.
- EDI mapping and normalization. Every carrier and TMS can implement EDI standards slightly differently. Handling this variance reliably is a combinatorial integration problem, not just a parsing one.
- Workflow embedding. The product must slot into existing operator routines. This requires understanding disparate roles,dispatcher, driver, billing clerk,and providing clear utility for each without adding cognitive overhead.
Melrose's blog posts suggest a focus on the EDI mapping challenge, detailing specific transaction sets [Melrose Blog, April 2025]. The terminal directory addresses the data accuracy problem directly, though its maintenance model is unclear.
At scale, the risks are operational. A single missed EDI 990 response could mean a load isn't covered. A wrong terminal code sends a truck to the wrong gate. The platform's reliability must approach 100% to become a default, not just a helpful tool. The $39 million war chest provides runway to solve these hard problems, but it also raises the stakes for delivering enterprise-grade robustness from a near-stealth foundation. The bet is that a clean, AI-assisted layer can absorb enough complexity from a fragmented industry to become its new central nervous system.
Sources
- [PitchBook, 2026] Melrose 2025 Company Profile: Valuation, Funding & Investors | https://pitchbook.com/profiles/company/525520-90
- [getmelrose.com/terminals, 2025] Melrose Terminals | Find a Terminal | https://www.getmelrose.com/terminals
- [Melrose Blog, 2024] 2024 Year in Review | Melrose Blog | https://getmelrose.com/blog/posts/2024-year-review
- [Melrose Blog, 2025] The smooth Integration of EDI and Your Transportation Management System | Melrose Blog | https://getmelrose.com/blog/posts/the-smooth-integration-of-edi-and-your-transportation-management-system
- [getmelrose.com/signup, 2025] Melrose - Automate you logistics operations | https://www.getmelrose.com/signup
- [f4.fund, 2026] Melrose, Logistics & Supply Chain | https://f4.fund/startups/getmelrose
- [Melrose Blog, April 2025] EDI Spotlight: 990 | Response to Load Tender | Melrose Blog | https://getmelrose.com/blog/posts/edi-spotlight-990-or-response-to-load-tender
- [LinkedIn, 2026] Khalid Karim - CoFounder @ Melrose | Ex-Uber, Amazon | https://www.linkedin.com/in/kmkarim/
- [getmelrose.com, 2025] Melrose ⎯ Automate all your Logistics with AI | https://getmelrose.com/