Editable FIields

Breadcrumb path: Products / Manage Products / Select a Laravo Brand Data or POS product

You can access this feature by clicking on Products from your main menu, and Manage Products from the dropdown menu. Select any Laravo (Brand Data) or Laravo (POS) product.

Editable FIields Fundamental

This section of the guide will walk you through the process of adding custom data entries for selected data fields for products that have a Data source of Laravo (Brand Data) or Laravo (POS).

Data fields can either use the data provided by Laravo or use the custom data entered by the user. Data fields that have the option 

Here is an example of a Laravo (Brand Data) product using POS Data Fields. Click on "POS"

Here is another example of the same Laravo (Brand Data) product using Custom Data Fields entered by the user.

List of All Data Fields that can use Custom Data Entry

• Product Information Section
• The Product Information section has two Editable Fields. The user can select either POS/Laravo or Custom. Click the Save button to save the desired settings.  
  1. Orderable:
  2. Does the Image Match the Selected Material?

 The image below shows the Editable fields for the Product Information Section.

• 

• Product Title Section
• The Product Title Section has one Editable Field. The user can select either POS/Laravo or Custom. Click the Save button to save the desired settings.  
  1. Product Title

The image below shows the Editable fields for the Product Title Section.

• 

• Product Description Section
• The Product Description Section has one Editable Field. The user can select either POS/Laravo or Custom. Click the Save button to save the desired settings.  
  1. Product Description 

The image below shows the Editable fields for the Product Description Section.

• Product Details Section
• The Product Details Section has thirteen Editable Fields. The user can select either POS/Laravo or Custom. Click the Save button to save the desired settings.  
  1. Subtitle
  2. Weight
  3. Collections
  4. Related Items GUID
  5. Date Arrival
  6. Age Group
  7. GTIN
  8. Retail Price
  9. Sale Price
  10. Cost
  11. Stock Number
  12. Stock Quantity
  13. Condition

The image below shows the Editable fields for the Product Details Section.

• Industry Standard Specifications Section

• The Industry Standard Specifications Section can have a multitude of Editable Fields depending on the production specifications. The user can select either POS/Laravo or Custom. Click the Save button to save the desired settings.  

The image below shows the Editable fields for the Product Description Section.

• Changing the Order of Industry Standard Specifications 
• In the Industry Standard Specifications Section, the user can change the order of the specifications. Click and hold the icon to drag and drop the specification to the desired position. 

• The order of the specifications will be reflected on the product page. 

• 

•  
• SEO Section
• The Product Description Section has one Editable Field. The user can select either POS/Laravo or Custom. Click the Save button to save the desired settings.  
  1. Page Title 
  2. Meta Title
  3. Meta Description
  4. Meta Keyword

The image below shows the Editable fields for the Product Description Section.

•  

Stock/Price Uploader

When using the Stock/Price Uploader, the user is able to define what Custom fields they want to use when uploading Stock/Price data. Alternatively, the user can also define using Laravo/POS data. 

Breadcrumb path: Products / Manage Products / Stock/Price Uploader

The user can select Laravo POS Data or Laravo Brand Data and download a CSV with Stock/Price data. 

The CSV will have several columns that will be used to define whether Laravo/POS Brand Data will be used or if Custom Data will be used. The following columns are used...

• Quantity POS
• Quantity Custom    
• Quantity Primary Source   
• Retail Price POS    
• Retail Price Custom    
• Retail Price Primary Source    
• Sale Price POS    
• Sale Price Custom    
• Sale Price Primary Source    
• Cost POS    
• Cost Custom    
• Cost Primary Source    
• Orderable POS    
• Orderable Custom    
• Orderable Primary Source    
• Condition POS    
• Condition Custom    

• Condition Primary Source

