The work, with the names attached.

THE WORK

• Incident analysis: an agent reads slow logs, server metrics and application logs alongside the code. Blank pages, slow searches and nightly outages can often be traced to a single query or a single line of config within the hour.
• Code review on every pull request, ours and the client team's, against the project's own coding standards. On the largest team that is a pass every half hour across four repositories, which also moves clean work on to test.
• Ticket preparation and estimation: tickets are investigated in the real code and on production before the team discusses them, with a reasoned estimate based on hundreds of previously estimated tickets.
• Autonomous development: a ticket with the right label gets built on its own, from branch and code to checks, pull requests and test scenario. The first was ready within eleven minutes and passed QA and review first time.
• Takeovers and upgrades mapped faster: modules compared against their originals, changelogs and patches read, and one set of AI guidelines per repository, with guardrails on what an agent may push and merge.

THE WORK

• Meta Pixel with a server-side Conversions API made to work on Hyvä, advanced matching included, replacing an extension that no longer did.
• GA4 purchase events that actually arrive: the Hyvä Checkout thank-you page sat in the full-page cache, so purchases went unreported.
• Sale prices fixed on product cards and product pages, with an override for a bug in Magento's special-price resolver, and the theme stripped of unused stylesheets and an entire unused parent theme.
• Checkout and trust: Apple Pay and Klarna logos on the payment methods, a Trusted Shops badge, and a REST API that no longer accepts unwanted uploads.
• GrumPHP, PHP-CS-Fixer and PHPMD as git hooks, dependency updates and core fixes through composer-patches, and a post-deploy script so a release needs no manual steps.

THE WORK

• Category pages that ran 8,380 database queries now run 1,272. A stock-label extension hooked into every template block, parsed the finished product grid back into HTML and loaded each product again, checking 36 attributes per product. We moved the label into the listing template itself, kept it for the 254 products that use it, and fixed a bug on the way that called sold-out products "in stock".
• Filters on brand pages did nothing, and every click added another piece to the address until it read /merken/<brand>/rond/rond/vierkant/punt. The cause was URL handling that had been switched off in the code we took over. It is back, and the brand router is patched so a broken address returns a 404 instead of trapping the visitor.
• Sixteen Mageplaza modules moved from a copy in app/code back to Composer. A plain diff showed some 270 changed files, nearly all of them reformatting, so we compared the code token by token: two changes were real. The same reformatting had broken one admin script, which left every admin form spinning forever without a single error in any log.
• From manual deploys to Bitbucket Pipelines with Deployer: staging, acceptance and production from the same pipeline, with three releases to roll back to. Magento and PHP on current versions, and the dead extensions removed.
• Adobe security patches shortly after each release, plus our own mitigation for StyleSmuggler before the patch existed.
• Tracking and discoverability: GA4 through Tag Manager, Meta Conversions API, and structured data with the right tax-inclusive price for Google Shopping, for configurable, grouped and bundle products alike.

THE WORK

• Search ran a query over the entire category link table, half a million rows, before it looked at a single keyword. An override on the search class and instant search switched off: the store and its admin are fast again.
• Empty pages with an HTTP 200: PrestaShop's template cache ran a DELETE with LIKE over a 77,000-row table on every product listing, and InnoDB was reading 262,000 rows a second. Found in the slow log, fixed at the source rather than with a restart.
• A PHP-FPM pool of its own for the admin, so a traffic spike on the storefront no longer drags the back office down with it.
• Cloudflare at the edge: abuse blocked through the API, because behind a proxy a firewall rule on the server address blocks nothing. And explicit cache headers, so Safari does not keep an old product page forever.
• Two VAT regimes in one catalogue: used parts under the margin scheme, new parts at 21%, and a product page that actually shows the right label.

THE WORK

