Export housekeeping data from Oracle Opera Cloud

Oracle Opera Cloud XML export for housekeeping

Three reports out of Oracle Opera Cloud are enough to run a hotel's housekeeping in ARPCLEAN. Two of them describe the building and run once. The third is the day's work, and it runs every morning.

You already know how to produce all three. There is no integration project behind them, no implementation call, and no CSV to clean up afterwards. The export behaves the same way it behaves in Opera Cloud today.

The three XML reports

Run these in Opera Cloud and leave the file names alone. ARPCLEAN reads the name to work out which report it has just received.

1. cf_roomtypes.XML lists every room type the hotel sells. It arrives first, and the Service Plans your team cleans against are built on it.
2. cf_rooms.XML is the physical room list: numbers, floors, and the room type each room belongs to. Together with cf_roomtypes.XML it gives ARPCLEAN the shape of the building.
3. task_sheet_report.XML is the day itself. Check-ins, check-outs, stayovers, and in-room requests such as an extra bed or a minibar restock.

The first two run once, when the hotel is set up. task_sheet_report.XML runs daily. That one file is what replaces printing the task sheet, sorting it by floor, and typing it up again on the other side.

Email the report, or upload it yourself

Every hotel gets its own @arpclean.com address, shown on the activation screen the moment you create the hotel. Send any of the three reports there and it imports on its own, in whatever order the files happen to arrive.

You can also upload the same file by hand from inside ARPCLEAN, and you can decide per file. A common split is to upload cf_roomtypes.XML and cf_rooms.XML once during setup, then let Opera Cloud email task_sheet_report.XML every morning without anyone touching it again.

Opera Cloud has no employee export

There is no staff export on that list, and there does not need to be one. Your cleaners, team leaders and inspectors work for your cleaning company, not for the hotel's PMS, so their details never have to leave Opera Cloud in the first place.

Two invitations bring them in instead. Invite your Team Leader, and they invite their own crew. Invite your Housekeeping Manager, and that is the person who keeps task_sheet_report.XML arriving each day. Nothing about how you staff a hotel depends on what its PMS is willing to hand over.

When the trial clock starts

The 30-day trial does not start when you sign up. It starts at the first successful task_sheet_report.XML import, the moment real work from a real hotel lands in the system.

That leaves you room to prepare. Creating the account, inviting your Team Leader and scheduling the export on the Opera Cloud side all cost nothing and burn no trial time. Every feature is open for those 30 days, no card is needed, and nothing is charged when they run out. There is no free plan waiting underneath, so access ends with the trial unless you subscribe.

What this replaces

A conventional Opera Cloud integration is a paid project. Expect a setup fee of €2,000-10,000 before the first hotel goes live, on top of the sales call and the implementation schedule that come with it.

Three XML reports carry none of that, and ARPCLEAN charges no setup fee at all. Once the trial ends the Pro plan is €199 per hotel per month, or €169 per month billed annually. The price does not move whether Opera Cloud sits behind every one of your hotels or only some of them.

Every hotel after the first

This is not a one-time setup you have to remember how to repeat months later. Your second hotel and your twentieth go through the same three exports from their own Opera Cloud property code: cf_roomtypes.XML and cf_rooms.XML once to build the structure, then task_sheet_report.XML daily to keep it running.

The steps do not change as your cleaning company grows. Only the number of hotel mailboxes does.