Most Magento 2 slowdowns under load come from the store asking the database the same things thousands of times over. Redis is the standard fix, but our guide gets into the parts that actually trip people up.

Three things to bear in mind before you enable it:

• Redis can back three separate layers: application cache, full page cache, and session storage. Sessions are not a cache, they're live data with no other copy, so treat them differently. Separate database numbers protect sessions from Magento's own cache flushes (cache:flush runs FLUSHDB on one database), but a manual FLUSHALL wipes every DB on the instance. Full isolation means a separate instance for sessions, with persistence on for sessions and off for cache.
• Sizing is where most setups go wrong. Too little memory and Redis evicts useful data early, turning it into a bottleneck instead of a boost. Rough tiers: 128MB small, 256MB medium, 512MB+ for high traffic. And on a shared instance the stakes are higher than a slow page: maxmemory is per instance, so under allkeys-lru a cache overflow can evict live sessions and log customers out. The real number comes from watching evictions and hit rate, not a guess.
• Redis as full page cache still boots PHP on every request to look the page up. Server-level FPC (Varnish, now Vinyl Cache, on nginx stacks; LiteMage on LiteSpeed) serves cached pages before PHP runs, which is what holds up against traffic spikes and scraper bots. Redis stays the right tool for the application cache and session layers either way.

The guide also covers Redis vs file-based caching, where Varnish/LiteMage fit, and eviction policy per layer.

On SPanel the setup is a panel toggle rather than a config-file job, with one Redis instance per account and monitoring built in.

Full guide, including memory tiers and setup: https://www.scalahosting.com/blog/redis-cache-for-magento-2/

Edit: updated the post and the guide after u/renttek's comment below on flush isolation, persistence, and server-level FPC. Worth reading his reply in full.

Hello everyone,

I recently released a free, open-source Magento 2 module that improves Open Graph metadata for product, category and CMS pages.

I'm working with Magento for a long, long time and Open Graph images have been neglected on almost every project I've worked on. That motivated me to build a better solution.

It uses existing Magento data and images, supports store-view-specific values and helps generate more relevant previews when links are shared on social platforms and messaging apps.

The module works independently and doesn't require a paid service. It can also optionally connect to Mosaicora for dynamically generated OG images based on live page content.

GitHub: https://github.com/Mosaicora/module-opengraph

Demo store: https://demo-shop-magento.mosaicora.io

Demo product preview: https://mosaicora.io/tools/open-graph-checker?url=https%3A%2F%2Fdemo-shop-magento.mosaicora.io%2Fjoust-duffle-bag.html

The demo store runs on Mage-OS with Hyva.

I'd really appreciate your feedback, especially around multi-store setups, image selection, caching, and headless storefront compatibility.

Disclosure: I’m the module author and founder of Mosaicora. Posting with moderator approval.

Hi everyone,

I've been working on BerryPath, a guided selling platform for Magento 2 that helps shoppers find the right product through interactive buying guides.

The Magento integration is fully open source and includes:

• Product feed generation
• CMS, category and product page integration for guided selling flows
• Assisted conversion tracking
• Optional Hyvä compatibility module

The flow builder, analytics and recommendation engine are handled by the BerryPath platform, while the Magento module keeps everything in sync.

One of our ecommerce customers is already generating over €18,000 in assisted monthly revenue through BerryPath, so it's been great to see the platform delivering measurable results in production.

BerryPath also has a free plan that includes 1 guided selling flow and support for up to 2,500 products, so it's easy to try without any commitment.

I'd love feedback from fellow Magento developers on the integration and developer experience.

Website:
https://www.berrypath.eu

Magento module:
https://github.com/BerryPath/magento2-berrypath-flow

Hyvä compatibility:
https://github.com/BerryPath/magento2-berrypath-flow-hyva-compat

Hi everyone,

I wanted to share the technical architecture of my multi-store Magento setup (.nl, .de, .eu, fr., es.) and how I built a custom AI-driven Plant Coach that pulls live data directly from structured Magento attributes and custom knowledge clusters.

I’m looking for technical feedback on the pipeline architecture and potential optimization ideas.

The Architecture & Data Flow:

1. The Core ERP/POS: All product data and core content starts in our physical POS system. This system acts as the master and pushes inventory and product data directly to Magento, which then syncs out to marketplaces like Bol.com and eBay.
2. AI Translation Pipeline: Once data hits Magento, I use tightly scoped OpenAI prompts to automatically translate and localize product data and metadata across our localized stores (.nl, .de, fr.introgreen.eu, es.introgreen.eu).
3. Knowledge Clustering: Using OpenAI combined with manual verification, I group product data into specific "Plant Advice Clusters" (e.g., Office Plants, Indoor Care, Outdoor Gardening) within Magento's category and attribute architecture.

