Architecture / Commerce
Commerce Architecture
Designing commerce platforms that survive their next replatform — domain model, integration boundaries, and a route off whatever you are on now.
Most commerce platforms are not badly built. They are built for a business that no longer exists. The catalogue grew, the channels multiplied, a marketplace got bolted on, and the seams that were reasonable in year one became the reason nothing ships in year six.
The work is deciding where the boundaries belong now, and finding a migration path the business can actually afford. That usually means running new services alongside the old core rather than attempting a rewrite, so the roadmap keeps moving while the architecture changes underneath it.
I have done this on Oracle Commerce ATG, on commercetools, and on the awkward middle ground where a company is halfway between the two.
Where this has been done
Technical Architect
Owned the commerce architecture for kohler.com across US and Canada, including long-term platform direction and the CI/CD pipeline the team shipped through.
Application Support Lead
B2B commerce on boeingdistribution.com — a platform I first built features for in 2013, when it was KLX Aerospace.
Sr. Developer
Owned the ATG/Endeca REST surface end to end — PDP, PLP, cart, checkout, promotions — and restructured the API so it could move off ATG later.