> For the complete documentation index, see [llms.txt](https://help.supplyd.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.supplyd.co/supplyd-erp/products/adding-products/fulfilment-rules-details.md).
# Fulfilment Rules Details
Completing the Fulfilment Rules helps ensure orders are fulfilled efficiently from the appropriate locations, reducing errors & improving order accuracy.
The **Fulfilment Rules** section allows you to define how the product should be fulfilled when an order is placed. Completing these settings helps ensure products are allocated and supplied from the appropriate locations according to your fulfilment requirements.
This document explains how to complete the **Fulfilment Rules** section of the **Add Product** form when adding a new product or editing an existing product in Supply’d.
***
### Completing the Fulfilment Rules Details
{% stepper %}
{% step %}
#### Open the Add Product Form
1. Select **Products** from the main menu to open the **Products** page.
2. Click the **Add +** button in the top right to open the **Add Product** form.
{% hint style="success" %}
👉 The [Adding a Product](/supplyd-erp/products/adding-products/adding-a-product.md) document provides detailed instructions on how to open this form.
{% endhint %}
***
{% endstep %}
{% step %}
#### Complete the Sections up to Fulfilment Rules Section
Following the guidelines for [Adding a Product](/supplyd-erp/products/adding-products/adding-a-product.md), complete the sections up to **Buy Product**.
***
{% endstep %}
{% step %}
#### Complete the Fulfilment Rules Section
{% hint style="warning" %}
For **Fulfilment Rules** to work correctly with carton-based picking, the following setup is required:
* Create your **Shipping Carton** and/or **Carton Container** inventory items first, as these are selected in the **Preferred Carton** field.
* In the [Pick & Pack Settings](/supplyd-erp/settings/pick-and-pack-settings.md#pick-and-pack) section of your [Pick & Pack Settings](/supplyd-erp/settings/pick-and-pack-settings.md), set **Count Mode** to **By Carton**. This mode is primarily intended for [Pick & Pack (Scanner)](/supplyd-erp/scanner/pick-and-pack-scanner.md#wave-pick), where products are picked and packed by carton rather than by individual unit.
{% endhint %}
**Pack In Carton**
Select whether the product should be packed in a shipping carton when shipped.
* **Yes:** The product will be packed into an appropriate shipping carton during **Pick & Pack** and may be grouped with other items being shipped together.
* **No:** The product will be shipped as is and will not be placed in a shipping carton. Use this for products already packaged for shipping or too large to fit in a carton.
{% hint style="info" %}
#### **Pack in Carton (Fulfilment Rules) vs Pack in Carton (Sales Channel)**
Although these settings have similar names, they serve different purposes.\
**Pack in Carton (Fulfilment Rules)** determines whether a product is packed into its standard fulfilment carton or tray before shipping. This is the carton used to group products during picking and packing.
For example:
* A 4-pack of canned tomatoes may be managed as individual cans in inventory but sold as a single 4-pack. The 4-pack is the product's fulfilment carton.
* In a bakery, bread may be packed into trays holding 20 loaves. The tray is the fulfilment carton, so **Pack in Carton** would be set to **Yes**.\
**Pack in Carton (Sales Channel)** determines whether the completed product also requires an additional shipping carton for delivery to the customer.
For example:
* The 4-pack of canned tomatoes may be placed into a cardboard shipping box for delivery, so **Pack in Carton** would be set to **Yes**.
* Bakery bread delivered in trays does not require an additional shipping carton, so **Pack in Carton** would be set to **No**.\
**In short:**
* **Fulfilment Rules** = *What is the product packed into as part of fulfilment?*
* **Sales Channel** = *Does the packed product need an additional shipping carton for delivery?*
{% endhint %}
**Preferred Carton**
Select the **Preferred Carton** for packing the product when shipping cartons are calculated for an order. If no carton is selected, Supply’d will automatically select the best-fit carton based on the product and order contents.
{% hint style="info" %}
This field will only show if **Yes** is selected in the **Pack In Carton** field.
{% endhint %}
**Qty Per Carton**
Enter the number of units of the product that fit into the **Preferred Carton**. This is used to calculate the number of cartons required for an order and during carton-based **Pick & Pack** workflows.
{% hint style="info" %}
This field will only show when **Pack In Carton** is set to **Yes** and a **Preferred Carton** has been selected.
{% endhint %}
**Order Cut-off**
An **Order Cut-off** defines how far in advance an order must be placed for a particular delivery day to be available. Once the cut-off time has passed, that delivery day will no longer be available to customers at checkout. Select **Not Set** to disable order cut-offs and allow delivery days to remain available without a cut-off.
**Delivery Delay**
Enter the number of processing days required before delivery. This ensures orders are only scheduled for delivery days that allow sufficient time for preparation and fulfilment.
***
{% endstep %}
{% step %}
#### Complete Remaining Fields
Complete the remainder of the form as outlined in the [Adding a Product](/supplyd-erp/products/adding-products/adding-a-product.md) document.
{% endstep %}
{% endstepper %}
---
# 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://help.supplyd.co/supplyd-erp/products/adding-products/fulfilment-rules-details.md?ask=&goal=
```
`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.