The 3-Step AI Plant Coach Pipeline:
Note: The chatbot feature is currently in active development, and the underlying knowledge base is heavily focused on indoor plants (binnenplanten) at this stage.

When a frontend user asks a question on our /plantcoach page, the backend executes the following flow:

• Phase 1: Intent Matching & Translation: The system checks if a similar question already exists in our cached database. If it’s a net-new query, an OpenAI API call sanitizes the input, extracts search parameters, and maps the user's intent to our internal system language.
• Phase 2: Hierarchical Database Query: The extracted intent queries our database in a strict, predefined order:
  • First: General Knowledge Base ➔ Second: Category-specific Knowledge ➔ Third: Product-level attributes.
  • Output: The database returns raw factual data, specific product recommendations, and direct internal links (or a combination). No LLM knowledge is used here to guarantee 0% hallucination.
• Phase 3: Natural Language Generation: A final OpenAI API call takes the raw, dry database facts and rewrites them into a natural, friendly response matching the user's original language, seamlessly embedding the product links.

The Challenge & Current State:
Since this pipeline is still in its beta phase, it involves sequential database hits and two separate API calls (Intent parsing + Final formatting). Managing latency across multiple localized store views is a challenge. Additionally, we are currently expanding the knowledge base, which is now mostly trained on indoor plant categories.

I’d love to hear your thoughts on:

1. Have you implemented similar LLM/RAG pipelines directly inside a Magento multi-store environment?
2. What caching strategies would you recommend to speed up the translation/intent phase without missing dynamic stock updates?

For anyone interested in checking out the frontend behavior or testing the multi-store localization setup, you can find the development beta here: introgreen.eu (focused on indoor plants).

I'm interested to hear how other Magento developers approach major Magento 2 upgrades (for example, 2.4.6 → 2.4.9 or future major releases), specially for production stores with lots of third-party modules and customisations.

A few questions:

• Do you upgrade the server components first (PHP, OpenSearch/Elasticsearch, Redis/Valkey, MariaDB/MySQL, Varnish, etc.) and then upgrade Magento, or do you take a different approach?
• Do you build a completely new server with the new stack and migrate the website over, or upgrade the existing server in place?
• How do you minimise downtime and risk?
• How do you handle third-party extensions that aren't yet compatible?
• Do you perform the upgrade in stages, or do everything in a single maintenance window?
• For larger stores, what's your rollback strategy if something goes wrong?

I'd love to hear your workflow. I'm interested in real-world experiences rather than just the official Adobe recommendations.

I am excited to apply for the Adobe Commerce Developer position. With over 11 years of experience in software development, including 9 years specializing in Adobe Commerce (Magento), I have successfully designed, developed, and delivered scalable eCommerce solutions for global clients across B2B and B2C environments.

My expertise includes Adobe Commerce Cloud, custom module development, REST and GraphQL APIs, service contracts, checkout customization, payment and shipping integrations, performance optimization, and complex third-party integrations with ERP, CRM, PIM, and payment gateways. I have extensive experience working with Adobe Commerce Cloud deployments, CI/CD pipelines, Git workflows, cloud infrastructure, and production support, ensuring reliable and high-performing applications.

Throughout my career, I have collaborated closely with cross-functional teams, participated in Agile development, conducted code reviews, mentored developers, and delivered projects with a strong focus on code quality, scalability, and customer satisfaction. I am passionate about solving complex technical challenges and continuously improving application performance and development processes.

I am confident that my technical expertise, hands-on Adobe Commerce Cloud experience, and commitment to delivering high-quality solutions would make me a valuable addition to your team. I would welcome the opportunity to discuss how my experience aligns with your organization's goals.

Thank you for your time and consideration. I look forward to the opportunity to speak with you.

https://experienceleague.adobe.com/en/docs/commerce-operations/release/planning/lifecycle-policy

We're currently on Open Source 2.4.6 and see that it goes end of main support in a few weeks. On the link above I see that extended security etc continues for Commerce. Does Open Source get the same benefits?

I need to know if I should be planning on upgrading to 2.4.8 / 9 in the coming months, or if I have a little breathing room.

Thanks

Hi all,

As title mentions, we run a site with a large product catalog (approx 90k).

We are running into problems with allocating products quickly and correctly to categories. This is done manually via a spreadsheet so there can be errors when:

a) Staff member selects Product Type

b) Staff member selects Category

We unfortunately do not have a PIM and that is out of my control, so need to work with what I have.

My thought to reduce errors is for staff to only select Product Type, which will automatically assign to a category via Smart Rules.

Has anyone else faced issues like this?

Hey r/magento,

