> 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-woocommerce.md).
# Sell on WooCommerce
Configuring these settings helps ensure products are accurately priced, displayed, and managed in your WooCommerce store.
The **WooCommerce** section contains the settings used to configure how a product is sold through your connected **WooCommerce** store. Completing these details ensures the product’s pricing, availability, and other WooCommerce-specific information are correctly configured.
This document explains how to complete the **Sell on WooCommerce** section of the **Add Product** form when adding a new product to Supply’d.
***
### Completing the WooCommerce Section
{% 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 WooCommerce
Following the guidelines for [Adding a Product](/supplyd-erp/products/adding-products/adding-a-product.md), complete the sections up to the **Sell on WooCommerce** section.
***
{% endstep %}
{% step %}
#### Complete the Sell on Sell On WooCommerce Section
Toggle this on if you want to sell the product through the specified WooCommerce store.
{% hint style="success" %}
In this example, **Sell on WooCommerce – WooCommerce Store?**, **WooCommerce Store** is the name of the WooCommerce store where the product will be sold. This will be the name of your connected WooCommerce store.
For example, if your WooCommerce store is named **Fresh Foods**, the section would appear as **Sell on WooCommerce – Fresh Foods?**
If you have multiple **WooCommerce stores** connected to Supply’d, a **Sell on WooCommerce** section will be displayed for each store, with each section showing its respective store name.
👉 The [WooCommerce](/supplyd-erp/settings/integrations/sales-channel-integrations/woocommerce.md) document explains how to connect and manage WooCommerce stores in **Supply’d**.
{% endhint %}
**Woo Store Price (inc Tax)**
If you want to use a different price for the product in WooCommerce you can override it here. This price will sync to WooCommerce only.
Leave blank if the WooCommerce price is the same as the product price entered in the **Sell Product** section.
**Woo Store Price (inc tax)**
If the product is on sale, enter the WooCommerce sale price here. This price will sync to WooCommerce only.
Leave blank if the product is not on sale or if the WooCommerce sale price is the same as the sale price entered in the **Sell Product** section.
**Woo Store Tax**
If you want to use a different tax for the product on WooCommerce, you can override the product tax here. This tax will sync to WooCommerce only.
Select **Same As Product** to use the product’s default tax setting, or select **GST** (or the applicable tax).
**Pack In Carton**
Select whether the product should be packed in a shipping carton when sold through the WooCommerce 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 WooCommerce 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 WooCommerce.
{% 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 categories you want to feature the product under in your WooCommerce store.
**Tags**
Select from a set of predefined tags that describe the product, such as **Vegan, Vegetarian, Nut-Free**, or **Gluten-Free**. Customers can use these tags to find products that match their preferences. Click the field to view the available tags.
**Featured**
Select whether the product should be featured on Ordermentum.
**Short Description**
Enter a brief description of the product to be displayed in your **WooCommerce** store.
**Stock Buffer**
Set a buffer for the product’s inventory sent to **WooCommerce**. A buffer reduces the available inventory sent to WooCommerce by the specified amount to help prevent overselling.
For example, if you have **50 units** in stock and set a stock buffer of **5**, Supply’d will send **45 units** as the available inventory in WooCommerce.
Leave blank to use the default set in your integration settings.
***
{% endstep %}
{% step %}
#### Repeat
If you sell the product in more than one **WooCommerce 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-woocommerce.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.
