Columbia Games / 29 September 2026
CCM v2: a dedicated retailer catalog and Net 30 checkout without mixing release scopes
The CCM v2 retailer release introduced controlled product access, a validated wholesale shopping cart and Net 30 payment terms, while keeping the separate WordPress catalog migration outside its deployment scope.
Situation
Consumer and retailer purchasing are not the same business process. Product visibility differs, payment methods differ, and a cart must not retain items that a customer is no longer allowed to order. The related WordPress catalog cutover had its own release constraints and could not safely be bundled into the new CCM v2 feature.
Approach
We built a B2B product catalog with permission-based visibility, cart sanitization and a checkout branch that offers Net 30 only to eligible retailers. Legacy payment fields, migration order and UAT scenarios were documented. We removed WordPress cutover scripts and CI dependencies from the CCM release so that the new commerce features could be tested and deployed independently.
Outcome
The retailer ordering flow was delivered through CCM v2 and promoted using the production release process. Functional checkout and migration checks succeeded; the broader Lighthouse gate was not fully green, so we did not present it as complete performance validation.