Revenue Execution Revenue Motions AI Execution Resources Schedule a Demo

For AS/400-based ERPs

Modernize
the business. Keep the AS/400.

viax is the governed execution layer that runs pricing, orders, promise dates and ecommerce outside the ERP. The business moves at its own speed, and the AS/400 keeps running it exactly as it does today. Low risk by design.

IBM i · AS/400 · SYSTEM OF RECORD viax · REVENUE EXECUTION ECOMMERCE SALES · CSR EDI · B2B

The AS/400 dilemma

The AS/400 already runs the business. Replacing it is the risky move.

3–5×

Typical timeline overrun for revenue change programs routed through ERP

  1. AS/400 NEW ERP · YEARS AWAY

    Path 01 · Replace

    Replace the ERP

    A multi-year, high-risk program: every motion re-implemented and every record migrated before the business sees a gain.

  2. AS/400

    Path 02 · Customize

    Customize the AS/400

    Every new price rule, channel or approval becomes RPG work for a shrinking team. Each change widens the blast radius.

The architecture

Channels engage. viax executes. The AS/400 records.

IBM i · AS/400 · SYSTEM OF RECORD ITEMS CUSTOMERS INVENTORY AR · GL ADAPTER viax · GOVERNED EXECUTION LAYER PRICING · QUOTE ORCHESTRATION PROMISE DATES TERMS · CREDIT APPROVALS RETURNS ECOMMERCE REPS · CSR EDI AI AGENTS 04030201
  1. 01CHANNELS

    Ecommerce, reps, EDI and AI agents call one governed API, not four point-to-point integrations into the AS/400.

  2. 02viax

    Pricing, orders, promise dates, terms and approvals run as Revenue Motions, in real time.

  3. 03ADAPTER

    A thin connection over DB2 for i, data queues or batch files. No RPG rewrite.

  4. 04AS/400

    Keeps running the business as it does today, with nothing to migrate. Same pattern when it’s one of several ERPs across divisions or acquisitions.

AI reasons. viax executes. ERP records.

What changes

What changes when execution moves outside ERP

Six outcomes for AS/400 shops, without migrating the ERP or putting the core at risk.

  1. 01 Speed

    Change pricing in days, not release cycles

    Contract, tiered and customer-specific pricing live in viax. The business changes rules; the AS/400 keeps its price file.

  2. 02 Speed

    Real-time answers on batch-era data

    Availability, credit and order status stay live in viax and sync to the AS/400 on its cadence. No nightly-job lag.

  3. 03 Control

    Business rules out of RPG

    Logic buried in RPG and tribal knowledge becomes explicit, versioned and auditable, no longer tied to a shrinking team.

  4. 04 Outside ERP

    One execution layer for every channel

    Web, reps, EDI and marketplaces share one set of pricing, promise and approval rules. No green-screen rekeying.

  5. 05 AI

    AI with a governed place to land

    Agents quote, check stock and place orders through deterministic rules in viax, never straight into the AS/400.

  6. 06 Outside ERP

    A future ERP move gets easier

    Pricing, orders and approvals already live in viax, so a future move is a system-of-record swap. The motions keep running.

Two ways to run channels

Behind your channels, or as the channel.

IBM i · AS/400 · SYSTEM OF RECORD ITEMS CUSTOMERS INVENTORY AR · GL viax · ONE SET OF RULES FOR EVERY CHANNEL PRICING · QUOTE ORCHESTRATION PROMISE DATES TERMS · CREDIT APPROVALS RETURNS COMMERCE CRM EDI MARKETPLACES B2B PORTAL DEALER PORTAL CPQ REP ORDERS

Platforms you keep

Your commerce platform, CRM, EDI and marketplaces keep their front end. viax supplies pricing, promise dates, orders and status behind them.

Delivered by viax

B2B customer portals, dealer portals, CPQ and rep order entry, built on viax where no strong platform exists today.

  • One set of rules either way

    Pricing, terms and promise dates are modeled once and served to every channel.

  • Start where the pain is

    Keep the platforms that work. Fill the gaps without buying another platform.

  • Swap channels without touching the rules

    Replace or add a front end later. The Revenue Motions don’t move.

For every seat at the table

One decision. Three ways to read it.

  • 01 · Finance

    No replacement program to fund.

    No multi-year ERP budget and no migration risk on the books. Every revenue change stops becoming a program. Proof before commitment. That’s the deal.

  • 02 · IT & Architecture

    The AS/400 stays stable.

    A thin adapter, no RPG rewrite, and one governed API for every channel. Deterministic execution gives AI a safe place to land.

  • 03 · Revenue & Commercial

    Change at the speed of the business.

    New pricing, terms and channels go live in days, without waiting on ERP release cycles or the RPG backlog.