Production

Comparing Factory Quotes in Apparel Without Spreadsheet Drift

Comparing Factory Quotes in Apparel Without Spreadsheet Drift
By Shubham Singh · Reviewed by Venkat Koripalli · · 10 min read

A production manager at a $15M contemporary brand pulls up three factory quotes for the same wool blend coat. Factory A quoted $42 FOB Shanghai, MOQ 300 per colorway. Factory B quoted $39 FOB Ho Chi Minh, MOQ 500 per style. Factory C quoted $46 FOB Porto, MOQ 150 per colorway, with a 30 day shorter lead time. She opens a spreadsheet. By the time she has converted MOQs, added estimated duty, guessed at freight, and tried to value the lead time difference, it is Thursday afternoon, the costing meeting is Friday morning, and two of the quotes are missing the trim line. She picks Factory B because it is cheapest at FOB. Six months later, the landed cost is higher than Factory A would have been.

What does it actually mean to compare factory quotes in apparel?

To compare factory quotes apparel teams must move past the FOB number and normalize every quote to a landed, all-in unit cost tied to a specific style, colorway, and order quantity. A factory quote is not a price. It is a bundle of assumptions: a fabric consumption estimate, a trim list, a labor rate, an MOQ, an Incoterm, a lead time, a payment term, and a set of implied surcharges (sampling, lab dips, grading, size breaks outside a standard range, late fabric arrival). Comparing quotes means comparing those bundles, not the headline numbers.

Most apparel brands in the $5M to $100M band do this in spreadsheets. The spreadsheet is rebuilt for every style. The line items vary by who built it. Last season’s costing logic is not auditable. That is the drift.

Why do spreadsheets fail at quote comparison?

The failure is not that spreadsheets are bad. The failure is that a quote comparison is a structured data problem disguised as a one-off document. Three things break.

First, the line items are not standardized across vendors. Factory A breaks out trims separately. Factory B bundles trims into the cut-make rate. Factory C lists fabric at a per-meter rate and assumes a consumption you cannot verify without the marker. When you paste these into a spreadsheet, you are not comparing apples to apples. You are comparing three different cost structures that happen to end in a dollar sign.

Second, the unit of comparison shifts. Sometimes the operator compares per-unit FOB. Sometimes per-unit landed. Sometimes total order value at MOQ. Sometimes margin at planned retail. Each of these tells a different story, and the spreadsheet rarely makes the choice explicit.

Third, the comparison is never linked to the style record. The quote lives in an email or a PDF. The spreadsheet lives on someone’s desktop. The style sits in a PLM or, more often, in a different spreadsheet. When the costing decision is made, there is no audit trail back to the assumptions that drove it. Six months later, when the landed cost comes in 14 percent higher than the quote, no one can reconstruct why.

This is breakpoint 2 of the 6 Breakpoints framework: production and supply execution drift from the plan. The drift starts at quote comparison and compounds through every PO, every fabric commitment, every shipment.

What does a normalized quote comparison actually look like?

From the fit calls I run with prospects each week, the brands that have escaped spreadsheet drift have done one specific thing: they have defined a fixed cost structure that every vendor quote gets force-fit into before it enters the comparison. The structure is non-negotiable. The vendor can quote however they like, but the production team translates it into the same lines every time.

The lines worth standardizing, at a minimum, are these.

  • Fabric cost at the planned consumption (with the consumption itself a tracked field, not assumed)
  • Trims, broken out, not bundled into cut-make
  • Cut-make-trim labor at the quoted rate
  • Sampling and lab dip fees, amortized across the order
  • Estimated duty by HTS code and origin
  • Freight, with the Incoterm explicit and the mode (sea, air, sea-air) called out
  • Payment terms, converted to a working capital cost
  • MOQ exposure, expressed as the cost of the units beyond the buy plan
  • Lead time, expressed in days from PO to ex-factory

That last point matters. Lead time is not a soft variable. A 30 day shorter lead time on a seasonal style is the difference between catching a reorder window and missing it. If you cannot price that into the comparison, you are not comparing quotes. You are comparing FOBs.

How should MOQ exposure get priced into the comparison?

This is the line item that kills more margin than any other, and it almost never makes it onto the spreadsheet.

If the buy plan calls for 220 units of a colorway and the factory MOQ is 500, you are not buying 220 units at $39. You are buying 500 units at $39, and 280 of them are going to sit. The question is what those 280 units cost you. If they sell through at full price six months late, the cost is the working capital and warehouse storage. If they go to markdown, the cost is the margin gap. If they go to a jobber, the cost is most of the unit cost.

A conservative rule: assume the units beyond your buy plan recover 40 to 60 percent of cost. Subtract that from the order value. Recompute the effective unit cost on the units you actually planned to sell. Now compare.

In the example at the top, Factory B at $39 with MOQ 500 against a buy plan of 300 is not $39 per unit. It is something closer to $50 per planned unit after the MOQ exposure is priced in. Factory C at $46 with MOQ 150 is $46. The cheapest quote, on paper, was the most expensive in practice.

When does the comparison need to live in the production module, not a spreadsheet?

Across the comparison conversations I have run this quarter, the threshold is consistent. If you are sourcing more than roughly 40 styles per season across more than three factories, the spreadsheet stops working. The reason is not volume. The reason is that the quote, the style, the BOM, the costing, and the eventual PO have to stay in sync, and a spreadsheet cannot enforce that sync.

