Getting started

Glossary

The most important planni terms explained.

Selling: Product, Event, Module

The basic building blocks

  • Product: the template for what you sell. There are three types: Event Product (a bookable date with capacity), Digital Product (courses, e-books, downloads) and Other Product (for example parking or catering).
  • Category: an internal grouping for products, used for example to filter event tables and workflows. Categories are not visible to your customers, and a product can belong to several.
  • Event: a concrete date or a series of dates created from an event product.
  • Module: a single date within an event. A one-day seminar has one module, a multi-part training has several. Attendees always book the whole event, never a single module.
  • Location: the place where a module takes place, physical with an address, or online with a meeting link.
  • Checklist: a list of items worked through for an event, for example "documents sent?". Checklist templates are assigned to products and can be extended per event.

Booking: Checkout, Order, Invoice

Around checkout

  • Event table: a widget you embed in your website as a code snippet, showing your published events as a table. It updates itself automatically.
  • Cart: the widget where a visitor collects the chosen products and goes through checkout.
  • Cart links: URLs that put a product, optionally with a specific date, straight into a visitor's cart, useful for individual buttons or newsletters.

Around the order

  • Order: the booking created when someone buys through checkout. Contains the purchased items and prices.
  • Orderer: the person who placed the order and whose billing details are on file.
  • Recipient: the person tied to a purchased item, for example the person who actually attends. The orderer and the recipient can be the same person or different ones, for instance when someone books for several colleagues.
  • Invoice: the billing document for an order, or for a contact or company, exportable as a PDF.
  • Discount code: a code buyers enter at checkout to get a reduction on selected products or categories.

Automation: Workflow, Email, Mailbox

How automatic messages happen

  • Workflow: an automation made of a trigger, for example "order created", and an action, for example sending an email template.
  • Email template: a reusable email with placeholders, such as first name or order details, that a workflow fills in and sends automatically.
  • Mailbox: an email account connected to planni, through which you receive and send email and through which workflows send email.
  • Central mailbox: exactly one of your connected mailboxes. Sender display, the assignment logic for incoming email, and the team signature only apply to this one.

Administration: Objects and access

Recurring settings

  • Custom fields: extra fields you create for contacts or orders, for example a cost centre. Several field types are available, such as text, date or file upload.
  • Calendar type: a colour-coded category for calendar entries outside of events, for example vacation or sick leave.
  • API key: an access key with configurable permissions for external integrations that access planni.
  • Roles: Super Admin, Admin, Backoffice Manager and Staff, they decide who can see and edit what. Explained in full under Roles and permissions.

On this page