> 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/pro/procurement/order-proposals.md).

# Order proposals

Order proposals in Equipme Pro: stock purchase from minimum stock and customer demand, dropshipping proposals per customer item, and how you use them to trigger an order with the supplier.

**Path:** **"Purchasing" → "Order proposals"**

The order proposals show you what you need to purchase. Equipme Pro continuously determines them from the confirmed customer orders and the minimum stock levels of your stock products. From here, you trigger orders with your suppliers.

The page has two tabs. A number on the tab shows how many proposals are open.

| Tab                  | Content                                                                            |
| -------------------- | ---------------------------------------------------------------------------------- |
| **"Stock purchase"** | Products you should reorder for your warehouse                                     |
| **"Dropshipping"**   | Customer items whose products the supplier should deliver directly to the customer |

## Stock purchase

### How the proposal is calculated

For each product marked as a **"Stock item"**, equipme calculates:

```
Available   = stored + in transit (ordered, not yet assigned to an order) − open customer demand
Quantity    = minimum stock − available
```

If the quantity is greater than 0, the product appears as a proposal. This way, a proposal covers both: open customer orders and topping up to your minimum stock.

{% hint style="info" %}
Only **confirmed** orders count as customer demand. Orders still waiting for confirmation in the [Order Inbox](/pro/sales/order-reception.md) and dropshipping orders are not included.
{% endhint %}

### The table

| Column                                             | Content                                                                                  |
| -------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| "Standard supplier"                                | Supplier of the default offer from the product master data                               |
| "Quantity"                                         | Suggested order quantity                                                                 |
| "Manufacturer", "Name", "Manufacturer part number" | Product                                                                                  |
| "Available"                                        | Calculated available quantity (can be negative if more has been ordered than is on hand) |

Clicking a row opens **"Orders based on demand"**: there you see which customer orders are behind the proposal. If it says "There is no unmet demand for this product. The order proposal is probably due to the minimum stock level for this product.", the proposal is based solely on the minimum stock.

### Triggering an order

1. Select one or more products.
2. Click **"Order"**. The **"New order"** page opens.
3. The **"Supplier"** preselected is the one that is the default supplier for most of the selected products. If you change the supplier, equipme takes over that supplier's default offer (or the newest offer) per product. If there is none, the price is set to €0.
4. Check the [order details, shipping and items](/pro/procurement/purchase-orders.md#creating-a-new-order).
5. Use **"Display demand fulfillment"** to define per item which customer orders the order should cover (see below).
6. Click **"Order"**.

### Assigning demand fulfillment

Under **"Display demand fulfillment"** you see per item: "Please select the customer orders that should be covered by this order."

| Column                                                 | Content                                                          |
| ------------------------------------------------------ | ---------------------------------------------------------------- |
| Checkmark                                              | The order is covered by this purchase order                      |
| "Order number", "Ordered on", "Customer", "Ordered by" | Customer order                                                   |
| "Purchase demand"                                      | Open quantity of the order                                       |
| **"Stock item"** row                                   | Quantity additionally ordered for your warehouse (minimum stock) |

If you set or remove checkmarks, equipme adjusts the order quantity automatically. Assigned customer items change to "Awaiting goods receipt" after ordering and are reserved directly at goods receipt.

## Dropshipping

Customer items from services for which **dropshipping** is enabled for provisioning appear here. Each row is a customer item ("Item"), expandable to show the products it contains and their default supplier.

| Column                                     | Content                                       |
| ------------------------------------------ | --------------------------------------------- |
| "Item"                                     | Number of the customer item                   |
| "Service name", "Customer"                 | What and for whom                             |
| "Delivery address", "Location", "Employee" | Where it should be delivered                  |
| "Order number", "Ordered on", "Ordered by" | Customer order                                |
| "Group", "Status"                          | hidden, can be shown via the column selection |

The table can be grouped by customer, delivery address, etc.

### Triggering a dropshipping order

1. Select one or more items. **A dropshipping order always applies to one customer only.** As soon as you select an item, items from other customers can no longer be selected.
2. Click **"Order"**.
3. If the selected items have different delivery addresses, choose one address for the entire order in **"Select shipping address"**.
4. On **"New order"**, the delivery address and, if available, possible recipients ("Recipient (name)", e.g. location contact or orderer) are prefilled. The items are grouped by customer item.
5. Click **"Order"**.

The products are assigned directly to the customer's service. You maintain the further delivery status in the [order](/pro/procurement/purchase-orders.md#maintaining-the-dropshipping-status).

{% hint style="warning" %}
For dropshipping, there is no minimum stock and no goods receipt in your warehouse. Without a dropshipping order, the customer item remains open.
{% endhint %}

## Permissions

Everyone with read permission for purchasing can view (e.g. "Purchasing Controller"). **"Order"** is only active with write permission (e.g. "Purchasing Manager", "Administrator").

## Frequently asked questions

**Why does equipme suggest more than customers have ordered?**

The proposal additionally tops up to the "Minimum stock". You see this share in the demand fulfillment in the "Stock item" row.

**A product is missing from the proposals even though a customer ordered it.**

Check whether the order is confirmed, whether the product is marked as a "Stock item" and whether enough goods are already stored or in transit.

**Can I bundle dropshipping items from several customers in one order?**

No. Create a separate dropshipping order for each customer.

**Why is an item's price set to €0?**

There is no offer for the product from the selected supplier. Enter the price in the order or store an offer in the [product master data](/pro/portfolio/products.md).


---

# 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/pro/procurement/order-proposals.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.