• A custom EDC import: products, prices and stock from the wholesaler's XML feed, in batches rather than product by product, with a report on what the feed contained. An item that drops out of the feed goes offline and comes back by itself as soon as stock returns, even when it sits under a configurable parent product.
• Orders go to EDC automatically the moment they are placed. When EDC ships, the status comes back through a webhook: the shipment is created with tracking, and a partial delivery triggers a notification.
• Stock through Magento's Multi-Source Inventory, with a repair route for the inconsistencies MSI leaves behind after large imports, and products matched on EAN alongside the supplier's SKU.
• Hosting managed by us behind Cloudflare, with Varnish, search on OpenSearch and fail2ban rules that block a scanner at account level: caught on this store means blocked on all our sites.
• Deployments through Deployer and Bitbucket Pipelines with a SonarCloud scan, the upgrade to Magento 2.4.8 and PHP 8.3, and affiliate tracking through Tradetracker.

THE WORK

• A content model for cars the dealer maintains without a developer: a sold status with a ribbon over the photo, warranty, and a battery type that only appears when the fuel is electric.
• Six languages without six times the work: fields that need no translation (price, year, mileage) live once in Storyblok, the copy around them comes from i18n.
• Photos through Storyblok's image service, watermarked and sized for each placement, with a lightbox that works on a phone too.
• A rebrand midway through: from Mobiliteitscenter Perry Verbruggen to Brommobiel Boxtel, including new domains, redirects from the old ones and a sitemap that brought the search engines along with it.
• LCP work with Lighthouse as the acceptance test, contact and newsletter forms handled server-side, and a WhatsApp button because microcar buyers call and message, they do not email.

THE WORK

• Magento and PHP on current versions, and the errors and warnings in every custom module from the previous agency cleared before anything new was added.
• A move to a new production server with a full rehearsal first: sync scripts for database and media, a step-by-step migration plan, and a production database whose duplicate URL rewrites had to be deduplicated first, or the new server would never have started.
• From manual uploads to a deploy pipeline from Bitbucket, and error monitoring with Flare so a dealer's error reaches us before the dealer calls.
• The things that bring a dealer portal to a halt: logins that locked after a single failed attempt, add-to-cart with special characters in names, a stuck index, timeouts under load and a SOAP integration that stopped loading order history.
• Search replaced with Algolia, with the category index switched off because on this catalogue it broke more than it delivered.

THE WORK

• From Magento 1 to Magento 2: a full replatform of an international store that kept selling throughout.
• From one server with one administrator to a renowned hosting company, so the store no longer depended on the knowledge and availability of a single person.
• Zero-downtime deployments: a release became routine instead of an evening job with the store in maintenance mode.
• A way of working where there was none: tickets in Jira, all code in Git on Bitbucket, and with that, for the first time, a clear view of what was being built and why.
• Final responsibility for all IT, from hosting and integrations to the developers working on it, so the platform could carry the growth to multi-million revenue.

THE WORK

• From Adobe Commerce Cloud to Magento Open Source on Hypernode: the Enterprise modules out, the data converted, and a new deployment pipeline with Deployer and automatic builds, a database sync for staging, monitoring and a Slack notification on every release.
• Storyblok inside Magento: a custom extension that imports stories from Storyblok, creates URL rewrites for them and renders the content in Magento pages and static blocks. Marketing builds pages without a developer, and the store stays one site.
• The bike configurator: batteries, frame sizes, brakes and wheel sizes as choices, with an extra price per option and the cheapest battery as the starting point. Delivered through an API to the separate product page frontend, with a per-product cache flush from the backend.
• The PIM import: products, prices per store and stock including batteries, with attribute mapping, price validation and metric alongside imperial, so a British customer sees their e-bike's range in miles.
• Leasing as a full sales channel: Lease a Bike as a payment method, a separate stock status with delivery times for lease, and the lowest lease price calculated across all variants. Plus the move to PHP 8.1 and the upgrade to Magento 2.4.7.

THE WORK

• Mail that arrives: DKIM on the domain, sending through Brevo instead of the web server, and the sending limit that was holding back order confirmations tracked down.
• From shared hosting to a server of our own, with Cloudflare in front. After that there was something to measure, and the evening problem was gone.
• Clean-up: plugins nobody used any more disabled and removed, the XML feed to the marketplaces repaired, and Search Console connected.