AI validation tweaks, add templates settings page and schema and routes

inventory-server/src/prompts/product-validation.txt

@@ -1,10 +1,10 @@
-I will provide a JSON array with product data. Process the array by combining all products from validData and invalidData arrays into a single array, excluding any fields starting with “__”, such as “__index” or “__errors”. Process each product according to the reference guidelines below. If a field is not included in the data, do not include it in your response unless the specific field guidelines below say otherwise. 
+I will provide a JSON array with product data. Process the array by combining all products from validData and invalidData arrays into a single array, excluding any fields starting with “__”, such as “__index” or “__errors”. Process each product according to the reference guidelines below. If a field is not included in the data, do not include it in your response (e.g. do not include its key or any value) unless the specific field guidelines below say otherwise. If a product appears to be from an empty or entirely invalid line, do not include it in your response.
 
-Respond in the following JSON structure in minified format (single line, no whitespace):
+Your response should be a JSON object with the following structure:
 {
   "correctedData": [], // Array of corrected products
   "changes": [], // Array of strings describing each change made
-  "warnings": [] // Array of strings with warnings or suggestions for manual review
+  "warnings": [] // Array of strings with warnings or suggestions for manual review (see below for details)
 }
 
 Using the provided guidelines, focus on:
@@ -14,94 +14,101 @@ Using the provided guidelines, focus on:
 4. Fixing any obvious errors or inconsistencies between similar products in measurements, prices, or quantities
 5. Adding correct categories, themes, and colors
 
-Use only the provided data and your own knowledge to make changes. Do not make assumptions or make up information that you're not sure about. If you're unable to make a change you're confident about, leave the field as is. All data passed in should be validated, corrected, and returned. All values should be strings. Do not leave out any fields that were present in the original data.
+Use only the provided data and your own knowledge to make changes. Do not make assumptions or make up information that you're not sure about. If you're unable to make a change you're confident about, leave the field as is. All data passed in should be validated, corrected, and returned. All values returned should be strings, not numbers. Do not leave out any fields that were present in the original data.
+
+Possible reasons for including a warning in the warnings array:
+- If you're unable to make a change you're confident about but you believe one needs to be made
+- If there are inconsistencies in the data that could be valid but need to be reviewed
+- If not enough information is provided to make a change that you believe is needed
+- If you infer a value for a required field based on context
+
 
 ----------PRODUCT FIELD GUIDELINES----------
 
 Fields: supplier, private_notes, company, line, subline, artist
 Changes: Not allowed
-Required: Return if present in the original data
+Required: Return if present in the original data. Do not return if not present.
 Instructions: If present, return these fields exactly as provided with no changes
 
 Fields: upc, supplier_no, notions_no, item_number
 Changes: Formatting only
-Required: Return if present in the original data
+Required: Return if present in the original data. Do not return if not present.
 Instructions: If present, trim outside white space and return these fields exactly as provided with no other changes
 
 Fields: hts_code
 Changes: Minimal, you can correct formatting, obvious errors or inconsistencies
-Required: Return if present in the original data
-Instructions: If present, trim white space and any characters that are not a number or decimal point and return as a string
+Required: Return if present in the original data. Do not return if not present.
+Instructions: If present, trim white space and any non-numeric characters, then return as a string. Do not validate in any other way.
 
 Fields: image_url
 Changes: Formatting only
-Required: Return if present in the original data
+Required: Return if present in the original data. Do not return if not present.
 Instructions: If present, convert all comma-separated values to valid https:// URLs and return
 
 Fields: msrp, cost_each
 Changes: Minimal, you can correct formatting, obvious errors or inconsistencies
-Required: Return if present in the original data
+Required: Return if present in the original data. Do not return if not present.
 Instructions: If present, strip any currency symbols and return as a string with exactly two decimal places, even if the last place is a 0.
 
 Fields: qty_per_unit, case_qty
 Changes: Minimal, you can correct formatting, obvious errors or inconsistencies
-Required: Return if present in the original data
+Required: Return if present in the original data. Do not return if not present.
 Instructions: If present, strip non-numeric characters and return
 
 Fields: ship_restrictions
 Changes: Only add a value if it's not already present
-Required: You must always return a value for this field, even if it's not provided in the original data
-Instructions: Always return a value exactly as provided, or return 0 if no value is provided. Do not leave this field out even if it's not provided.
+Required: You must always return a value for this field, even if it's not provided in the original data. If no value is provided, return 0.
+Instructions: Always return a value exactly as provided, or return 0 if no value is provided.
 
 Fields: eta
 Changes: Minimal, you can correct formatting, obvious errors or inconsistencies
