> For the complete documentation index, see [llms.txt](https://support.rosysalonsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.rosysalonsoftware.com/rosypay/checkout-using-the-cloud-terminal/adding-editing-a-product.md).

# Adding/Editing a Product

## Adding a New Product

**Proceed to:** **Manage** > **Inventory** > **Products** > **New Product**

{% hint style="info" %}
Please enter the information in the fields. Fields in Red are required.
{% endhint %}

{% stepper %}
{% step %}

## Name

This will be the description of the product.

*Example: Deep Cleansing Shampoo*
{% endstep %}

{% step %}

## Brand

The company that makes the product. Select from the drop-down box.

{% hint style="info" %}
Brands should be entered prior to adding new products. Find out [how to add Brands](/inventory/adding-editing-brands-and-distributors.md) here.
{% endhint %}
{% endstep %}

{% step %}

## Product Group

These are categories that organize your Products *within* each Brand, and normally determine what *type* of Product it is.

*Example: Shampoo, Conditioner, Treatment*

{% hint style="info" %}
Product Groups should be entered prior to adding new products. Find out [how to add Product Groups](/inventory/adding-editing-product-groups.md) here.
{% endhint %}
{% endstep %}

{% step %}

## SKU

Can be the same as a UPC, a Distributor code, or anything you want it to be!
{% endstep %}

{% step %}

## UPC (barcode)

This is the number on the sticker in which you scan on the Product. This is the *entire* number including the number of the far left and the far right.
{% endstep %}

{% step %}

## Size

Size should be entered to differentiate a Product from other sizes of the same Product. Size unit should be entered in this field as well.

*Example: 2.5 Fl. Oz., 1 each, Large*
{% endstep %}

{% step %}

## Taxable

Will you be charging tax for this particular Product?
{% endstep %}

{% step %}

## Retail

Will this product be sold for Retail or used for Professional purposes? If the Product is sold for Retail, this drop-down should be set to "YES".
{% endstep %}

{% step %}

## Active

This will determine the status of the product. If you are no longer selling the Product, you'll change its Active drop-down to "NO".
{% endstep %}

{% step %}

## Salon Cost

This is what you as a Salon pay for the Product.
{% endstep %}

{% step %}

## Retail Cost

This is what you charge the Client for the Product.
{% endstep %}

{% step %}

## On Hand Quantity

The number of Products you currently have in the Salon.
{% endstep %}

{% step %}

## Target Quantity

The quantity you prefer to keep in the Salon to cover potential sales.
{% endstep %}

{% step %}

## Use Up Time (Days)

Average length of time to use up a Product. This can be used for suggestive selling.

*Example: If a client purchases a shampoo that has a use up time of 28 days. When they come back after the 28 day period, you will receive a notification at the top of your Checkout Ticket reminding you to suggest another!*
{% endstep %}

{% step %}

## Save

Click **Save** once you are finished.
{% endstep %}
{% endstepper %}

## Editing a Product

**Proceed to:** **Manage** > **Inventory** > **Products**

{% stepper %}
{% step %}

## Select the Product

Click on the name of the Product you would like to edit.
{% endstep %}

{% step %}

## Adjust fields

Adjust any necessary fields.
{% endstep %}

{% step %}

## Save

Click **Save** once finished.
{% 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://support.rosysalonsoftware.com/rosypay/checkout-using-the-cloud-terminal/adding-editing-a-product.md?ask=<question>&goal=<endgoal>
```

`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.