A stuck or constantly recalculating indexer slows down the entire store, from stale prices to empty search results. This article explains the available indexer modes, why the Price Index and Category Products are the most expensive, which changes trigger an unwanted full reindex, and how to reliably diagnose and fix stuck indexers using indexer:status, the indexer_state table, and growing mview changelog tables.

Anyone who rewrites the invoice logic or credit memo processing in Magento 2 completely via preference risks conflicts with every additional module and every core update. Plugins on InvoiceRepositoryInterface, CreditmemoManagementInterface, and ShipmentRepositoryInterface allow targeted extensions: custom numbering, approval workflows for credit memos, additional totals lines, and automatic invoice creation on shipment, without replacing the core logic.

Magento 2 · Admin UI

Admin Grid with UI Component
a modern backend interface

Admin grids are among the most useful, yet also most frequently cursed, building blocks in Magento 2. Anyone who fails to cleanly separate Listing XML, Data Provider and Collection quickly ends up with a backend that technically works but is hard to understand and extend.

18 min read Backend Magento 2.4.8

Table of Contents

1. 1. What makes a good Magento 2 admin grid
2. 2. Listing XML and UI Component basic structure
3. 3. Data Provider, Collection and data flow
4. 4. Filters, sorting and actions
5. 5. Maintainability and extensibility
6. 6. Common mistakes
7. 7. UI Component grid vs. custom backend solution
8. 8. Magento 2 support
9. 9. Summary
10. 10. FAQ

1. What makes a good Magento 2 admin grid

A good Admin Grid Magento 2 is not an end in itself and not just a plain data container. It is a working tool for the people who search, filter, review, export or trigger follow-up actions in the backend. Good

Tests that depend on the current time, randomly generated UUIDs, or pseudo-random values are flaky: they sometimes fail and sometimes don't, and the cause is hard to reproduce. Clock interfaces, UUID factories, and controlled randomness solve this problem at its root, without complicating the production code.

A misconfigured Elasticsearch or OpenSearch installation noticeably slows down every category page and every faceted search in Magento. This article shows how index mapping, shard sizes, JVM heap, and query patterns determine actual response time, how to find bottlenecks with the Explain API and cluster health checks, and how to avoid expensive wildcard and fuzzy queries in layered navigation.

A Vue checkout flow directly determines the conversion rate of a Magento shop. Teams that cleanly separate steps, validation and abandonment tracking prevent users from bouncing right before purchase completion because of unclear error messages or lost progress.

Every Magento deployment handles sensitive data: SSH keys, database passwords, Composer auth tokens, Redis connections, and API keys. The question of where these secrets are stored determines how exposed a deployment process is in the event of an incident. GitLab CI/CD variables are a practical starting point, but they are not the best choice for every secret.

An additional checkout step, for example a gift wrapping selection or an age verification, cannot simply be bolted onto Magento 2 with a template override. With Hyvä Checkout and Magewire, a custom checkout step becomes a properly registered, server side validated component, without KnockoutJS and without fragile jsLayout merges.

Adminhtml controllers bundle access control, form processing, and redirect logic in one place, which is why unit and integration tests need to complement each other to cover both the pure logic and the interplay with the Magento backend stack.

The right debugging tool for GraphQL is not always the best known one. Whether browser-embedded, desktop app, or API client, each tool has its place in the diagnostic workflow. Knowing each tool's strengths means debugging queries, auth issues, and resolver errors more efficiently.