ENProgramme administrator
Sets dates, capacity, variants, price and registration fields.
Commerce, courses and fulfilment
Courses and conferences from date to attendee list.
Dates, capacity, registration, pricing, payment and organiser material in one institutional sales flow.
For course, conference and continuing-education organisers.
See the process
From start to finish
A participant registers, orders and receives programme confirmation.
Programme and date
The organiser publishes the programme, date, capacity and available variants.
Participant registration
The participant enters their details and chooses a suitable date or option.
Order and payment
The order follows the configured payment method or an internal organisational rule.
Attendance confirmation
The participant receives confirmation and documents while communication stays together.
Organiser list
The organiser gets a current list and finance data follows the configured integration.
Who is involved
Who is responsible for what.
Participant
Chooses a date, orders attendance and receives confirmation.
Organiser and finance
See capacity, payment, attendee lists and finance hand-off.
What happens when something goes wrong
Full capacity, changed date or unpaid order
The system blocks overbooking and supports controlled changes or cancellation.
The result
Confirmed registration, payment status, attendee list and finance hand-off.
Product and integrations
The solution connects to the systems you already use.
Forms, roles and rules follow the way your team works. Every integration keeps the source of truth and error ownership clear.
Explore the product: Commerce, courses and fulfilment →EOCPayment gateway by deploymentFinance systemDocument generationIdentity and customer groups
Related solutions
What can connect to this workflow
Concise answers
Frequently asked questions
Who is this solution for?
For course, conference and continuing-education organisers.
What happens when the input is incomplete or incorrect?
Full capacity, changed date or unpaid order. The system blocks overbooking and supports controlled changes or cancellation.
What is the outcome of the workflow?
Confirmed registration, payment status, attendee list and finance hand-off.
Next step
Facing a similar situation?
Tell us how the work runs today and where it gets stuck. We will reply with a concrete next step, not a generic presentation.
Describe my situation