Business Systems & ERP/WMS Modernization
Rearchitecting how Fullscript's commerce platform talks to NetSuite and the WMS — cutting transaction load by 43% and unlocking cross-subsidiary fulfillment.
Problem
The integration layer between our commerce platform, NetSuite ERP, and our warehouse management system had grown organically for years. It was generating an enormous volume of NetSuite transactions, was brittle to schema changes, and could not support the cross-subsidiary fulfillment model Fullscript needed to grow.
Context
Healthcare commerce platform serving 70,000+ practitioners and millions of patients. Strict accounting and inventory accuracy requirements. Multiple subsidiaries with different fulfillment networks. Legacy integration patterns predating the current scale.
What changed
- Led the team through a redesign of the order-to-cash and fulfillment integration to consolidate redundant transactions.
- Partnered with platform engineering to rework the invoicing pipeline so it leveraged native NetSuite capabilities instead of custom middleware.
- Co-designed and shipped cross-subsidiary fulfillment with the WMS and finance partners — an order in one entity could be fulfilled by another without manual reconciliation.
- Worked with the architecture group to establish alignment standards so future integrations followed the same patterns.
Systems introduced
- Consolidated NetSuite integration patterns
- Native-NetSuite invoicing pipeline replacing custom middleware
- Cross-subsidiary fulfillment workflow
- Carrier API rate-shopping integration
Measurable impact
- 43% — NetSuite transaction reduction
- 95% — Invoicing maintenance overhead reduction
- $3M+ — Carrier savings (2 years)
- 70K+ — Practitioners served on platform
Lessons learned
- The cheapest integration is the one you don't write — lean on the platform first.
- Transaction volume is a tax; reducing it pays compound interest in cost, performance, and reliability.
- Modernization works best when it's tied to a business outcome the org actually wants.
Scaling BSE Project Throughput by ~300%
How we tripled what the Business Systems Engineering org could ship without adding headcount — by fixing the operating model, not the people.
Building Asynchronous Information Flow with Asana
Replacing status meetings and Slack archaeology with a single async source of truth across five business divisions.