-Required: Return if present in the original data
+Required: Return if present in the original data. Do not return if not present.
 Instructions: If present, return a full month name, day is optional, no year ever (e.g. “January” or “March 3”). This value is not required if not provided.
 
 Fields: name
 Changes: Allowed to conform to guidelines, to fix typos or formatting
-Required: You must always return a value for this field, even if it's not provided in the original data
+Required: You must always return a value for this field, even if it's not provided in the original data. If no value is provided, return the most reasonable value possible based on the naming guidelines and the other information you have.
 Instructions: Always return a value that is corrected and enhanced per additional guidelines below
 
 Fields: description
 Changes: Full creative control allowed within guidelines
-Required: You must always return a value for this field, even if it's not provided in the original data
+Required: You must always return a value for this field, even if it's not provided in the original data. If no value is provided, return the most accurate description possible based on the description guidelines and the other information you have.
 Instructions: Always return a value that is corrected and enhanced per additional guidelines below
 
 Fields: weight, length, width, height
 Changes: Allowed to correct obvious errors or inconsistencies or to add missing values
-Required: You must always return a value for this field, even if it's not provided in the original data
-Instructions: Always return a reasonable value (weights in ounces and dimensions in inches) that is validated against similar provided products and your knowledge of general object measurements (e.g. a sheet of paper is not going to be 3 inches thick, a pack of stickers is not going to be 250 ounces, this sheet of paper is very likely going to be the same size as that other sheet of paper from the same line). If a value is unusual or unreasonable, change it to match similar products or to be more reasonable. Do not return 0 or null for any of these fields.
+Required: You must always return a value for this field, even if it's not provided in the original data. If no value is provided, return your best guess based on the other information you have or the dimensions for similar products.
+Instructions: Always return a reasonable value (weights in ounces and dimensions in inches) that is validated against similar provided products and your knowledge of general object measurements (e.g. a sheet of paper is not going to be 3 inches thick, a pack of stickers is not going to be 250 ounces, this sheet of paper is very likely going to be the same size as that other sheet of paper from the same line). If a value is unusual or unreasonable, even wildly so, change it to match similar products or to be more reasonable. When correcting unreasonable weights or dimensions, prioritize comparisons to products from the same company and product line first, then broader category matches or common knowledge if necessary.Do not return 0 or null for any of these fields.
 
 Fields: coo
 Changes: Formatting only
-Required: Return if present in the original data
-Instructions: If present, return a valid two character country code, using capital letters
+Required: Return if present in the original data. Do not return if not present.
+Instructions: If present, convert all country names and abbreviations to the official ISO 3166-1 alpha-2 two-character country code. Convert any value with more than two characters to two characters only (e.g. "United States" or "USA" should both return "US").
 
 Fields: tax_cat
 Changes: Allowed to correct obvious errors or inconsistencies or to add missing values
-Required: You must always return a value for this field, even if it's not provided in the original data
+Required: You must always return a value for this field, even if it's not provided in the original data. If no value is provided, return 0.
 Instructions: Always return a valid numerical tax code ID from the Available Tax Codes array below. Give preference to the value provided, but correct it if another value is more accurate. You must return a value for this field. 0 should be the default value in most cases.
 
 Fields: size_cat
 Changes: Allowed to correct obvious errors or inconsistencies or to add missing values
-Required: Return if present in the original data or if not present and applicable
-Instructions: If present or if applicable, return a valid numerical size category ID from the Available Size Categories array below. Give preference to the value provided, but correct it if another value is more accurate. A value is not required if none of the size categories apply.
+Required: Return if present in the original data or if not present and applicable. Do not return if not applicable (e.g. if no size categories apply based on what you know about the product).
+Instructions: If present or if applicable, return one valid numerical size category ID from the Available Size Categories array below. Give preference to the value provided, but correct it if another value is more accurate. A value is not required if none of the size categories apply, but it's important to include if one clearly applies, such as if the name contains 12x12, 6x8, 2oz, etc.
 
 Fields: themes
 Changes: Allowed to correct obvious errors or inconsistencies or to add missing values
-Required: Return if present in the original data or if not present and applicable
+Required: Return if present in the original data or if not present and applicable. Do not return any value if not applicable (e.g. if no themes apply based on what you know about the product).
 Instructions: If present, confirm that each provided theme matches what you understand to be a theme of the product. Remove any themes that do not match and add any themes that are missing. Most products will have zero or one theme. Return a comma-separated list of numerical theme IDs from the Available Themes array below. If you choose a sub-theme, you do not need to include its parent theme in the list.
 
 Fields: colors
 Changes: Allowed to correct obvious errors or inconsistencies or to add missing values
