What counts as an asset in ezerve?

An asset is anything customers' bookings consume. ezerve deliberately keeps the shape simple: every asset is a person, a place, or a thing, plus a free-form subtype tag ("station", "guide", "rental") so your language stays yours.

People, places, things

• People — stylists, guides, instructors, a lawyer's hour. Person assets can be linked to your staff so schedules and bookings line up.
• Places — chairs, courts, docks, rooms, lanes. Usually exclusive: one booking at a time.
• Things — kayaks, bikes, projectors, party tents. Often pooled: you care that a kayak is free, not which one.

Exclusive or capacity

The one decision that matters most: does this asset serve one booking at a time, or several?

• Exclusive (capacity left empty): one overlapping booking, ever. The database enforces it — see how double-booking is prevented.
• Capacity N: a seat pool. A kayak fleet with capacity 8 accepts up to 8 overlapping bookings; the 9th is refused.

Rule of thumb: if the units are interchangeable (eight identical kayaks), model one asset with capacity 8. If they differ in ways customers care about (Chair 1 by the window, Chair 2 in the back — or kayaks of different sizes), model them as separate exclusive assets and let an offering pool them.

Per-asset booking rules

Each asset carries its own scheduling personality, covered in detail in availability rules:

• weekly open hours (and seasonal date ranges),
• buffers before and after each booking (turnaround time),
• minimum lead time and how far ahead bookings are allowed,
• slot granularity (offer times every 15, 30, or 60 minutes).

Every asset gets an address

Assets have web-friendly slugs from the moment they're created, so links to them are readable (/book/kayak-fleet, not /book/8f3a…). Names can change freely; slugs keep your links working.