Resort sales team automates product launches across every booking channel

1The problem

• Product rates and packages lived in a SharePoint master, but publishing meant re-keying them into the sales channel platform by hand — 10 windows, 149 mouse clicks, and over 7 minutes per recorded run.
• Launches were date-bound: rate codes had to go live on their bind dates, so staff watched calendars and executed under time pressure.
• Three hotel properties shared the process, so every manual re-entry was also a standardization risk — the same product configured slightly differently each time.
• Errors surfaced late and informally; there was no unified log of what was published, extended, or withdrawn, or when.

2What we did

1. 1An unattended robot exports the two master data sources — rates and packages — from the SharePoint product master into a working file for robotic processing.
2. 2It analyzes both sources to determine the action required, and validates required columns before any job starts — bad rows stop before they reach the portal, not after.
3. 3Each change routes into one of eight scenario workflows: new rate preparation before launch, rate binding on the go-live date, new package preparation and binding, withdrawing rates or packages, extending to new sales windows, and pulling selected windows off an existing offer.
4. 4The robot logs into the product portal and executes each scenario end to end, working through setup, binding, and close-out steps exactly as prescribed.
5. 5Every stage writes its own error log, and each run produces a robot summary file that is uploaded back to SharePoint — one place to see everything that happened.
6. 6Predefined business exceptions are handled gracefully per workflow; anything unknown is captured with a screenshot and recorded as a system exception.
7. 7Each completed workflow emails the business users — including failures, so nothing disappears silently.