> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/classes/administrative-functions/place-orders.md).

# Place orders

{% @arcade/embed flowId="eXMIsWy9lYPWo2MHqXQ3" url="<https://app.arcade.software/share/eXMIsWy9lYPWo2MHqXQ3>" %}

***

### Selecting a product or service

When you open a product or service in the Marketplace, you see all relevant information such as pricing, description, and available options.

<figure><img src="/files/bp0Z3s6ertlYrK2MLXyL" alt=""><figcaption></figcaption></figure>

From here, you do not place the order directly.\
Instead, you assign the selected item to its intended recipient using the **Assign** action.

This applies to:

* individual employees
* multiple employees
* teams
* departments or locations

At this point, you are defining **who should receive what**, not executing the order yet.

***

### Assigning services via the Marketplace

Assigning a service in the Marketplace prepares it for ordering.\
You select the target recipient and confirm the assignment. This step defines the scope of the order and ensures the service is linked to the correct employee, team, or location.

<figure><img src="/files/uIGL6XgOo5vYEywWUatS" alt=""><figcaption></figcaption></figure>

This approach is especially useful when:

* multiple people need the same setup
* teams are onboarded together
* standardized services are rolled out
* assignments should be prepared centrally

***

### From assignment to approval

<figure><img src="/files/A2FGgho7gf5mQ4rIXJFd" alt=""><figcaption></figcaption></figure>

After a service is assigned, the order is not executed immediately.\
Instead, it appears in the approvals.

This approval step allows the assignment to be reviewed before it turns into an actual order. Once the approval is granted, the order is executed.

***

### Executing the order

After approval, the order is created in the system.\
The service is assigned to the selected recipient and moves into the standard fulfillment process.

From here on, the usual workflows apply, including provisioning, delivery, and service activation.


---

# 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:

```
GET https://hub.equipme.io/classes/administrative-functions/place-orders.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.