# Minimum order quantity (MOQ): how Optiply handles it

MOQ is the smallest number of units you buy of one product from one supplier. **Lot size** is the multiple you buy in, such as a carton of 12 units. Optiply rounds a positive required quantity up to the supplier's lot size and raises it to the minimum order quantity (MOQ). It does so unless the supplier's **Stock availability** limit caps it.

## What MOQ and lot size mean in Optiply

MOQ answers this question: what is the minimum quantity? Lot size answers another: in what increments can I order? Lot size is the number of units in each ordering increment, which can match a pack size. MOQ sets the minimum total quantity.

Optiply keeps MOQ and lot size as separate settings for each product and supplier relationship. As a result, the same product can have different purchasing rules at different suppliers. A value of `1` allows individual units without an additional minimum or multiple. When you add a supplier relationship by hand, both fields start at `1`. An integration or import can create the relationship with other values.

## How Optiply applies MOQ and lot size to purchase advice

For a product being replenished with a positive required quantity, Optiply rounds that quantity up to a lot multiple and raises it to the MOQ. MOQ by itself does not trigger an order: when the product's target is already covered, MOQ is no reason to buy.

Other settings can also affect the final purchase advice, including:

- In ordinary replenishment, economic order quantity can raise the advised quantity or leave it unchanged, but it does not lower it. A manual **Minimum stock level** can raise the result, and a **Maximum stock level** can cap it or make it zero. Optiply still adjusts a positive result to lot size and MOQ.
- The supplier's **Stock availability** limit works the other way when it is enabled and the supplier's stock is known. Optiply then rounds down to complete lots, and the purchase advice can end below the MOQ or at zero.

## How MOQ, lot size and economic order quantity work together

MOQ, **Lot size** and economic order quantity are separate inputs in Optiply. Setting one does not remove the others, so your standard MOQ stays when you also set a lot size. For a positive required quantity, Optiply first applies MOQ and the lot size. When the product has an economic order quantity, Optiply then raises the result to at least that quantity, rounded to the lot size. The ordinary MOQ, lot size and economic order quantity calculation has no percentage rule for choosing a pack quantity over the MOQ.

Before you work out a quantity, check what a "pack quantity" means in your setup. A lot size, an economic order quantity and a unit factor for your ERP export are different things. Take MOQ 3, **Lot size** 3 and a required quantity of 12 units:

- Without an economic order quantity, 12 is a multiple of 3 and above the MOQ, so the result is **12 units**.
- With an economic order quantity of 60 units, Optiply raises the result to **60 units**.

Both results apply before stock caps, supplier stock limits or manual edits. Check which field holds the 60 before you change MOQ or **Lot size** in Optiply.

## Example: MOQ of 30 and lot size of 12 for inner tubes

This example uses made-up numbers. You sell bicycle inner tubes. Your supplier ships them in cartons of 12 and accepts orders from 30 tubes.

- **Lot size:** 12
- **Minimum order quantity:** 30
- Required quantity: 18 tubes

With ordinary replenishment, no economic order quantity adjustment, no manual minimum or maximum and no supplier **Stock availability** limit:

1. Optiply rounds 18 up to the next complete lot: `2 × 12 = 24` tubes.
2. 24 is below the MOQ of 30, so Optiply adds another lot: `24 + 12 = 36` tubes.
3. The resulting quantity is **36 tubes**, three lots. 36 meets both rules. 30 tubes would meet the MOQ but not the lot multiple.

Now the required quantity is 40 tubes instead of 18. Optiply rounds 40 up to `4 × 12 = 48` tubes. 48 is above the MOQ of 30, so the resulting quantity is **48 tubes**.

In both cases, check the resulting quantity in the purchase advice before you place the order.

## Where to find MOQ and lot size in Optiply

Open **Products**, select the product and open **Suppliers**. The linked supplier row shows **Minimum order quantity** and **Lot size**.

Check the supplier name before you edit. Changing the row of one supplier does not change the other suppliers of that product.

In Optiply's data, for example in the supplier-product import, MOQ is the field `minimumPurchaseQuantity`. Which field in your WMS fills MOQ depends on your integration. Ask Support for your integration's mapping.

## How to change MOQ and lot size in Optiply

Before you change MOQ or lot size:

- You need permission to edit the product.
- To add a supplier relationship, you need an available supplier to select.
- **Minimum order quantity** and **Lot size** are whole units of at least `1`.
- Check your integration's field ownership before you correct the same value by hand again and again. A connected source may manage it.

