Fireworks Inventory Management Built for Real Display Operations

The unit problem: cases are packaging, not inventory

Ask two people at the same company how much 4-inch product is on hand and you will often get two different answers, because one is counting cases and the other is counting shells. Both are being reasonable. The case is how product arrives; the shell is how a show consumes it. Inventory that only understands the shipping container will be wrong the first time someone opens one.

Firework OS tracks the unit you actually consume and treats the case as packaging around it. A sealed case of twenty-four is twenty-four units in a known container. Once it is opened, it is however many units remain — and the record says so instead of rounding up to “a case.”

Partial cases and loose product

Partials are where accuracy quietly dies. A case that left full and comes back with eleven shells is not a case, and a shelf full of half-used product is not stock you can plan against unless someone has written down what is in it.

What a partial needs to be useful

• A real count of units remaining, not an estimate and not a container count.
• A specific storage location so the next crew finds it before they open a sealed case.
• A link back to where it came from — which show it was returned from, and when.
• Priority in the next allocation, so open product moves before new product does.

Loose product behaves the same way. The rule that keeps a magazine trustworthy is simple: if it is on the shelf, it exists in the system with a number and a place.

Actual on-hand vs. what the sheet says

“On hand” is a stronger claim than most spreadsheets can support, because a spreadsheet does not know that forty of those shells are already committed to Saturday and twelve are sitting on a truck. Firework OS separates the numbers that matter operationally:

• Physically present in the magazine.
• Allocated to a show but not yet loaded.
• Loaded out and currently off-site.
• Returned but pending review — damaged, water-exposed, or otherwise not straight back to stock.

When those are distinct, “available” becomes a number you can build a show against. When they are collapsed into one column, every planner in the company starts keeping a private side list — which is how companies end up with three versions of the truth.

Allocating from real stock

Planning against real inventory changes the conversation with the client, because a shortfall shows up in the office in June instead of on a dock in July. In Firework OS a show's product list is built by reserving items from specific magazine stock. Anything short is flagged at allocation time, while there is still room to substitute deliberately and record the substitution as a substitution.

This is also the foundation of reconciliation: the allocation is the baseline every later number gets measured against.

Avoiding double allocation

Double allocation is the classic July failure. Two shows, same weekend, same product, two planners, one spreadsheet that has no concept of a reservation. Nobody made a mistake — the tool simply had no way to say “this is already promised.”

Once allocation is a real state on the item rather than a note in a cell, the second show sees reduced availability immediately and the conflict surfaces while it is still cheap to fix. That single behavior removes a surprising amount of peak-season stress.

Knowing where product is stored

Multi-magazine operations lose more time to searching than to counting. Recording the magazine — and the location within it — for every receipt, allocation, load-out, and return means the load crew gets a pick list instead of a scavenger hunt, and returned product goes back somewhere findable. It also means the movement history is meaningful, which is what the Magazine module exists to keep organized.

History beats a corrected number

Any system can show you a current quantity. What you need in October is why the quantity changed in July. Firework OS keeps inventory movement additively: receipts, allocations, load-outs, returns, and adjustments are events with a who, a when, and a reason, so a correction does not erase the number it replaced. That is the difference between a count you trust and a count you argue about. See Inspection-Ready Records.

Why generic warehouse software misses this

• It assumes product ships out and stays out. Display product leaves, gets partly consumed, and returns the same night.
• It has no concept of a magazine, a storage location constrained by what it can hold, or movement records worth retaining.
• It treats a case as an atomic unit, so partials either disappear or get rounded.
• It has no show — the object that everything else in a display operation hangs from.
• It cannot express 'allocated to Saturday' as different from 'on the shelf'.

Firework OS supports inventory and magazine recordkeeping. It does not make your company compliant with ATF, DOT, state, or local requirements and does not provide legal advice. Keeping the records your operation is required to keep, correctly, remains your responsibility.

Want to see it against your own product list? Book a demo, or review the features and packages.