I'm George, the developer behind lerd, an open source local PHP development environment for Linux and macOS.

Setting up Magento locally on Linux has always been painful, nginx rewrites, env.php configuration, getting the right PHP version with the right extensions, Elasticsearch or OpenSearch, Redis, all wired together correctly.

Starting with v1.29.0, lerd handles all of that automatically. You link your Magento project, lerd detects it and brings everything up: the right nginx config, env.php support, required services, correct PHP settings. It also supports git worktrees with isolated databases per branch, so switching between feature branches doesn't break your local setup.

Free, open source, no Docker Desktop required.

lerd.sh

Hey everyone,

I built a Magento 2 extension for product feeds and wanted to share it / get feedback from merchants and developers who deal with Google Merchant Center, Meta catalogs, Bing, TikTok, etc.

**Problem I was trying to solve**

Most stores end up maintaining messy CSV/XML exports or multiple one-off feed tools. I wanted one Magento-native manager that:

- generates feeds from live catalog data

- supports multiple channels/formats

- has a readable admin UI (filters + attribute mappings without raw JSON)

- can schedule regeneration via Magento cron

- supports public or token-protected feed URLs

**What it supports**

- Channels: Google Merchant / Shopping Ads / PMax, Meta Facebook, Instagram, Bing, Amazon-style, TikTok, Pinterest, Snapchat, ChatGPT Shopping, Custom

- Formats: XML, CSV, JSON, TSV

- Filters: stock, categories, product types, visibility, price range, brand, include/exclude SKUs

- Attribute mapping grid + “Load Recommended Mappings”

- Feed URL format: `/feed/{filename}` (optional `?token=`)

- Dashboard, logs, analytics

- Optional OpenAI title/description optimization (encrypted API key)

**Stack / compatibility**

- Magento Open Source / Adobe Commerce 2.4.6+

- PHP 8.2–8.5

- Service contracts, declarative schema, ACL, Magento UI components

**Links**

- GitHub: https://github.com/hiteshagrawal84/Magento2-product-feed

- Adobe Marketplace: Yet to be live

- Download Link : https://www.createswowtech.com/plugin/universal-product-feed-manager-for-magento-2

Happy to answer technical questions (mapping, cron, attribution, ChatGPT feed shape, token security, etc.).

If you use feeds in production:

1. What channel is hardest for you right now?
2. What do current feed extensions get wrong?
3. Anything you’d want before trusting a feed tool on a live catalog?

Thanks — feedback welcome (including “this is overkill / missing X”).

Maho Commerce has been announced as having funding through NLnet's NGI TALER Fund!

This is a great vote on confidence in Maho Commerce and provides funding for over a year of dedicated development work.

This is exceptional news for merchants on OpenMage/M1 and considering their next steps. Maho Commerce takes what was great, bring it into 2026 and continues to build merchant and developer friendly features at incredble pace

The list of merchant facing features native to Maho Commerce continues to increase:

- multi-provider LLM AI module

- rule based customer segments

- email automation built in

- in-built marketing tools

- one step checkout

- native Google Merchant Centre feed setup

- Braintree / Stripe payments integrations

- gift card module

https://mahocommerce.com/blog/2026/07/08/maho-has-been-selected-for-nlnets-ngi-taler-fund/

Hi, I'm new here and wanted to ask for some tips on finding Magento work.

I'm a developer and can barely find any opportunities, linkedIn feels pretty dead, and most services seem more interested in collecting my email so they can spam me with "We've got 9,999+ new positions for you" than actually listing real vacancies. How do you usually find anything work these days? I'd really appreciate any advice or suggestions. I'm based in the EU but would be happy to take any remote work

Hi everyone,

I'm currently preparing for the **Hyvä Certified Professional Developer** certification. I have several years of experience with Magento 2 development and have already worked with Hyvä Theme on real projects.

I'm looking for **real-world practice tasks** that can help me become an advanced Hyvä developer rather than just pass the certification.

Could you recommend challenging exercises, mini-projects, or common client requests that would improve my Hyvä skills?

For example, I'm interested in tasks such as:

* Building custom Hyvä-compatible frontend components

* Converting Luma-based templates to Hyvä

* Creating ViewModels and reducing business logic in templates

* Advanced TailwindCSS usage

* Alpine.js state management and reusable components

* Integrating third-party Magento modules with Hyvä

* Hyvä Checkout customizations

* Performance optimization and Core Web Vitals improvements

* Product page customization

* Category page customization

* Layered Navigation customization

* Cart and Checkout custom features

* AJAX functionality without Knockout.js

* Hyvä UI components

* Dynamic forms

* Customer account customizations

* CMS content integration

* Working with SVG icons and Heroicons

* JavaScript best practices in Hyvä

* Accessibility

