The Visual Merchandiser is a Commerce feature, but category merchandising rules can be technically rebuilt in Magento Open Source as well. Coupling product order to stock level, margin and sales figures requires understanding position values, plugin points on the product collection, and the effect on the catalog index.

Magento 2 · APIs

REST vs. GraphQL
when to use which API

In Magento 2, the question of REST or GraphQL is rarely purely technical. Both approaches are useful, but they fit different frontends, data flows, and team structures. Good decisions therefore come from use cases, not from API fashion.

17 min read REST & GraphQL Magento 2.4.8

Table of Contents

1. 1. What REST and GraphQL each do well in Magento 2
2. 2. Strengths and limits of REST
3. 3. Strengths and limits of GraphQL
4. 4. Frontend, headless, and integration perspective
5. 5. When which API fits your project
6. 6. Typical wrong decisions
7. 7. REST vs. GraphQL, side by side
8. 8. Magento 2 support
9. 9. Summary
10. 10. FAQ

1. What REST and GraphQL each do well in Magento 2

REST vs GraphQL Magento 2 is not a question of old versus new, but of access pattern versus access pattern. REST is strong when clear resources, established integrations, and stable endpoints are the priority. GraphQL is strong when frontends need to flexibly

Module dependencies in Magento exist on two separate layers: composer.json controls which package gets installed at all, and module.xml sequence controls in what order it gets loaded. Mixing the two builds circular dependencies that only surface at setup:upgrade and are hard to untangle without a clean refactoring.

Magento 2 · Search

Tuning Elasticsearch and OpenSearch
Synonyms, Boosters, Filters

A good search experience in Magento 2 doesn't come from a running search server alone. Only when synonyms, relevance, filter logic, and catalog data work together with real domain knowledge does search deliver results that users actually find helpful.

18 min read Search Tuning Magento 2.4.8

Table of Contents

1. 1. What good search tuning in Magento 2 actually means
2. 2. Using synonyms wisely
3. 3. Steering boosters and relevance deliberately
4. 4. Thinking filters and search facets through properly
5. 5. Catalog data as a search quality topic
6. 6. Common mistakes
7. 7. Search server tuning vs. content-driven search logic
8. 8. Magento 2 support
9. 9. Summary
10. 10. FAQ

1. What good search tuning in Magento 2 actually means

Running Elasticsearch Magento 2 or OpenSearch Magento 2 is not enough on its own to get good product search. A search server can respond fast and correctly and still prioritize

Anyone who only knows setup:upgrade, cache:flush and indexer:reindex is giving up most of the diagnostic and maintenance power the Magento CLI actually offers. Hidden gems such as dev:di:info, indexer:set-mode, maintenance:allow-ips and admin:user:unlock solve concrete problems in seconds that would otherwise require manual database queries, code searches or a full maintenance blackout.

A naive GraphQL resolver that triggers its own database query for every list item quickly produces hundreds of individual queries on nested queries. GraphQL batching following the DataLoader pattern collects these requests and resolves them in a single, efficient call, with a noticeable impact on response times and database load.

A Stripe integration in Magento 2 is more than just an API call in the checkout. Clean payment methods need configuration, secure API adapters, gateway commands, and controlled error handling across order placement, capture, and reversal.

A CMS block in Magento only stores the current state, every change overwrites the previous version with no history and no way back. A custom CMS block versioning setup creates a traceable change history, a diff between versions and a safe rollback, all without Enterprise staging.

Choosing between Adobe Commerce and Magento Open Source decides license cost, available enterprise features and the entire operating structure of a shop. Whoever makes this call without solid criteria either pays for functionality they never use, or laboriously rebuilds what the other edition already includes.

Custom Magento 2 GraphQL resolvers connect the schema, query logic and service layer. What matters most is clear types, clean resolver classes and an architecture that does not push business logic directly into the resolver.