Ski Rental Software: Sizing Forms, Bookings and Returns With AI

A small ski hire shop should take bookings online with a pre-arrival sizing form, tag every item with a unique number and scan it out and back, and make damage terms part of the booking. Software holds the bookings and tags; AI drafts the form questions and messages, while a technician still does the fitting.

Ski hire is a rush business. A shop may do half its season on twenty weekends, and the queue at the counter is where the day goes wrong. The aim of everything below is to move work from the counter to the days before arrival, and to know where every ski is at closing time.

Follow me on Instagram@sagnikteaches

The pre-arrival sizing form

A sizing form is a list of facts staff need to pick kit. Done before arrival, it means the technician can pull boots and skis while the customer walks in. Done badly, it produces wrong sizes and a second queue. This is the question list I would use.

Connect on LinkedInSagnik Bhattacharya

PRE-ARRIVAL SIZING FORM (one per person)
1. Name and date of birth (or age)
2. Height (cm or ft/in; say which)
3. Weight (kg or lb; say which; used by the technician only)
4. Boot size and which system it is in (EU, UK, US or mondopoint)
5. Do you ski or snowboard? If boarding: regular or goofy stance?
6. Ability: first time / can link turns on green and blue runs / confident on red and black runs
7. Do you want a helmet? (head size if known)
8. Do you have your own boots or a helmet already?
9. Anything staff should know (injuries, a recent change in weight, very wide feet)?
10. Hire period: first day and last day
Tick: I understand a technician will check and adjust my equipment at pick-up.

Three details save most mistakes. First, ask which sizing system a boot size is in, because a size 8 in one system is a different boot in another. Second, ask for ability in plain descriptions, not labels, since people overrate themselves when given a number. Third, include the line that a technician checks and adjusts at pick-up. That sets the customer's expectation and keeps the technician in charge of the fit and the binding settings, which should never be set from a web form.

Subscribe on YouTube@sagnikteaches

Where AI helps with the form

AI is good at the wording and the sorting, not the decision. Use it to turn your list into a friendly page, to translate it for visitors who speak other languages (have a staff member check the result), and to summarise a day's forms into a pick list for the technician.

Here are today's sizing forms as rows. For each person, give: name, boot size
with the system stated, height, ability, ski or board, and a suggested kit
category (beginner ski, intermediate ski, performance ski, snowboard).
Flag any row where boot size has no stated system, height or weight looks
odd, or ability seems inconsistent with a first-time answer.
Do not suggest binding settings. Output a table.

Illustrative output: a table with twelve rows, two flagged. One says height 18 in (a likely typo for a child's or adult's height) and the other gives a boot size with no system. What you would fix: ring or message those two customers; and treat the "suggested kit category" as a hint that the technician confirms. A model can be wrong about categories, so a human decision stays in the loop.

Bookings that cannot oversell kit

The booking system needs to know how many of each kit type you own, so it can stop selling what you do not have. Count your stock by category and size band, not by individual pair, for online booking purposes. For example: 40 beginner ski packages, 25 intermediate, 15 performance, 20 snowboards, 80 helmets, adult and junior pools kept separate.

• Availability by day. A rental of three days takes one unit for three nights. Software should count a unit as out from the first to the last day.
• Prep buffer. Skis returned at 17:00 need wiping and checking before they go out at 08:30. Keep a rule that a returned unit is only available again the next morning, and block same-day turnaround unless you really do it.
• Groups and families. A family of four is four sizing forms and one booking. Make the booking owner responsible for sending the link to the others.
• Deposits. Take a deposit, or a card hold, at booking if your terms allow it, and say clearly what it covers.
• Peak days. Cap online bookings for the busiest days below your actual stock, and keep a few units for walk-ins and swaps.

Most ski rental systems and general rental systems do this. When comparing them, test whether they handle categories, a prep buffer and multi-person bookings. Then compare the price and the text-message costs from each vendor's own page. For ideas from similar seasonal hire businesses, see the bike hire availability tutorial and the kayak rental tutorial, which deal with weather and waivers in the same rhythm.

Kit tracking: tags, scans and five statuses

An item you cannot find is lost money. Give every ski, board, pair of boots, pole set and helmet its own tag number, and mark it where it will survive a season: an engraved or heavy-duty sticker, plus a barcode or QR code. Use a pattern you can read at a glance.