When quote comparison sits inside the production module, three things change. The BOM that drives the quote is the BOM that drives the PO. If the trim spec changes, the quote is flagged as stale. If the fabric consumption is revised after the first sample, the costing rolls forward. The audit trail is built in. Six months later, when finance asks why the landed cost diverged, the answer is one click, not a forensic exercise.

This is also where the 6 to 9 hours per week of reconciliation work at a $15M brand starts to compress. That number is the visible cost of disconnected operations. The invisible cost is the decisions made with bad data, and quote comparison is one of the cleanest examples of it.

Why do landed cost estimates drift from quoted FOB?

The drift between FOB and landed is rarely random. It is structural, and it is predictable if the comparison framework is built for it.

Duty is the first source. HTS classifications vary by fiber content, construction, and gender, and the difference between an 8.5 percent rate and a 16 percent rate is decided by a single line on the customs declaration. If the quote does not specify the HTS code and origin, the duty estimate in the comparison is a guess.

Freight is the second. A factory quoting FOB has handed you the cost from their door to the port. Everything from the port to your warehouse is yours, and ocean freight rates in the post-2021 environment have moved enough that a stale estimate can be off by hundreds of dollars per cubic meter. Comparing two FOB quotes without current freight from each origin is comparing two incomplete numbers.

Surcharges are the third. Fabric late by more than two weeks: surcharge. Size break outside the standard range: surcharge. Repeat lab dip: surcharge. These show up on the invoice, not the quote. A factory with a tighter surcharge policy can be cheaper at quote and more expensive at landed than a factory that prices the surcharges into the base rate.

The POV here is simple. Comparing factory quotes at FOB is not comparison. It is a screening step. The real comparison happens at landed unit cost, at the planned buy quantity, against the planned retail.

How should sample rounds and lead time factor into the decision?

Sample rounds are a cost the spreadsheet almost never captures. A factory that takes four rounds to hit the fit target has not just spent your sampling budget. It has burned six to eight weeks of the development calendar, and on a seasonal style, that calendar is the constraint.

Lead time should appear in the comparison as a dollar value, not a date. The conversion is rough but defensible. If a 30 day shorter lead time lets you place a reorder that you would otherwise miss, the value of those 30 days is the margin on the reorder. If a 30 day longer lead time pushes the delivery into a markdown window, the cost is the margin gap on the original buy.

A factory that quotes $2 higher per unit but ships 30 days earlier on a 1,500 unit order is, at a 50 percent sell-through assumption, often the cheaper choice. The spreadsheet rarely shows this because the spreadsheet does not know what selling season the style is for.

What does the costing meeting look like when this works?

When quote comparison is normalized and lives inside the production module, the costing meeting changes shape. The conversation stops being about whose number is right and starts being about which trade-offs the brand wants to make.

Factory A is $3 more per unit but holds a tighter MOQ and ships in 90 days. Factory B is cheaper at FOB but the duty and MOQ exposure put it ahead at landed. Factory C is the most expensive on paper but the lead time advantage is worth $4 per unit on the planned sell-through. The merchant and the production lead are now arguing about strategy, not arithmetic.

This is what BP2 looks like when it is held. The plan and the execution stay close because the costing decision is auditable, the assumptions are explicit, and the comparison is structured the same way every season.

What this means for an apparel operations team

Quote comparison is not a procurement task. It is a data architecture task that touches PLM, production, and finance. If the comparison happens in a spreadsheet that is rebuilt every season, the brand is rediscovering the same costing mistakes every season. The 6 to 9 hours per week of reconciliation work at a $15M brand is the symptom. The cause is that the operational data is not connected, and quote comparison is one of the places where that disconnection costs the most.

The fix is not better spreadsheet templates. The fix is to define the cost structure once, hold every vendor to it, and keep the comparison tied to the style record from quote through PO through landed cost. The brands that do this stop losing margin to MOQ exposure they did not price in and surcharges they did not anticipate.

The production lead, the sourcing manager, and the CFO should all be able to open the same costing record six months after the decision and reconstruct why it was made. If they cannot, the next decision is being made with worse information than it should be.

6 Breakpoints Framework

Where is your operation on the 6 Breakpoints curve?

The assessment scores your apparel operation across all six breakpoints (product data, production, inventory truth, order flow, warehouse execution, reporting) and identifies which one is hurting you most.

Frequently asked questions

Where this fits in the Uphance platform

S
Written by
Shubham Singh
Solutions Consultant, Apparel Operations, Uphance

Shubham writes about evaluating ERP fit, assessing operational complexity, and how apparel brands can tell whether their current systems are helping or holding them back. As a Solutions Consultant at Uphance, he runs discovery conversations and fit assessments for apparel brands moving off patchwork stacks of PLM, PIM, inventory, and B2B tools. His articles cover ERP selection, vendor RFPs, comparison frameworks, and the operational signals that tell a brand it has outgrown spreadsheets and point solutions. He focuses on how mid-market apparel teams evaluate connected platforms against the cost of staying with what they have.

V
Reviewed by
Venkat Koripalli
Founder & CEO, Uphance

Venkat is the Founder and CEO of Uphance and the author of the 6 Breakpoints of Apparel Operations framework. He writes about operational clarity for apparel brands as complexity grows across channels, warehouses, partners, and teams. His work focuses on why disconnected operations, not growth itself, create the chaos most mid-market brands feel between $5M and $100M in revenue, and on the operating-model patterns that decide whether scaling a brand strengthens execution or fractures it. He argues that the status quo is the real competitor in apparel software, and that the right move is fewer systems with deeper connection, not more dashboards.

More from the blog