WebSoftOS
Event & Rental ERP · Illustrative scenario
How a rental house tracks bookings, dispatch, returns and deposits
Utsav Tent & Decor House (fictional) · Lucknow, Uttar Pradesh. A tent, décor and AV rental business handling 20–40 events in peak wedding months.
Illustrative scenario. The company in this story is fictional. It shows how a business of this profile would typically set up and use WebSoftOS. It is not a customer testimonial and it does not report measured results.
The starting point
- Item availability was checked from memory, causing clashes in wedding season.
- Security deposits and damage deductions were tracked in a notebook.
- Dispatch and return checklists were on paper, so shortages surfaced late.
How WebSoftOS would be set up
- Rental item master with quantities and pricing rules.
- Event bookings with availability check across dates.
- Dispatch and return challans with condition notes; security deposit handling.
- Payment links and GST invoicing.
Before and after
| Step | Before | With WebSoftOS |
|---|---|---|
| Booking | Diary and phone calls | Availability checked against date-wise stock |
| Dispatch | Paper checklist | Dispatch challan generated from the booking |
| Return | Counted on arrival, noted by hand | Return recorded against dispatch with shortages flagged |
| Deposit | Notebook entry | Deposit held and settled against damages |
What the team can do afterwards
- Double-booking of the same items is flagged at booking time.
- Shortages and damages are tied to the specific event.
- Advance payments can be collected through payment links.
Rollout
Typical rollout: 2–3 weeks, starting with the item master and a few upcoming events.