Groupon will call your system every 60 minutes to update our cache of availability for all the products that we offer on our platform. This is done to ensure that our customers have an indication the services and products are available on Groupon.
The availability data provided by your system need to be based on when a Groupon customer can make a reservation. For example, if a merchant has a tour reservations available at 10:00 and an end time of 11:00 then you need to provide this amount to Groupon.
As Groupon needs to present potential bookings by the different options available for a product during the booking the attributes used to present these bookings must meet the following quality requirements:
1. Make sure that ticket types are unique and named consistently. For example, do not send a ticket type for “Adult” and “Adults” for the same deal.
2. For ticket types based on age groups, specify the age range for each label. For example: “Senior (age 65+).”
3. All questions asked in the Additional Info section of a booking need to be General Data Protection Regulation (GDPR) compliant and approved by Groupon’s legal team, especially if a question is pertaining to a child.
4. Questions in the Additional Information section should be spelled correctly, be checked for grammar errors, and be written in a question format that will make sense to your users.
5. The Additional Information section should not include questions such as “How did you hear about us?”, because you already know the deal is being purchased on Groupon.
The order in which attributes are sent to Groupon are the order in which they will be displayed on the iFrame. Tours and Attraction deals should be sent in the following order:
Questions in the Additional Info section must be of the following types based on the CheckoutFields spec. You must have prior approval from the Groupon legal department to collect email and phone number information.
Note: Due to the size of request Groupon's latency SLA does not apply to availability ingestion.
