Issue and return gear without inventory drift

August 1, 2026

All posts

Warehouse

In Snikevent the catalog is SKUs (models), while the warehouse tracks physical units (EquipmentAsset) with QR/serial and status. Issue and return run through a warehouse workflow tied to a project.

Before issue, check availability: project dates, existing reservations, maintenance, and prep time. The conflict engine surfaces shortages instead of silent overbooking.

On return, record condition. Damage moves a unit to damaged/maintenance with a note so the repair queue does not live in chat threads.

Warehouse UX supports a sticky project and SKU/serial + Enter; photo scan (OCR) and an offline PWA queue help when the venue network drops.

Every movement leaves asset history and audit trails — easier to answer “where did that loom go” after a festival.

Try it on your projects