Skip to main content
Q-Code

Catalogue and booking · 2 modules

What are the catalogue and booking modules?

The catalogue and booking modules are the two that let a site show real stock and real availability: listings and booking.

Listings is one engine that reshapes itself for cars, property, products or services, and booking holds real availability and time zones rather than a contact form pretending to be a diary. Taking a deposit or a payment on either is a Stripe-based skill built for the project, not a module.

The 2 modulesAll 20 modules

Why this group exists

What catalogue and booking is for.

A car, a flat, a haircut and a bag of coffee want genuinely different fields and genuinely different filters. A fixed product schema fits one of those and fights the other three, so listings is told what shape its items are rather than assuming one.

Booking holds the calendar side of the same problem: iCalendar confirmations that every calendar app already reads, built from opening hours and what is genuinely free. Where money changes hands on either, that runs through Stripe Checkout as a skill built for the project, on an account in the owner’s name, rather than a module every site carries whether it sells anything or not.

The modules

2 in this group.

Listings

@ccd/listings

One listing engine that reshapes itself for cars, property, products or services.

  • Defines the fields for your kind of item, then generates the filters from those fields.
  • Holds up to ninety photographs an item, through the gallery module, in a viewer that works on a phone.
  • Writes descriptions from the real specification, so nothing is invented.

Booking

@ccd/booking

Real availability and real time zones, confirmed by email and added to a calendar.

  • Publishes only the slots that are genuinely free, from opening hours and existing bookings.
  • Confirms by email and adds the appointment to a calendar the customer already uses.
  • Takes a deposit through a payment skill built for the project, when a no-show is expensive.

Q&A

Questions about the catalogue and booking modules

Can the listings module handle something that is not a product?

Yes, and that is the point of it. The fields are defined per project, so the same engine runs a car forecourt, a lettings list, a menu or a portfolio of past work.

Do the AI descriptions make things up?

They are written from the field values on the item and told to use nothing else. If the mileage field is empty the description does not mention mileage, which is the only safe behaviour when the text is a claim about a real object.

Is payment an installable module?

No. Taking money is built as a Stripe-based skill for the specific project, on the owner’s own Stripe account, rather than shipped as a module every site carries whether it sells anything or not.

The other groups

Where to look next.

  • Foundations

    Visibility engine, Analytics, Security baseline, Legal pages, Cookie consent.

  • Content

    Self-improving blog, FAQ, Testimonials, Gallery, Footer.

  • Engagement

    Contact form and inbox, Newsletter, Social profiles, AI chat.

  • Accounts and agents

    Admin dashboard, Sign-in and members, Google connections, Agent access.

Describe the feature, not the module.

You are not expected to know which of these you need. Say what the site should do and the build reaches for the parts that already exist.

See how a build worksThe whole library