# Pending Products

This tutorial provides step-by-step instructions for managing Pending Products in Omnitron.

## <mark style="color:red;">Step 1: Access to Omnitron​</mark> <a href="#step-1-access-to-omnitron" id="step-1-access-to-omnitron"></a>

* Get access to the Omnitron panel.
* Enter your Username and Password, and then click the **Sign In** button.\
  ![](https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FSm1Cc5pafA0lLxEnP9Xm%2Fimage1.png?alt=media\&token=4608fc68-3773-4d86-8542-8beae387d43d)

## <mark style="color:red;">Step 2: Navigate to Pending Products Page​</mark> <a href="#step-2-navigate-to-pending-products-page" id="step-2-navigate-to-pending-products-page"></a>

* Follow the **Integration** sidebar and click the **Pending Products** page.<br>

  <figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FA3nzhXF1kehaN82CEkkQ%2Fimage2.png?alt=media&#x26;token=41eeb7bb-9519-4d16-9095-104e4860922d" alt=""><figcaption></figcaption></figure>
* This page is used to view and manage Pre Products that have been transferred from the client’s ERP system to Omnitron through services but are yet to be fully productized. Any products added from the ERP system are automatically displayed on this page. This screen includes a filtering area and a list of pending products.

{% hint style="info" %}
In order to automatically fetch products onto the pending product list, products need to be active and assigned with related information (such as SKU, Base Code, and Product Name) on the client’s ERP system.
{% endhint %}

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FxV5j6B5X8v3uL4PC1Wa5%2Fimage3.png?alt=media&#x26;token=95e73411-a589-4c12-8085-9343b0399f15" alt=""><figcaption></figcaption></figure>

* By default, the system allows users to filter products based on various criteria such as SKU, Base Code, Product Name, Attribute Set Name, Image, and whether the product has an Attribute Set. To customize these filters, users can click the filter icon located in the top-right corner, where additional filters can be added or removed according to their preferences.
* Upon selecting a filter, it is promptly incorporated into both the filtering area and the product list tabs. Moreover, users have the option to employ Exclude filters when listing products. Alternatively, filtering can be achieved by uploading a file in either CSV or XLS format, a feature also accessible in the top-right corner.
* For file uploads, adherence to a specific template is required. This template can be obtained at the bottom of the page by clicking the **Download Pending Products Template** button.
* To export a list of selected products, users can choose the "Export to Excel" option from the Action Select menu, resulting in the generation of an Excel file. Likewise, the "Export to CSV" option allows for downloading the list in CSV format. To remove selected products, users can utilize the "Delete Selected" option found within the same drop-down menu.

## <mark style="color:red;">Step 3: Adding Bulk New Product​</mark> <a href="#step-3-adding-bulk-new-product" id="step-3-adding-bulk-new-product"></a>

Click the **+ New Product** button on the Pending Products page. This button is used to add products before integration between the client's ERP platform and Omnitron. Click the button to upload a CSV file with the related information of the products to be added. The CSV file must include **Product Name** and **SKU** information.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FpP52GgE7JAGCiecqriKo%2Fimage4.png?alt=media&#x26;token=52fd433b-2b30-483b-8ea0-167a77585daa" alt=""><figcaption></figcaption></figure>

## <mark style="color:red;">Step 4: Bulk Product Update​</mark> <a href="#step-4-bulk-product-update" id="step-4-bulk-product-update"></a>

Located in the upper-right corner, the **Bulk Product Update** button can be used for updating pending products in bulk. In order to use this feature, begin by filtering and selecting the desired products from the list. Navigate to the **Select Action** drop-down menu, select **Export Selected to CSV**, and click the **Apply** button. Once you've entered the updated information into the file, proceed to click the **Bulk Product Update** button and upload the new file.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FKICcYOR2a9dJiIvtLrsT%2Fimage5.png?alt=media&#x26;token=e4ee67e7-88d9-4efd-8aa7-e0b933d9b19a" alt=""><figcaption></figcaption></figure>

