Magento development
Magento 2 extension development
We build Magento 2 and Adobe Commerce extensions as proper Composer modules. They use plugins, observers and dependency injection instead of core changes, so your store stays upgradable. We can also update your older modules for newer Magento versions.
- Modules for Magento 2 and Adobe Commerce
- Hyvä and Luma storefront support
- Upgrades and marketplace review readiness
Modules that follow the Magento way
A Magento 2 module has a clear structure: registration.php, etc/module.xml, a composer.json, dependency injection in di.xml, and declarative schema in db_schema.xml. We build to that structure and change core behaviour through plugins, observers and preferences, never by editing vendor files.
We write for the storefront you run. Luma stores use layout XML, templates and Knockout or UI components. Hyvä stores use Alpine.js and Tailwind, and often need a compatibility module. We build for the one you have and test it on a copy of your store.
What we build
Capabilities
Custom modules
New features packaged as Composer modules with declarative schema, data patches, configuration and ACL.
Plugins and observers
Changes to core behaviour through interceptor plugins and event observers, without touching core code.
Payment methods
Payment integrations for gateways that Magento does not support, including redirect and on-page flows, webhooks and refunds.
Shipping methods
Carrier modules with live rates, label creation and tracking, tied into the checkout and the admin order.
GraphQL and REST
Custom GraphQL schema and resolvers, and REST endpoints for headless storefronts, apps and outside systems.
Admin UI components
Admin grids, forms and system configuration built with UI components, so staff can manage the feature.
Hyvä and Luma support
Storefront output for Luma, or Hyvä-compatible versions of your module with Alpine.js and Tailwind.
Upgrades and review readiness
Moving modules to newer Magento and PHP versions, and cleaning code against Magento's coding standard before a marketplace review.
Use cases
Problems these extensions solve
A gateway Magento lacks
Your customers use a payment provider with no Magento module. We build one that supports your checkout.
Courier rates and labels
Staff book couriers outside Magento. We bring rates, labels and tracking into the order screen.
A module blocks your upgrade
An old custom module fails on a newer Magento or PHP version. We update it and test the store after the change.
Hyvä migration
You are moving to Hyvä and some modules show no output. We build compatibility so those features work again.
Data for an app or headless site
Your app or front end needs data that Magento does not expose. We add GraphQL types and resolvers for it.
Slow or messy customisations
Core files were edited long ago. We move that logic into a clean module so upgrades stop being risky.
What you receive
- Module source code you own, installable with Composer
- Declarative schema, data patches and configuration files
- Admin configuration screens and ACL rules
- Install, upgrade and uninstall tested on a clean Magento
- Notes on the Magento, PHP and storefront versions tested
- Coding-standard check results
- Marketplace submission files, if you plan to publish
Technology
- PHP
- Magento 2 / Adobe Commerce
- Composer
- Dependency injection (di.xml)
- Plugins and observers
- Declarative schema
- GraphQL
- UI components
- Layout XML and PHTML
- Knockout.js and RequireJS
- Hyvä (Alpine.js, Tailwind CSS)
- MySQL
How we work
From first message to handover
- 1
Requirements review
We read your brief and check your Magento version, edition, PHP version and storefront, and list the modules you already run.
- 2
Technical design
We decide on the module layout, the plugins and events to use, the data tables and the admin screens, and share the design.
- 3
Build and test
We build on a local or staging Magento copy, with unit and manual tests for checkout, admin and API behaviour.
- 4
Storefront and conflict check
We test with Luma or Hyvä, your theme and your other modules, and fix any conflicts or caching problems.
- 5
Release and marketplace review
We help you deploy to production. If you plan to publish, we prepare the package for the technical review and handle the findings.
FAQ
Questions about magento extensions
Do you support both Magento Open Source and Adobe Commerce?
Yes. We build for both. We check the code against the edition and version you actually run.
Can you make our module work with Hyvä?
Usually yes. Hyvä uses a different front end, so storefront parts often need a compatibility layer. We review your module first.
Can you update a module we already have?
Yes. We can work on your existing extension. We will review the code and tell you what we find before we quote.
Do we own the code?
Yes. You own the code we write for you.
How much will it cost and how long will it take?
We quote after reviewing your requirements. It depends on the features, the version and the outside systems.
Will it survive Magento upgrades?
We avoid core edits and use plugins, observers and declarative schema. We can also test and update the module when you upgrade.
Can you prepare an extension for the Adobe Commerce Marketplace?
We can prepare the code and files to meet the technical review checks. The review decision belongs to the marketplace team.
Tell us what your Magento store needs
Write to info@lyrakart.com with your Magento version and what you want built. We will review it and reply with a quote.