Multi-warehouse inventory for fireworks operators.

Inventory in PyroApex starts with the product catalog, but it does not stop at product names and quantities. Each item can carry UPC fields, packing display values, physical dimensions, media, cost information, and the warehouse relationships that explain where that stock can actually ship or be picked up. That matters in fireworks because a product can be sellable online, held for wholesale, staged in a retail store, or available only from a specific source.

The admin workflow is designed to make those details visible before they turn into customer problems. Catalog health reports call out missing media, incomplete data, and records that need cleanup. Cost reporting gives operators a way to understand on-hand value instead of treating inventory as a blind count. Linked inventory sources connect storefront availability to the places staff can fulfill from, so the selling channel is not making promises the warehouse cannot keep.

PyroApex also treats cleanup and recovery as normal operating needs. Soft-deleted resources can be restored when someone removes the wrong product, and hard-delete paths exist when a tenant needs a permanent cleanup. Cross-tenant catalog clone flows copy media with the product record, which reduces the manual rebuild work for operators who run more than one selling entity or need to seed a new catalog from a proven one.

Why fireworks inventory is different.

Generic inventory tools often assume one warehouse, one ecommerce channel, and parcel shipping. Fireworks operators need a stronger model. A single SKU can have different pack styles, carton counts, pickup rules, and warehouse constraints. Product dimensions are not decoration; they feed shipping math, pallet density, and routing decisions. UPC support is not just for checkout speed; it keeps receiving, labels, and counter sales tied back to the same catalog record.

The practical result is fewer disconnected spreadsheets. Product teams can clean catalog data, warehouse staff can see source relationships, and store teams can sell against the same stock model. When the season gets busy, staff should not have to ask whether a website count came from the back room, the main warehouse, or a legacy import. PyroApex keeps those answers close to the product record.

How it supports the rest of the platform.

Inventory data feeds the storefront, POS, wholesale access, shipping calculations, and reporting. The storefront needs accurate availability. POS needs barcode-friendly product records. Wholesale needs assigned pricing to map onto real products. Shipping needs dimensions as structured JSON, not a note field. Reporting needs cost and quantity data that can survive imports, cleanup, restores, and warehouse moves.

That connected model is the main difference between PyroApex and a stack of generic add-ons. Operators can still bring outside data in, but the platform normalizes it into a fireworks-aware catalog that every selling and fulfillment workflow can use.