OMS layer before vendor pitch.
Forrester Wave Leader for order management — rarely the right path in the DACH B2B mid-market. In under 15 percent of mid-market setups does Fluent beat native platform OMS in Spryker or SFCC. The other 85 percent pay for a layer that their complexity never activates. We assess honestly before that layer enters the stack diagram.
Three data points on market reality — not a dismissal of the platform, not a recommendation against it. Fluent is a legitimate Forrester Leader in international retail. In the DACH B2B mid-market, the question is not whether Fluent is good, but whether you carry the distribution complexity that makes Fluent worthwhile.
Fluent Commerce has been in the Leader column for order management since Forrester Wave Q2 2023 — shoulder to shoulder with Manhattan Active Omni and IBM Sterling OMS. Platform substance is not in question. The question is not platform quality but use-case fit.
Source: Forrester Wave: Order Management Systems · Q2 2023As of 2026: fewer than five implementers with a dedicated Fluent delivery organization in DACH. The Lünendonk OMS top 10 does not list Fluent. Established partners (Pivotree, Intellias, Ignitiv) are international with no dedicated DACH office. Those using Fluent in DACH build nearshore delivery chains or bring in senior architecture from abroad. Implementer risk is real, not theoretical.
Source: Lünendonk OMS study 2024/2025 · Industry research FatUnicornPublicly communicated Fluent cases are 70 to 75 percent retail/fashion setups with BOPIS, Click and Collect, and Ship-from-Store as core levers. B2B industry accounts for an estimated under 15 percent. The platform data model comes from this use-case cluster: account hierarchies for corporate-subsidiary-buyer hierarchies are either custom-built in DACH B2B setups or "in development".
Source: Fluent public case studies · Forrester OMS market structuresMulti-location inventory with decentralized stock, availability as a commercial promise (same-day, Click & Collect, premium SLA), drop-ship scale that structurally overloads native platform logic. That is where the OMS layer pays off.
Central warehouse, ERP-driven stock availability, linear order pipeline. Native OMS components in Spryker or SFCC suffice. Fluent would be license costs plus custom rules DSL plus implementer risk without clear leverage.
Four triggers, four numeric thresholds. Those who cross at least three have an OMS selection conversation — probably, but not necessarily, with Fluent. Those who cross none build out native platform OMS and skip the layer.
Three or more fulfillment locations with real stock (warehouse, branch, drop-ship vendor). Available-to-promise as a commercial contractual commitment, not "roughly so". Platform stock logic, linear and centrally scaled, no longer works here — the OMS layer carries the distribution reality.
Ten or more external suppliers in the order pipeline, each with their own interfaces, stock snapshots, and shipping SLAs. Order splitting and multi-vendor routing is daily business, not an edge case. Native platform OMS breaks at this point. The OMS layer orchestrates.
Click & Collect, Ship-from-Store, Return-to-Any-Store as commercial reality, not a pilot project. The branch is a fulfillment node with its own stock and its own SLA. Rare in the DACH B2B mid-market, but when it applies, a load-bearing lever on conversion and service perception.
Order routing decision weighs shipping cost, SLA commitment, stock scarcity, and ideally CO2 footprint simultaneously. When routing rules are not statically mappable via if-else but score-based via a custom rules DSL, then the OMS layer is not a luxury — it is an architecture decision.
Three patterns from real OMS selection sparring mandates — not implementer horror stories, but platform realities that don't come up in the vendor demo but surface at the latest in the architecture workshop.
Fluent's routing engine works via a proprietary rules DSL: powerful in capability, steep in learning curve. Those sold "no-code OMS" discover in the first architecture workshop that every non-trivial routing rule is a mini engineering project. Lock-in comes from the DSL: migration to another OMS layer would mean logic rebuild, not configuration export.
Fluent's platform data model comes from retail/fashion. DACH B2B-typical account hierarchies (corporate → subsidiary → site → buyer with Approval-Workflows and contract-based pricing) are not a platform default. Those who ask in the demo hear "in development" or "mappable via custom rules". Both mean: re-implementation investment, not configuration investment.
Standard retail implementation in Fluent is significantly lighter than B2B industry with custom account hierarchies plus ERP integration. DACH implementer footprint is thin, senior architecture skill frequently comes from abroad, discovery effort is higher than with Spryker or SFCC. Risk margin is considerably larger than the vendor demo suggests.
Those who assume "no-code OMS out-of-the-box" and get "DSL engineering plus DACH implementer bottleneck" lose the business case. Frame reset belongs before the RFP, not at cutover.
OMS selection is not a license conversation — it affects logistics, inside sales, IT architecture, and sales. We sit down with those who after the introduction will work with routing rules, availability commitments, and drop-ship SLAs, not the vendor selling the platform and not the implementer earning on every DSL rule.
What we build should make the daily work of the people who use it more pleasant and more productive. We automate repetitive routine wherever we can, so your people get time back for what really matters: decisions, relationships, creativity. Systems are tools, not the point.
Your people sit at the table, not in the recipient seat. Decisions emerge jointly, with data and at eye level. No consultant black box, no hidden playbook. What we think, we think out loud and with you.
We train your teams while we work, methods, tools, decision frameworks. Handover point is clearly defined: from there your in-house organisation carries it alone. When you don’t need us anymore, we’ve done our job right.
24+ Jahre IT-Background gebündelt im Team — 14 Jahre davon in B2B-Commerce. Architektur-Cases bei Großkonzernen, Aufbau und Steuerung verteilter Expertenteams über mehrere Zeitzonen hinweg, technologie-agnostische Projektrettung. Schwerpunkte: Plattform-Architektur, Projektrettung, Team-Operations — technologie- und vendor-agnostisch.
Chris Zepernick
Implementers earn when the system gets built. Resellers earn on the license. We earn on sparring — and we win that not through pitches but through honest assessment. If the four triggers don't hold, we say so. Even when the mandate then means "build out native OMS in Spryker" and continues without us.
How we workWorked through the four triggers, hit three or more? Or is it a gut feeling that the OMS layer won't carry? A few minutes on the phone and we'll sort out honestly whether Fluent fits your setup, or whether Spryker or SFCC native OMS is the better choice.
