What Is the Buying Committee in an Apparel ERP Deal and How to Read It

It is a Thursday in late September. A $22M contemporary womenswear brand has six people on a video call: the COO, the CFO, the head of wholesale, the ecommerce director, the production manager, and a fractional IT consultant. They are 40 minutes into a software demo and the conversation has fractured. The CFO is asking about month-end close and revenue recognition across channels. The head of wholesale is asking about EDI 850 ingestion from a specific Nordstrom routing guide. The ecommerce director keeps returning to Shopify inventory sync timing. The production manager has not spoken in 15 minutes. Nobody in the room actually disagrees that the current setup is broken. They just cannot agree on what to fix first, or who decides.

What is the apparel erp buying committee and why does it behave this way?

The apparel erp buying committee is the cross-functional group inside a wholesale plus DTC apparel brand whose collective agreement is required to replace spreadsheets, QuickBooks, a 3PL portal, a PLM tool, and a Shopify backend with a connected operations system. It is not a procurement committee in the traditional enterprise sense. It is a working group of operators who each own a piece of the chaos and each have a different definition of what success looks like.

In the $5M to $100M revenue band, the committee almost always includes six roles: a COO or head of operations, a finance owner (CFO or controller), a wholesale or sales operations lead, an ecommerce or DTC lead, a production or sourcing lead, and an IT or systems owner (often fractional or outsourced at this size). Founders sit in too, usually as the tiebreaker rather than the driver. Each of these people reads the same demo through a different lens, and that is the thing most vendors get wrong.

Why does the committee fracture during evaluation?

The committee fractures because the operational pain is distributed unevenly across the org. The COO sees the cost in hours. The CFO sees it in close timing and chargebacks. The wholesale lead sees it in retailer compliance penalties. The DTC lead sees it in oversells during a drop. The production manager sees it in cut tickets that no longer match the PO that triggered them. None of them are wrong. They are each describing a different breakpoint inside the same brand.

From the fit calls I run with prospects each week, the most common failure mode is that the brand has framed the evaluation as a software selection problem when it is actually an operational architecture problem. The deck has a feature matrix. The matrix has 80 rows. Three vendors get checkmarks against most rows. The committee then argues about the checkmarks instead of about which workflow is actually breaking the business.

For a $15M brand running wholesale plus DTC plus a 3PL, the back-of-envelope cost of the status quo is six to nine hours a week reconciling inventory across Shopify, the 3PL portal, and the wholesale system, a two to three percent oversell rate at peak, and effectively one FTE doing data plumbing instead of merchandising or planning. That is the number the committee should be aligning on, not the feature matrix.

How do you read each seat on the committee?

Reading the committee well means knowing what each person is actually optimizing for, which is usually different from what they say in the kickoff call. Below is how the six seats typically read in this revenue band.

What does the COO or head of operations care about?

The COO is the only person on the call who is paid to see the system end to end. They care about whether a single order, from a wholesale PO or a Shopify checkout, flows cleanly through allocation, pick, pack, ship, and invoice without human intervention. Their objection language sounds like “we are spending too much time in spreadsheets,” but what they are really asking is whether the new system removes the manual reconciliation step between three tools. If the demo shows a connected order flow, the COO is usually the first advocate.

What does the CFO or controller care about?

The CFO is reading the deal through breakpoint six of the 6 Breakpoints framework, the one where reporting becomes reactive and political instead of operational. They care about how long month-end close takes, whether revenue by channel ties back to the GL without a Friday-night spreadsheet, and whether wholesale chargebacks and DTC returns post to the right period. Their hardest objection is almost never about cost. It is about whether the numbers in the new system will match the numbers in QuickBooks or NetSuite at close.

What does the wholesale or sales ops lead care about?

This person lives in EDI documents, retailer routing guides, and ASN deadlines. They care about whether the system can ingest an 850, send an 856 within the retailer’s ship window, and generate a UCC-128 label that the major accounts will not reject. Their objection language is the most technical on the call and the most ignored. Lufema is a useful reference point here: multi-entity wholesale across multiple brand catalogs through a B2B portal is the kind of complexity that exposes whether a vendor actually understands wholesale or has bolted it on.

What does the ecommerce or DTC lead care about?

The DTC lead is reading the deal through inventory truth and order flow. They care about whether ATS on Shopify reflects what is actually pickable at the 3PL, whether a same-day drop will oversell, and whether returns get processed back into available inventory in days rather than weeks. Magnolia Pearl is the proof point here: drop cycles, same-day fulfillment, international duties on returns. If the DTC lead cannot trust the inventory number that Shopify shows the customer, every other feature in the demo is theoretical.

