Fireworks Inventory Reconciliation: From Show Load-Out to Post-Show Returns

What reconciliation actually means

Inventory reconciliation is the process of proving that three numbers agree for every product on a show: what you allocated and loaded out, what was actually expended, and what physically came back into a magazine. When those three agree, your magazine count is trustworthy and your next show can be planned against real stock. When they disagree, you have an exception that needs an explanation before the record is closed.

For a professional display company the hard part is not arithmetic. It is that the count changes hands: an office allocation becomes a load sheet, a load sheet becomes a truck, a truck becomes a lead shooter's decisions in a field at dusk, and the field becomes whatever gets stacked back on the shelf at midnight. Reconciliation is the discipline of keeping one continuous record across all of those handoffs.

Why reconciliation breaks on paper and spreadsheets

• The allocation lives in a spreadsheet, the load sheet is printed, and the return count is written on the back of it. Three artifacts, no single source of truth.
• Substitutions made in the field never make it back to the office copy, so the shortfall looks like a loss instead of a documented swap.
• Partial cases get counted as whole cases—or not counted at all—because nobody wants to open and recount at 1 a.m.
• Multiple crews return to the same magazine the same weekend, and the counts are entered days later from memory.
• The person who knows what happened is the only place the explanation exists. When they are unavailable, the record has a hole.
• Corrections overwrite the original number, so a month later there is no way to see what changed or why.

None of this is carelessness. It is the predictable result of a July schedule and a record-keeping method that cannot follow product through movement. The fix is structural: reconcile against the same record the load-out was built from.

Step 1: Pre-show allocation from magazine stock

Reconciliation begins before anything is loaded. Build the show's product list against actual magazine stock rather than a wish list, and allocate—reserve—each item to the show so it cannot be silently promised to a second display on the same date.

• Allocate by item and quantity, with the source magazine recorded for each line.
• Flag anything short at the allocation stage, while there is still time to substitute deliberately.
• Record substitutions as substitutions, with the item they replaced, so the reason survives the season.
• Freeze the allocation as the baseline for the show. Every later number is measured against it.

In Firework OS this is the link between magazine inventory and the show record, so the allocated quantity, the show it belongs to, and the magazine it came from are one entry instead of three documents. See how inventory and shows connect on the platform overview.

Step 2: Outbound load-out, load sheets, and the BOL

The load sheet should be generated from the allocation, not retyped from it. Retyping is where quantities drift. At the dock, the crew confirms each line as it is loaded and marks the exceptions immediately—short load, wrong lot, damaged case, item pulled.

What the outbound record should capture

• Item, quantity loaded, and the magazine each unit came out of.
• Who performed the load-out and who verified it.
• Date and time of departure, and the vehicle or trailer the load went onto.
• Any difference between allocated quantity and loaded quantity, noted at the dock rather than reconstructed later.

Transportation paperwork—bills of lading, load sheets, and the document packet that travels with the vehicle—should be produced from that same confirmed load, so the paperwork in the cab and the record in the office describe the same truck. Your company is responsible for determining what documentation each shipment requires and for the accuracy of what you sign. Firework OS is built to help you assemble and retain those documents consistently; it does not decide your requirements for you.

Step 3: Field changes on show day

Shows change. A wind call trims a segment, a rack fails, a client asks for a longer finale, a device is pulled for a reason the lead shooter judged sound. If those changes are not captured while they happen, reconciliation turns into an argument with the past.

• Capture the change at the site, on a phone, with the reason attached—not on a napkin.
• Distinguish not fired from pulled from misfire/dud from damaged. They reconcile differently and they matter differently.
• Record who made the call. An explanation with a name behind it is worth ten without one.
• Note anything that will need special handling on return so the magazine crew is not surprised.

Step 4: Post-show returns and the return count

The return count is the single highest-leverage step in the whole sequence, and it is almost always performed by tired people. Keep it short and structured: count what physically comes off the truck, line by line, against the outbound record, and enter it once.