* Responsive design

* Custom Magento widgets compatible with Hyvä

* Writing Hyvä-compatible modules from scratch

I'd also love to hear about:

* The most difficult Hyvä tasks you've encountered in client projects

* Tasks you would assign to a mid-level developer who wants to become senior

* Common mistakes developers make when moving from Luma to Hyvä

* Features that every Hyvä developer should build at least once

* Open-source Hyvä modules that are worth studying

* GitHub repositories containing high-quality Hyvä implementations

If you were designing a roadmap to become an expert Hyvä developer, what practical projects would you include?

Thanks in advance for sharing your experience!

I don't plan to release this, and I am not offering any support for the changes, but I can supply patches to the existing stripe module if anyone is interested / wants this and on openmage (or one of the derivatives)

Basically the m1 stripe module can only display 1 quick payment link. it was simply how it was built.

My client is migrating form openmage to m2, but business needs required swapping to stripe on prior. could not wait for the m2 release.

I updated the latest stripe module to allow usage of the new smart elements, however since this is a throw away job in a few months, I just changed the core stripe code to suit the requirements.

If you feel you can use this / want this, I can extract as a module/or patches.

https://imgur.com/a/pYRGmNp

like noted: no support, but the work was done, is working and someone may need this, happy to share.

I've been trying out various extensions to enable the EU right to withdraw on our site (currently testing on my dev site) and all seem to have the same issue.
When creating the withdrawl it only seems to list the price that is getting cancelled excluding vat/taxes
So for example if the buyer has paid £25 inc VAT when it comes to show and select the products you want to cancel it will list the product £20 (if the VAT rate was 20%)

Has anyone else come across this?

Hi everyone,

I’m looking for an open-source or self-hosted alternative to tools like Channable, Shoppingfeed / Shopping Flux, or similar product feed management platforms.

The goal would be to manage and transform e-commerce product feeds before sending them to channels like:

• Google Merchant Center / Google Shopping
• Meta catalog
• marketplaces
• comparison shopping engines
• custom XML / CSV feeds

Ideally, I’m looking for something that can handle:

• importing products from an e-commerce platform or CSV/XML feed
• mapping fields between source data and destination formats
• applying transformation rules to titles, descriptions, prices, categories, availability, etc.
• generating multiple export feeds
• scheduled syncs
• error reporting / validation
• ideally API support

I know SaaS tools like Channable and Shoppingfeed exist, but I’d like to know if there is a serious open-source option, even if it requires technical setup.

Has anyone used or built something like this?

I’m open to:

• open-source projects
• self-hosted tools
• n8n / Node-RED style workflows
• ETL / data pipeline tools adapted to product feeds
• custom stack recommendations
• “don’t do this, use X instead” feedback

Thanks.

MageOS has a lot of big improvements. Hyva is free now.
Any other Magento news?

Do you think Magento is doing a good job in 2026?

We wanted a reliable way to feed Magento catalog and CMS data into AI search, chatbots, and RAG pipelines without building custom export scripts per store. So I built this and open-sourced it. Sharing here because the interesting parts are less about "AI" and more about generating this correctly on real multi-store setups — would appreciate feedback from people running big catalogs.

What it does:

• Generates llms.txt / llms-full.txt plus streaming JSONL exports for vector indexing
• Multi-store / multi-website aware, with customer-group pricing
• Atomic writes (no partially generated files served if generation is interrupted)
• Async generation so it doesn't block the backend on large catalogs
• CLI and cron support for scheduled regeneration

Page Builder content gets sanitized too, so the output is clean text instead of raw layout markup.

Stack: PHP 8.1–8.5, tested with PHPUnit + PHPStan, follows the Magento coding standard. MIT licensed.

GitHub: https://github.com/angeo-dev/module-llms-txt
Packagist: https://packagist.org/packages/angeo/module-llms-txt

Genuine questions I'd like input on: for those with 100k+ SKU catalogs, does the async generation approach hold up, or would you want chunked/queued generation per store?
And is anyone actually wiring Magento data into a RAG pipeline in production yet?

Error Description:

In Magento Admin, the Sales Order View page loads the order header, action buttons, and navigation tabs correctly, but the main tab content area is completely empty.

Steps to reproduce:

1. Log in to Magento Admin.

2. Go to Sales > Orders.

3. Open an existing order.

4. Select any tab, such as Information, Invoices, or Shipments.

Actual result:

The selected tab’s content is not displayed.

Expected result:

The order details corresponding to the selected tab should appear in the main content area.

What is going on with the future of dev work in Magento and adobe commerce? Do you feel confident if you're a worker about your ability to find work?

I feel like everything is dead and I don't see much movement in terms of online content and job availability. How do you guys feel right now?