What Is FireworkOS? The Operating System for Professional Fireworks Companies

One system instead of six half-systems

Most professional fireworks companies run on a stack nobody chose on purpose. Inventory is a spreadsheet. Magazine records are on paper in a binder. Shows live in a calendar and a client email thread. Bills of lading are a Word template someone retypes every July. Crew credentials are a folder of scanned PDFs. Everything works right up until the week you have eleven shows, two trucks, and a shooter asking which magazine the 4-inch shells went back into.

Firework OS exists to replace that with a single operating picture. One record for each product, each magazine, each show, each load, each crew member — and one history you can follow when someone asks what happened. This article is the map. The rest of the resources library goes module by module.

It starts in the office

The first thing most companies feel is the paperwork load on the office side: purchase orders, receiving, product data, customer and event details, and the stack of documents that has to travel with each show. Firework OS keeps that work in one place so the same data feeds every step downstream instead of being retyped three times.

• Supplier catalogs and purchase orders, so what you ordered and what you received are the same record.
• Receiving that lands product into a specific magazine and location rather than into a general pile.
• Customer and event details attached to the show record, not scattered across inboxes.
• Documents stored with the object they belong to — the show, the shipment, the crew member.

Magazine: ATF magazine and log recordkeeping

The Magazine module is specifically about magazine and log recordkeeping. It is where you keep organized records of what is stored where, what moved in, what moved out, and what was adjusted — with the movement history retained instead of overwritten. That is its entire job. Crew scheduling, qualifications, and assignments are handled separately, in Crew and Readiness.

Keeping the record in a system rather than a binder mainly buys you retrieval. When you need to show a specific movement for a specific magazine on a specific date, you search instead of digging. More detail in ATF Magazine Logs Without the Paper Chase.

Show planning against real stock

A show record in Firework OS holds the customer, the event, the site basics, the planned product, and the people. The important part is that planned product is allocated from actual magazine inventory. You are not building a wish list — you are reserving real cases and real loose product, which means the same shells cannot be quietly promised to two shows on the same Saturday.

See Building a Fireworks Show in FireworkOS and Fireworks Inventory Management.

Load-out, BOLs, and the show packet

When the truck loads, the crew confirms lines against the allocation, and that confirmed load-out is what generates the paperwork. The bill of lading and the rest of the outbound packet come from the same record, so what is in the cab matches what is in the office.

What travels with the show

• The show details: site, times, contacts, and the plan.
• Load sheets tied to the confirmed load, line by line.
• Transportation documentation for the shipment, produced from that load.
• Return workflow, so what comes back is counted against what went out.

More in Fireworks Bills of Lading and The FireworkOS Show Packet.

The field, and what comes back

Shows change. Wind trims a segment, a rack goes down, a client wants a longer finale, a device gets pulled. Firework OS is built to capture those changes where they happen, on a phone, with a reason and a name attached — and then to make the return count structured rather than reconstructed from memory at 1 a.m. Reconciliation closes the loop: what left, what was expended, what came back, and what needs an explanation. That sequence is covered in Fireworks Inventory Reconciliation.

Crew readiness and training

Product is only half an operation. The other half is whether the right qualified people are on the right show with current documents. Crew profiles carry qualifications, credentials, and expiration visibility; training records keep the history of what someone has completed. Assignments then draw on people who are actually ready. See Crew Readiness and Training Records.

Audit history and security

Because every step writes to the same system, the history is a byproduct rather than a project. Records are additive — corrections are recorded as corrections instead of silently replacing the original number — so you can see who changed what, when, and why. Access is role-based, so a seasonal driver and an operations manager do not see the same thing. The security page describes the controls, and Inspection-Ready Records covers retrieval in practice.

What Firework OS does not do

Firework OS supports recordkeeping and operations. It does not make your company compliant with ATF, DOT, state, or local requirements, it is not approved or certified by any regulator, and it does not provide legal advice. Determining what your operation is required to do — and keeping those records correctly — remains your company's responsibility.

If you want to see how the modules fit your operation, walk through the platform, the feature detail, and the packages, or book a demo and we will run it against your season.