## <mark style="color:red;">Step 5: Productization of Pending Products​</mark> <a href="#step-5-productization-of-pending-products" id="step-5-productization-of-pending-products"></a>

### <mark style="color:red;">Selecting an Attribute Set​</mark> <a href="#selecting-an-attribute-set" id="selecting-an-attribute-set"></a>

To initiate the process, start by defining attribute sets containing mandatory information like size and color for the pre-products received from the client's ERP software. These sets can be defined within the **Product Attributes** menu under the **Products and Catalogs** module. For example, in the clothing category, attributes such as color and size can be defined. Refer to the related document for detailed information on [Product Attributes & Product Attribute Sets](https://docs.akinon.com/tutorials/omnitron/products-and-catalogs/how-to-create-product-attributes-and-attribute-sets-in-omnitron).

Once attribute sets are defined, filter the pending product list to focus on products that require an attribute set selection. Subsequently, select the desired products from the list. Navigate to the **Select Action** drop-down menu, select the **Select Attribute Set** action, and then click the **Apply** button.

A new side menu will appear, displaying attribute sets pre-defined in the **Products and Catalogs** module. Here, select the appropriate attribute set for the product's attributes (e.g., color, size) and assign it to the product. For example, select "Size-Color," which includes both "color" and "size" attributes for an undershirt.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FbLF6h0YmWWjMkqONEUUD%2Fimage6.png?alt=media&#x26;token=2e6216c0-46d1-4089-b0c9-c65980080efc" alt=""><figcaption></figcaption></figure>

### <mark style="color:red;">Approving Products​</mark> <a href="#approving-products" id="approving-products"></a>

To approve products, begin by filtering the pending products list to include those with selected attribute sets. Navigate to the **Select Action** drop-down menu, select the **Approve Selected** option, and click the **Apply** button. Through this process, pre-products that have been approved are productized and moved to the **Product Pool** within the **Products and Catalogs** module. It's important to note that products without selected attribute sets are not approved through this step.

In the event of an error during the approval process, the system generates an Excel file containing a list of products with errors. This file includes detailed information such as the error reason, as well as the product's base code and SKU number.

<figure><img src="https://3333414532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIbwGN7KwvYi0iLbjtnXz%2Fuploads%2FQAaXBVaDJofeYaJm1YYV%2Fimage7.png?alt=media&#x26;token=c78387d1-f538-499f-84da-570a896ee6a3" alt=""><figcaption></figcaption></figure>

### <mark style="color:red;">Approving All Products​</mark> <a href="#approving-all-products" id="approving-all-products"></a>

To approve all products on the pending list, first, filter products with selected attribute sets. Then, select the **Approve All Products** option from the **Select Action** drop-down menu and click the **Apply** button. This process results in all pre-products being productized and moved to the **Product Pool** within the **Products and Catalogs** module. If any errors occur during the approval, they are processed within the **Errors and Warnings** panel located to the right of the Omnitron panel. Users can view errors here and export them as a CSV file, which includes the error reason, base code, and SKU number of the affected products.

For specific errors:

* For the error **"Product is not valid, missing attributes"**: Users should enter the errored attribute in the Integration>Mapping field.
* For the error **"No defined attribute value"**: Users should enter the attribute in the Products and Catalogs>Product Attributes>Attributes field.
* For the error **"... attribute already exists"**: Users should check the base code via the product pool. If another product with the same attributes exists, it cannot be imported with a different SKU.

{% hint style="info" %}
Three possible reasons for errors during the approval process: no defined attribute value, no mapping, and products previously added to the product pool. For example, if an error occurs while approving red shoes with color and size attributes, possible reasons include overlooking the definition of "Red" as a value for the "Color" attribute on the “Product Attributes” page, missing mapping for the color "Red," on the “Mapping” page or having a product with the same attributes but a different SKU in the product pool. In such cases, users need to investigate the SKU value in the product pool to resolve the error.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.akinon.com/tutorials/omnitron/integration/pending-products.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
