Körber WMS Problems: Why Warehouse Teams Call It 'Stepping Back 20 Years' (2026)

Körber (formerly HighJump) is the warehouse management system that mid-market distributors, 3PLs, and manufacturers run for inventory management, order fulfilment, and shipping operations. With mixed G2 ratings between 3.5 and 4.2 depending on the product line, the platform handles core warehouse workflows — receiving, put-away, picking, packing, shipping — at a functional level. The documented problems are architectural. G2 reviewers describe the system as "built on old programs pieced together" and "stepping back 20 years." EDI configuration is called "horrendous." The system requires VPN access with no native mobile app. There is no built-in cost tracking. And the knowledge dependency is extreme: reviewers warn that if one or two key people leave, "you're in serious trouble." The small add-on ecosystem means warehouse teams that hit these limits build custom software alongside the platform.

What does 'built on old programs pieced together' actually mean for daily operations?

Körber's WMS product line is the result of multiple acquisitions. HighJump was acquired by Körber in 2017, and HighJump itself was built through acquisitions of earlier warehouse software products. The result is a platform where different modules feel like different applications — because they were. The receiving module, the inventory module, the shipping module, and the reporting functions each carry their own interface patterns, navigation logic, and data structures from their original codebases.

For warehouse staff, this means learning multiple interface patterns within a single system. A process that starts in receiving, moves through inventory allocation, and ends in shipping crosses module boundaries that feel like system boundaries. Training new warehouse staff takes longer because the system doesn't behave consistently across functions. The "huge learning curve" that reviewers describe is not about warehouse management complexity — it's about software complexity layered on top of warehouse management.

The architectural age also shows in performance. Operations that should be instant — looking up inventory levels, checking order status, scanning a bin location — carry latency that adds seconds per transaction. Across thousands of daily transactions in a busy warehouse, those seconds accumulate into hours of lost productivity.

Why is EDI configuration in Körber described as 'horrendous'?

EDI (Electronic Data Interchange) is how warehouses exchange order, shipment, and invoice data with retailers, distributors, and trading partners. Every major retailer — Walmart, Target, Amazon, Costco — has specific EDI requirements. A 3PL serving 15–20 retail clients manages 15–20 different EDI configurations, each with its own document formats, field mappings, and compliance requirements.

Körber's EDI configuration requires deep system knowledge. Setting up a new trading partner's EDI connection involves mapping document types (850 purchase orders, 856 advance ship notices, 810 invoices), configuring field-level translations between the partner's format and Körber's internal data structure, and testing each document type against the partner's validation rules. G2 reviewers describe this process as horrendous because it's manual, error-prone, and requires specialist knowledge that's scarce even within the Körber consultant ecosystem.

When an EDI configuration breaks — a retailer changes their requirements, a field mapping produces incorrect data, or a new document type is required — the fix requires the same specialist knowledge. If the person who configured it has left the company (the "if 1–2 key people leave" risk), the troubleshooting starts from scratch.

What operational gaps does the VPN-only access create?

What custom software do warehouse teams build alongside Körber?

The most common build is a real-time operations dashboard. Körber tracks the data — inventory levels, order status, pick progress, shipping queue depth — but presenting it in a format that warehouse supervisors can use in real time, without VPN access, on a tablet or wall-mounted display, requires a custom layer. The dashboard reads from Körber's database, aggregates across modules, and presents KPIs: orders picked per hour, dock-to-stock time, fill rate, and backlog by priority. This is the view that operations managers need and Körber's native interface doesn't provide accessibly.

Integration middleware is the second pattern. Körber connects to ERPs (SAP, NetSuite, Dynamics), shipping carriers (FedEx, UPS, USPS), and marketplace platforms (Amazon, Shopify). Each connection requires configuration that compounds the specialist knowledge dependency. A middleware layer that standardises these integrations — providing a single API surface for ERP sync, carrier rate shopping, and marketplace order ingestion — reduces the per-integration configuration burden and makes the integration knowledge transferable rather than locked in one person's head.

EDI automation is the third build. A system that handles trading partner onboarding, document mapping, validation, and error handling with a configuration interface that operations staff (not EDI specialists) can manage. This directly addresses the "horrendous" EDI experience and reduces the specialist knowledge dependency that makes the system fragile.

When does building alongside Körber make sense vs replacing the WMS?

WMS replacement is one of the highest-risk projects in supply chain operations. The WMS controls every physical movement in the warehouse — every receipt, every pick, every shipment. A failed WMS migration stops the warehouse. The migration timeline for a mid-size operation (50,000–200,000 SKUs, 5–15 trading partners) is typically 6–12 months, and the risk of operational disruption during cutover is significant enough that many companies delay replacement for years, absorbing the operational pain rather than accepting the migration risk.

Building alongside Körber addresses specific pain points without touching the core transaction engine. A real-time dashboard doesn't change how Körber processes inventory — it adds a visibility layer. Integration middleware doesn't change Körber's internal data model — it standardises the connections. EDI automation doesn't replace Körber's EDI processing — it wraps it in a manageable interface. Each build reduces operational pain incrementally, without the risk of a full WMS replacement.

Madgeek builds custom software for warehouse and supply chain operations alongside Körber, Manhattan Associates, Blue Yonder, and other WMS platforms. Discovery calls are 30 minutes. For a complete map of where every supply chain platform stops: the supply chain software gap map. For related reading: custom ERP development.