Order form with TCMS integration

I have a new customer who wants to sell tickets for events via his website (which I am currently creating for him with F6).

There are 7 events that take place throughout the year. These are to be maintained as blog posts (TCMS1) or objects (TCMS3) by the customer himself. At the end of a year, the events for the following year are then entered. The events are presented 'as usual' with a Blog List and a corresponding Blog Post page. Each Blog post could link to the order page with the form.

It should be possible to order tickets for these events using a form. Payment should be made by direct debit or alternatively by invoice. This means that no online payment options such as PayPal etc. are required.

Ecwid is too expensive for the customer, and he doesn't actually need a real “store”, as only order emails are to be sent to the customer and the tickets are to be sent manually once payment has been received.

The problem: Since a buyer should also be able to order tickets for several events at once (so that he only has to enter his address once), the order form would need a list automatically generated from the titles of the blog posts or objects with checkboxes for the events and a number field for the number of tickets per event. There should then be a field in which the total cost of the order appears (possibly via Pi-Stack?). By the way, all tickets cost the same (€ 18.-). The order form could be created with F6 Forms or FormSnap. A signature function would be important because of the direct debit authorization; but signature stacks (now) exist for both solutions.

The ordered events (incl. the respective number of tickets) should be sent as a nicely formatted e-mail to the buyer for confirmation and as an order to my customer.

Is this feasible purely with F6, TCMS, feeds etc. and additional stacks or would a store be required for this?

Below is a screenshot of the form area that concerns the events (the other fields are not a problem). I would be very grateful for any tips on this... 🙂

11 replies