How to Manage Swag Inventory Without a Spreadsheet

Every company merch program starts with a spreadsheet, and every spreadsheet tells the same lie. It says there are 40 hoodies. There are 12, they are all size Small, and two different people have separately promised 30 of the hoodies that do not exist to two different events. Nobody did anything wrong, exactly. The system just has no way to be right.

Inventory is a solved problem in every other corner of commerce, and the solutions translate directly to swag. Here is the working vocabulary, the handful of numbers that matter, and the point at which the spreadsheet has to go.

Why Spreadsheets Fail at Merch Specifically

A spreadsheet fails at swag for three structural reasons. It has no concept of reservation, so stock that is promised but not yet shipped looks available to the next person. It updates only when a human remembers, so every count drifts toward fiction between updates. And it usually tracks products instead of sizes, which for apparel is the same as not tracking at all.

The Five Numbers That Run a Program

• On hand: units physically on the shelf. The number a warehouse count produces.
• Reserved: units committed to orders that have not shipped yet. Invisible in most spreadsheets, and the number one cause of double-promised stock.
• Available: on hand minus reserved. The only number anyone should make promises against.
• Low-stock threshold: the level where a product flags for attention, ideally set per product, since running low on 50 event tees and running low on 50 executive jackets are different emergencies.
• Burn rate: units leaving per week or month. Without it, every reorder is a guess.

Track Variants, Not Products

For apparel, the unit of truth is the size, not the product. A line that says 200 tees in stock can conceal zero mediums, and mediums and larges are always the first to go. Track every size as its own count, and order against a size curve rather than evenly: a common starting split is roughly 10 percent Small, 25 to 30 percent each Medium and Large, 20 percent XL, and 10 to 15 percent 2XL and up, adjusted to what your team actually wears. Then watch which sizes deplete fastest and let the curve correct itself with each reorder.

Receiving: Where Good Counts Are Born

Inventory accuracy is won or lost the day goods arrive. Count cartons against the packing list before signing for anything, open a sample carton and verify contents and sizes, and report discrepancies to the producer within a day or two, while claims are still easy. Label cartons with contents and date received, and pull from the oldest stock first so nothing ages in a back corner. Ten minutes of discipline at the dock saves the phantom-inventory archaeology project six months later.

Reorder Points: The Only Formula You Need

A reorder point is burn rate multiplied by production lead time, plus a safety buffer. If a tee burns 25 units a week and a reorder takes four weeks to produce and deliver, the reorder point is around 125 units, and waiting past it means a stockout is already scheduled. Production minimums set how much to order when the flag trips; our guide to minimum order quantities covers those floors. During the fourth quarter, lengthen the lead-time side of the formula, because production and freight both slow down.

Counts, Audits, and the Activity Trail

Even good systems drift from reality, so schedule cycle counts: a quarterly walk of the physical shelf against the system, investigating any variance over a couple of percent. Just as important is an activity trail showing who changed what and when. When a count moves from 80 to 30, there is a story, and a system that cannot tell it leaves you interrogating coworkers instead of reading a log.

If You Are Keeping the Spreadsheet for Now

Plenty of programs are one closet and twelve SKUs, and a spreadsheet genuinely is enough at that size, if it borrows four habits from real inventory systems. Give every size its own row, never a single count per product. Add a reserved column next to on hand, and compute available from the two, so promises get made against the right number. Put one named person in charge of updates, with a fifteen-minute weekly ritual, because a spreadsheet six people edit on memory is fiction with a grid. And write the low-stock threshold into a column with conditional formatting, so the sheet at least turns red before the mediums are gone.

That upgraded spreadsheet will carry a small program for a surprisingly long time. What it still cannot do is update itself when something ships, which means every count is only as fresh as the last human touch, and that is the crack everything eventually falls through.

When to Move Off the Spreadsheet

The honest trigger is the first double-promise, the first stockout that surprised everyone, or the first month someone spends real hours reconciling a closet. At that point the options are inventory software you run yourself or a managed program where the merchandise lives in a fulfillment warehouse and the tracking comes with it. Whichever way you go, demand the same four things: live counts per size, reservation logic, per-product low-stock alerts, and an exportable history. Our comparison of swag management platforms covers how the vendors in that second category price it.

That second model is what we run: client inventory lives in our warehouse tracked to the size level, with reserved and available counts, per-product thresholds, and a full activity log visible in the portal. The swag management overview shows how the program works, and the instant estimate tool prices it for your inventory in about two minutes.