Magento 2
Adobe Commerce and Open Source. Modules to Magento standard, PSR-compliant, with setup scripts and uninstall path.
CPS Software
Twelve proprietary extensions for Magento, developed from fifteen years of real-world shop operations. All in use, all of one piece, all with the same backend menu. Organized by the problem they solve — not by technology.
What we do here
Not as a side product. Twelve extensions have developed over fifteen years, each from a real case, all in productive use with customers. Plus custom development: integrations, middleware, interfaces.
Adobe Commerce and Open Source. Modules to Magento standard, PSR-compliant, with setup scripts and uninstall path.
Plugins and blocks where a builder isn't enough. No dependency on a page builder tool.
Laravel. Our own system, running our control center, customer portal, and this website.
CPS Software
Twelve extensions for Magento 2, all in productive use, all with shared foundation and shared update path. Each entry has its own anchor.
Adobe Commerce and Magento Open Source, versions 2.4.x
Magento 2
Upload restrictions, API bot registration blocks, filters against search spam.
The caseHundreds of fake accounts daily via the API and garbage in search stats.
Magento 2
WebP and AVIF delivery from your own house, shrinking oversized uploads on save.
The caseAn external image service cost monthly and delivered no images on outage.
Magento 2
Search suggestions with preview image and price, category prefilters, typo tolerance.
The caseStandard search didn't find articles that were clearly in the catalog.
Magento 2
Logs every outgoing email with recipient, template and timestamp in the backend.
The caseNo one could prove whether an order confirmation ever left the house.
Magento 2
Legally compliant withdrawal form with backend management and proof of receipt.
The caseWithdrawals came via email, phone and paper — with no verifiable proof of receipt.
Magento 2
Latest articles as default sort, additional sort criteria per category.
The caseNew stock disappeared behind old stock because Magento sorted by position.
Magento 2
Base price information per German law, currency-aware for EUR and CHF.
The caseTwo countries, two currencies, one warning letter risk for every quantity specification.
Magento 2
Wishlist for customers, usable without account, session- and account-spanning.
The caseCustomers put articles in the cart just to remember them.
Magento 2
Business closures with notification banner in shop and delivery time countdown for Amazon.
The caseOrders ran into factory vacations and delivery time was wrong anymore.
Magento 2
Traffic light in product grid: which article arrived at Amazon, which is stuck.
The caseMarketplace sync ran, but nobody saw what actually got transferred.
Magento 2
Auto-fixes a Magento bug that cripples saved grid views.
The caseAfter every update, the product grid wasn't callable for individual editors.
Magento 2
Shared foundation: configuration, license check, logging, shared update path.
The caseEach extension brought its own helper classes — twelve times the same code.
Custom blocks for client projects
What we develop for WordPress projects happens project-based so far and isn't published as a standalone extension. What from that is worth as a catalog entry, we list here once it's packaged.
Modules in our own system
In our own system, these features aren't add-ons, they're included — image optimization, search, mail log and legal texts run there without an extension. What becomes available as add-on, we'll list here once it's ready.
Custom Development
The bigger part of our development isn't in the catalog. Enterprise extensions that fetch hundred thousand articles from an interface and process them per customer.
Product master data, attributes, media and translations from the PIM into the shop — nightly, differential, with log.
Amazon, eBay, Zalando, Otto from one stock. Prices, availability and status come together in one place.
Inventory management, POS, accounting, shipping providers. Whatever won't talk to each other gets a translator.
REST, GraphQL, SOAP, SFTP, CSV. Even the formats nobody really uses anymore and that still have to work.
On request, in any system
Magento 2, WordPress, Shopware, TYPO3, or your own system: We build to fit precisely into the existing architecture — using the interfaces and events the system itself provides, not by intervening in foreign code. The scope contains exactly what's needed, nothing more. Less code means less attack surface, fewer conflicts on update, and less that someone has to understand in two years.
Craftsmanship
How collaboration works
We look at your shop, version, extensions and data flows. After that, both sides know what we're talking about.
Written estimate based on effort, with assumptions and risks. No flat rate that gets renegotiated later.
Separate development environment, versioned, with test data. You get interim states to review.
Testing on a copy of your system, with your data. Only then does anything go to production.
The extension stays in our care — compatible with the next Magento version, without you asking.
Next step
Tell us what the system should do and where it's failing today. We'll tell you if it needs an extension or if one already exists.
We get back to you within two business days — personally.