When we started the MedSupply Partners engagement, they were paying PunchOut2Go $50–100/month per connection for cXML middleware. With four hospital procurement networks (Prendio, Dana-Farber, VCU, Penn State), costs were adding up — and the middleware was a black box we couldn't debug.
The Problem with Middleware
PunchOut middleware like TradeCentric/PunchOut2Go sits between your storefront and the buyer's procurement system. Every cXML PunchOutSetupRequest and PunchOutOrderMessage passes through their servers. When something breaks — and with hospital procurement, things break — you're filing support tickets with a third party instead of reading your own logs.
For MedSupply, the specific issues were:
- No visibility into cXML parsing errors
- Buyer-specific pricing wasn't mapping correctly through the middleware
- Cart transfer failures were silent — the buyer would just see a blank cart
- Each new institution required middleware configuration (more cost, more delay)
What We Built
The Fowara Tenant Portal handles cXML natively — 10 files in the .NET backend that parse PunchOutSetupRequest, manage browser sessions with BigCommerce SSO, transfer cart contents back as PunchOutOrderMessage, and inject orders via OrderRequest.
The entire flow is logged, debuggable, and tenant-isolated. Adding a new institution is a database record, not a vendor ticket.
Results
- $50K+/year saved in middleware fees (at scale)
- Full visibility into every cXML exchange
- New institution onboarding: hours instead of weeks
- Quality pipeline: code review → security review → integration tests → E2E before go-live
The lesson: if a critical business flow depends on a third-party black box, and you have the engineering capacity to own it — own it.