> 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-wedderburn-details.md).
# Sell on Wedderburn Details
Configuring these settings helps ensure product information is accurately shared with Wedderburn, making it easier to manage products and maintain consistent information across systems.
The **Sell on Wedderburn** section contains settings used to configure how a product is managed and displayed through your connected **Wedderburn** integration. Completing these details helps ensure the relevant product information is correctly configured and shared with Wedderburn.
This document explains how to complete the **Sell on Wedderburn** section of the **Add Product** form when adding a new product to Supply’d.
***
### Completing the Sell on Wedderburn 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 Wedderburn
Following the guidelines for [Adding a Product](/supplyd-erp/products/adding-products/adding-a-product.md), complete the sections up to **Sell on Wedderburn**.
***
{% endstep %}
{% step %}
#### Complete the Sell on Wedderburn Section
Toggle on to sync this product with **Wedderburn**.
{% hint style="success" %}
In this example, **Sell on Wedderburn – Wedderburn?**, **Wedderburn** is the name of the connected Wedderburn integration. This identifies the Wedderburn connection that the product will be synced with. The connection name will be the name you chose when setting up the **Wedderburn** integration.
For example, if you named your Wedderburn connection **Main Warehouse**, the section would appear as **Sell on Wedderburn – Main Warehouse?**
If you have multiple **Wedderburn** integrations connected to Supply’d, a separate **Sell on Wedderburn** section will be displayed for each integration, with each section showing its respective connection name.
👉 The [Wedderburn](/supplyd-erp/settings/integrations/sales-channel-integrations/wedderburn.md) document explains how to connect and manage Wedderburn integrations in **Supply’d**.
{% endhint %}
**Wedderburn Price (inc Tax)**
If you want to use a different price for the product in **Wedderburn**, enter it here. This price will sync to **Wedderburn only**.
Leave blank if the Wedderburn price is the same as the product price entered in the **Sell Product** section.
**Wedderburn Sale Price (inc tax)**
If the product is on sale, enter the **Wedderburn sale price** here. This price will sync to **Wedderburn** only.
Leave blank if the product is not on sale or if the Wedderburn sale price is the same as the price entered in the **Sell Product** section.
**Wedderburn Tax**
Select whether to use the product’s existing tax settings or apply a tax, such as **GST**, for **Wedderburn**. This tax setting will sync to **Wedderburn** only.
**Pack In Carton**
Select whether the product should be packed in a shipping carton when sold through the **Shopify** 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 Shopify 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 **Shopify**.
{% hint style="info" %}
This field is only displayed when **Carton** is selected in **Sold As** and is required when **Carton** is selected.
{% endhint %}
**Is Weighed**
Select whether or not the product is weighed. This indicates that the product’s quantity is measured using a scale.
**Override PLU**
Enter a **PLU** (Price Look-Up) code to sed to Wedderburn.
Leave blank to use the **SKU/Barcode** defined in your Wedderburn settings.
**Product Name**
Enter the product name that will be displayed in Wedderburn.
**Short Description**
Enter a brief description of the product to be displayed in Wedderburn.
**Locations**
Select the locations where the product is available or should be managed in Wedderburn. Leave blank to use the default locations.
**Sub Group**
Select the sub group to which the product belongs in Wedderburn.
**Format**
Select the format used for the product in Wedderburn, such as how the product is presented or sold.
**Colour**
Select the colour associated with the product in Wedderburn.
**Default Tare**
Enter the default tare weight for the product. This is the weight of the packaging or container that should be deducted when weighing the product. Leave blank for none.
***
{% endstep %}
{% step %}
#### Repeat
If you have more than one Wedderburn connections, 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-wedderburn-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.
