● The qoliber approach
Quality. Over quantity.
We design Magento, Mage-OS and Adobe Commerce extensions for teams that care about long-term maintainability: easier to inspect, integrate and run in production. Clean code, yours to own.
- On the market
- 14+ yrs
- Development
- 100k+ h
- Extensions
- 43
- Hyvä & ElasticSuite
- Gold
● The focus thesis
Built like infrastructure, not quick patches.
Every module is a reusable building block for real projects — something that solves a recurring Magento problem without dragging fragile code into every store it lands in.
That is why the questions that usually come up after launch — cache behaviour, indexer safety, upgrade paths, performance impact — are part of the architecture conversation from the start. And why every module we add is one we intend to maintain — not ship and forget.
-
01
Clean, readable code
PSR-compliant, no encrypted blobs — code you can read, review and extend with confidence.
-
02
Compatibility-first
Hyvä and ElasticSuite compatibility are baseline requirements, not late-stage patches bolted on at the end.
-
03
Production-first
Cache behaviour, indexer safety, upgrade paths and performance impact are part of the architecture conversation.
-
04
Tested & documented
Real test coverage, open documentation and responsive support — no vendor lock-in.
● The engineering bar
What "quality" actually means.
Many third-party modules hide architectural risks — overridden classes, direct ObjectManager use, cache violations, careless indexer writes. They surface months later, usually during an upgrade or a traffic spike. These are the rules that keep ours out of that story.
| Standard | What it means in practice |
|---|---|
| Service contracts | APIs and interfaces define the integration points — no coupling to Magento's internal logic. |
| Clean dependency injection | No ObjectManager abuse, plugin-safe design, no hidden runtime surprises. |
| No core rewrites | Magento is extended through its own APIs and plugins, never patched — so upgrades stay clean. |
| Index & cache safety | Indexers and cache layers stay stable and predictable; no data writes that break incremental indexing. |
| Hyvä & ElasticSuite | Frontend and search stack remain intact. See the matrix. |
| Composer delivery | Versioned releases through Private Packagist, reproducible in your CI/CD pipeline — not ZIP files. |
| Long-term maintenance | Ongoing support through Magento and Mage-OS version changes, with documentation to match. |
● The receipts
Quality you can audit.
Numbers our extensions publish on their own product pages — static analysis, coding standards and the size of their test suites.
| Extension | Static analysis & standards | Tests |
|---|---|---|
| GDPR Compliance Suite | PHPStan level 8 · Magento coding standards | 600+ automated tests |
| Social Login Pro | PHPStan level 8 · PSR-12 · Magento EQP 0 issues | 400+ tests · CI matrix PHP 8.1 – 8.5 |
| Advanced Product Feeds | PHPStan level 8 · zero reported errors | ~400 PHPUnit unit & integration tests · scale-tested on 100k+ products |
| Advanced Products Notifications | PHPStan level 8 · PSR-12 · Magento EQP 0 issues | 230+ PHPUnit + Playwright tests |
| Request for Quote | PHPStan level 8 · PHPCS (Magento + PSR-12) | 243 unit tests · 19 Playwright end-to-end tests in 12 specs · integration suites |
| Reward Points | — | 20 / 20 Playwright end-to-end tests in 14 specs · PHPUnit unit + integration |
| Gift Cards | PHPStan level 8 · Magento coding standards · PSR-12 · PHPMD | 18 Playwright end-to-end tests · PHPUnit + integration · 4 external review rounds before 1.0 |
| 3D Packaging for Magento 2 | — | 213 unit + 53 integration tests · 19 Playwright tests in 4 functional specs |
| Guest Wishlist for Magento 2 | PSR-12 · strict types | 292 unit tests · 18 Playwright end-to-end tests (Luma + Hyvä) |
| Delivery Slots | PHPStan level 8 · zero findings | Verified end-to-end on Hyvä 1.5 · PHP 8.1 – 8.5 |
| Multiblog for Magento | PHPStan level 8 | Playwright end-to-end + PHPUnit |
| Nebula Admin | phpcs 0 / 0 | 463 PHPUnit · 130 Vitest · 31 bridge tests |
| Trident Prism | Rust · zero unsafe code · 3 independent security audits | 631 tests — unit, E2E, Chrome, Docker |
As published on each product page. — means the page doesn't publish that figure.
● The honest "no" list
What you won't find in our code.
The shortcuts that make modules cheap to ship and expensive to own.
Encrypted blobs
Every line is readable. Your engineers can review it, debug it and extend it.
Core rewrites
We extend Magento through its own APIs and plugins — never by patching the core.
ObjectManager shortcuts
Dependencies are injected and visible, so nothing surprises you at runtime.
ZIP downloads
Composer and Private Packagist: versioned releases and reliable updates.
"Hyvä later" patches
Hyvä and ElasticSuite support are part of the module, not a follow-up project.
Vendor lock-in
Open documentation and code you own — you're never stuck waiting for us.
● Agency-first · one-to-one
We don't talk to your merchants.
Quality is also about who you have to deal with. We serve agencies and dev teams, not merchants — the agency keeps the client relationship and the spotlight.
The partner programme →We never compete for clients
We build the modules; agencies build the stores.
Merchants are sent to partners
When merchants come to us directly, we recommend our partners.
Engineers on the other end
Partners get a private Slack with our engineering team — conversations at PR level, not ticket queues.
“We partnered with qoliber because, like us, they do things differently. They build top quality Magento extensions we can trust will work as expected and not cause issues down the line.”
● Read before you buy
Judge us by the code.
Pick an extension, read its product page and docs, and ask an engineer anything. An engineer replies within one business day, usually in under 4 hours (Mon–Fri, CET).