Use Product Rules when generated or enriched product content needs consistent final adjustments. Rules run after Listagrow’s AI work, so they are useful for business requirements that should take priority over an individual AI result.
Rules apply when a future job runs in the selected workflow. They do not retroactively update products that are already waiting in Review Products. Start with a small number of rules, test them on a focused set of products, and review the result before using them at catalog scale.
Add a product rule
- Open Brand & Content and choose Product Rules.
- Select Add Rule.
- Give the rule a clear name, then choose its Rule type and Target field.
- Configure the value, source field, transformation, tags, or price adjustment required by that rule.
- Choose whether the rule applies when you Generate, Enrich, or do both.
- Add a condition when the rule should apply only to products that match a specific situation.
- Add the rule, then select Save at the top of Brand & Content.

Choose a rule type
Choose the smallest rule that expresses the outcome you need:
- Set value (keep existing) fills a target only when it is empty or, for supported numeric fields, zero. Use it for safe defaults such as a fallback inventory quantity.
- Set value (overwrite) replaces the current target value every time the rule runs. Use it only when your business rule must win over source data and generated content.
- Copy from another field copies a selected source field to the target. You can limit the copy to empty targets.
- Append tags adds a comma-separated list of tags while skipping duplicates.
- Remove tags removes exact tag names and can optionally remove tags that match a regular-expression pattern.
- Transform (modify value) truncates text, multiplies a value, strips HTML, or changes text capitalization.
- Price adjustment (markup / markdown) changes a price or compare-at price by a percentage or fixed amount.

Choose a target field
Rules can target the title, description, price, compare-at price, inventory quantity, SKU, barcode, weight, tags, vendor, product type, SEO title, SEO description, or a custom field path.
When you select Custom field, enter the exact field path expected by your catalog configuration. Use this only when the destination is known and tested; an incorrect path will not create a reliable catalog workflow.
For price adjustments, the target is limited to price and compare-at price. The labels can vary by connected platform.
Safe examples
- Set a default inventory quantity of
10only when the quantity is empty. - Copy a barcode into an SKU only when the SKU is empty.
- Append
seasonal, clearancetags to a selected workflow. - Remove tags that start with
old-using a pattern such as^old-.*. - Truncate an SEO title to meet a destination requirement.

Configure price adjustments
Use a price-adjustment rule when a generated or enriched product needs a consistent markup or markdown.
Choose one of four adjustments: percentage markup, percentage markdown, fixed-amount markup, or fixed-amount markdown. By default, the calculation uses the target price. You can instead choose the other price field as the base value, such as calculating a sale price from the compare-at price.
For example, a 20% markup using compare-at price as the base can calculate a sale price from the list price. The rule skips an empty or zero base price, and a fixed markdown never produces a negative price.

Transform values carefully
Transforms are useful when the source value is correct but needs a consistent format.
- Truncate to length limits text to a maximum character count.
- Multiply by factor changes a numeric value, such as applying a conversion factor.
- Strip HTML tags turns formatted text into plain text.
- Capitalize first letter, Uppercase, and Lowercase standardize text casing.
Apply transformations sparingly. A transformation changes every value that reaches the rule, so validate it on representative products before relying on it.

Add a condition
Turn on Add condition (only run if…) when a rule should run only for matching products. You can test whether a field is empty, has a value, equals or differs from a value, compares numerically, or contains text.
Conditions can use standard product fields as well as category and internal product-category values. With a connected store, category and vendor conditions use the active platform’s available values to help you choose an accurate match.
Examples:
- Add a fallback vendor only when the vendor field is empty.
- Apply a tag only when the category is a specific product family.
- Apply a markup only when the current price is greater than zero.

Select the workflow
Use Generate for rules that should apply to new products created from images or source files. Use Enrich for rules that should apply when Listagrow improves products from a connected catalog. Select both only when the same requirement belongs in both workflows.
Configure SKU generation
The SKU Generation section controls how Listagrow supplies SKUs.
- Turn on Generate SKUs automatically to fill blank SKU fields when new products are generated.
- Turn on Replace existing SKUs only when enrichment should rewrite SKUs already in your catalog.
- Choose a preset that combines category, product, variant, brand, and a sequence number. The preset descriptions explain the catalog type each format suits.
- Choose Custom pattern only when a preset does not meet your operational requirement.
- Set a sequence length from
1to8; Listagrow pads the example sequence with zeros. - Set a starting number, then check the live example SKU before saving.
Custom patterns can use {brand}, {cat}, {prod}, {var}, and {seq}. For example, {cat}-{prod}-{var}-{seq} produces a format similar to FUR-SDBRDCBN-OAK-0001 when that information is available.
Review the example carefully before enabling replacement of existing SKUs. Existing SKUs may be used by inventory, fulfillment, reporting, or other sales systems.