• Quantity
• The columns Quantity POS, Quantity Custom, and Quantity Primary Source control whether the Quantity of an item is showing Laravo POS Data or Laravo Brand Data.
  1. Quantity POS/Laravo:  This column shows the Quantity coming from the Laravo POS. This column is non-editable and will always be overwritten with the data provide by  Laravo POS Data or Laravo Brand Data.
  2. Quantity Custom: This column shows the Quantity that is custom-defined by the user. The user can edit this column to define the quantity of the item. 
  3. Quantity Primary Source: This column allows the user to define if the item will use Custom Data or Laravo POS/Brand Data. If the value of the column is "custom" the item will use the values defined in the column Quantity Custom. Alternatively, if the value of the column is "source" the item will use the values defined in the column Quantity POS/Laravo.

The example below shows that the column Quantity Price Source is defined using "source" meaning the item will use the quantity defined in the column Quantity POS. The column Quantity POS uses POS/Brand data from Laravo. 

The example below shows that the column Quantity Price Source is defined using "custom" meaning the item will use the quantity defined in the column Quantity Custom. The column Quantity POS uses POS/Brand data from Laravo. 

•  
• Retail Price
• The columns Retail Price POS, Retail Price Custom, and Retail Price Primary Source
   control whether the Retail Price of an item is showing Laravo POS Data or Laravo Brand Data.
  1. Retail Price POS/Laravo:  This column shows the Retail Price coming from the Laravo POS. This column is non-editable and will always be overwritten with the data provided by  Laravo POS Data or Laravo Brand Data.
  2. Retail Price Custom: This column shows the Retail Price that is custom-defined by the user. The user can edit this column to define the Retail Price of the item. 
  3. Retail Price Primary Source: This column allows the user to define if the item will use Custom Data or Laravo POS/Brand Data. If the value of the column is "custom" the item will use the values defined in the column Retail Price Custom. Alternatively, if the value of the column is "source" the item will use the values defined in the column Retail Price POS/Laravo.

The example below shows that the column Retail Price Source is defined using "source" meaning the item will use the Retail Price defined in the column Retail Price POS. The column Retail Price POS uses POS/Brand data from Laravo. 

The example below shows that the column Retail Price Source is defined using "custom" meaning the item will use the Retail Price defined in the column Retail Price Custom. The column Retail Price POS uses POS/Brand data from Laravo. 

• Sale Price
• The columns Sale Price POS, Sale Price Custom, and Sale Price Primary Source
   control whether the Sale Price of an item is showing Laravo POS Data or Laravo Brand Data.
  1. Sale Price POS/Laravo:  This column shows the Sale Price coming from the Laravo POS. This column is non-editable and will always be overwritten with the data provided by  Laravo POS Data or Laravo Brand Data.
  2. Sale Price Custom: This column shows the Sale Price that is custom-defined by the user. The user can edit this column to define the Sale Price of the item. 
  3. Sale Price Primary Source: This column allows the user to define if the item will use Custom Data or Laravo POS/Brand Data. If the value of the column is "custom" the item will use the values defined in the column Sale Price Custom. Alternatively, if the value of the column is "source" the item will use the values defined in the column Sale Price POS/Laravo.

The example below shows that the column Sale Price Source is defined using "source" meaning the item will use the Sale Price defined in the column Sale Price POS. The column Sale Price POS uses POS/Brand data from Laravo. 

The example below shows that the column Sale Price Source is defined using "custom" meaning the item will use the Sale Price defined in the column Sale Price Custom. The column Sale Price POS uses POS/Brand data from Laravo. 

• Cost
• The columns Cost POS, Cost Custom, and Cost Primary Source
   control whether the Cost of an item is showing Laravo POS Data or Laravo Brand Data.
  1. Cost POS/Laravo:  This column shows the Cost coming from the Laravo POS. This column is non-editable and will always be overwritten with the data provided by  Laravo POS Data or Laravo Brand Data.
  2. Cost Custom: This column shows the Cost that is custom-defined by the user. The user can edit this column to define the Cost of the item. 
  3. Cost Primary Source: This column allows the user to define if the item will use Custom Data or Laravo POS/Brand Data. If the value of the column is "custom" the item will use the values defined in the column Cost Custom. Alternatively, if the value of the column is "source" the item will use the values defined in the column Cost POS/Laravo.