-Required: Return if present in the original data or if not present and applicable
-Instructions: If present or if applicable, return a comma-separated list of numerical color IDs from the Available Colors array below, using the product name as the primary guide. A value is not required if none of the colors apply. Most products will have zero colors.
+Required: Return if present in the original data or if not present and applicable. Do not return any value if not applicable (e.g. if no colors apply based on what you know about the product).
+Instructions: If present or if applicable, return a comma-separated list of numerical color IDs from the Available Colors array below, using the product name as the primary guide (e.g. if the name contains Blue or a blue variant, you should return the blue color ID). A value is not required if none of the colors apply. Most products will have zero colors.
 
 Fields: categories
 Changes: Allowed to correct obvious errors or inconsistencies or to add missing values
-Required: You must always return at least one value for this field, even if it's not provided in the original data
-Instructions: Always return a comma-separated list of one or more valid numerical category IDs from the Available Categories array below. Give preference to the values provided, particularly if the other information isn't enough to determine a category, but correct them or add new categories if another value is more accurate. Do not return categories in the Deals or Black Friday categories, and strip these from the list if present. If you choose a subcategory at any level, you do not need to include its parent categories in the list. You must return at least one category.
+Required: You must always return at least one value for this field, even if it's not provided in the original data. If no value is provided, return the most appropriate category or categories based on the other information you have.
+Instructions: Always return a comma-separated list of one or more valid numerical category IDs from the Available Categories array below. Give preference to the values provided, particularly if the other information isn't enough to determine a category, but correct them or add new categories if another value is more accurate. Do not return categories in the Deals or Black Friday categories, and strip these from the list if present. If you choose a subcategory at any level, you do not need to include its parent categories in the list. You must return at least one category and you can return multiple categories if applicable. All categories have equal value so their order is not important. Always try to return the most specific categories possible (e.g. one in the third level of the category hierarchy is better than one in the second level).
 
 ----------PRODUCT NAMING GUIDELINES----------
 If there's only one of this type of product in a line: [Line Name] [Product Name] - [Company]
@@ -167,6 +174,10 @@ Important Notes
 - Use the minimum amount of information needed to uniquely identify the product
 - Put detailed specifications in the product description, not its name
 
+Edge Cases
+- If the product is missing a company name, infer one from the other products included in the data
+- If the product is missing a clear differentiator and needs one to be unique, infer and add one from the other data provided (e.g. the description, existing size categories, etc.)
+
 Incorrect example: MVP Rugby - Collection Pack - Photoplay
 Notes: there should be no dash between the line and the product
 
@@ -202,7 +213,7 @@ If no description is provided, make one up using the product name, the informati
 Important Notes:
 - Every description should state exactly what's included in the product (e.g. "Includes one 12x12 sheet of patterned cardstock." or "Includes one 6x12 sheet with 27 unique stickers." or "Includes 55 pieces." or "Package includes machine, power cord, 12 sheets of cardstock, 3 dies, and project instructions.")
 - Do not use the word "our" in the description (this usually shows up when we copy a description from the manufacturer). Instead use "these" or "[Company name] [product]" or similar. (e.g. don't use "Our journals are hand-made in the USA", instead use "These journals are hand made..." or "Archer & Olive journals are handmade...")
-- Don't include fluff like “this is perfect for all your paper crafts” most of the time. If the product helps to solve a unique problem or has a unique feature, by all means describe it, but if it’s just a normal sheet of paper or pack of stickers, you don’t have to pretend like it’s the best thing ever.
+- Don't include statements that add no value like “this is perfect for all your paper crafts”. If the product helps to solve a unique problem or has a unique feature, by all means describe it, but if it’s just a normal sheet of paper or pack of stickers, you don’t have to pretend like it’s the best thing ever. At the same time, ensure that you add enough copy to ensure good SEO.
 - State as many facts as you can about the product, considering the viewpoint of the customer and what they would want to know when looking at it. They probably want to know dimensions, what products it’s compatible with, how thick the paper is, how many sheets are included, whether the sheets are double-sided or not, which items are in the kit, etc. Say as much as you possibly can with the information that you have.
 - !!DO NOT make up information if you aren't sure about it. A minimal correct description is better than a long incorrect one!!