r/Magento

The June 19 deadline for the new EU withdrawal rule is going to have a mandatory impact. Has anyone heard any updates on their end about potential delays, or is everyone actively updating their B2C and D2C stores across the European-wide market? There are a few other related rules taking effect on June 19 as well.

As we know, in Magento, adding this button is not a simple drag and drop fix. It has to align with everything else in the backend: inventory syncing, invoicing, accounting purposes, reporting, and getting the frontend UI right.

To actually comply, you have to tie a two step form directly into the customer order history, make sure the data handling checks all the GDPR boxes, and trigger an automated receipt email instantly.

I have been mapping out the logic to get this working without disrupting existing setups. If anyone is stuck figuring out the technical architecture for their own store, feel free to drop a comment or send a DM.

Today, running a Magento store means keeping up with high performance, seamless UX, and efficient workflows. Custom Magento extensions help achieve all of that — and more. But to get the most out of them, you need a trusted development partner. Here are the top Magento extension development companies you can rely on. Each has a strong track record and a deep focus on Magento development, so you can confidently choose the right fit for your store.

1. Whidegroup

Whidegroup emphasizes their deep understanding of ecommerce business processes. They don’t just develop websites. Grasping how online sales work, they help merchants build effective business strategies rooted in performance-optimized, user-centric Magento stores. Their approach nurtures long-term growth by aligning store functionality with customer behavior, conversion goals, and operational efficiency.

Main strengths:

• Recognition as an official Adobe Partner
• Custom Magento development services
• A full suite of development services, including audit, design, development, testing, and ongoing support
• High code quality and website performance optimization
• Expertise in Magento 1 and Magento 2 architecture and peculiarities
• Free support period for developed custom solutions

2. Mageplaza

Mageplaza is a globally recognized Magento 2 extension provider with over 200 modules. They offer both free and premium extensions for SEO optimization, user experience, streamlined checkout, and other online store functions. Custom Magento development services are also available.

Main strengths:

• Over 200 third-party Magento 2 extensions
• Custom development services
• Ongoing maintenance and support services for Magento websites

3. BSS Commerce

BSS Commerce is a Vietnam-based Magento development agency recognized for its extensive portfolio of over 150 Magento 2 extensions. Their offerings cater to various ecommerce needs, including B2B solutions, SEO enhancements, checkout optimization, and multi-store management.

Main strengths:

• Strong focus on B2B
• Over 150 Magento 2 extensions covering diverse functionalities
• Custom development services
• Rigorous testing processes

4. Amasty

Amasty is a Magento development company with over 13 years of experience in the ecommerce industry. The company has developed over 300 third-party Magento extensions for various aspects of online retail. Notable products include the Improved Layered Navigation, One Step Checkout Pro, and Elastic Search extensions. Beyond their extensive extension library, Amasty also offers custom Magento development services.

Main strengths:

• More than 300 Magento extensions providing diverse functionalities
• Customization and bespoke development services
• Compliance with Magento’s coding standards
• Dedicated support and maintenance services

5. Dinarys

Dinarys is a European ecommerce development company specializing in Magento development. Dinarys adopts a client-centric approach, emphasizing flexibility and responsiveness in their project management. Customers appreciate their team’s communicative approach and flexibility in adapting to evolving requirements.

Main strengths:

• Bespoke Magento development services
• A wide range of other Magento-related services
• Emphasis on effective communication, flexibility, and responsiveness to client needs

Hi everyone, I wanted to share some insights from a recent Magento migration case study involving Strand Books, the iconic NYC bookstore known as "18 Miles of Books." This project tackled the challenge of transforming a historic physical retailer into a high-performance global digital marketplace managing 4.7 million products. Here’s a breakdown of the key challenges, strategies, and outcomes that might resonate with anyone facing large-scale ecommerce migrations.

Challenge: Managing Scale and Complexity

• Catalog Size: 4.7 million SKUs spanning rare collectibles to new releases.
• Transaction Failures: Database deadlocks during peak traffic caused orders to be charged but not recorded internally, damaging customer trust.
• Discovery Degradation: Complex product editions often lost their detailed formatting during inventory sync windows, confusing customers.
• Integration Friction: Manual overnight syncing between storefront, inventory, and marketing tools led to stock inaccuracies and delayed campaigns.

Revenue Risk: High-profile launches risked site crashes during critical sales windows.

• Strategic Approach: Building Resilience and Real-Time Accuracy
• High-Availability Guardrails: Implemented redundant servers to ensure zero downtime during hardware issues.
• Real-Time Data Pipeline: Centralized messaging system to instantly update inventory and orders across the platform.
• Catalog Batch Optimization: Advanced batch processing to index millions of records without slowing site performance.
• Replay Functionality: Enabled instant restoration of complex product listings if they reverted to basic entries.
• Enhanced Discovery Tools: Added pre-order logic and product badges to guide customers through millions of options.

