SC070 / Illustrative project scenario / About 3 min read

Planning shirt assortments for distribution and exchanges

This illustrative shirt-order scenario focuses on how approved sizes are grouped for issue, exchange and replenishment after the garment design itself has been settled.

The project situation

Imagine a workplace buyer ordering an approved shirt style for voluntary staff wear. Initial size preferences are provisional, and some wearers may request exchanges after trying the garment. Packing every shirt into fixed department bundles could simplify the first handout while making the remaining stock difficult to identify and redistribute.

Upstream and downstream

Upstream dependency

The order plan would depend on approved garment references and an aggregated size request, without requiring names in the manufacturer's packing brief. The buyer would need to decide when preferences become purchase quantities and how later changes are handled.

Downstream dependency

The person responsible for distributing shirts would need to distinguish unopened stock, available exchange garments and items awaiting a buyer decision. Replenishment would depend on what is actually available by size, rather than the assortment originally delivered or a remembered distribution list.

How UCHANGE could coordinate the work

  1. Separate demand from packing preference

    UCHANGE could help the buyer review the aggregated size assortment independently of its proposed department bundles. The buyer would approve the purchase quantities and identify which distribution groups are settled enough to influence packing before the manufacturer prepares the order.

  2. Choose the distribution arrangement

    An independent garment manufacturer could propose size-grouped packing or buyer-defined mixed bundles. UCHANGE could coordinate a packing example, and the person responsible for distributing shirts would walk through a handout and exchange using fictional requests to compare the work involved.

  3. Define the remaining-stock record

    The buyer would establish how the person responsible for distributing shirts records available garments and pending exchanges. UCHANGE could align the packing descriptions with those categories, keeping personal staff information in the buyer's own process and garment references in the supplier handoff.

The decision that matters

The tradeoff to resolve

Department bundles could shorten the initial sorting task while becoming awkward when preferences change across groups. Size-grouped stock could support exchanges but require more local preparation before issue. The buyer would choose the arrangement that fits its distribution process rather than assuming the most detailed factory packing is best.

What to review before proceeding

Assortment approval
Compare the approved purchase assortment with the manufacturer's packing plan and identify any change that reflects a revised buyer decision rather than a packing adjustment.
Exchange walkthrough
Use fictional size requests to review how an exchange is fulfilled and how the remaining available stock would be updated afterward.
Replenishment reference
Check that the stock record identifies the approved garment version and sizes clearly enough to prepare a later order without reconstructing the original bundles.

What this makes clear

Packing decisions should support the life of the assortment after delivery. A convenient first handout would not, by itself, establish a workable exchange and replenishment process.

Questions for your brief

  • When do provisional size preferences become approved purchase quantities?
  • Who would manage exchanges across the original issue groups?
  • What information must remain visible when only part of a bundle is left?
Discuss your project ↗

Mention SC070 if this scenario helps explain your requirements.

Prepared with AI assistance from UCHANGE’s stated service scope and hypothetical buyer requirements. No customer records or measured project results were used.

Product suitability, supplier capability, inspection methods, compliance requirements, costs and timing would need to be confirmed for an actual project.

Publisher: UCHANGE. Service-scope context: What we do and How we work.

Updated · Content guide