Magento GraphQL can be extended in a targeted way, but opening up the schema without preparation builds performance problems into your project through N+1 database queries. The right approach goes through extension attributes, cleanly isolated resolvers, and a clear separation between schema definition and data access.

Every plugin increases memory usage, extends startup time, and can slow the IDE down. The question is not which plugins exist, but which ones genuinely add value to your own workflow, and which ones can be disabled without any loss.

Magento 2 · MSI

Understanding MSI properly
Custom Source and reservations

Multi Source Inventory solves a real problem in Magento 2, but in everyday practice it is often misunderstood. Anyone who mixes up sources, stocks and reservations quickly ends up building inventory logic that is either factually wrong or operationally unstable.

18 min read MSI Magento 2.4.8

Table of Contents

1. 1. What MSI actually models in Magento 2
2. 2. Creating and thinking about a Custom Source in Magento 2
3. 3. Understanding reservations in Magento 2
4. 4. Data flow between Source Items, Stocks and Salable Quantity
5. 5. Typical extension scenarios with MSI
6. 6. Common mistakes
7. 7. MSI versus classic single-stock thinking
8. 8. Magento 2 support
9. 9. Summary
10. 10. FAQ

1. What MSI actually models in Magento 2

MSI Magento 2 stands for Multi Source Inventory and, for the first time, cleanly separates physical sources, logical stocks and salable quantity. This matters because in real projects,

A new product attribute does not automatically end up where it is needed for search and filtering in the Elasticsearch index. Only a deliberate custom attribute mapping with dedicated FieldMapper classes ensures that searchable, filterable and the right field type fit together, instead of relying on Magento's default derivation.

Magento 2 already ships with a working caching solution in the form of its built-in full page cache, yet many projects put Varnish in front of the shop anyway without checking whether the actual requirements call for it. This article compares both approaches based on traffic volume, hosting setup and team skills, and uses VCL examples, purge strategies and monitoring commands to show when the extra operational effort of Varnish really pays off.