Execution Highlights: Streamlining Transactions and Alerts

• Intelligent Shipping Logic: Supported mixed carts combining in-store pickup and warehouse shipments seamlessly.
• Financial Data Integrity: Immediate invoice generation for gift card transactions eliminated tax and shipping discrepancies.
• Proactive Alerting: Automated internal notifications for transaction failures allowed issues to be resolved before customers noticed.

Business Value Delivered

• Operational Stability: Shifted from risky manual syncs to 24/7 automated data integrity.
• Infrastructure Resilience: With Cloudflare shielding and a 15-year SSL certificate, the site handles traffic spikes without performance loss.
• Revenue Growth: Supported complex subscription models and high-visibility pre-order campaigns reliably.
• Tax & Compliance Precision: Automated tax exemption handling achieved penny-perfect financial reporting.

Takeaways for Executives Considering Magento Migrations

1. Prioritize architectural resilience to prevent transaction failures that erode customer trust.
2. Real-time data synchronization is critical for large catalogs to maintain accurate inventory and discovery.
3. Automate alerting to move from reactive firefighting to proactive issue resolution.
4. Invest in user experience enhancements like product badges and pre-order logic to help customers navigate complexity.
5. Ensure financial processes handle edge cases like gift cards to avoid costly discrepancies.

Would love to hear from others who have managed large-scale migrations or complex catalog challenges. What strategies worked for you to maintain stability and customer experience during the transition?

I noticed a high authority e-commerce site that ranks in top 7 serp results for its niche running a magento store is getting none of its unsponsored Google shopping listings presented compared to stores running Shopify. New sites that are barely 3 years old and have low serp positioning are having their products in the free shopping ads section in the serps page and in the shopping page.
The magento site is running mirasvit advanced product feeds and has valid products in magento center but just keeps getting beat by smaller less popular stores.

Of course I even see product pages from these Shopify stores now many times beating the magento stores.

The magento store has more overall traffic, more extensive product descriptions etc.

I am starting to question whether there is outright preference for the feed generated by Shopify stores for visibility in Google Shopping Ads.

I would appreciate input from the magento community members.

Thank you in advance.

Released yesterday, May 12, 2026, this version is a foundation release designed to purge a decade of tech debt. It is a strategic migration, not a routine patch.

Here is the fluff-free technical breakdown.
🔧 Platform requirements 
PHP 8.4 / 8.5 — PHP 8.3 support dropped
MySQL 8.4 LTS — MySQL 8.0 dropped
MariaDB 11.4 LTS — MariaDB 10.6 dropped
OpenSearch 3.x — index format changes from 2.x, reindex likely
RabbitMQ 4.1 or ActiveMQ Artemis 2 (new option)
Valkey 8, Varnish 7.7, Nginx 1.28, Composer 2.9

🔐 Security & API
CAPTCHA/reCAPTCHA now properly enforced on REST and GraphQL account creation (this was a long-standing gap)
2FA: admins only need to configure ONE enabled provider
Configurable admin password minimum length (PCI DSS 4.0 alignment)
Bulk async performance regression from APSB25-08 patch fixed
500+ issues fixed in core

🧱 Framework modernisation, three core components replaced
Laminas MVC → native PHP MVC
Zend_Cache → Symfony Cache
TinyMCE → HugeRTE
Symfony 7.4 LTS across the board
jQuery UI 1.14.1, jQuery Validate 1.21, Chart.js 4.5, Less.js 4.2.2, Underscore 1.13.7, Uppy 4.13.4. Every front-end library bumped

If you're currently on 2.4.6 or 2.4.7, you shouldn't jump directly to 2.4.9. You should first upgrade to 2.4.8 to bridge the massive gap in database and PHP requirements before making the final move. 2.4.9 is the right move for long-term stability, but the architectural lift is bigger than the version number suggests.

I was looking at a Magento 2 store recently, mid-sized B2B. While going through their analytics I noticed a big drop-off right at the payment step. Dug in a bit and found they had a 5-step checkout, a promo popup that fired exactly when someone clicked proceed to payment, and their payment methods didn’t really match their actual customer base. They had three options showing that barely anyone used, and the one method most repeat buyers preferred wasn’t even visible without scrolling.

The fixes weren’t complicated. Popup disabled, address fields trimmed down, payment method order cleaned up, and the preferred option moved to the top.They saw fewer drop-offs after that within a couple of weeks.

