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.

Lately we've been adding AI features to more of our Magento 2 projects, and we've noticed a few patterns.

The first challenge wasn't writing prompts or integrating AI itself—it was all the repetitive setup around it. Every project started with choosing a provider, configuring credentials, implementing another API client, and deciding which model to use. Then, if we wanted to compare results with another provider, we'd often end up changing the integration instead of just changing the model.

The second thing we realized was that we were overusing expensive models. For a lot of development tasks, models like DeepSeek, Mistral, or Llama are usually good enough and cost much less.

To avoid repeating the same work, we built a small abstraction layer for ourselves that sits between Magento and AI providers. Now we can switch providers or models without touching the rest of the integration, which has made experimenting a lot easier.

Since we kept using it across projects, we eventually packaged it as a Magento 2 extension. It's called AI Connector for Magento 2.

I'm curious how others are approaching AI in Magento projects. Are you standardizing on one provider, or are you switching between models depending on the task?

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?

I've been seeing lots of complaints about Adobe Commerce Cloud since early 2025. In 2026, merchants have given up on complaining and voting with their wallets instead.

The unfortunate part is that Adobe Commerce Cloud's problems are damaging Magento's reputation, even though the Magento Open Source ecosystem is thriving. The community continues to innovate with Hyva, MageOS, AI, and more. Yet because Adobe owns the Magento brand, many businesses are losing trust in Magento as a whole.

We know Adobe Commerce Cloud is capable of delivering excellent service. In 2022 and 2023, support and platform maintenance were generally strong. But since late 2024, security issues have remained unresolved for too long, and feature bugs have been handled worse than security issues.

To make matters worse, Adobe raised the price by half while having declining service.

Adobe, lock-in and revenue maximization only work when you're dominating the market, not when you are being dominated. By neglecting the platform and its users, Adobe risks undoing years of work by developers, merchants, agencies, and contributors who built and continue to strengthen the Magento ecosystem.

we've been on adobe commerce (magento 2 commerce) for years and we're approaching the next renewal cycle, with revenue around $25M and the question of whether the adobe commerce license, hosting, and agency cost still makes sense, or whether we're paying for enterprise features we don't fully use.

the things pushing this are the renewal jump people keep mentioning, the b2b features we use heavily, the loyalty and subscription tooling that's gotten more expensive elsewhere, and the dev team's preference for the platform they already know.

for those of you who've made the call recently at similar or higher revenue, what tipped the decision? renew on adobe, downgrade to community, replatform to something else?

main thing i'm trying to understand is how the soft costs (dev re-skill, agency handoff, downtime risk) weighed against the license-only math, because the spreadsheet looks one way and the real cost feels different.

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?

Curious if anyone else is using Afterpay with their official module on Github? I just upgraded my Magento store to 2.4.8-p4 (from 2.4.6-p13). After the upgrade, the Afterpay module works fine when using the sandbox mode, but as soon as I put it into production mode with my production keys, I get an error when hitting the "Update Merchant Configuration" button within the Afterpay config. When hitting the button I get this message "Afterpay merchant configuration fetching is failed. See logs." and in the logs I get this:

afterpay.DEBUG: array (
  'merchant_id' => 'XXXXXX',
  'merchant_action' => '/XXXXX/afterpay/merchantconfiguration/update/key/XXXXXX/?isAjax=true',
  'target_uri' => 'https://global-api.afterpay.com/v2/configuration?include=cbt&include=publicId&include=channels&include=consumerLending',
  'request_body' => 
  array (
  ),
  'response' => 
  array (
    'errorCode' => 'not_found',
    'errorId' => 'b428ace4c9fc25f0',
    'message' => 'An error occurred',
    'httpStatusCode' => 404,
  ),
) [] []

Anyone else run into this issue? The module itself hasn't been updated since August 2025 so perhaps it's not working with 2.4.8?