Returns triage screen
One queue, one decision per row, rules applied at the edge. Replaced a spreadsheet, a shared inbox and a daily phone call between warehouse and customer service.
Six hours a week returned
Projects
Client platforms are my employer’s work, not mine to display, so there is no logo wall here. What follows is the work I can show: packages anyone can install, contributions to Magento core and the shapes of internal tools I have built, described as patterns rather than customers.
Open source
Packagist →Published through Deploy Ecommerce and under my own name. Download counts and stars are indicative; the useful measure is that other people’s production stores depend on them.
Internal tools
Patterns, not clientsOne queue, one decision per row, rules applied at the edge. Replaced a spreadsheet, a shared inbox and a daily phone call between warehouse and customer service.
Six hours a week returned
Compares platform, ERP and WMS on demand, shows the three-way diff and lets an operator replay the feed that drifted rather than raising a ticket.
Drift found before customers find it
CI applies each m2-hotfix to a branch, runs the smoke suite and opens the PR with the diff annotated. A human still reads the hunks and still presses merge.
Patch backlog measured in days, not quarters
Dead-letter queues with the original payload attached, and a screen that lets support replay a failed order safely because the import is idempotent.
Support action, not an engineering one
Talks & appearances
Placeholder rowsStack
What the work touchesDay job
Adobe CommerceMagento 1 & 2Mage-OSLaravelAlso shipped on
SymfonyWordPress / WooShopify APIsNode servicesPHP 4 → 8.4APIs
RESTGraphQLSOAPWebhooksOAuth 2 / JWTMessage queuesIntegrated with
ERPWMS & 3PLPIMPaymentsMarketplacesCouriersTax & EPOSPlatform work for retailers sits with Deploy Ecommerce. Happy to talk through the technical detail in a conversation, references included.
Issues and PRs welcome on anything above. Get in touch for reviews or joint work.