What surprised me was how long it had been sitting like that. Nobody had flagged it internally because it looked fine on the surface. The store was well designed and fast.

Does this kind of thing happen often for others here? Do you usually audit checkout UX proactively, or does it only get attention when the numbers start dropping? And what’s the one change you’ve made that had the biggest impact?

evaluating composable commerce platforms for a €120M GMV multi-country fashion business and would appreciate honest takes from anyone who has been through the procurement at similar scale.

we're currently on a Magento 2 monolith across 7 european markets and looking to replatform in the next 12 months.

shortlist is SCAYLE, commercetools, and Spryker, each handles PIM and OMS integration natively, has decent integrator coverage in DACH and benelux, and each is being pitched as the right call for our shape of business.

specifically trying to compare TCO at the 3-year mark including integrator hours and operational overhead (not just license cost), multi-country VAT and tax handling depth across DE, FR, NL, IT, ES, BE and AT, realistic migration timeline from Magento 2 with PDP-level data and historical SEO equity preserved, and which platform's professional services team genuinely shows up versus which one pushes everything onto partners.

anyone in mid-market retail who has run this evaluation in the last 12 months and is willing to share which platform was the right call for your specific shape, and which one almost was but turned out to have a hidden constraint that broke the model?

I work in ERP–eCommerce integration and this is probably the most misdiagnosed problem I see in B2B commerce setups: discount sync appears to work perfectly, but promotions behave incorrectly in ways that take weeks to surface.

Here's the root cause, and it's not technical, it's architectural.

The core mismatch

ERP systems like Business Central, SAP B1 treat discounts as rules. A 12% promotional discount isn't just a number, it's an instruction set:

• Valid between Date A and Date B
• Applicable only to customers in pricing group X
• Triggered only at a minimum quantity of N units
• Tied to a specific marketing campaign

eCommerce platforms like Adobe Commerce (Magento), Shopify, BigCommerce treat discounts as display states. A promotion is either on or off. When you sync from ERP to eCommerce, most integrations move the value (12%) but not the reasoning behind it.

The storefront interprets "12% discount" and applies it. Universally. Until someone turns it off.

Three failure modes this creates

1. Promotions outlive their expiry

ERP ends promotions automatically at the defined end date, no manual action needed. eCommerce promotions are state-based, they stay active until explicitly deactivated.

When the sync carries the discount value but not the expiration rule, promotions that have closed in ERP continue running on the storefront. Customers see and order against discounts that no longer exist.

The damage: customers get invoiced at full price after ordering against a "live" promotion. Support tickets follow. Repeat buyers start calling to verify discounts before ordering, defensive behavior that signals broken trust.

2. Browse price ≠ checkout price

ERP calculates discounts at order processing time, using live rules at the moment of commitment. eCommerce shows pricing at browse time, a pre-calculated snapshot from when the product page was loaded.

If anything between those two moments changes the applicable discount (quantity thresholds, customer group logic, promotion state), the checkout price differs from what the product page showed.

New buyers hit this and abandon. No error message. No indication anything went wrong. Just a cart left behind.

3. Customer-specific discounts apply universally

Account-level pricing agreements and group-specific promotions in ERP are tied to specific customer segments. When the sync strips that context, the discount becomes universal, visible and applicable to anyone who visits the product page.

This creates incorrect pricing expectations for customers who shouldn't see those prices, and can create margin exposure depending on the discount depth.

What actually fixes it

The integration needs to carry rule metadata alongside the discount value:

• Start and end dates (so expiry triggers automatically in eCommerce)
• Customer group and account eligibility (so discounts apply only to the right segments)
• Quantity thresholds (so tier-based discounts activate correctly)
• Campaign identifiers (so promotions tie back to marketing calendars)

Additionally, checkout calculation needs to use live ERP rules, not the browse-time snapshot, so the price a customer sees on a product page matches what they're charged.

When you build it this way, discount logic is enforced consistently across both systems. Promotions expire when they're supposed to. Prices are stable from browse to checkout. Account agreements stay account-specific.

How to diagnose this in your setup

A few questions worth asking:

• Do promotions ever stay active on your storefront after they've been closed in ERP?
• Do customers ever question why the checkout total differs from the product page?
• Does finance notice margin inconsistencies that don't match campaign performance?
• Do repeat buyers call or email to confirm discounts before placing orders?

If any of these are familiar, the integration is moving values but not logic.

Happy to go deeper on any specific ERP or eCommerce platform combination if useful.

Everyone is talking about the expected release of Magento 2.4.9-p1 in November 2026. Does anyone have an idea about the confirmed date for this?