SK-A-0231   adult ski set, beginner, 160 cm
BT-A-0114   boots, adult, mondopoint 270
SB-J-0042   snowboard, junior, 130 cm
HL-A-0305   helmet, adult, medium

Then use five statuses and nothing else: available, reserved, out, returned (to check), in repair. Scan at pick-up to move an item to out, and scan at return to move it to returned. A technician checks each returned item and moves it to available or in repair. The returned-to-check status is the one most shops lack, and it is the one that stops damaged kit going straight back out.

A spreadsheet version for a small shop

Not every shop needs software on day one. A spreadsheet with one row per item (tag, type, size, status, last service date, notes) and a phone camera to photograph new damage can run a shop of a few hundred items. The trouble starts at counter speed: typing statuses during a rush is slow, and two staff editing the same file cause mistakes. That is the point to move to a system with barcode scanning.

Damage terms that customers read

Damage disputes are worst when terms are vague. A clear one-page set of terms, accepted at booking and again at pick-up, makes them easier. Draft it with AI if you wish, but have a qualified adviser review the final text, since rules on fees and liability vary.

Normal wear: light scratches on the base, edge nicks, dirty or damp kit.
Damage: broken or bent skis or poles, cracked boot shells, deep core shots,
broken bindings, missing parts, damaged helmets, damage from misuse.
Charges: repair at cost up to the replacement value; we will show you the damage
and a quote before charging. Lost items are charged at the replacement price
listed on your booking confirmation.
Late returns: kit not returned by [time] on the last day is charged as an
extra day. Please call us if you will be late.
Helmets: any helmet that has taken a hard impact must be replaced; tell us.
Check at pick-up: please check your kit and tell us about damage before you leave.

Note the last line. A walk-around at pick-up, ideally with a photo of each item, protects both sides. For a tidy pick-up routine borrow from the campervan handover checklist tutorial, which solves the same "who damaged what" problem for bigger kit.

Ask AI for a plain-English version

Give the assistant your approved terms and ask for a version a teenager could read in 30 seconds: "Rewrite this at reading age 12, keep every number and condition, add nothing." Compare line by line. If the model changed "up to the replacement value" to "all costs", throw that draft away.

The returns routine

1. Customer returns the kit. Staff or a self-service rack take it in. Scan each tag; the status moves to returned.
2. Counter check. Count the items against the booking, not just by sight. Skis plus poles plus boots plus helmet should match the sizing form.
3. Technician check. Look at bases, edges, bindings, boot buckles and helmet shells. Photograph any new damage next to the pick-up photo.
4. Decide and record. Normal wear: available after prep. Damage: in repair, with a note and the cost estimate.
5. Message the customer. Normal returns get a thank you and a review request. Damage gets a call or message with photos and a quote.

The decision at step 4 is where AI has no business. It can draft the message at step 5, but the judgement about whether a scratch is wear or damage belongs to a person. Draft this message once and reuse it.

Hi [first name], thanks for returning your kit today. While checking it we
found damage to [item and tag]: [plain description]. The repair cost is $[amount]
(see photo attached and your damage terms). We'll hold the charge for 48 hours
so you can reply; call us on [number] if you'd like to talk it through.

Keep the tone factual. If the amount is more than the deposit, say so in the first line, so the customer is not surprised by a second charge.

The messages that save the counter

Write the six messages once, in your own voice, and keep them in your system as templates. Use AI to produce second and third versions in a different tone, or to shorten them for SMS. Keep every price, date and policy as a variable the system fills, not text the model rewrites.

A worked example: a 120-set hire shop on a Saturday

Take an illustrative small shop with 120 ski and board sets and a Saturday with 45 bookings covering about 130 people. Without advance forms, each person takes about 6 minutes at the counter for sizing questions and paperwork. With three technicians that is 130 x 6 = 780 minutes, or 260 minutes (4.3 hours) each. A queue builds from 08:00 and some customers reach the slopes at 10:30.

Now suppose 70% of customers fill the form in advance. Those take about 3 minutes at the counter, to confirm and fit. The other 30% still take 6. Then: 91 x 3 + 39 x 6 = 273 + 234 = 507 minutes, or 169 minutes (2.8 hours) per technician. That is about 90 minutes of counter time saved per technician on one Saturday, and the queue is shorter at the busiest hour. The figures are assumptions; time the counter on one real Saturday and use your own.

