> 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/release-updates/2026/november.md).

# November

### **Update 19.11.2026 Release**

Both updates in this release are available to suppliers, managed customers and standalone customers. They are built to work together.

{% embed url="<https://app.arcade.software/share/9cbzqVqPUTlEz0KLHSux>" %}

### Start an approval request yourself

Until now, an approval request only existed once someone requested something in the marketplace. We created it automatically and sent it into the approval flow you configured. That works for single products. It doesn't work when the need is bigger: an event, a new office, a project that has to be approved before anyone orders anything.

You can now start an approval request yourself.

**It starts with a request form.** Under **Offer management → Request forms**, you build the templates for these requests. Each one has a name, a description, an image and its own form. Once it's active, it appears in the marketplace in its own section, right below your templates.

![The Request forms section in the marketplace, right below the templates](https://3918610632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNunUyX5NO7xn5mXKS3V%2Fuploads%2Fs6eY60T5Fw0Mnv7MYFOn%2F01-marketplace-request-forms.png?alt=media)

**Building the form.** The designer offers a wide range of question types, from single-line text and dropdowns to checkboxes, sliders and yes/no questions. Mark a question as required, and nobody can continue without answering it. On the **Logic** tab, you show a question only when it makes sense: ask for the address of a new location only if someone picks New location. On the **Translations** tab, you add the wording for every language your users work in. We don't translate your questions for you. Before you save, the **Review** step shows the entry as it will appear in the marketplace and the complete form.

**Fill it in, then add what you need.** Open the request form in the marketplace and fill it in. With **Add services**, you add everything the project needs: products from the marketplace, items from stock, or a product request for something that isn't in your portfolio at all. You see the total one-time and monthly costs before you send it. You can also send the form on its own and add services later.

**Your request starts as a draft.** When you send it, we save it in **Approvals** with the status **Draft**. A draft is visible only to you. No approval flow starts and nobody is notified. You can add and remove services as often as you like. The form answers can't be edited in a draft yet. To change them, delete the draft and create it again. Deleting a draft removes it with all its services.

![An approval request saved as a draft, with form answers, requested services and total costs](https://3918610632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNunUyX5NO7xn5mXKS3V%2Fuploads%2FFWu2SeJ4UdoglMVYNchp%2F02-approval-request-draft.png?alt=media)

**Submit it when you're ready.** From then on, the request runs through your approval settings like any other. If your setup sends approvals to the supervisor, the supervisor is assigned and gets the usual email. The approver sees your form answers, every requested service and the total costs. If something suitable is already in stock, they use **Exchange for stock items**, pick the item from your inventory, and the position becomes a call-off from stock. Anything that isn't needed, they take out with **Remove service**. Then they approve or reject the request. Approved services continue to purchasing as usual. Every change along the way is recorded in the **History** tab.

***

### Request products that aren't in your portfolio

Sometimes the right product simply isn't in your portfolio. An employee found a monitor at an electronics store. Someone needs balloons for the New Year's party. Until now, there was no way to ask for things like that in equipme.

There is now a new offer type: **Request**. You create the product in your service portfolio as usual. In the pricing step, you choose **Request** instead of purchase, rent or leasing. A request has no price of its own, so all you set is the currency and who the offer is available to. On the product's **Form** tab, you then build the form that asks for what you need to know, such as a description or a link to the product.

![The offer type Request in the pricing step of a new product](https://3918610632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNunUyX5NO7xn5mXKS3V%2Fuploads%2FM1bQUQT1zWjJkFiQKEtX%2F03-offer-type-request.png?alt=media)

In the marketplace, the product shows **Price on request**. Whoever requests it fills in the form and assigns it like any other product, to themselves or to an employee. If they know the price, they enter it as a one-time or monthly price. That price counts toward the total costs the approver sees, so nobody approves a budget that leaves out half the items.

![A product with Price on request in the marketplace, with its form and an optional price](https://3918610632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNunUyX5NO7xn5mXKS3V%2Fuploads%2FjDYkxk1o2I6MjnUMxQhS%2F04-price-on-request.png?alt=media)

**Handling a request.** The request shows up in **Order requests** with the type **Request**, and in Approvals if your approval settings apply. Whoever handles it sees the form answers and can adjust the price, for example once they've found a better offer. Then they have two options. They reject the request, and the requester gets the usual email. Or they use **Exchange for stock items** to replace it with something you already have. Since a request never has stock items of its own, the filter **Same product** stays empty here. Look under **Same category** or **All available** instead. If you buy the product yourself, add it to your stock first and then exchange the request for it.

**A request can be approved, but never ordered.** There is no real offer behind it, so it never reaches a supplier. It stays inside your organization. When the rest of an approved request goes to purchasing, request items stay in Order requests until someone handles them.

**One product, several offers.** A Request offer can sit next to normal offers on the same product. You might rent out a monitor model at a fixed price and still allow requests for the same model from another store. Because Request is an offer type and not a separate kind of product, everything you already control per offer applies: country restrictions, suppliers and self-service visibility through tags.

**Combine it with your request forms.** Product requests are what makes the first update in this release work. When you plan an event, you add what's in your portfolio and request everything that isn't, all in one approval request.

***

### **Update 12.11.2026 Release**

### Send orders to your own suppliers automatically

When you order products from a supplier you have added yourself, the order no longer has to be passed on by hand. Set the supplier's order type to **Automatic**, and every order goes out by email to all addresses listed under **Order recipients**, with a PDF that contains the complete order.

<figure><img src="https://3918610632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNunUyX5NO7xn5mXKS3V%2Fuploads%2FuFSB0JfQlkcRg9CNbbLc%2FEdit-Supplier-Dialog-Steps.png?alt=media&amp;token=cc9178c2-fdbe-495f-880c-c5fc01cdd759" alt=""><figcaption></figcaption></figure>

This keeps your own suppliers in the same flow as everything else you order through the marketplace. Nobody has to remember to forward an order, and the supplier receives the same information every time.

If you prefer to handle orders yourself, keep the order type on **Manual**. In that case, no email is sent and you place the order with the supplier as before.

You find the setting in the supplier's details under **Order type**. Order recipients are managed separately on the supplier's overview, so you can send orders to a shared sales inbox without adding it as a contact.

<figure><img src="https://3918610632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNunUyX5NO7xn5mXKS3V%2Fuploads%2FSbtAim1123ENScdLNOnM%2FOrder-Recipients-Card.png?alt=media&amp;token=5cd24e21-d382-48c7-8733-a023b1d239c7" alt=""><figcaption></figcaption></figure>

***

### **Update 05.11.2026 Release**

Both updates in this release are for suppliers and available in Equipme Pro.

### Authorized signatory for your customers

Every customer has someone who signs contracts. Until now, equipme had no place for that person. You kept it in your head, in an old email or in a separate CRM.

<figure><img src="https://3918610632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNunUyX5NO7xn5mXKS3V%2Fuploads%2F85yuhneS2JxYFfnscaFh%2FCustomer-Details-Card.png?alt=media&amp;token=c54deac7-b5ce-4d8c-b25f-89d93a4a6b7e" alt="" width="563"><figcaption></figcaption></figure>

You can now record the **Authorized signatory** directly in the customer details, alongside the account manager and the contact. You pick the person from the customer's employee list. Free text and external email addresses are not possible: the signatory has to exist as an employee of that customer in equipme. That ties the field to a real person whose details stay current with the rest of the customer's data.

For now, each customer has one authorized signatory.

**Not the same as the account manager.** The account manager belongs to your own organization and looks after the customer. The authorized signatory sits on the customer's side.

***

### You decide which shared customer data you take over

<figure><img src="https://3918610632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNunUyX5NO7xn5mXKS3V%2Fuploads%2FKvlg43HhSa7rTJbRODbO%2FPartner-Connect-Partnerships%20(1).png?alt=media&amp;token=b37ce209-dc54-4b89-8675-db188541cc4d" alt=""><figcaption></figcaption></figure>

Partnerships in Partner Connect work in one direction. When you activate a partnership with another supplier, you unlock their offers for your customers. They only see yours once they activate a partnership with you as well. So far, Partner Connect only showed one side: the partners you connected with.

The new **Partnerships** tab shows the other side. It lists every supplier who has entered into a partnership with you.

**What partners share.** A partner who turns on **Share contact information** shares three things about the customers you have in common: the contact, the authorized signatory and the customer number. Until now, sharing covered the contact only, and it simply arrived on your side. You never confirmed that you wanted it.

**What you take over.** Select a partnership and choose which of the three fields you take over. The dialog also shows you whether the partner currently shares at all.

<figure><img src="https://3918610632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNunUyX5NO7xn5mXKS3V%2Fuploads%2FhnwAKwzUoASXPIfntchl%2FTake-Over-Shared-Data-Dialog%20(1).png?alt=media&amp;token=d847e7c2-faf1-41c9-a862-49baa074812e" alt=""><figcaption></figcaption></figure>

Before you tick a box, keep three things in mind:

* **Taken-over fields are read-only.** They stay in sync with your partner, and you can no longer edit them in the customer profile.
* **Your partner's changes always win, including empty values.** If they clear a field, it is cleared on your side too.
* **A taken-over customer number becomes yours in practice.** It appears on your own orders and invoices. If your accounting relies on your own numbering, leave this box unticked.

**Fields you don't take over stay yours.** You maintain them yourself, for example with your own customer number. If you stop taking over a field, we clear it so you can enter your own value.

**The authorized signatory is the exception.** You have no access to the employees of a partner's customer, so you can only fill this field by taking it over.

This applies to partnerships between suppliers only. Standalone customers and managed customers are not affected.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hub.equipme.io/release-updates/2026/november.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
