# Frankenstack A Frankenstack is a fragmented retail technology landscape made up of disconnected systems. Discover how EVA helps retailers kill the Frankenstack by replacing complexity with one unified commerce platform that connects the entire retail operation. *defy legacy* # The Franken­stack® A Frankenstack is a retail tech stack built from disconnected point solutions. Most retailers have built their tech landscape in layers: systems added over years, vendors that don't talk to each other, integrations nobody fully understands. That's a Frankenstack. EVA replaces the complexity with one connected commerce platform. --- *The definition* ## What is a Frankenstack? A Frankenstack is a retail technology environment built up over years of tactical decisions: legacy systems, point-to-point integrations, and bolt-on solutions that were never designed to work together. The result is a fragile, expensive architecture where every change risks breaking something else, data lives in silos, and real-time visibility across channels is structurally out of reach. It's the single biggest reason retailers can't deliver [unified commerce](https://newblack.io/eva-platform/unified-commerce). Inventory accuracy, order orchestration, and consistent customer experiences all depend on a coherent data model. A Frankenstack doesn't have one. **A Frankenstack isn't a foundation to build on. It's a constraint to replace.** --- *What we did* ## We gave retail’s biggest problem a name Retail technology doesn’t become complicated overnight. It happens one system, one integration and one workaround at a time. And eventually, the stack becomes impossible to untangle. We called that problem the Frankenstack and registered the term as a [European Union Trademark](https://euipo.europa.eu/eSearch/#details/trademarks/019227705) so retailers could put a name to the complexity they have been living with. A shared name creates a shared conversation. And a shared conversation makes change possible. **We are here to make that change happen by replacing the Frankenstack, not adding to it.** --- *Kill the Frankenstack* ## Defy Legacy and Embrace Change with the EVA platform In 2015, we founded New Black with a simple belief: retail should not be held back by its technology. The Frankenstack was making businesses more complex, fragmented and difficult to evolve. Our mission was clear: unify retail on one platform and give retailers the freedom to focus on their customers. That’s where EVA was born. --- > With EVA, we replaced a fragmented retail setup with one unified commerce foundation, transforming POS, loyalty and fulfilment across 1,000+ stores in months, not years. > > — KIKO Milano, 1,000+ stores in 25 countries ![KIKO Milano store associate helping customer using EVA mPOS](https://cdn.sanity.io/images/zr9y60d3/production/68995be195cf76d43a05f839048064bce4f79671-1376x979.png) --- *The path forward* ## From Frankenstack to Unified Commerce The answer isn't more integrations. It's a platform where inventory, orders, customers, and commerce run on one shared data model, in real time, across every channel. ![EVA Checkout App on iPad](https://cdn.sanity.io/images/zr9y60d3/production/e699f5e2a283fd87c046bfe4337e9de30ea09fe7-1536x864.png) *Unified data model* ### One source of truth across every channel In a Frankenstack, customer records, inventory positions, and order data exist in separate systems. EVA replaces this patchwork with a single data layer where every channel reads from and writes to the same information simultaneously. [Explore Unified Commerce](https://newblack.io/eva-platform/unified-commerce/) ![Inventory](https://cdn.sanity.io/images/zr9y60d3/production/c528764710f99d5b42b4db538317b29014a958bb-1536x864.png) *Real-time inventory* ### Visibility across every store and warehouse Batch syncs and nightly jobs leave your inventory data hours behind reality. EVA's Inventory 360 gives you live stock positions across warehouses, stores, and distribution, enabling ship-from-store, endless aisle, and accurate click & collect without manual reconciliation. [Explore Inventory 360](https://newblack.io/eva-platform/inventory-360/) ![Person delivering on bike](https://cdn.sanity.io/images/zr9y60d3/production/4cad5c258a4b1b3b623076ae3c7ce7f3d31d23e2-1536x864.png) *Order orchestration* ### Route every order to the right fulfilment point A Frankenstack makes order orchestration brittle: every flow is custom-engineered, every edge case a potential failure. EVA's OMS routes orders across ecommerce, stores, and fulfilment networks from one rule-based layer, with no bespoke integration work required. [Explore Order Management](https://newblack.io/eva-platform/order-management/) ![City skyline](https://cdn.sanity.io/images/zr9y60d3/production/8ec42840179281dc639e303c8df54f9533fb32bc-1536x864.png) *Global compliance* ### Expand into new markets without rebuilding In a Frankenstack, each new market adds more systems and local workarounds. EVA includes built-in fiscalisation and digital tax reporting across 45+ countries, so compliance is embedded in every transaction, not bolted on afterwards. [Explore Compliance](https://newblack.io/eva-platform/compliance/) --- *From phased migration to full switch* ## Replace the Frankenstack on your terms - ![OMS](https://cdn.sanity.io/images/zr9y60d3/production/c47fae286bcbfcd04e5ea7b9210e9c52b4be9862-1080x1536.png) — **Order Management** - ![Mobile POS](https://cdn.sanity.io/images/zr9y60d3/production/2c07e3d13f290a5999bca3516effb04dc0b211ae-1080x1536.png) — **POS & Mobile POS** - ![Inventory](https://cdn.sanity.io/images/zr9y60d3/production/53f6bf3773e2b38fdd4532fe47db2e007594ef4b-1080x1536.png) — **Inventory 360** - ![Clienteling](https://cdn.sanity.io/images/zr9y60d3/production/aa3fe07984da363e59b0b5a762fce2e71e791134-1080x1536.png) — **Clienteling** - ![EVA Loyalty App](https://cdn.sanity.io/images/zr9y60d3/production/3c74250c9a9993c5b35899cba1cc876abf0747bb-1080x1536.png) — **Loyalty Engine** - ![EVA Promotions](https://cdn.sanity.io/images/zr9y60d3/production/0ab374406cb51b60317126b72f1926f6af4b3f8a-1080x1536.png) — **Promotion Engine** - ![headless commerce](https://cdn.sanity.io/images/zr9y60d3/production/f6868187cb8c20996ff11ed0c39ee80e0ee876cc-1080x1536.png) — **Headless Commerce** --- *FAQ* ## Understand the problem before you replace it ### What is a Frankenstack? A Frankenstack is a retail tech stack built from disconnected point solutions added over time, without a unified architecture. The result: tools that don't share data, create operational silos, and break when any single integration fails. In practice, this means a POS, ecommerce platform, OMS, and loyalty tool chosen independently and held together by custom integrations nobody fully owns. The Frankenstack is a registered EU trademark (EUIPO #019227705) coined by New Black. ### What does a Frankenstack look like in practice? The clearest signs: inventory that differs between your store and webshop, an IT team spending more time maintaining integrations than building capabilities, and customer data living across systems that can never be fully reconciled. If launching click and collect required a custom project, or if your teams work around the systems rather than with them, you have a Frankenstack. ### Who coined the term Frankenstack? New Black coined the term in Amsterdam in 2015, after seeing the same fragmented architecture pattern across every major retail implementation they worked on. The name references Frankenstein's monster: something assembled from parts that were never designed to work together. New Black holds the registered EU trademark (EUIPO #019227705, Class 42). ### Is Frankenstack a registered trademark? Yes. Frankenstack is a registered EU trademark owned by New Black B.V., filing number EUIPO #019227705, Class 42 (Software services). The trademark is active. New Black registered it to establish ownership of the concept and ensure consistent use across the industry. ### What is the difference between a Frankenstack and a composable commerce platform? A Frankenstack grows without a plan: systems added for individual problems, connected through point-to-point integrations, never reconciled into a coherent whole. A composable commerce platform is built on a unified data model where capabilities share data natively. The difference is not the number of systems but the presence or absence of that shared data layer. Frankenstacks accumulate complexity; composable platforms are designed to contain it. ### How do you fix a Frankenstack? The only durable fix is replacing it with a platform that has a unified data model at its core. Adding middleware or an API gateway reduces friction but doesn't eliminate the root cause: independently managed systems with separate data models. Those layers add cost, latency, and new failure points. Retailers on EVA have consolidated POS, OMS, inventory, and ecommerce onto one platform, either all at once or starting with the most painful capability. ### Can you just add an integration layer or middleware to fix a Frankenstack? No. Middleware patches friction; it doesn't fix the structure. When systems have separate data models, an integration layer still translates and synchronises between them, introducing latency, failure points, and maintenance overhead. Every vendor API update or new system added means the integration layer needs updating too. The only fix is consolidating onto a platform where no translation is needed in the first place. ### What is the business cost of running a Frankenstack? Direct costs include integration maintenance, overlapping vendor licensing, and IT time keeping connections alive. Indirect costs are often larger: slower time to market because every new feature needs an integration project, missed revenue from capabilities like endless aisle that aren't viable on a fragmented stack, and teams spending their time working around systems. Technical debt in a Frankenstack isn't just a technology cost. It's a human one. ### How long does it take to replace a Frankenstack? Retailers on EVA have gone live at enterprise scale in under 12 months, including deployments across more than 1,200 stores in multiple markets. EVA's unified architecture removes most of the custom integration work that extends traditional timelines, since POS, OMS, and inventory already share one data model. Both phased and all-in approaches work. The right starting point is whichever part of the Frankenstack is causing the most immediate friction. ### Why can't you just optimize a Frankenstack instead of replacing it? Optimisation works when the architecture is sound. A Frankenstack's problems are structural: the systems were never designed to share data, and no amount of tuning changes that. You can improve individual components, but you cannot give a fragmented stack a unified inventory position, a shared customer record, or real-time cross-channel visibility. Those require a coherent data model that a Frankenstack doesn't have. At some point, the only decision that resolves the problem is a structural one.