Blog

Peak season does not break the storefront. It breaks the seam between the storefront and the ERP. This is a Q4 readiness guide for B2B distributors running Adobe Commerce or Magento against Epicor Prophet 21, Dynamics, NetSuite or Infor. It covers the ERP integration failures that only show up under load - stale stock, wrong contract pricing, orders that never reach the ERP, sync jobs that quietly fall behind - and what you can still fix in the weeks left before Black Friday 2026.

To hide a payment method at Magento 2 checkout you change the answer the method gives when Magento asks whether it can be used, not what the checkout renders. That answer comes from the can_use_checkout handler in the payment method's ValueHandlerPool. Here is the full availability chain, the config value object that belongs in it, the unit test around it, and why a layout override or a JS mixin only hides the button while leaving the method selectable. Applies to Magento Open Source 2.4.6 through 2.4.9, Adobe Commerce and Mage-OS.

Adobe Commerce ships a B2B order approval workflow on the paid tier. Magento Open Source and Mage-OS do not, so anyone who needs one has to build it. This guide walks the six decisions a Magento 2 B2B order approval workflow forces on you: how to flag an account as approval-required, how to replace the payment step at checkout, how to hand the cart to an approver, how to bring the finished order back without breaking totals, what happens to discounts and free gifts on the round trip, and what to do when an approver says no. Applies to Magento Open Source, Adobe Commerce and Mage-OS, versions 2.4.6 through 2.4.9.

Your Magento store will not shut down when Adobe support ends. But after the August 11, 2026 end of support for Magento 2.4.5 and 2.4.6, security patches stop, PCI DSS compliance gets hard to defend, and the eventual upgrade grows every month you wait. Here is what actually happens after Magento end of life, and the three honest ways out: upgrade to 2.4.8 or 2.4.9, move to Mage-OS, or replatform. Applies to Magento Open Source, Adobe Commerce, and Mage-OS builds.

We build payment gateway modules from scratch for Magento Open Source, Adobe Commerce and Mage-OS, and maintain them for years: our longest-running integration has shipped eleven releases across five years, including a migration onto the provider's API v2.0. This is what that work actually involves. Who needs a custom payment module, what a module has to do beyond calling the API, the six places payment integrations really fail (order-flow timing, webhook trust, guest checkout, multi-store scope, double submission, email timing), how Magento Open Source, Adobe Commerce and Mage-OS differ in practice, how Shopify, WooCommerce and OpenCart change the problem, and how to tell whether a module is genuinely maintained.

On June 24 Shopify told merchants it no longer supports the sale of e-cigarettes and gave them until July 8 to remove the listings. Reuters reported it, Shopify confirmed it, and stores started disappearing. Here's what's actually confirmed, what's still unanswered, and why the mechanism behind it should interest you even if you've never sold a vape: on a hosted platform, your catalog lives inside someone else's acceptable use policy. Self-hosted Magento and Mage-OS trade that away, with honest limits.