### Change MOQ or lot size on a linked supplier row

1. Open **Products**, select the product and open **Suppliers**.
2. Edit **Minimum order quantity** or **Lot size** on the linked supplier row.
3. Enter the new values and choose **Save**.
4. Reopen or reload the product.
5. Check that the supplier row shows the saved values before you review later purchase advice.

### Add a supplier relationship with its MOQ and lot size

1. Open the product's **Suppliers** tab and choose **Add new...**.
2. Select the supplier.
3. Enter **Lot size** and **Minimum order quantity**. Both start at `1`.
4. Complete the other required fields, including **Purchase price**.
5. Add the supplier relationship, then **Save** the product's suppliers.
6. Check that the linked supplier row shows the quantities you entered.

### Change MOQ or lot size for many products at once

For bulk changes, follow the [supplier-product import guide](/article/import-supplier-products). Its template is the template for changing MOQ in bulk. It has separate columns for MOQ (`minimumPurchaseQuantity`) and lot size (`lotSize`), and each row names one product and one supplier. Before you change MOQ for all suppliers at once, ask Support which import route to use and which supplier relationship counts.

### If you cannot edit or save MOQ or lot size in Optiply

- A missing or locked **Minimum order quantity** or **Lot size** field does not mean zero. Select a supplier first.
- If editing or saving is unavailable, check your permission to edit, pending changes and whether the supplier is ignored.
- Correct invalid values before you save.
- If saving fails, reload the product and check what was actually kept.

## MOQ and lot size when you edit a proposed order line

You can edit the **Quantity** of a proposed order line when the product has a lot size, if you have edit permission. The order line shows **MOQ** and **Lot size** separately. Which quantities the editor accepts depends on your account's settings, such as whether quantities are exported as lots. See [Purchase order editor](/article/purchase-order-editor). Optiply keeps the quantity it advised for a proposed order line as a separate value from the line's order quantity. After you edit, check the validation message and the saved line.

## How MOQ differs from minimum order value and order cadence

- **MOQ and minimum order value.** MOQ is a number of units for one product at one supplier. [Minimum order value](/article/minimum-order-value) is a monetary threshold for the whole supplier order.
- **MOQ and order cadence.** MOQ is set per product. How often you order is set per supplier, through the supplier's reorder period. MOQ does not set the order cadence: it is not an instruction to order every particular number of days. [Fixed order costs](/article/fixed-order-costs) are a separate purchasing input.
- **Lot size and an ERP purchase-unit factor.** Optiply's purchase advice rounds with the supplier-product **Lot size** and applies MOQ as a separate minimum. A purchase-unit factor that converts order quantities for your ERP export, such as `PurchaseUnitFactor`, depends on your connector. Ask Support how your integration maps it before you use it as the lot size.

## Questions customers ask about MOQ and lot size

### What does minimum order quantity mean?

MOQ is the smallest number of units you buy of one product from one supplier, while **Lot size** is the multiple you buy in, such as a carton of 12 units. For a positive required quantity, Optiply rounds up to a lot multiple and raises it to the MOQ, but MOQ by itself does not trigger an order when the product's target is already covered.

### Is there a template to change the MOQ in bulk?

The [supplier-product import guide](/article/import-supplier-products) has the template for changing MOQ in bulk, with the separate columns `minimumPurchaseQuantity` for MOQ and `lotSize` for lot size, and each row names one product and one supplier. Before you change MOQ for all suppliers at once, ask Support which import route to use and which supplier relationship counts.

### How do I change the minimum order quantity for a supplier?

Optiply keeps MOQ per product and supplier relationship, so open **Products**, select the product, open **Suppliers**, edit **Minimum order quantity** on that supplier's linked row and choose **Save**. Changing the row of one supplier does not change the other suppliers of that product.

### Say the MOQ and order multiple is 3, the advice is 12 and the pack quantity is 60. How many pieces are ordered?

With MOQ 3, **Lot size** 3 and a required quantity of 12 units, the result is 12 units without an economic order quantity and 60 units when the 60 is an economic order quantity, both before stock caps, supplier stock limits or manual edits. A lot size, an economic order quantity and a unit factor for your ERP export are different things, so check which field holds the 60 before you change MOQ or **Lot size**.

### Which field is MOQ in my WMS?

In Optiply's data, for example in the supplier-product import, MOQ is the field `minimumPurchaseQuantity`. Which field in your WMS fills MOQ depends on your integration, so ask Support for your integration's mapping.
