The B2B e-commerce iceberg: 5 cracks beneath the surface

A few months ago we hosted Jason Greenwood — founder of Greenwood Consulting, one of the most followed voices in B2B eCommerce internationally and host of an industry podcast with hundreds of episodes — for a live session dedicated to a topic that comes up in every conversation we have with our industrial clients: what does an Ecommerce Experience Platform really need to manage enterprise B2B, and why does so much of the market narrative tell a different story from operational reality.

A few weeks later, Greenwood published an analysis that sparked considerable debate across the eCommerce ecosystem: an argument as provocative as it is well-documented on why Shopify Plus B2B, despite years of investment around features like company profiles, price lists and B2B checkout, remains structurally unsuited to enterprise complexity.

We found his framework so precise in describing the problem that it's worth revisiting here — not to talk about Shopify again, but to use the same critical lens to explain why Rewix was built from day one with an architecture designed to solve exactly these five cracks.

The iceberg nobody talks about

Greenwood uses an effective image: what a B2B platform shows on the surface — company profiles, price lists, payment terms — is only the visible tip of an iceberg. Below the surface lies the real operational complexity: a contractual pricing engine, multi-tier organizational hierarchies, approval workflows, real-time ERP integration, and product variant management with dozens of interdependent attributes.

It's a distinction we share, though with a fundamental difference in how we approach it. Many platforms built for retail add a B2B layer over time on top of a B2C architecture: the result is almost always a convincing surface that hides a fragile foundation, made of third-party apps and custom-built middleware patching the gaps. Rewix chose the opposite path: building the eCommerce Platform starting from the iceberg, not the tip. The ERP as the system of reference, integration as the backbone, and only afterward the user experience on the surface.

Discover the key challenges in B2B eCommerce projects →

The five cracks, seen by those who build B2B every day

1. The pricing engine isn't a feature, it's an equation

In industrial B2B, price is not "one product, one price." It's a layering of rules — contracts negotiated per individual customer, volume discounts, time-bound validity windows, raw material surcharges, regional promotions — that must be resolved according to a clear priority, a true pricing cascade. A platform with a flat price-list model, no matter how many price lists it supports, rarely has an engine capable of automatically arbitrating between competing rules.

In Rewix, this isn't an add-on to configure later: multiple price lists, conditional rules by customer/channel/role, and bidirectional synchronization with the ERP are the starting point of the data model. When a sales rep updates a contract in the ERP, that price has to show up correctly on the storefront — not "eventually," but because the ERP remains, by design, the single source of truth.

2. Organizations aren't flat (and neither should permissions be)

A junior buyer at a branch office who needs an order approved by a regional manager and then by finance isn't an exception: it's the norm in multi-site organizations. A single-tier company structure, with binary roles between admin and orderer, simply doesn't describe how enterprise customers actually operate.

The answer we look for in Rewix isn't to fake an approval with a checkout workaround, but to treat roles, permissions and product visibility as a native property of the customer's organization, governed together with the ERP system that structure is already mapped in. Complexity doesn't always get resolved in the storefront: often it gets resolved upstream, letting the integration layer carry the organizational truth rather than invent it.

3. Finite variants, infinite configurations

An industrial pump with dozens of interdependent attributes, a unit of measure that changes between order and invoice, a weight-to-pieces conversion that has to happen before the order ever touches the ERP: the industrial catalog rarely lends itself to three sizes and four colors, and a product model built for retail breaks down in the face of this complexity.

Rewix's data model is designed for deep variants and API-callable configurators, precisely because industrial B2B product logic emerges from dependencies between options, not simple size/color combinations.

4. The ERP is the system of record. Full stop.

The point here is simple and non-negotiable: the ERP — SAP, Oracle, NetSuite, Dynamics, or whichever system is installed — is the system of record in enterprise B2B, and the eCommerce Platform is only the engagement layer. The two systems must talk to each other in real time, with resilience, and with the catalog able to remain operational even when the ERP is down for scheduled maintenance.

This is exactly the logic behind how we designed Rewix: API-first integration with procurement and ERP systems, real-time synchronization of stock and lead times, orchestration between PIM, ERP, CRM and suppliers as an infrastructural layer — not as a separate project to refinance every time a requirement changes.

5. When the app ecosystem becomes the problem, not the solution

Once you pass a certain number of third-party apps stitched together to simulate native functionality — quote management, approval workflows, advanced B2B search, multi-warehouse routing — you're no longer managing a cohesive platform. You're managing a fragile, loosely coupled system, with a breaking point, an update cycle and a risk surface for every single piece — exactly the kind of setup an enterprise IT department views with suspicion during a security review.

That's why in Rewix deep integration isn't delegated to a marketplace of independent apps, but remains part of the native architecture, backed by the Zero11 group — with Aiability bringing the AI/data layer whenever extra operational intelligence is needed, not another plugin to maintain and reconcile with everything else.

The real cost of "there's an app for that"

Greenwood effectively flips the pricing conversation: a platform license can look incredibly competitive, but it confuses license cost with total cost of ownership. Once you add up the stack of apps needed to approximate B2B functionality, the custom development for ERP middleware, and the ongoing operational oversight of an architecture made of independent pieces, the math changes dramatically — and it changes precisely in the years when the business should be scaling, not chasing technical debt.

That's why at Rewix we treat deep integration as an upfront investment to design properly, not a cost that quietly accumulates after go-live.

Assess whether your current eCommerce Platform is ready for B2B complexity →

What Shopify Plus does well (and why it isn't our playing field)

It's worth saying this with the same honesty Greenwood writes with: Shopify Plus B2B is a solid choice for a DTC brand opening a wholesale channel, or for a mid-market company with simple pricing and flat organizational hierarchies. That isn't the segment we compete in. Rewix is built for the industrial manufacturer, the distributor with thousands of SKUs and hundreds of customer-specific contracts, the company with multi-site structures and procurement integrations to manage — the same segment that, according to Greenwood, needs platforms architected from the ground up for B2B complexity, not adapted after the fact.

Discover how Rewix unifies B2B Commerce and CPQ for industrial manufacturers →

The questions to ask anyone before you sign

One of the most useful parts of Greenwood's analysis is the list of questions every enterprise buyer should ask before signing a contract. We're repeating them here because they apply to any Ecommerce eXperience Platform — Rewix included, and rightly so:

• How is the conflict between a contracted price, a volume discount and a regional promotion resolved in a live environment, not a static demo — and how does it sync with the ERP when the contract changes?
• Can you see, live, a multi-level company hierarchy with differentiated product visibility and spend-threshold-based approval?
• Is procurement system integration native, or does it require a third-party app — and what does it really cost, maintenance included?
• What happens to the catalog if the ERP goes into scheduled maintenance? Can customers keep browsing and ordering?
• How does the platform handle a product with dozens of configurable attributes and dependencies between options, and what is its native logic for unit-of-measure conversion?

If the answer you get includes phrases like "we can build that" or "there's a partner for this," you already have your answer. It's not a native capability. It's a workaround.

Architecture, not disguise

Greenwood closes his piece by returning to the classic image of the emperor with no clothes: marketing can dress up even a platform that, underneath, doesn't have the architecture to back up the promise. Enterprise B2B can't be improvised with a well-tailored disguise. It's built by deciding, from the very first data schema, which side of the iceberg you want to start from.

This is the conversation we had with Jason in our live session, and it's the same one we keep having every day with clients who come to us after trying — and abandoning — solutions built for something else.