> 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/sell-on-ordermentum-details.md).
# Sell on Ordermentum Details
Configuring these settings helps ensure products are accurately displayed, priced, and managed in Ordermentum, providing customers with up-to-date product and availability information.
The **Sell on Ordermentum** section contains the settings used to configure how a product is displayed and sold through your connected **Ordermentum** store. This includes Ordermentum-specific details such as pricing, featured status, badge labels, and stock availability.
This document explains how to complete the **Sell on Ordermentum** section of the **Add Product** form when adding a new product to Supply’d.
***
### Completing the Sell on Ordermentum 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 Sell on Ordermentum
Following the guidelines for [Adding a Product](/supplyd-erp/products/adding-products/adding-a-product.md), complete the sections up to **Sell on Ordermentum**.
***
{% endstep %}
{% step %}
#### Complete the Sell on Ordermentum Section
Toggle this on if you want to sell the product through the specified **Ordermentum store**.
{% hint style="success" %}
In this example, **Sell on Ordermentum – Test?**, **Test** is the name of the Ordermentum store where the product will be sold. This will be the name of your connected Ordermentum store.
For example, if your Ordermentum store is named **Fresh Foods**, the section would appear as **Sell on Ordermentum – Fresh Foods?**
If you have multiple **Ordermentum** stores connected to Supply’d, a **Sell on Ordermentum** section will be displayed for each store, with each section showing its respective store name.
👉 The [Ordermentum](/supplyd-erp/settings/integrations/sales-channel-integrations/ordermentum.md) document explains how to connect and manage Ordermentum stores in **Supply’d**.
{% endhint %}
**Test Price (inc Tax)**
If you want to use a different price for the product in your Ordermentum store, enter it here. This price will sync to the Ordermentum store only.
Leave blank if the Ordermentum price is the same as the product price entered in the **Sell Product** section.
**Test Sale Price (inc tax)**
If the product is on sale, enter the Ordermentum store **sale price** here. This price will sync to the Ordementum store only.
Leave blank if the product is not on sale or if the Ordermentum sale price is the same as the price entered in the **Sell Product** section.
**Test Tax**
Select whether to use the product’s existing tax settings or apply tax, such as GST, when selling the product on Ordermentum. This tax setting will sync with the Ordermentum store only.
**Pack In Carton**
Select whether the product should be packed in a shipping carton when sold through the Ordermentum store.
* **Default** - The product will be packed according to the setting selected under **Sell Product** for this product.
* **Yes** - The product will be packed in an aggregated shipping carton during packing.
* **No** - The product will be shipped as is, without any additional cartons.
**Sold As**
Select whether the product is sold on Ordermentum by the **Unit** or as a **Carton**.
When **Carton** is selected, an additional **Carton Qty** field will appear.
**Carton QTY\* \[required field]**
Enter the number of units contained in each carton when selling the product on Ordermentum.
{% hint style="info" %}
This field is only displayed when **Carton** is selected in **Sold As** and is required when **Carton** is selected.
{% endhint %}
**Categories**
Select the **Ordementum categories** you want to feature the product under in your Ordermentum store.
**Featured**
Select whether the product should be featured on Ordermentum.
**Badge Label**
Enter the label you want to display as a badge on the product in Ordermentum.
**Track Inventory**
Select whether or not inventory should be tracked for this product in the Ordermentum store.
{% hint style="info" %}
In general, this field will default to **Yes** when **Sell on Ordermentum** is enabled.
{% endhint %}
**Out of Stock**
Select whether or not the product should be shown as out of stock in Ordermentum.
* **No** - If inventory is tracked, the current stock level in **Supply’d** determines the product’s stock status. If inventory is not tracked, the product will be shown as in stock.
* **Yes** - The product will be shown as out of stock in Ordermentum, regardless of its current stock level in **Supply’d**.
***
{% endstep %}
{% step %}
#### Repeat
If you sell the product in more than one **Ordermentum Store**, repeat the last step for each store.
***
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.supplyd.co/supplyd-erp/products/adding-products/sell-on-ordermentum-details.md?ask=&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.
