Forty gift bags is a project. Four hundred is a supply chain.
The instinct is to reorder whatever worked at the smaller outing. Same vendor, same quarter-zip, same tissue paper. It holds together right up until a client wants a logo drop on a compressed timeline, a size run comes back lopsided, or the mill that nailed 40 units can't touch 400 without an eight-week lead time nobody priced in.
The buyer changes, and so does the brief.
Member-guest gifting is one person picking something they'd be proud to hand a friend. Corporate gifting is an events team buying on behalf of a client relationship they don't control the taste of. They're not optimizing for delight. They're optimizing for risk: will this embarrass us in front of a customer, can fifteen logos go out on fifteen orders without a change-order nightmare, can this happen again next quarter without starting from zero.
That's a sourcing brief. It just arrives dressed as a gift.
Where corporate programs actually break.
Rarely the garment. Almost always three other places.
Decoration. Embroidery digitizing for a client's mark, color-matching across a dozen logos on the same blank, holding registration steady across a run — real setup time that a "just add a logo" quote never accounts for.
Size curves. A 40-piece order can be eyeballed. A 400-piece order across a dozen companies needs real data, or a buffer built into the plan on purpose. The alternative is a scramble two weeks out.
Logistics. One event, fifteen logos, fifteen ship-tos, fifteen invoices, one deadline. A fulfillment problem wearing a gifting hat — and usually the thing that decides whether a vendor can actually hold the account.
What scale actually requires.
Not a bigger version of the small program. A different one, built from the start:
A base garment with a decoration process proven at volume, not proven once on a sample. Ask for a photo of the last 400-piece run, not the first.
A size plan built from real attendee data, not a guess — with a buffer built in on purpose, not a rush reorder built in by accident.
A production calendar that treats decoration lead time as its own line, because it is one, and it's the one that gets forgotten until it's expensive to fix.
One person who owns the whole multi-client order. Not fifteen threads landing on an events team's desk the week of.
The part worth saying plainly.
A program built to scale costs more per unit at 40 pieces than the lowest quote in the inbox. That's not padding — it's the vendor pricing in the infrastructure to hit 400 without falling apart, not just fabric and thread for a sample size. It's the difference between an events team that can say yes to a bigger ask next year, and one still recovering from this one.
The quarter-zip still matters. Nobody's arguing otherwise. But whether the program survives a bigger client list has less to do with the product than with whether the sourcing behind it was built to grow before it had to.