Mountify Help
BG → mountify.eu
Resources

Equipment stock and parallel capacity

The 'Equipment' category, the stock field, and how to read the oversold signals in the schedule.

8 min read Updated 2026-07-26

If you own six identical rackets, three identical laser devices or ten lockers, there’s no point creating six, three or ten separate rows. The Equipment category lets you keep one row with a count — and that count turns straight into parallel capacity: “Stock: 6 — can serve up to 6 parallel bookings.”

This article covers how to create such a resource, how the count becomes capacity, what it costs on your plan, and how to read the oversold signals in the schedule.


1. First — the kind must be “Equipment”

The Stock count field only exists on resources whose kind is in the Equipment category. If you can’t see it, the kind is something else.

Creating such a kind:

  1. Catalog → under Team & resources, click Resource kinds.
  2. Press Add kind.
  3. Name — e.g. “Devices”, “Rackets”, “Cameras”. The hint is “Name shown to your team in the admin panel — keep it short.”
  4. CategoryEquipment. The hint confirms: “Movable items, possibly with quantity (cameras, instruments, machines).”
  5. Pick an icon from the grid.
  6. Create.

Right after creation you get “The "" kind is ready — add the first one.” with an Add button.

The “Located in” field

Only the Equipment category shows a Located in dropdown, with Not tied to a place plus every Places-category kind. If you have none, it reads “Add a place kind first”.

The hint says “When set, equipment is suggested alongside the matching place during booking.”

To be honest: today this field only records the link. It doesn’t change what the customer is offered during booking and it doesn’t auto-assign the equipment together with the room. Treat it as an organisational note, not automation. If you want a device reserved along with a service, make it an add-on on that service — see Service add-ons.


2. The “Stock count” section

  1. Catalog → .
  2. Add (or the pencil on an existing row).
  3. In the Sections rail, click Stock.

The section is titled Stock count and described as “How many interchangeable units are in stock.”

It contains:

  • a stepper — minimum 1, maximum 100;
  • a line under it that updates live: “6 units — can serve up to 6 parallel bookings.”;
  • the hint “How many units of this equipment you have. Customers will book one from the available pool.”

The live preview on the right also grows a line: “Stock: 6 — can serve up to 6 parallel bookings.”

If the kind isn’t Equipment, the section is replaced by the sentence “Stock count only applies to equipment.”


3. One row with a count vs. N separate rows

Both work. The difference is control versus convenience.

One row, stock 6Six separate rows
Customer picks a specific unitnoyes (with Client picks which one)
Individual name / photo per unitnoyes
Own column in the schedulenoyes
Take one unit out for repairno — lower the countyes — deactivate one row
Plan spots66
Upkeepone cardsix cards

Rule: one row with a count when the customer doesn’t care which unit they get (rackets, helmets, lockers). Separate rows when the units have names the customer distinguishes (Court 1 vs Court 3, Room #2).

See also Multiple identical units & availability.


4. The count costs money

This is the most expensive thing in this article to skip.

Your plan’s bookable-spots limit is counted as the sum of stock counts across active resources, not as a number of rows. A “Rackets” row with a stock of 6 eats 6 of Pro’s 15 spots — exactly as much as six separate rows would.

Consequences:

  • Don’t type “100” for peace of mind. Type the real number.
  • Raising the count from 3 to 6 asks for three free spots. If there aren’t any, the save goes through but the resource stays inactive.
  • Lowering the count frees the spots immediately.
  • A resource no active service requires isn’t counted at all — whatever its stock.
  • Equipment used only as an add-on isn’t counted either.

Full rules: Your plan’s bookable-spots limit.


5. How the count works at booking time

At booking time a service asks for a certain number of units of the kind. Usually one, but it can be more — set under Resources & add-ons → Quantity on the add-on itself:

ModeWhat it does
Fixed number”We always reserve exactly this amount.”
Client chooses how many”The customer will see a step picker with specified limits.” — with Minimum, Maximum, Default
per attendeeone unit per N people

The system adds up the units taken by every overlapping booking and compares that with the total stock. As long as one unit is free, the slot is offered.

Important: capacity is counted per kind, per location, per day — not per row. Two rows — “Rackets A” with a stock of 4 and “Rackets B” with 2 — form a pool of 6 for that branch.

Which leads to something easily missed: the pool includes every non-archived row of the kind at that location — including inactive and hidden-from-customers ones. So the oversell check can “see” more capacity than a customer can actually book.


6. Oversold signals in the schedule

The schedule carries two different signals and they don’t mean the same thing.

SignalTypeMeaning
Conflict — red badge, striped borderhardthe same single-unit resource is double-booked
Oversold — amber badgesoftthe kind’s pool is over-allocated for that window

The amber badge carries the tooltip “Stock pool oversold for this window”, and in the conflicts panel the row reads “Pool over-allocated (5 / 4)” — meaning 5 units are needed at that moment while the kind has 4 at that location.

If a booking is both, red wins: the hard conflict styling overrides the amber pill.

Where “Oversold” comes from

  • An admin booking made despite the pool being full (the admin form is more permissive than the public one).
  • The stock count lowered after bookings already exist — the most common cause.
  • Bookings moved between days or locations.
  • One row of the kind archived while the others were already full.

What to do

  1. Open the conflict panel and see which bookings are involved.
  2. Decide: move one of them, raise the count back, or cancel.
  3. The amber badge disappears by itself once the number drops below capacity.

The system never cancels anything automatically and never blocks the day. The signal is for you — so you know you’ve promised more than you have.


7. Lowering the count safely

  1. Before touching the count, open the schedule for the coming weeks and filter by that kind.
  2. Look for windows where more units are in use than the new count.
  3. Change the count and save.
  4. Go back to the schedule — if amber badges appear, move the affected bookings.

Lowering the count never deletes bookings. It only shrinks the pool, which can raise the oversold signal.


8. Worked examples

Tennis club: 4 courts + rental rackets. Courts are Places — four separate rows, because the customer picks a court. Rackets are Equipment — one row with a stock of 10. That’s 14 plan spots. If that’s too many, make the rackets an Always included add-on and they stop being charged.

Cosmetology studio: 2 rooms + 3 lasers. Rooms are Places (2 rows). Lasers are Equipment — one row with a stock of 3. The “Laser hair removal” service takes a room as the main resource and a laser as an add-on. Only the anchor requirement is charged against the plan.

Photo studio: 1 hall + 6 lenses. The hall is a Place. Lenses are Equipment with a stock of 6 and an add-on set to Client chooses how many (minimum 1, maximum 3).


9. Troubleshooting

I don’t see the “Stock count” section. The kind isn’t in the Equipment category. Change it under Catalog → Resource kinds → Edit.

I can’t enter more than 100. 100 is the per-row maximum. For more, create a second row of the same kind — the pools add up.

The save was refused with “A person is a single resource, so it can’t have a quantity above 1.” The resource sits in a person kind. Two people are two resources.

I raised the count and the resource stayed inactive. There weren’t enough free plan spots. Look for the “Bookable-spots limit reached” notice.

Customers see fewer free times than I expect. The pool is counted per location. If the equipment is pinned to another branch via Home location, it doesn’t exist for this one.

“Oversold” is showing and everything looks fine. Check whether a row of that kind was archived — it leaves the pool while its bookings stay.

The count is charged to my plan but the device is only a helper. If it’s used purely as an add-on it shouldn’t be charged. If it is, some service is using it as its main resource.


What’s next