On the return side, suppose 3% of sets come back with a disputed mark. Without photos, staff spend maybe 10 minutes per dispute and sometimes absorb the cost. With pick-up photos and terms, a typical dispute takes 3 minutes. On 40 returns a day, that is 1.2 disputes at 10 minutes against 3 minutes. The saving is small per day but real across a season, and the main gain is fewer arguments.

A customer's journey, end to end

Illustrative: a family of four books a five-day hire online in October for February. They receive a confirmation with four sizing form links. Two forms are completed that evening, one a month later, and one at the counter. Three days before arrival a reminder goes to the booking owner. On arrival, the technician pulls the pre-picked kit for the three completed forms, fits the fourth person from scratch, scans each tag to move it to out, and photographs the items next to the customer. The family leaves in 20 minutes. At return, tags are scanned, a technician finds one boot buckle bent, photographs it and sends a message with a quote. The family replies within the hour and pays the amount.

Nothing in that story needed AI at the decision points. AI wrote the form wording, the six message templates and the damage-terms summary. The tags, scans and fitting did the work.

Swaps, early returns and lost items mid-hire

The booking is not finished when the kit leaves the shop. Boots pinch, a child's skis turn out too long, a pole goes missing on a chairlift. Decide the rules now and write them into the terms, so staff are not inventing policy at the counter.

Swaps

Offer a free swap of boots or skis on the first day if the fit is wrong. Record the swap in the system by scanning the returned item and the new one against the same booking, so the tag history stays accurate. A swap that is not scanned is how a pair of boots ends up listed as out for three weeks. Add a note to the sizing record, such as "boots one size up, snug at the heel", so the next hire for the same customer starts closer to right.

Early returns and extra days

Customers who come back a day early rarely expect a refund, but some will ask. State your rule plainly (for instance "no refund for unused days, but we will hold the kit free for a later date within the season if you tell us before pick-up"). For extra days, make it easy to extend by text or at the counter, with the price shown. Have AI draft three replies: one for an extension request, one for a refund request that you decline politely and one for a weather-related request that you decide to grant. Fill in your decisions; the assistant supplies the tone.

Lost or stolen items

Record the tag, the date and the customer's account of what happened, and then apply the replacement charge in the terms. Take a card hold at booking so that a lost item is not a debt you chase. A short, calm message works better than a legal one: "We've recorded [item, tag] as lost on [date]. As in the damage terms you accepted, the replacement charge is $[amount]. If it turns up, bring it in and we will refund the charge."

Junior kit and the growth problem

Children are the trickiest customers. They grow between seasons, forget their boot size and ride kit that gets rough use. A few practical rules help.

• Ask a parent for age, height and boot size, and for the child's ability in plain words, not a level name.
• Keep junior stock in its own pool in the system, so a booking for a child cannot be filled from adult stock.
• For season-long junior hire, schedule a mid-season fit check; kids can outgrow boots in weeks.
• Use a quick counter checklist: boots fit with the child standing, heel down; skis suit height and ability; helmet snug with the strap fastened.
• Keep the technician's judgement final, whatever the form said.

A short prompt can prepare a parent-friendly confirmation message: "Write a 60-word text for parents confirming a junior ski hire. Include the pick-up time, that a technician will check the fit with the child present, and that they can swap boots free on the first day. Do not mention safety settings." Illustrative output: "Hi [first name], your child's ski hire is booked for [dates]. Please bring them to the shop at [time]. A technician will fit the boots and skis with them standing there, and you can swap boots free on day one if they pinch. See you soon." What you would fix: check the swap wording matches your policy.

Bad-weather days and changes of plan

Snow does not always arrive on schedule. Decide in advance what you offer when lifts close or conditions turn: a free date change within the season, a credit, or no change. Whatever you choose, put it on the booking page and in the confirmation so a customer is not surprised. Then prepare a message you can send to everyone booked on an affected day with one click.

Hi [first name], lifts are closed on [date] because of [reason]. Your hire for
[date] can be moved to another day this season at no charge: reply with a new
date or use [link]. If you'd prefer a credit for next season, reply CREDIT.
We'll hold your kit until you confirm.

