--- title: "Product Import" canonical: "https://kb.myframeworks.com.au/space/FRAM/28409372/Product%20Import" format: markdown --- The **Product Import** function allows you to bulk create and update product records in Frameworks. The screen supports both importing product data from a CSV file and exporting existing product data to a CSV template. This function streamlines the process of managing product attributes across large numbers of products. Common uses for this function include: - Moving a range of products from one product group to another. - Updating sell prices for a range of products. - Updating product descriptions in bulk. - Assigning a price rounding method to multiple products. - Updating product classifications, UOM settings and other product attributes. Adding a range of new products from a supplier is better handled by the [Electronic Product Catalogue (EPC)](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28391542) module. > ✅ Refer to [Product Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28378114) for information on maintaining individual product records. > This process involves downloading a template CSV file, editing it with your required data, and uploading it back to Frameworks for processing. It is recommended to run the import with the **Report Only** option enabled first to validate your data before committing changes. --- ## Accessing Product Import To access the **Product Import** function: 1. Click the **Frameworks Menu** and navigate to **Inventory > Maintenance > Product Import** from the navigation tree. 2. The **Import Criteria** tab opens by default. --- ## Downloading a Template Downloading a template is recommended as it provides the correct CSV file format with the appropriate column headings for your import. ![image-20260401-234322.png](media://3843402b-70e4-4e62-8745-20c321444373) ### Steps 1. From the **Process** drop-down menu, select **Export**. 2. From the **Update Field** list, select the fields you want to include in your template (hold the CTRL key to select multiple fields). 3. Use the **From Product** and **To** fields to filter the product range if required. Use the **From Product Group** and **To** fields to filter by product group if required. Leave the ranges blank to include all products. 4. Click **Submit** to send the export task to the Task Scheduler. You can choose to download a template without any data by clicking the **Download Template Only (No data)** button. The template file downloads instantly and can be opened, edited and saved as a CSV file to your PC. --- ## Uploading the Import Once you have edited your CSV file with the product data you want to import, you can upload it to Frameworks. ![image-20260401-234400.png](media://5c2f9b26-1342-48e7-83e3-e4d35fe94faa) ### Steps 1. From the **Process** drop-down menu, select **Import**. 2. From the **Update Field** list, select which fields you want to update from your CSV file (hold the CTRL key to select multiple fields). The fields selected here must match the columns in your CSV file. 3. Click the **Upload CSV** button to open the **File Upload** window. 1. Click the **Browse** button to browse your PC. 2. Select your edited CSV file. 3. Click **Open** to confirm the file selection. 4. Click **Upload** for the file to be ready for import. 5. The filename displays in the **Import File** area once uploaded. 4. Choose to enable or disable the **Report Only** checkbox. 5. Click **Submit** to send the import task to the Task Scheduler for processing. > ℹ️ When the **Report Only** checkbox is enabled, Frameworks validates your data and produces a report of any errors that need to be corrected in your CSV file before the actual import can proceed. --- ## Import Rules The import follows the same validation rules as the **Product Maintenance** screen: - The **Product Id** column is required in every import file. Frameworks uses the Product Id to match import rows to existing product records. - Fields included in the import file but not selected in the **Update Field** list are ignored during processing. - Invalid field values (for example, a text value in a numeric field or an unrecognised code) are rejected and reported in the output. - The import updates existing product records. To create new products, ensure all required fields are included in the CSV file. --- ### Market Cost UOM The product import supports a **Market Cost UOM** column. This column allows you to specify the UOM in which the market cost is expressed in your CSV file. The system converts the market cost to the product's stocking UOM during import. The following rules apply when importing **Market Cost** and **Market Cost UOM** values: - If the **Market Cost UOM** column is omitted from the import file, the system treats the entered market cost as already expressed in the product's stocking UOM. No conversion is applied. - If the **Market Cost UOM** column is included and the UOM matches the product's stocking UOM, no conversion is applied and the cost is imported as entered. - If the **Market Cost UOM** column is included and the UOM differs from the product's stocking UOM, the system converts the market cost to the stocking UOM using the configured conversion factor before saving. - If the **Market Cost UOM** value is not a valid UOM for the product, the import logs an error for that row and skips the market cost update for that product. Other fields in the same row that do not have errors are still processed. - If the **Market Cost UOM** is valid but no conversion factor is configured between the source UOM and the stocking UOM, the import logs an error for that row and skips the market cost update for that product. The **Market Cost UOM** column is only relevant when the `InvUseProdCostingMth` system flag is enabled. When the flag is disabled, market cost UOM handling does not apply. It is recommended to run the import with **Report Only** enabled first to validate market cost UOM values before committing changes. See the **Schedule and Output Tabs** section for details. --- ## Schedule and Output Tabs The import and export tasks are recommended to be run as a once-off by clicking the **Submit** button on the **Import Criteria** tab. For large imports, the task can be scheduled to run after hours via the **Schedule** tab. After a task is submitted, the screen navigates to the **Output** tab where you can view any generated reports, including validation results from **Report Only** runs and import processing summaries. If the **Report Only** option was enabled and there were no errors in the generated report, repeat the upload process with **Report Only** disabled to commit the changes. If there were errors, resolve them in your CSV file before importing. > ✅ Refer to [Scheduled Task - Scheduling and Output](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28402256) for information on scheduling tasks and viewing output. > ✅ ## Related Information > ✅ > ✅ - Refer to [Product Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28378114) for information about individual product fields. > ✅ - Refer to [Electronic Product Catalogue (EPC)](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28391542) for information about adding products from suppliers. > ✅ - Refer to [Understanding Market Cost and UOM Conversion](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/714801314) for information about how market cost UOM conversion works. > ✅ - Refer to [Use the Market Cost Calculator](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/716472333) for step-by-step instructions on converting a supplier-quoted cost using the calculator. --- ## Additional Information ### Product Type Values When defining the **Product Type (int)** field, use one of the following integer values: - 0 = Normal - 1 = Non-Stock - 2 = Promotional - 3 = Run Out - 4 = Random Sheet - 5 = Manufactured - 6 = Miscellaneous - 7 = Special - 8 = Template ### Dimension Field Validation The product import validates the **Width**, **Depth** and **Length** fields. **Width** and **Depth** are decimal fields with a valid range of 0 to 99.999. **Length** is a decimal field with a valid range of 0 to 999.999. Values outside these ranges are rejected during import. ### Show Inches? Values The **Show Inches?** field can be included in the import CSV file to set the inches display preference for imperial UOM products in bulk. The import column label is **Show Inches?**. Valid values for the **Show Inches?** column are: - **Y** — Enable the **Show Inches?** checkbox. The inches entry field is displayed in the tally maintenance popup when the product is added to a transaction. - **N** — Disable the **Show Inches?** checkbox. The inches entry field is hidden in the tally maintenance popup. > ⚠️ **Important:** If the **Show Inches?** column is included in your import file for a product that does not have an imperial unit of measure (for example, EA, LM or BX), the **Show Inches?** checkbox is not visible in **Product Maintenance** and the imported value has no effect on the tally popup. No import error is generated in this case. > ✅ Refer to [Product Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28378114) for information about the **Show Inches?** checkbox and when to enable it. ### Market Cost UOM Values The **Market Cost UOM** column accepts any UOM code that is configured as a valid UOM for the product (as a stocking, purchasing, or alternate UOM) and that has a conversion factor defined. Common lumber UOM codes that may appear in market cost imports include: | Code | Description | | --- | --- | | BF | Board Foot | | LF | Lineal Foot | | SF | Square Foot | | LM | Linear Metre | | M2 | Square Metre | | M3 | Cubic Metre | | EA | Each | | BX | Box | The specific codes available for any given product depend on the UOMs configured in **Product Maintenance** > **Units of Measure** for that product. A UOM that is not configured against a product is not valid for that product's import row, even if it exists in the system. > ✅ Refer to [Understanding Market Cost and UOM Conversion](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/714801314) for an explanation of how conversion works. > ✅ > ✅ Refer to [Product Maintenance](https://sterlandsupport.atlassian.net/wiki/spaces/FRAM/pages/28378114) for information on configuring UOMs against a product.