An event rental business should track tents, tables and chairs in three tiers: serial-tagged items for tents and heaters, quantity counts for tables and chairs, and a damage log on every return. Software then calculates availability across each hire window. AI helps after the data exists, turning orders into readable pick lists and returns into damage summaries.
Roundups of rental software list features. They rarely show you how to put a 20-by-40 tent, 40 trestle tables and 400 chairs into a system so that the numbers stay true after a busy June. This tutorial does that, step by step: item set-up, counting by barcode or by hand, double-booking checks, damage logs, and the places where AI saves time and the places where it should stay out.
Why tents, tables and chairs need different treatment
A rental business holds three kinds of stock, and one setting for all three causes most of the errors I hear about.
- Serialised items. Each unit has an identity: Tent 3, Heater 7. You care about its history, its service date and whether it is out right now. Tents, heaters, generators, lighting rigs and some specialist furniture belong here.
- Quantity items. Units are interchangeable and you track a number: 400 white chairs, 40 six-foot tables. You care how many are free on a date, and how many have been written off.
- Kits. A tent is not one thing. It is a frame, a roof, sidewalls, weights, a floor and a lighting set, and a missing sidewall means the tent cannot go out. Kits tie components to a parent item.
When you set up the system, decide the type for every item first. If you enter a tent as a quantity of six, you lose the history of which tent has the torn roof. If you enter chairs as individually tagged units, you will spend weekends scanning stackable chairs with no benefit.
What the software has to do, and what one vendor says it does
Event Rental Systems' page, read in October 2026, says it lets you track availability, avoid double bookings and manage your rental catalogue in real time, and lists plans starting at $79.95 (Launch, with inventory tracking and order management), $149.95 (Standard), $249.95 (Pro) and $399.95 (Elite) a month. Its pricing has a toggle for under or over 50 inventory items (Launch is labelled for fewer than 10), but the page did not show how prices change, it adds a $99 yearly hosting fee and an unstated one-time setup fee, and it does not mention barcodes, damage logging or quantity versus serialised items. Those are questions for a demo, which is the point: a home page claim is a starting list, not an answer.
Goodshuffle Pro is another name that ranks for this search, but its page was not readable by my tools, so I make no claims about it. Do the same with any vendor: make a list of what you need, and ask for each item in a live demo with your data.
Ask every vendor for these eight capabilities, and note which are included in the price you are quoted:
- Quantity and serialised items in the same catalogue.
- Kits with component checks.
- Availability by date range, including delivery, return and cleaning buffers.
- A hard stop or warning when a quote exceeds free stock.
- Barcode or QR scanning on a phone for out and in.
- Condition and damage notes per item, with photos.
- Maintenance flags that take an item out of availability.
- An exportable pick list and a returns checklist per order.
Step 1: build the catalogue in the right order
Start with what makes money. List your 30 to 50 most-hired items and enter those first, not the whole warehouse. For each, record the type (serial, quantity or kit), the quantity owned, the hire price, the replacement cost and the storage location. Replacement cost matters later, when a damage fee needs a number.
An illustrative starter catalogue for a small business:
| Item | Type | Owned | Hire price | Replacement cost | Notes |
|---|---|---|---|---|---|
| 6 m × 12 m frame tent | Kit, serialised | 3 | $650 | $4,200 | Frame, roof, 6 sidewalls, 24 weights |
| 6 ft trestle table | Quantity | 40 | $9 | $85 | Stored on racks, bay 2 |
| White resin chair | Quantity | 400 | $1.80 | $18 | Stack of 10 |
| Patio heater | Serialised | 8 | $45 | $310 | Service every 6 months |
Take the tent as an example. Its kit lists the frame, the roof, six sidewalls and 24 weights. When an order goes out, the system should ask you to confirm each component, so a tent leaves with six sidewalls, not five. A missing sidewall on a Saturday morning is a very expensive mistake that a checklist prevents.
Step 2: set the opening counts, by scan or by hand
Your system is only as good as the first count. Close the warehouse for a day if you can and count every line. There are two ways to do it, and a mix usually works best.
Barcode or QR tags: where they pay for themselves
Tag serialised items and anything with a repair history. A phone scan at loading and at return confirms exactly which tent or heater went out, and what condition it came back in. The tags cost little; the time cost is the discipline of scanning every time. If the team skips scans at peak times, you get false certainty, which is worse than honest manual counts.
Manual counts: where they are enough
For 400 chairs, count in stacks of ten. A stack is 10, so 400 chairs is 40 stacks, and a count by stack takes minutes rather than hours. For trestle tables, count by rack. The record is the count, the date and the counter's initials. Written on the load sheet, a manual count beats an unscanned barcode.
A realistic sum for a two-person team: scanning 120 serialised items at about 20 seconds each is 40 minutes, and counting 440 quantity items by stack and rack is about 25 minutes. A full count of the main lines is therefore roughly an hour, against half a day for individual tagging of everything. That is an estimate, so time your own.
Step 3: stop double bookings before they happen
A double booking happens when the system sees a date, but the stock is out for the whole window. Availability for any item on a given day should equal what you own, minus what is reserved for overlapping windows, minus what is in repair, minus what you hold as a buffer.
A worked double-booking check
Say you own 400 chairs. Event A needs 250 chairs from Thursday delivery to Monday return. Event B, a wedding on Saturday, wants 200 chairs. The system must answer by looking at the whole window: 400 − 250 = 150 free on Saturday, so Event B cannot have 200. It should say so when you build the quote, not when you load the truck. If you also hold a 5 per cent buffer for breakages (20 chairs), free stock is 130.
The three failure modes to test in a demo:
- Event-date-only logic. The system checks only the event day and ignores delivery and return. Test a Thursday-to-Monday hire against a Saturday-only hire.
- No buffer for repair. A damaged tent goes to the workshop but still shows as available. Mark an item "in repair" and confirm availability drops.
- Quote versus order. A quote does not reserve stock, but an accepted order does. See where the status change happens and whether it is automatic.
A realistic mistake (illustrative): a business holds two quotes for the same weekend, one for 300 chairs and one for 180, with 400 owned. Both clients accept by Wednesday, and the shortfall is discovered on Thursday afternoon, when it is too late to buy chairs in. A "hold" status with an expiry date on every quote would have flagged the clash on day one. For the booking side of this, party rental booking software with quotes and availability tools goes into more detail.
Step 4: a damage log that settles arguments
Rental damage disputes are won or lost on records. Every return should capture condition on the way in and the way out, with photos for anything above a minor mark. A simple scheme works for all items.
| Grade | Meaning | What happens |
|---|---|---|
| A | Clean, no marks | Back to stock |
| B | Cosmetic wear, fully usable | Back to stock, note logged |
| C | Needs cleaning or minor repair | Removed from availability until fixed |
| D | Damaged or missing, not usable | Written off or repaired; charge per contract |
Take an example: a tent returns with a 15 cm tear in a sidewall. The checker grades the sidewall D, photographs the tear, and the kit goes to status C because it is incomplete. The software removes the tent from availability for the weekend after next, giving the repair team a deadline. The contract is what lets you charge for it, which is why party rental contract terms for damage, weather and deposits matters; have an adviser check anything you plan to charge.
Keep the log specific. "Damaged" is useless. "Sidewall 4, 15 cm tear near a seam, photo attached, grade D" can be actioned. Keep the log by item and by order, so you can see both which customer returns things broken and which item breaks most. If one chair model fails often, the log tells you before the bill does.
Step 5: where AI earns its place
Once the data is in, AI can save time on the paperwork. It should not decide what stock exists. Here are three uses, each with its limit.
Pick-list summaries
An order for an event is a long list. A warehouse team wants it grouped by area and loading order. A prompt over the exported order does this:
Turn this rental order into a pick list for the warehouse team.
Group by: tents and kits, tables and chairs, linen and small items.
Within each group, list item, quantity and storage location.
At the top, list anything that needs a check before loading (kits, heaters, anything flagged "service due").
At the bottom, show total counts by group. Do not change any quantity.
ORDER: [paste exported order lines]A realistic output (illustrative):
CHECK BEFORE LOADING: Tent 2 (all 6 sidewalls, 24 weights); Heater 5 (service due next month).
TENTS AND KITS: 6 m × 12 m frame tent × 1 (bay 1).
TABLES AND CHAIRS: 6 ft trestle table × 12 (rack 2); white resin chair × 120 (stacks of 10, bay 3).
TOTALS: 3 line groups, 133 items.
What you would fix: the total adds a tent, 12 tables and 120 chairs to 133, which is right, but check any total the AI gives against the source. Never let a summary be the only record, and keep the instruction "do not change any quantity" in every prompt. Ask a team member to tick the printed list as items are loaded.
Return-day damage summaries
Paste the day's return notes and ask for a table: order, item, grade, action, estimated charge from the replacement cost column. The AI formats; you decide the charge. If your notes are terse, say so in the prompt and tell it to mark anything unclear as "check", not to guess.
A returns-day example, filled in
Here is what a day's returns notes might look like after an AI pass, using invented notes. The raw notes were: "Order 1042 chairs 120 back, 2 cracked. Table 14 leg bent. Heater 5 fine but dirty. Tent 2 sidewall 4 torn, no weights missing."
| Order | Item | Grade | Action | Estimated charge (replacement cost) |
|---|---|---|---|---|
| 1042 | White resin chair × 2 | D | Write off | 2 × $18 = $36 |
| 1042 | 6 ft trestle table 14 | C | Repair leg, out of stock until fixed | Repair cost, to confirm |
| 1042 | Patio heater 5 | B | Clean, back to stock | None |
| 1042 | Tent 2, sidewall 4 | D | Replace sidewall, kit status C | Check contract and sidewall price |
Two points to verify by hand. All 120 chairs came back, 2 of them cracked, so writing off 2 is right, but the AI should not decide whether a cracked chair is wear or customer damage. That is a judgement under your contract. And "repair cost, to confirm" is the honest answer when the notes give no number; a draft that invents a figure is a prompt to tighten your instruction.
Reorder and shortfall emails
When the system shows that your busiest weekend needs 520 chairs and you own 400, an AI draft to a supplier for 120 chairs on short hire takes seconds. Again, you provide the facts, and the draft only reworks the words. For forecasting stock needs across a season, AI inventory forecasting for small businesses explains the method.
Where AI should stay out
Do not use AI to count stock, to decide whether a tent is safe to use, or to mark an item as available. Safety checks on structures and heating equipment belong with trained people following the manufacturer's guidance, and the record should be theirs. Use AI to write up the list, not to replace the check.
Comparing options with a practical scorecard
Because many vendors publish only "starting at" prices, send each the same brief and score the replies. Use your own numbers:
- Items in the catalogue (say 120 lines) and how many are serialised (say 25).
- Orders a month (say 60) and peak orders in a single weekend (say 18).
- Users: office, warehouse and drivers.
- Must-haves: kits, scanning, damage photos, buffers, pick lists.
- Integrations: accounting, online quote requests, payment links.
Then ask each vendor to enter your 4 sample items from the table above, build the Thursday-to-Monday example, and run the damage grade D on a sidewall. The vendor who can do all three on a screen share, without a script, usually knows rental. For a plan that lists "starting at" prices, such as the Event Rental Systems range of $79.95 to $399.95 a month, find out what the starting price excludes, such as users, text messages, payment fees, the yearly hosting fee and the setup fee. Also compare with general inventory tools; best AI inventory tools for small retailers shows what retail tools do, though most lack date-based availability, which is the essential rental feature.
Rolling it out over four weeks
- Week 1: enter the 30 to 50 top items, with type, quantity, price, replacement cost and location. Do the opening count of those lines.
- Week 2: run live orders through the system in parallel with your current method. Compare every pick list.
- Week 3: add barcodes to serialised items, switch on scanning at loading and return, and start the damage grades.
- Week 4: retire the old method, and start a weekly reconciliation of system quantity against a shelf count for three random lines.
The reconciliation is the control that keeps the data honest. If the difference on any line stays above two or three per cent for three weeks, find the process leak: unrecorded loans, returns scanned to the wrong order, breakages not logged. Related rental trades solve the same handover problem, for example campervan rental software with handover checklists, and the checklist style carries over.
Four questions to ask after two months
After two months, ask four questions. Did you have a double booking, and if so, did the system warn you? How long does a full pick list take to prepare compared with before? What share of damage was recorded at the return, rather than found later? And how far apart are the system and the shelf on your three random lines? If the answers are no double bookings, a faster pick list, most damage logged on return and a gap under two per cent, the software is paying for itself. If any is poor, fix the process step it points to before you consider changing vendor.
Questions rental owners ask about inventory software
Do I need barcodes for chairs?
Usually not. Chairs and folding tables are quantity items: you care how many went out and came back, not which one. Barcode or tag items that are individually valuable, have serial numbers or have a repair history, such as tents, heaters, lighting and specialist furniture. Count the rest in batches.
How often should I count rental stock?
Count high-value serialised items at every return, and quantity items at the end of each busy week, with a full count once or twice a year. Compare the system's number with the shelf. A running difference of more than two or three per cent on any line means a process problem, not bad luck.
How do I stop double-booking a tent?
Make the system calculate availability for the whole rental window, including the delivery and return days and a cleaning or inspection buffer, and let it block a booking when stock is short. If it only shows the event date, you will still double-book across multi-day hires.
Can AI count my stock from photos?
Do not rely on it for counts. AI is better at summarising paperwork, such as a pick list, a damage note or a day's returns, than at counting. Count by hand or scan, then use AI to turn the data into a readable sheet, and check the totals against the source.
Further reads
- How to Run a Stocktake Faster With AI and a Phone Scanner — A faster stocktake with a phone scanner.
- Ski Rental Software: Sizing Forms, Bookings and Returns With AI — Returns handling for a fast-turnover rental.
- AI Photo Booth for Events: Hire or Buy, Costs and Guest Privacy — Hire or buy an AI photo booth: the break-even sum, the vendor claims to check, and the consent signage and retention rules that protect your guests.
- Music Store POS System: Serial Numbers, Rentals, Repairs and AI — A checklist for choosing a music shop POS: serial-tracked stock, rentals, repair tickets, trade-ins, a test script and where AI really helps.
- Which Tool Hire Software Suits a Small Shop? Deposits, Quotes and AI — A buyer's guide for a small tool hire shop: the features that stop double-booking and lost deposits, two priced tools, and where AI helps with quotes.
- Tuxedo Rental Software: Fit Dates, Returns and AI Reminders — A party roster, measurement form, late-return fee formula and seven-message reminder sequence for a formalwear hire shop, plus when to buy software.
- AI Entertainment for Events: What Party Hire Firms Can Add to a Package — Five AI add-ons a party hire firm can sell, a costed caricature station for 150 guests, and the venue and consent points to settle before listing any.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Event Rental Systems product and pricing page, read in October 2026 (starting prices by plan, real-time availability). Goodshuffle Pro's page blocked automated reading, so no claims are made about it; confirm features with each vendor.