• Count against the outbound load, so every line has an expected number beside it.
• Record the receiving magazine for each returned line, not just the fact that it came back.
• Segregate anything that is not straightforwardly returnable to stock—damaged, water-exposed, unfired devices needing review—and record it as its own category.
• Capture who received and who verified the return, with a timestamp.
• Enter the count the same night when it is possible. Same-night entry is the difference between a count and a recollection.

Reloading returned product into the correct magazine—and having the record say so—is what keeps the next show's allocation honest. Details of the inventory and magazine modules are on the features page.

Step 5: Partial cases and loose product

Partial cases are where inventory accuracy quietly dies. A case that left full and comes back with eleven of twenty-four shells is not “a case.” If it is recorded as one, the magazine count is wrong from that moment forward and every downstream allocation inherits the error.

Practical handling

• Track the unit you actually consume. If shows draw shells, count shells and let the case be packaging.
• Return partials to a known, labeled location so the next crew finds them before opening a full case.
• Reconcile partials by unit count, not by container count.
• Consume open partials first on the next show, and allocate them explicitly so they leave the shelf on the record.
• Recount partials at each handoff. They accumulate error faster than sealed stock.

Step 6: Reconciling allocated vs. fired vs. returned

The reconciliation itself is a simple identity applied per line:

Work line by line rather than by total. A show that balances in aggregate can still hide a twelve-unit shortfall in one item offset by a miscount in another. Per-line reconciliation finds that; totals hide it.

• Zero variance with a complete return record: close the line.
• Variance explained by a documented field change or substitution: attach the explanation and close it.
• Variance with no explanation: leave the line open as an exception. Do not force it to zero.

Step 7: Exception handling

Exceptions are normal. The goal is not zero exceptions—it is zero unexplained exceptions and a consistent way of resolving the ones you have.

• Assign every open exception to a person and a due date, so it is not closed by attrition.
• Require a written reason for a resolution that changes a quantity, and keep the original figure visible beside it.
• Escalate repeat patterns—the same item, the same crew, the same magazine—because a pattern usually means a process problem, not a counting problem.
• Close the show record only when no line is silently unresolved. A closed show with unexplained variance is a record you cannot rely on next season.

Step 8: Traceable history you can reference later

Months later, the question is rarely “what is the number?” It is “who entered this, when, and what did it say before?” That requires history that adds entries rather than overwriting them.

• Every quantity change carries an author, a timestamp, and a reason where one applies.
• Corrections are recorded as new entries, so the prior value and the change are both visible.
• Documents generated for a shipment stay attached to the show and the load they came from.
• Records are retrievable by show, by magazine, by item, and by date range—because that is how questions actually arrive.
• Access is role-based, so field crews record what they should and administrative changes stay with the people accountable for them.

How Firework OS handles access control, roles, and data handling is described on the security page.

Software recordkeeping vs. your regulatory obligations

This distinction matters enough to state plainly. Firework OS is operational software. It helps you capture inventory movement, generate and retain transportation and load-out documentation, and keep a consistent, traceable history of who recorded what and when. That support makes accurate records easier to produce and easier to find.

It does not make your company compliant, and it does not guarantee compliance with ATF, DOT, state, or local requirements. Determining which records, licenses, storage conditions, documentation, and reporting apply to your operation—and keeping them accurate and current—remains your company's responsibility. Firework OS does not provide legal, regulatory, or compliance advice. Work from the requirements that apply to you and, where appropriate, with qualified counsel or your regulating authority; use the software to execute the recordkeeping consistently.

A reconciliation checklist you can adopt this season

• Allocate from real magazine stock, and freeze the allocation as the show baseline.
• Generate the load sheet and transportation packet from the confirmed load-out, never retyped.
• Confirm each line at the dock, with the loader and verifier named.
• Capture field changes at the site, categorized, with the reason and the person.
• Count returns against the outbound record the same night, by consumable unit.
• Handle partials by unit count and return them to a labeled location.
• Reconcile per line, not by total, and leave unexplained variance open.
• Assign, date, and resolve exceptions in writing before closing the show.
• Keep an additive history: corrections add entries, they do not erase them.