What does the production or sourcing lead care about?

The production manager is the quietest seat and the one most often skipped. They care about whether the PO that goes to the factory is the same PO that lands in inventory as a receipt, whether style attributes carry from PLM into PIM without rekeying, and whether a fabric substitution at the mill propagates back into the product record. Their objection is rarely raised in the demo. It surfaces three months into implementation when data does not line up.

What does the IT or systems owner care about?

At the $5M to $100M band this role is usually fractional or outsourced. They care about integration patterns, who owns the API contract with Shopify and the 3PL, and whether the vendor will own the EDI maps or pass that to a third party. Their objection language is about ownership boundaries, not technology. If they cannot tell who is on the hook when the 3PL changes its export format, they will block the deal.

What objections actually predict a stalled evaluation?

The objections I hear most often in evaluations are not the ones that kill deals. The objections about price, contract length, and implementation timeline are surface-level. They get negotiated. The objections that predict a stalled evaluation are the ones where two people on the committee are describing the same workflow in incompatible terms.

A real example: the wholesale lead says “we need allocation logic that respects committed pools.” The DTC lead says “we need Shopify ATS to be accurate.” These are the same problem. They are both asking for channel-aware available-to-sell, where wholesale-committed inventory is netted out of the DTC pool before Shopify ever sees the number. If the committee does not realize these are the same request, the evaluation will stall because each person thinks the other is asking for something different.

The second pattern is when finance asks for a clean close and ops asks for real-time inventory, and nobody connects the two. They are connected. If inventory movements do not post to the GL in near real time, finance will close late, and the brand will spend the first ten days of every month rebuilding the prior month from spreadsheets. This is breakpoint six in plain English.

What is the right way to run the committee?

The right way is to stop running the evaluation against a feature matrix and start running it against the 6 Breakpoints. Each seat on the committee owns one or two breakpoints. Map the objections to the breakpoints, and the conversation gets clearer in about an hour.

Product data fragmentation (breakpoint one) is owned by production and DTC merchandising. Production and supply execution drift (breakpoint two) is owned by the production manager. Inventory truth (breakpoint three) is owned jointly by ops and DTC. Order flow (breakpoint four) is owned by wholesale and DTC. Warehouse execution (breakpoint five) is owned by ops, with the CFO as a secondary stakeholder because of chargebacks. Reporting (breakpoint six) is owned by finance and the COO.

Once the committee can see which seat owns which breakpoint, the feature matrix collapses. The question stops being “which vendor has more checkmarks” and becomes “which vendor closes the breakpoints that are actually costing us money this quarter.”

What is the point of view the committee should adopt?

Wholesale should not run through Shopify’s native flow. That is the single most useful POV to bring into the evaluation because it forces the committee to confront a decision that almost every $10M to $20M brand has been avoiding. Shopify is excellent at DTC. It is not built to honor wholesale ship windows, EDI compliance, B2B pricing tiers, or allocation against committed pools. When a brand tries to make Shopify do both, the cost shows up as oversells, chargebacks, and a CFO who cannot close the books.

The corollary POV: if retailer chargebacks exceed one percent of wholesale revenue, the integration is the problem, not the warehouse. The committee tends to blame the 3PL. The 3PL is usually executing what the system tells it to execute. The real failure is upstream, in how the 850 was ingested, how the ship window was calculated, and whether the 856 went out before the appointment.

When should the committee bring the founder in?

The founder belongs in two moments and no others. The first is the framing conversation, where the committee agrees on which breakpoints are in scope and which are deferred. The second is the final architecture decision, where the trade-off between speed of implementation and depth of integration gets made. In between, the founder should stay out. Founders who sit through every vendor demo distort the conversation because their authority outweighs the operational expertise of the people who will actually use the system.

What this means for an apparel operations team

If you are about to start an evaluation, the work before the first demo matters more than the demos themselves. Map your committee to the 6 Breakpoints. Identify which breakpoints are costing you measurable hours and dollars right now. Write down the back-of-envelope numbers, six to nine hours a week on reconciliation, two to three percent oversell at peak, one FTE on data plumbing, and use those as the scorecard.

Then read each seat on the committee for what they actually optimize for, not what they say in the kickoff. The COO wants end-to-end flow. The CFO wants a clean close. Wholesale wants EDI that does not generate chargebacks. DTC wants ATS that matches reality. Production wants data that does not get rekeyed. IT wants clear ownership of the integration surface.

If the committee can hold those six lenses at the same time and agree on which breakpoints to close first, the evaluation will take eight to twelve weeks instead of nine months. If it cannot, the brand will buy the wrong system or, more often, buy no system and spend another year on spreadsheets.