The example below shows that the column Cost Source is defined using "source" meaning the item will use the Cost defined in the column Cost POS. The column Cost POS uses POS/Brand data from Laravo. 

The example below shows that the column Cost Source is defined using "custom" meaning the item will use the Cost defined in the column Cost Custom. The column Cost POS uses POS/Brand data from Laravo. 

• Orderable
• The columns Orderable POS, Orderable Custom, and Orderable Primary Source
   control whether the Orderability of an item is showing Laravo POS Data or Laravo Brand Data.
  1. Orderable POS/Laravo:  This column shows the Orderable coming from the Laravo POS. This column is non-editable and will always be overwritten with the data provided by  Laravo POS Data or Laravo Brand Data.
  2. Orderable Custom: This column shows the Orderability that is custom-defined by the user. The user can edit this column to define the Orderability of the item. 
  3. Orderable Primary Source: This column allows the user to define if the item will use Custom Data or Laravo POS/Brand Data. If the value of the column is "custom" the item will use the values defined in the column Orderable Custom. Alternatively, if the value of the column is "source" the item will use the values defined in the column Orderable POS/Laravo.

The example below shows that the column Orderable Primary Source is defined using "source" meaning the item will use the Orderability defined in the column Orderable POS. The column Orderable POS uses POS/Brand data from Laravo. 

The example below shows that the column Orderable Source is defined using "custom" meaning the item will use the Orderability defined in the column Orderable Custom. The column Orderable POS uses POS/Brand data from Laravo. 

• Condition
• The columns Condition POS, Condition Custom, and Condition Primary Source
   control whether the Condition of an item is showing Laravo POS Data or Laravo Brand Data.
  1. Condition POS/Laravo:  This column shows the Condition coming from the Laravo POS. This column is non-editable and will always be overwritten with the data provided by  Laravo POS Data or Laravo Brand Data.
  2. Condition Custom: This column shows the Condition that is custom-defined by the user. The user can edit this column to define the Condition of the item. 
  3. Condition Primary Source: This column allows the user to define if the item will use Custom Data or Laravo POS/Brand Data. If the value of the column is "custom" the item will use the values defined in the column Condition Custom. Alternatively, if the value of the column is "source" the item will use the values defined in the column Condition POS/Laravo.

The example below shows that the column Condition Primary Source is defined using "source" meaning the item will use the Condition defined in the column Condition POS. The column Condition POS uses POS/Brand data from Laravo. 

The example below shows that the column Condition Source is defined using "custom" meaning the item will use the Condition defined in the column ConditionCustom. The column Condition POS uses POS/Brand data from Laravo. 

When the CSV file is edited with the desired settings, it can be uploaded back to the same location where you downloaded the CSV.

Breadcrumb path: Products / Manage Products / Stock/Price Uploader

Here you can select a Brand that has Laravo POS/Brand Data that you want to upload your Custom Fields to. Also, select File Based on Guid and match the Column Name for Guid with the column "Guid" on the CSV. Make sure the spelling is correct when matching the File Based on Guid with the Guid column. 

The following fields can be matched to update the Brand that has Laravo POS/Brand Data. 

• Column Name for Status
• Column Name for Quantity  
• Column Name for Quantity Primary Source  
• Column Name for Retail Price
• Column Name for Retail Price Primary Source  
• Column Name for Show Price
• Column Name for Sale Price  
• Column Name for Sale Price Primary Source  
• Column Name for Cost
• Column Name for Cost Primary Source  
• Column Name for Orderable
• Column Name for Orderable Primary Source  
• Column Name for Condition
• Column Name for Condition Primary Source  

Here is an example of the Retail Price being updated to use Custom Data. The field Column Name for Retail Price is set to be the same as the column Retail Price Custom in the CSV. 

When all fields are set to match the columns on the CSV, select the CSV and click upload. The data for the selected brand will be updated with the defined settings on the CSV. 

Now that you have learned about Editable Fields, this completes the section of the user manual.