Apparel procurement runs on two buying clocks that almost never synchronize. The pre-season clock fires 5–8 months before a collection reaches the floor: a boutique buyer committing to Fall/Winter styles in March, writing purchase orders against a seasonal budget before a single unit has sold. The replenishment clock fires continuously: core basics, carryover bestsellers, and any style that sells through faster than planned need reordering against live stock signals — not seasonal assumptions. Closed-loop procurement is the buying workflow where each step — demand signal, purchase order, supplier confirmation, receiving, and accounting handoff — feeds the next in one connected record without retyping. For an apparel business, that loop is what holds both clocks in sync across a catalog that changes every season and a supplier roster spread across multiple time zones and channels.
What makes apparel procurement different
Five structural facts separate apparel procurement from general retail buying:
Minimums may apply by style, color or size run. A white linen shirt is not one item from a wholesale brand's perspective. It is a matrix: Small, Medium, Large, XL in the same colorway — plus any additional colors the buyer wants to carry. A supplier may set minimums per size run or colorway, meaning a buyer who wants one color of one style must commit to a full size distribution to clear the minimum order quantity. A procurement system that tracks the shirt as a single SKU with one reorder point will misrepresent both what was ordered and what needs to be replenished.
Seasonal pre-buys are committed before demand is known. Pre-season orders are placed months before delivery and carry contractual commitment: deposit, cancellation and delivery terms depend on the agreed contract. A boutique committing $40,000 in Spring/Summer pre-buys in October is working against a sales plan and historical trend, not actual sell-through. If the season underperforms, that inventory arrives fully obligated into a markdown cycle.
Read before ordering
A dense operator briefing for teams that need sharper buying, cleaner supplier follow-up, and fewer expensive surprises.
Delivery arrives in multiple waves. Most wholesale brands ship pre-buy orders across two or three delivery windows: a first drop of core styles, a second drop of fashion pieces a month or two later, sometimes a third. A single purchase order can span three receiving events across three months. Software that assumes one PO equals one delivery cannot track which units have arrived and which are still in transit.
Markdown pressure makes overbuying expensive.Slow-moving inventory in apparel compounds faster than in most categories because style relevance decays alongside physical shelf life. An extra 8 units of a fashion color that did not resonate becomes a 40% markdown event — not a reorder at cost. The carrying cost of wrong-season apparel runs well above the 20–30% annual holding rate for generic durables.
Imported stock needs a full cost comparison.Landed cost includes relevant freight, duty, insurance and handling in addition to the supplier price. Use shipment-specific inputs and the accounting team’s approved allocation policy.
Open-to-buy: the budget that must become purchase orders
Open-to-buy (OTB) is the financial planning framework most apparel buyers use to control seasonal spend. The formula:
OTB = Planned Sales + Planned EOM Stock + Planned Markdowns − BOM Stock − On Order
OTB establishes the dollar budget available for new orders in a period without overshooting planned inventory investment. A boutique planning $120,000 in annual purchases uses OTB to allocate that budget by season, by category, and by vendor — ensuring a favorite brand's Fall collection does not consume budget needed for basics reordering in Q4.
The execution gap OTB creates: the formula tells you how much to buy. It does not tell you what happened to what you bought. Whether the pre-buy POs were confirmed by suppliers, when Wave 1 arrived, what was substituted, what the final received cost was after a price change, what AP should see — none of that is OTB. That is procurement execution.
A living PO connected to a pre-buy commitment tracks each delivery window as a separate receiving event. When Wave 1 of a Fall/Winter order arrives in early September — 44 units across three colorways — that event closes the first delivery window, updates on-hand inventory by variant, and surfaces the Wave 2 expected arrival. Accounting sees a partial receipt against the PO. The balance of committed inventory remains on-order, not yet in cost.
Faire and the wholesale ordering channel
A boutique may use Faire alongside direct brand accounts. Confirm the payment and return terms for the particular order, including eligibility and exclusions, rather than assuming every order has the same credit or return policy.
It does not simplify receiving. A Faire order generates a physical shipment with a packing list, line items that may or may not match the order exactly, and an invoice that flows through Faire's system. Brands substitute sold-out styles. Shipments arrive in multiple cartons across multiple days. Receiving quantities sometimes differ from invoice quantities.
Those discrepancies belong on a living PO — captured upstream before accounting inherits the bill — not in a separate reconciliation process conducted from a Faire order history page.
For boutiques ordering from Faire and direct-wholesale brands simultaneously, the procurement challenge is a unified view: what is confirmed, what is in transit, what has been received, what has been invoiced, across all channels. A buyer who tracks Faire orders in one place and direct-brand orders in a spreadsheet has two partial pictures of their inventory position, not one.
Replenishment: basics, bestsellers, and the size-run constraint
Seasonal pre-buys are planned; replenishment is reactive. For apparel, replenishment applies to two categories with different mechanics.
Core basics — white tees, classic denim, everyday socks — have stable, predictable demand and respond to standard reorder point logic (run your own numbers with the reorder point calculator):
ROP = (consumption rate × lead time) + safety stock
For a white crew-neck tee selling 10 units per month, with a 14-day domestic supplier lead time and a 95% service level (z = 1.65, σ = 2.5 units per month):
safety stock = 1.65 × 2.5 × √(14/30) ≈ 2.82 units → round up to 3
ROP = (10/30 × 14) + 3 ≈ 8 units on hand
That reorder point is a practical trigger for a basics replenishment PO. Blanket purchase orders for basics work well with domestic suppliers: a standing commitment for a seasonal quantity at a locked price, drawn down through individual releases when stock reaches the reorder point. The supplier gets volume predictability; the buyer gets price certainty across the season.
Bestseller replenishment is judgment-adjacent even when well-supported by data. A style tracking 160% of planned sell-through in Week 4 of the season is a candidate for a reorder — but only if: the brand has inventory remaining, the lead time allows delivery before the season ends, and the MOQ for the reorder is viable against the expected remaining sell-through. If the season has six weeks remaining, the supplier needs two weeks to ship, and the MOQ is 12 units, the decision is: will 12 units sell in four weeks at full price? That judgment belongs with the buyer. The procurement system handles the execution once the decision is made.
Size distribution in replenishment orders. Even when a style sells well in aggregate, the size distribution in replenishment may differ from the original buy. If the original size run was 2S / 4M / 4L / 2XL and Medium sold out first, the replenishment run might be 0S / 6M / 2L / 0XL. A system that only tracks the total quantity, not the size-level breakdown, will generate incorrect replenishment quantities.
Receiving apparel: variant accuracy, wave tracking, and substitutions
Apparel receiving has a complexity layer most procurement systems flatten: variant-level accuracy within a style shipment. When a carton of 12 shirts arrives — 2 Small, 4 Medium, 4 Large, 2 XL — the receiving event must capture those quantities at the variant level, not as 12 undifferentiated units.
Why variant-level receiving matters:
Inventory accuracy. If the system records "12 shirts" without capturing the size breakdown, the first sale of a Medium will draw down inventory incorrectly. Count discrepancies surface at physical inventory, not at the moment they are created.
Invoice reconciliation. Brands occasionally ship size allocations differently from what was invoiced — 3 Large shipped where the invoice says 4, with an adjustment note buried in the packing slip. Those differences belong on the living PO before the invoice is approved.
Substitution tracking. A brand that ships a substitute colorway for a sold-out one has made a change that affects every downstream record: inventory by color, expected margin per style, and recipe/BOM costing if the item is part of a gift set or bundle. The substitution is captured as a supplier-confirmed change on the living PO, not discovered at count.
Supplier communication around delivery — tracking numbers, wave arrival dates, partial-shipment notices — should update the living PO before the carton arrives. A buyer who knows Wave 2 is delayed three weeks can adjust in-season markdown timing; a buyer who finds out at receiving has already lost that option.
Compare the full landed cost
Compare a complete quote rather than applying an economy-wide tariff average to a garment. Classification, origin, applicable trade measures, shipment terms and fees affect the actual import cost; obtain the shipment-specific inputs from the broker or responsible import specialist.
For an illustrative unit-cost comparison, assume a $12 purchase price, $1.80 freight, $1.64 duty supplied for the example, $0.25 insurance and $0.35 handling:
Total modeled unit cost = 12 + 1.80 + 1.64 + 0.25 + 0.35 = $16.04
Gross margin at $24 selling price = (24 − 16.04) / 24 = 33.17%
The $1.64 duty is an assumed input, not a current tariff quote. Accounting determines which actual costs belong in inventory and when they become cost of goods sold. A recorded freight line and per-unit cost allocation are separate capabilities to verify.
Compare alternate suppliers on equivalent specifications, delivery windows, landed cost and approved sourcing criteria. Do not assume a particular country is always the lower-cost option.
What to look for in procurement software for apparel
Six requirements that distinguish purpose-fit tools from general inventory systems:
Variant-level inventory (size × color matrix). The system must track inventory at the size-color variant level natively — not through single-SKU workarounds — so receiving, reorder points, and sell-through analysis all reflect the actual variant mix.
Multi-wave delivery tracking per PO. A pre-season PO with three delivery windows must be receivable in three separate events, each of which updates inventory and closes its delivery window independently. The PO should show total committed, received to date, and remaining expected.
Supplier reply parsing across channels. Brands confirm via email, Faire platform notifications, or brand portals. The system should absorb confirmations, substitution notices, and shipping updates from any channel and update the living PO without manual reentry.
Landed cost allocation. Duty, freight, and handling should be allocatable to the PO at receiving so on-hand unit cost reflects the true COGS basis from day one.
Multi-supplier and multi-channel order management. Faire orders and direct-brand orders should flow through the same procurement workflow — confirmation, receiving, invoice reconciliation — not managed in separate systems.
QuickBooks Online or Xero handoff. COGS should reflect the supplier-confirmed, received, landed unit cost — not the original FOB price without duty or freight. The accounting handoff closes the loop between the buying decision and the financial record.
Closing the loop
LineNow connects your POS sales (Shopify, Square, Lightspeed), your supplier relationships, and your procurement workflow in a single closed loop. A Fall pre-buy becomes a living PO with three delivery windows. When Wave 1 arrives with a colorway substitution, receiving captures the change before the invoice routes to AP. When a brand emails a price-hold notice for next season's core styles, AI reads the message and attaches the update to the PO. Confirm where freight and duty allocation occur before accounting closes the month; attaching order-level costs does not prove automatic per-unit capitalization.
Landed Costs Without ERP Headaches — how duty, freight, and handling are allocated on live purchase orders before accounting inherits the purchase
Procurement for Specialty Retailers — the broader framework for specialty retail replenishment, multi-channel demand management, and supplier execution
