RTP - Sales Transaction & Order Processing

Overview

When selling in RTP, staff have the option to use Sales Transaction or Order Processing. There isn’t much guidance from RTP itself as to which one to use or why, and both are fairly similar.

So how should you decide which to use? It will vary by resort based on business needs, but an overview of how the two compare:

Sales Transaction

• Aimed at quick ‘walkup’ style transactions

• May or may not be collecting guest information (names, DOBs, contact details, etc)

• Aimed at transactions requiring no follow up

Order Processing

• Aimed at anything being pre-booked or sold remotely (eg online or over the phone)

• Collecting guest information (names, DOBs, etc)

• Used for items which will be fulfilled later (eg once they get to the rental shop)

• Great for products that customers have a tendency to want to cancel, swap days, etc, as it’s much easier to see what they have used, refunded, cancelled, etc.

Recommendations

For RTP products that aren’t mapped in flaik (eg all your non-lesson products) it’s ultimately up to the resort to decide whether to use Sales Transaction or Order Processing. It might even vary by department or the type of product being sold.

As for your lesson products, for any RTP product mapped in flaik we recommend always using Order Processing.

• Depending on your RTP <>flaik sync settings, you may need to change private Assign/Request status in RTP, and that can only be done in Order Processing.

• If guests frequently want to change booking dates/times/etc, it’s easier to manage in Order Processing than Sales Transaction (as otherwise you’d need to read through Transaction History to determine what they have or haven’t used)

• Inventory Pools - Sales Transaction allows for inventory pools to be oversold in certain situations, whereas Order Processing handles the inventory pool ceiling correctly.