Magento 2 / implementation experience
Practical architecture and hands-on engineering for the store, integrations and operations your business depends on.
I’m Daniel Kenney. My more than 15 years of Magento experience span architecture, migrations, integrations and production troubleshooting. I bring that background to Magento 2 implementations and focused improvements.
Implementation capabilities
The work can be a focused improvement or part of a larger implementation. We start with the outcome, the dependencies and the smallest useful scope.
Start with the business processes, existing implementation and technical constraints. Map the store, integrations and dependencies, then agree on a practical implementation plan.
Useful outputs include a system map, implementation priorities and the tradeoffs behind key decisions.
Build focused Magento 2 modules and connect payment, subscription, ERP and operational systems. Make ownership of data, failure handling and the behavior at each system boundary explicit.
The implementation should fit the platform’s extension points and your existing codebase, with changes that your team can review and maintain.
Plan catalog, customer and order mappings before moving data. Work through consolidation rules, identifiers, relationships and reconciliation, then test the migration process against representative data.
My Mediotype work included tooling to consolidate multiple Magento 1 stores into one Magento 2 installation across catalog, customers and orders.
Follow evidence across application code, pricing and promotions, caches, infrastructure and integrations. Use observability to narrow the problem, reproduce it where possible and validate a focused fix.
Historical work with New Relic, Varnish, Akamai and NetSuite informs that approach; the tools and investigation should fit your environment.
Keep implementation scoped and inspectable. Review the code, test important commerce behavior and prepare deployment, recovery and handover steps with the people who run the store.
A passing local test is one checkpoint. Release readiness also depends on your environment, operational constraints and agreed acceptance criteria.
Selected historical experience
These examples describe past responsibilities across Magento and ecommerce roles.
Architecture & technical leadership
Solutions architect & lead engineer
The Magento 2 work combined solution design with hands-on engineering: translating requirements, coordinating distributed delivery, and resolving behavior across pricing, promotions and caching.
Magento 1 → Magento 2
Magento project & migration leadership
Led primarily Magento 2 projects and Magento 1-to-2 migrations, including tooling that consolidated multiple Magento 1 stores into a single Magento 2 installation. That work spanned catalog, customer and order data, where mapping, reconciliation and integrity matter as much as moving records.
Connected commerce systems
Payment, subscription & ERP integrations
Worked on payment, subscription and ERP integrations, along with Magento 1 upgrades. This experience informs how I approach dependencies across checkout, recurring orders, back-office operations and platform changes.
Production diagnosis
Performance & integration troubleshooting
Troubleshot Magento 1 production behavior involving New Relic, Varnish, Akamai and NetSuite. The work connected application symptoms with caching, infrastructure and ERP dependencies rather than treating each system in isolation.
These examples describe historical work and do not imply current employment or client endorsement.
How delivery works
I can work directly with you or alongside your engineers and agency. The implementation should fit your conventions, release process and responsibilities.
Understand the current system, define success and agree on scope, dependencies and estimates.
Use focused tasks and agent-assisted development where appropriate, under my direction and code review.
Test relevant commerce and integration behavior, prepare operational steps and support an agreed release and handover.
Getting started
Tell me where customers encounter purchase friction and where operations slow your team down. We’ll look for ways to improve the customer experience, streamline operations and uncover revenue opportunities, then agree on a useful first step, scope and estimates.
Discuss your projecthello@kenneylabs.comMagento 2 engineering: $75/hour. Scope, estimates and engagement terms agreed before work begins.