This is the one message that a bulk tool plus a template genuinely earns its keep on, because on a bad-weather morning you may have 60 bookings to contact before 07:30. Test the bulk send with two staff phones before the season, and check that opt-outs are respected.

Mistakes that show up in the first season

• Sizing system confusion. A visitor writes boot size 9 meaning a different system from yours. Fix: make the system a required field and show a size chart link.
• Kit that reappears too soon. Returned skis go straight into the next booking with no check. Fix: the returned (to check) status and the prep buffer.
• Waivers or terms not accepted. Customers click through without reading. Fix: shorten them, add a short summary at the top, and have staff point at the key lines at pick-up.
• Overbooking a weekend. The online limit equals your total stock. Fix: cap online bookings below stock and keep walk-in units.
• Autopilot AI replies. A model tells a customer that a binding "will be set safely" or promises a size. Fix: keep AI for drafting and make technicians own all fit and safety statements.

How to check it is working

After the first month of the season, review four numbers. Counter minutes per customer at peak (should fall as forms are completed in advance). Percentage of customers who completed the form before arrival (aim to rise week on week, and send the reminder earlier if it stalls). Items missing at closing (should be zero; if not, scanning is being skipped). Damage disputes per 100 returns (should fall as photos and terms take hold).

If one number refuses to move, fix the habit, not the software. A form nobody completes needs a shorter form and a better reminder. A scanning step that is skipped needs the scanner at the point where kit leaves the counter. For a wider view of where AI fits next in a hire business, the event rental inventory tutorial shows tag-and-scan tracking on larger stock.

Questions ski hire owners ask about software and sizing

What should a ski sizing form ask?

Height, weight, age, boot size with the sizing system named, skiing ability level, whether they ski or snowboard, stance if boarding, helmet needs and any injuries or notes. The form collects facts for staff to use. Binding settings and final fitting stay with a trained technician at the counter.

Can AI choose the right skis for a customer?

It can sort and summarise sizing answers and suggest a kit category for staff to confirm. It should not decide binding settings or safety-related fits. A technician checks the customer, boots and bindings together, and the form only saves time before that check.

How do I track which skis are out?

Give every item a unique tag number, mark it with a barcode or QR sticker, and scan it at pick-up and return. Use a few statuses: available, reserved, out, returned, in repair. A spreadsheet can work for a small shop; software helps once scanning and availability are needed.

What should damage terms say?

State what counts as normal wear, what is damage, how you assess it and what you charge for repair or replacement. Have the customer accept the terms at booking and at pick-up. Ask a qualified adviser to review the wording, since rules on fees and liability vary.

How early should I send the sizing form?

Send it with the booking confirmation, then a reminder two or three days before arrival. Forms done in advance cut counter time, but many customers will still arrive without one, so keep a quick counter version.

Further reads

• Tuxedo Rental Software: Fit Dates, Returns and AI Reminders — Fit details and hire dates in another sizing-led rental.
• Which Tool Hire Software Suits a Small Shop? Deposits, Quotes and AI — Deposits and quotes for a tool hire counter.
• E-Bike Rental Software: Bookings, Waivers and Battery Checks — Battery checks and waivers for e-bike hire.
• Party Rental Contract: Damage, Weather and Deposit Terms With AI — Damage, weather and deposit clauses for hire contracts.
• AI Inventory and Check-Out Reports: A Letting Agent's Guide — Check-out reports that show what is missing.
• Dive Shop Software: Courses, Gear Hire and Waivers Handled With AI — Gear hire and waivers in a dive shop.
• AI for a Car Rental Business: Enquiries, Availability and Damage Notes — Damage notes and enquiries for car hire.
• AI in Sports Business: Team Kit Orders With Sizes, Names and Numbers — One club, 30 players, three squads: an order form, a duplicate-number check, a supplier order sheet and parent reminders, with sums and sample prompts.
• Ice Rink Software: Session Booking, Lessons and Party Enquiries — Set capacity from ice and hire stock, run lesson blocks with waitlists, take party enquiries to a deposit, and see where AI helps and where it must not.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: no vendor facts are quoted in this tutorial; it describes the forms, tags and wording a ski hire shop needs. Check each software vendor's own pages for pricing and features.