> For the complete documentation index, see [llms.txt](https://mtrsolution.gitbook.io/eventic/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mtrsolution.gitbook.io/eventic/orders/the-add-to-cart-and-order-process.md).

# The add to cart & order process

In this section, we are going to highlight the order process.

An order can be defined as the purchase of tickets. An order can be placed and paid online, or via the Point of sales and in this case paid in cash.

## How is an order placed in Eventic?

1. Attendees choose an event and click on the Tickets button
2. A pop up with the event tickets information shows where the attendee chooses the tickets number to buy
3. Next, attendees click on the Add to cart button
4. Attendees continue to add tickets to the cart or simply move to Checkout
5. The Checkout form contains the billing information and the payment method
6. Once the Pay Now button is clicked, the attendee is redirected to the secure payment gateway form
7. Upon payment success, the attendee is redirected to the order confirmation page 
8. An confirmation email containing the tickets (PDF) is sent to the attendees


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://mtrsolution.gitbook.io/eventic/orders/the-add-to-cart-and-order-process.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.