IBM WebSphere Commerce — now technically rebranded as HCL Commerce following HCL Technologies' acquisition of the product from IBM in 2019 — remains one of the most widely deployed enterprise B2B and B2C e-commerce platforms in the world, with a particularly large installed base in retail, manufacturing, and distribution organisations that built their digital commerce operations on WebSphere Commerce V7 and V8. WebSphere Commerce's architecture — the Commerce Server (WebSphere Application Server-based), Commerce database (IBM DB2 or Oracle Database), Search Server (IBM WebSphere Commerce Search, Solr-based), and the Management Centre and Accelerator front-end tooling — represents a significant institutional investment in customisation, integration, and content management configuration that cannot be migrated to a new platform without a full re-commerce programme.
The ownership transition from IBM to HCL created a support complexity that many WebSphere Commerce customers have navigated poorly: IBM continues to support WebSphere Commerce V7 and V8 under Passport Advantage for organisations that remained on IBM support contracts, while HCL provides support for V9 and the new HCL Commerce V9.1 platform for customers who took the HCL migration path. Third-party support on IBM WebSphere Commerce V7, V8, and V9 cuts annual support costs by 50–65%, removes all migration pressure from both IBM and HCL, and preserves your proven commerce platform while you evaluate any replatforming on your own commercial and operational timeline — not IBM's or HCL's.
Running IBM software? Third-party support cuts IBM costs by 50–90%. Free cost analysis, no obligation.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
IBM WebSphere Commerce V7 (7.0.x) reached End of Support in September 2020 — IBM no longer provides patches, fixes, or security updates. IBM WebSphere Commerce V8 (8.0.x) reached End of Support in September 2022. V9 (9.0.x, now HCL Commerce) transitions customers to HCL support contracts. For any organisation on WebSphere Commerce V7 or V8 still on IBM support, the support has already ended — TPS is the only viable structured support option available. See our IBM TPS complete guide for IBM's Passport Advantage lifecycle framework.
HCL Commerce V9.1 and Replatforming — The Total Migration Cost IBM and HCL Don't Quote
HCL Commerce V9.1 — HCL's current strategic platform — is a containerised, Kubernetes-based redesign of the WebSphere Commerce architecture. The migration from WebSphere Commerce V7 or V8 to HCL Commerce V9.1 is not an upgrade. It is a full re-implementation of the commerce platform with a fundamentally different deployment model, a React.js-based Emerald or Sapphire storefront replacing the Madisons and Aurora JSP-based storefronts, and a microservices-oriented transaction service architecture replacing the WebSphere Commerce monolithic application server model.
For a large B2B or B2C retailer on WebSphere Commerce V7 or V8 with a heavily customised storefront (10,000–40,000 lines of custom JSP, custom commands, custom REST handlers, and custom Management Centre extensions), the migration to HCL Commerce V9.1 requires: full storefront re-development in React.js Emerald/Sapphire framework (V9.1 storefronts are not JSP migrations — they are complete front-end rebuilds); transaction service customisation migration to HCL's V9.1 custom service framework; Search (Solr) configuration and index schema migration to V9.1's Search V2 framework; HCL Commerce DevOps toolchain (OpenShift/Kubernetes deployment, Helm chart configuration, CI/CD pipeline) setup and team training; re-integration of all ERP, OMS, PIM, and payment gateway integrations against V9.1 REST API endpoints (which differ from V7/V8 command-based integration patterns); and full regression testing of all commerce business processes. System integrator estimates for a full V7/V8-to-V9.1 migration consistently range from £1.5M–£5M for a complex B2C retail implementation, with 18–36 month delivery timelines. GoVendorFree IBM TPS replaces that with a fraction of the annual maintenance cost.
IBM WebSphere Commerce Version Matrix — TPS Eligibility
| Version | Platform / Architecture | IBM/HCL Support Status | TPS Available |
|---|---|---|---|
| WebSphere Commerce V6 (6.0.x) | WAS 6.x, DB2/Oracle, JSP storefront (Madisons theme) | End of Support — Sep 2016 | ✓ Yes — TPS only viable support |
| WebSphere Commerce V7 (7.0.x) | WAS 7/8, DB2/Oracle, Aurora storefront, REST APIs (early) | End of Support — Sep 2020 | ✓ Yes — large TPS cohort |
| WebSphere Commerce V8 (8.0.x) | WAS 8.5.5, DB2/Oracle, Management Centre V8, SOA APIs | End of Support — Sep 2022 | ✓ Yes — ideal TPS candidate |
| WebSphere Commerce V9 (9.0.x) | Docker-ready, React starter store (early), HCL transition release | HCL Commerce — HCL support | ✓ Yes — TPS available |
| HCL Commerce V9.1.x | Kubernetes/OpenShift, React Emerald/Sapphire, microservices | Active HCL support | ✓ Yes — TPS available |
GoVendorFree TPS Coverage for IBM WebSphere Commerce
GoVendorFree's IBM TPS covers the complete WebSphere Commerce stack — Commerce Server, Search Server, database layer, and integrations. Coverage includes:
- Commerce Server Core (WAS-based): WebSphere Application Server 7.x/8.5.5 hosting stability for Commerce; Commerce Server configuration (WCND) stability; Commerce Transaction Server stability; wcs-bootstrap and EJB deployment advisory; Commerce cluster configuration (WAS cluster for Commerce Server HA) advisory; Commerce JVM tuning (heap, GC policy, thread pool) advisory; Commerce database connection pool advisory (DB2 and Oracle)
- Storefront and Presentation: Aurora and Madisons JSP storefront stability; Commerce Starter Store (V9.x React) advisory; custom Command Framework (AbstractECAction, AbstractECTargetableCommand) advisory; Commerce REST API (V7/V8 BOD REST) stability; custom Widget and Layout Editor advisory; Commerce Preview application stability; B2B contract and B2B account management UI advisory
- Commerce Database Layer: IBM DB2 UDB Commerce schema stability advisory; Oracle Database Commerce schema advisory; Commerce database migration script advisory (within supported version range); MEMBER/ORDPAYINFO/ORDERS Commerce core table advisory; Commerce scheduled job (JobStatusCmdImpl) advisory; Commerce messaging (WebSphere MQ integration) advisory
- Search (Solr) Server: WebSphere Commerce Search (NuSolr / Solr) stability; Solr index configuration and schema advisory; Commerce search profile and indexing job advisory; TypeAhead and search relevance tuning advisory; Solr cluster configuration for Search HA advisory; index rebuild and delta-index scheduling advisory
- Payment and Order Management Integration: Commerce Payment Rules Framework advisory; CyberSource, Adyen, Worldpay, Stripe WebSphere Commerce integration advisory; Order Management System (OMS) integration advisory (IBM Sterling OMS, Manhattan, Oracle OMS); ERP integration (SAP, Oracle EBS) for order and inventory advisory; PIM integration advisory
- Security and Compliance: HTTPS/TLS configuration for Commerce Server and Storefront; IBM Tivoli Access Manager / Security Access Manager integration advisory; Commerce user registry (LDAP/AD) integration advisory; PCI DSS scope advisory for WebSphere Commerce environments; GDPR/PECR cookie consent and data subject rights advisory for Commerce customer data
Retail and B2B Distribution — WebSphere Commerce TPS Cohort
IBM WebSphere Commerce's two dominant TPS cohort sectors — multi-channel retail and B2B distribution — each face migration complexity and operational constraints that make TPS the financially rational choice.
In multi-channel retail, WebSphere Commerce V7 and V8 powers many established UK and European mid-market retailer digital commerce operations — department stores, fashion and apparel retailers, home and garden retailers, and specialist retailers who built their online channels in the 2010–2018 period on WebSphere Commerce as the enterprise-grade alternative to Magento and Hybris. These environments are typically deeply customised: bespoke pricing logic, custom promotions engine extensions, multi-language and multi-currency configurations for cross-border trading, and custom fulfilment and click-and-collect integrations with OMS and WMS platforms. The operational constraint during peak trading windows (Black Friday through Christmas) creates a firm change freeze that makes any replatforming project a multi-year planning cycle — which TPS supports far more cost-effectively than IBM/HCL standard support. See our retail industry practice for the WebSphere Commerce TPS framework.
In B2B distribution and manufacturing, WebSphere Commerce underpins B2B self-service portals where contract pricing, customer account management, EDI order integration, and complex product catalogue management are embedded over years of Commerce B2B contract configuration. IBM WebSphere Commerce's B2B capability — buyer approval workflows, contract-based pricing, account hierarchy management, and purchase order requisition integration — represents institutional configuration investment that a migration to a SaaS commerce platform (Salesforce Commerce Cloud, Shopify Plus, SAP Commerce Cloud) cannot preserve without full re-implementation of B2B business logic. Our manufacturing industry practice covers the B2B distribution WebSphere Commerce TPS framework.
The IBM Passport Advantage ELA unbundling dimension is also relevant for WebSphere Commerce TPS decisions. Many organisations hold WebSphere Commerce licences within an IBM ELA that also covers WebSphere Application Server, IBM DB2, IBM MQ, and other IBM middleware components. GoVendorFree's IBM Passport Advantage advisory provides an ELA unbundling analysis that isolates the Commerce component licence cost and identifies which IBM Passport Advantage components can be exited or replaced alongside TPS adoption — creating a combined saving across the IBM middleware estate rather than a single-product cost reduction.