// b2b e-commerce & orocommerce developer
i build and extend long-lived b2b commerce platforms — orocommerce enterprise, pim and erp / etl integration, customer-specific pricing and catalogs. also full-stack vue / nuxt and ai-driven document workflows. usually lead developer, engagements measured in years, not months.
large parts catalogs and product information (pim), customer-specific pricing and visibility, corporate buyer accounts, erp / etl integration. orocommerce enterprise with custom symfony bundles — sometimes shopware or magento.
orocommerce ee · symfony · pimautomated reading, validation, and extraction of structured data from regulated documents. pdf ingestion pipelines, external classification apis, async workflows.
laravel · nuxtinternal business platforms for regulated industries — chemicals, occupational safety, product data. multi-tenant, audited, long service life.
php · postgres · elasticsearcharchitecture, small-team leadership, and in-place upgrades that don’t take the platform down. i typically own a product from first release through the team that grows around it.
architecture · upgrades · mentoring// two case studies. both are firm-neutral by client request — stack, architecture, and outcomes are in scope; identity is not.
Full-stack development on an enterprise B2B parts platform — 20+ custom Symfony bundles extending OroCommerce EE, a three-layer per-customer visibility model replacing Oro's stock resolver, SAP Middleware integration, and a Vue 3 machine viewer over interactive equipment sketches.
End-to-end ownership of an AI-driven platform for authoring, validating, and tracking chemical Safety Data Sheets — from PDF ingestion pipelines through to a Nuxt SPA.
b2b e-commerce developer and full-stack engineer, working independently since 2010. my clients are primarily in b2b commerce, industrial manufacturing, and regulated enterprises. most engagements span years rather than months, allowing me to take long-term ownership of the products i build.
i typically serve as lead developer, responsible for the platform from its initial architecture and first release through to the leadership of the small team that evolves around it.
i don’t do drop-in sprints. engagements start with architecture and a first cut of the platform, and i stay long enough that the product still belongs to one mind a few years later.
catalogs in the hundreds of thousands of items, product information (pim) fed from an upstream erp, multi-tenant corporate accounts, in-place migrations on production systems without service interruption.
backend services, apis, and modern web frontends. i do my own ops when the team is small enough to need it, and i hand it off cleanly when it grows.
chemicals, occupational safety, product data, industrial parts. the constraints are interesting and the products outlive their first generation of engineers.
if you’re building a long-lived backend platform — b2b commerce, regulated documents, internal tools that need to be there in five years — i’d like to hear about it.
i take on one new engagement at a time. send the brief and we’ll talk.