Commerce platforms shouldn’t own your revenue logic

Most B2B commerce stacks follow the same pattern:

Commerce platform handles:

• Catalog

• Cart

• Checkout

• Basic pricing logic

ERP handles:

• Pricing records

• Contracts

• Credit

• Fulfillment

• Financial posting

Then integration and orchestration layers try to stitch it together.

The result:

• Synchronous ERP calls at checkout

• Pricing duplication across systems

• Fragile integrations

• Slow performance

• Upgrade anxiety

• Customizations that compound over time

Commerce becomes tightly coupled to ERP behavior.

Change becomes coordination.

viax as the commerce backend

viax can sit behind any commerce experience — bespoke front-end, open source framework, composable commerce, marketplace channel — as the governed execution layer.

Commerce becomes the experience layer.

viax becomes the execution backend.

ERP remains the system of record.

This separation changes everything.

Commerce calls viax for:

• Price determination

• Eligibility validation

• Discount stacking

• Approval routing

• Contract enforcement

• Entitlement generation

• Credit validation

• Lifecycle state transitions

ERP is invoked only when:

• Orders are finalized

• Financial records are posted

• Inventory is adjusted

• Compliance records are required

Execution is externalized.
ERP stays stable.

A unified pricing engine across channels and systems

Most enterprises don’t have a pricing problem.
They have a pricing distribution problem.

Pricing logic lives:

• Partly in ERP

• Partly in CPQ

• Partly in commerce

• Partly in spreadsheets

• Partly in integration code

viax centralizes pricing determination into a single engine.

Capabilities include:

• Multi-tier discount stacking

• Contract-specific overrides

• Regional price logic

• Volume and usage-based pricing

• Bundle-aware pricing

• Customer- and partner-specific pricing

• Promotional logic

• Approval-triggered pricing thresholds

• Real-time eligibility checks

All modeled once.
Invoked across:

• B2B commerce

• Inside sales portals

• Dealer portals

• Marketplace channels

• Agentic AI interfaces

• APIs

One determination engine.
Multiple channels.

Real-world pricing complexity without ERP customization

ERP pricing engines were built for structured, static pricing models.

Modern B2B revenue models include:

• Hybrid hardware + subscription bundles

• Usage-based tiers

• Trial-to-paid transitions

• Entitlement-based pricing

• Multi-party cost allocation

• Regional compliance constraints

• Channel-based incentives

• MRO and procurement-specific flows

Embedding this logic in ERP increases customization and upgrade risk.

Embedding it in commerce duplicates logic.

Embedding it in integrations creates drift.

viax models pricing and policy explicitly — outside ERP — so complexity is governed without destabilizing core systems.

Multi-ERP and post-M&A environments

M&A introduces structural fragmentation:

• One business line on SAP

• Another on Infor

• Acquired company on Oracle

• Legacy AS/400 still running core orders

Traditional options:

• Force ERP consolidation

• Duplicate commerce stacks

• Build complex integration meshes

• Live with pricing inconsistency

viax provides a unified execution layer across heterogeneous ERPs.

Commerce calls viax.
viax determines outcomes.
viax routes to the appropriate ERP based on context.

Benefits:

• Consistent pricing across business units

• Unified customer experience

• Reduced integration complexity

• ERP migration optional, not urgent

• Simplified carve-outs and divestitures

You don’t need ERP consolidation to achieve pricing consolidation.

Execution outside ERP is not anti-ERP

Externalizing pricing and revenue execution does not replace ERP.

It protects it.

ERP should:

• Record transactions

• Enforce financial controls

• Manage inventory

• Support compliance

• Maintain audit trail

ERP should not:

• Own real-time determination logic

• Coordinate cross-system lifecycle state

• Serve as the runtime engine for commerce experiences

Separating execution reduces ERP blast radius.

Upgrades shrink in scope.
Customizations decrease.
Change becomes model-driven.

Commerce becomes composable. Pricing becomes deterministic.

When viax operates as the commerce backend:

• Front-end teams build freely

• AI agents invoke governed pricing

• Channels share a common execution core

• Multi-ERP landscapes simplify

• M&A integration accelerates

• Pricing changes become model updates, not ERP projects

Stop duplicating pricing logic.

Model it once.

Execute it everywhere.

Let ERP record the outcome.