Common Troubleshooting: Child Registration
Q: How do I assign Child Registration to an attribute instead of the whole product?
A: When assigning the Child Registration classification to a product in the assignment page, product attributes should appear under the dropdown once selected. Use the checkboxes to assign the classification to the desired attribute. If the attributes do not appear, ensure the attributes are correctly applied to the product.
Q: Child Registration is not appearing in checkout.
A: Most common resolutions are:
Ensure the Product Classification “Requires Child Registration” is created.
Ensure the “Requires Child Registration” Classification is assigned to the product. Clear the cache in admin and refresh your browser.
Q: Can you explain the logic for multiple child registrants and emergency contact information?
A: Below find a few scenarios that explain the child registration function:
Scenario 1: Kiddo 1 and 2 have no profile data in RTP|One, Kiddo 3 has RTP data, no changes are made to prepopulated data
Logged in User = Mom, Mom has phone # on file, Kiddo 1 has no data, Kiddo 2 has no data, Kiddo 3 has Dad as Emergency Contact
Rental profile 1 → Kiddo 1 → Mom’s phone # is prepopulated → no changes are made
Rental profile 2 → Kiddo 2 → Mom’s phone # is prepopulated → no changes are made
Rental profile 3 → Kiddo 3 → Dad’s phone # is overwritten by Mom → no changes are made
Result = Kiddos 1, 2, and 3 have mom’s phone #
NOTE: Any subsequent field that is edited and saved with different emergency contact data will retain newly save keyed in entry.
Scenario 2: Kiddo 1 and 2 have no profile data in RTP, Kiddo 3 has RTP|One data, changes made to prepopulated data
Logged in User = Mom, Mom has phone # on file, Kiddo 1 has no data, Kiddo 2 has no data, Kiddo 3 has Dad as Emergency Contact
Rental profile 1 → Kiddo 1 → Mom’s phone # is prepopulated → change Emergency contact to Uncle Bob and submit → Uncle Bob’s EC# saved to RTP profile
Rental profile 2 → Kiddo 2 → Uncle Bob’s phone number is prepopulated → Submit
Rental profile 3 → Kiddo 3 → Dad’s phone # is overwritten by Uncle Bob’s phone # → Submit
Result = Kiddos 1, 2, and 3 all of Uncle Bob’s phone # as emergency contact
NOTE: Any subsequent field that is edited and saved with different emergency contact data will retain newly save keyed in entry.
Scenario 3: Kiddo 1 and 2 have no profile data in RTP, Kiddo 3 has RTP data, changes made to Kiddo 2
Logged in User = Mom, Mom has phone # on file, Kiddo 1 has no data, Kiddo 2 has no data, Kiddo 3 has Dad as Emergency Contact
Rental profile 1 → Kiddo 1 → Mom’s phone # is prepopulated → no changes are made → Submit
Rental profile 2 → Kiddo 2 → Mom’s phone # is prepopulated → changes are made to make # Uncle Bob’s phone number → Submit
Rental profile 3 → Kiddo 3 → Dad’s phone # is overwritten by Uncle Bob’s phone # → No changes are made
Result = Kiddo 1 has mom’s phone #, Kiddos 2 and 3 have Uncle Bob’s phone # for their emergence contact
NOTE: Any subsequent field that is edited and saved with different emergency contact data will retain newly save keyed in entry.