1. Home
  2. Selling Tickets
  3. Required Child Listings - Chobble Tickets

Parent/child listings

A parent listing can require buyers to choose child listings before they can check out. Useful for required extras, bundled items, and any booking where one thing requires another.

When one booking needs another

Some bookings do not stand alone. A festival pass might need a camping pitch. A course booking might need a materials kit. A ticket might require a meal add-on. Chobble Tickets lets you mark a listing as a parent, and require buyers to choose one or more child listings before they can check out.

The parent and child are both ordinary listings, each with its own price, capacity, dates, questions, and description. The parent/child link is a relationship between them, configured from the listing edit page.

How buyers choose

When a buyer books a parent, the booking form shows a child selector underneath. They pick quantities of the child listings that, together, match the parent's quantity. A live "X of Q chosen" hint shows whether they have picked enough.

If only one child is bookable, it auto-selects, so the buyer does not have to do anything. Children that do not fit the chosen date or duration are disabled, so a buyer cannot pick an incompatible option.

A festival pass checkout with two passes and one place each in general and quiet camping, totalling £120
The child quantities must add up to the number of parent tickets before checkout can continue.

Children are only seen through the parent

A child listing is not advertised on its own. It does not appear in public event listings, feeds, galleries, share links, QR codes, or the JSON API entry points. Buyers only encounter a child through its parent's booking page.

A parent with no bookable children left shows as sold out, because there is nothing to choose.

Single-level only

A child cannot also be a parent. This keeps the booking flow simple and avoids deeply nested choices. A daily child inherits the parent's date, and a multi-day child must match the parent's duration.

On the attendee record

The attendee detail page shows the relationship: a parent row lists the children it "includes", and a folded child row shows it is an "add-on under" the parent. The shared order token ties them together.

The public JSON API advertises a parent's required children on its detail and availability endpoints, and the booking endpoint accepts a children array alongside the parent quantity.