the specialty — supply-chain integration

The integration layer between your commerce systems and your warehouse.

WMS, OMS, ERP, dropship — connected with event-driven architecture that survives peak. I design it, I build it, and I'm on-site when it goes live.

WMS / WESOMSERPEDIdropshipKafkaevent-drivenidempotencyKubernetesTerraformgo-livepeak readiness
01

When to call me

These projects have hard dates and no second chances. That's the work I take.

A new fulfillment center is coming online

Integration architecture from day zero — event contracts, system boundaries, and the failure modes nobody scoped.

You're migrating or replacing a WMS

Cutover without losing orders: parallel-run strategy, idempotent replays, and a rollback path that actually works.

Your OMS or ERP is changing underneath everything

Keeping fulfillment running while the system of record moves — translation layers, versioned events, staged migration.

Peak season is closer than it looks

Throughput, backpressure, dead-letter hygiene, and the on-call runbook — assessed and fixed before November, not during it.

the proof

Five years inside Nordstrom's supply-chain technology.

I joined as a consultant through PeloTech in 2018. A year later, Nordstrom hired me full-time — the strongest endorsement a consultant can earn. Through 2023, I architected and built their warehouse integration across four major workstreams:

  • 3P dropship integration — event-driven integration with a third-party dropship service, built for high availability and throughput on Java and Kafka.
  • WMS integration — architected the event-driven system translating events between third-party warehouse systems: 22 microservices on Kubernetes, Terraform, GitLab CI/CD — as technical lead for the engineering team.
  • Omnichannel warehouse launch — supported the go-live of a new omni-channel fulfillment facility, where the integration layer had to be right on day one.
  • WMS evaluation — evaluated top-tier WMS platforms for selection, so I know the vendor landscape from the inside.
02

How we can work together

Fixed scope, written deliverables, and a price agreed before anything starts.

fixed-scope · ~2 weeks

Integration Architecture Review

A structured review of your fulfillment integration — event flows, failure modes, idempotency, observability — with written findings, a risk register, and a prioritized roadmap. The low-risk way to start.

fixed-scope · before peak

Go-Live & Peak-Readiness Assessment

For a launch or a holiday season that can't slip: load and backpressure analysis, replay and recovery drills, cutover planning, and the runbook your on-call team will actually use.

advisory · vendor-neutral

WMS Evaluation & Selection Support

An engineer's view of the WMS landscape — evaluation criteria, integration-cost reality checks, and reference architecture for whichever platform you choose. I don't take vendor commissions.

project · architecture + build

Integration Architecture & Build

The main event: I design and build the integration layer — event contracts, services, infrastructure, delivery pipelines — and stay accountable through go-live, on-site if that's what the cutover needs. I work with modern AI-assisted tooling, which is how one accountable architect keeps a team's pace; the judgment and the review are always mine.

For implementation partners

If you're an SI or WMS implementation partner short on senior integration engineers mid-rollout: I take a small amount of overflow work, with zero ramp on event-driven integration. Quiet, reliable, and your client never waits on me.

Have a go-live on the calendar?

Tell me what's launching, migrating, or keeping you up at night. I'll tell you honestly whether I can help — and the simplest path if I can.

Get in touch