Skip to main content
Q-Code

Commerce · 3 modules

What are the commerce modules?

The commerce modules are the three that let a site take money or take bookings: catalogue, payments and appointments.

The catalogue reshapes itself for whatever you sell, payments run through your own Stripe account, and bookings hold real availability. Between them they cover selling a thing, selling a slot, and listing something that is not for sale at all.

The 3 modulesAll 17 modules

Why this group exists

What commerce is for.

Commerce is where template builders usually stop being useful, because 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.

The answer here is one engine that is told what shape its items are, rather than four engines that each assume one. Money and calendars then plug into that, and both run on accounts you hold.

The modules

3 in this group.

Catalogue engine

@ccd/catalogue

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, with a gallery that works on a phone.
  • Writes descriptions from the real specification, so nothing is invented.

Payments

@ccd/payments

Stripe Checkout on your own Stripe account, with receipts from your own domain.

  • Takes one-off payments, deposits and subscriptions without holding a card number on the site.
  • Pays out to your account directly, with no platform cut in the middle.
  • Sends the receipt through the mail module, so it comes from your address.

Bookings

@ccd/bookings

Real availability, real time zones, and a deposit taken at the point of booking.

  • 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 the payments module when a no-show is expensive.

Q&A

Questions about the commerce modules

Whose Stripe account is the money paid into?

Yours. The payments module connects the site to your Stripe account and Stripe pays you directly. Q-Code takes no percentage of what you sell.

Can the catalogue 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 with no price on it at all.

Do the AI descriptions make things up?

They are written from the field values on the item and are 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.

The other groups

Where to look next.

  • Foundations

    Visibility engine, Domains and SSL, Branded email, Analytics.

  • Content

    Editable pages, Self-improving blog, Media library, Brand voice.

  • Engagement

    Forms and inbox, Testimonials, Social profiles.

  • Growth

    Newsletter, Lead capture, Agent interface.

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