Configure Structured Fields | Listagrow Help Center

Use Structured Fields to choose the connected-platform fields Listagrow should populate during generation or enrichment. It is a shared configuration surface for supported connected platforms, including Shopify, WooCommerce, and CS-Cart. Each platform keeps its own field set.

Structured Fields are useful when ordinary titles, descriptions, tags, and SEO content are not enough. Typical uses include Shopify metafields, WooCommerce custom product data, and CS-Cart product features or custom fields.

For a Shopify-focused overview, see AI Shopify Metafields and Category Attributes.

Choose the platform first

Open Brand & Content and choose Structured Fields.
Select the platform tab you want to configure.
Confirm the connected store in the selector at the top of the app.
Make your changes, then select Save at the top of Brand & Content.

Do not assume a field added under one platform will be used by another. Configure every destination that needs its own structured data.

Configure a field

The configured-fields list shows the fields Listagrow knows about for the selected platform. Each item includes its label, platform namespace and key when the platform provides them, and its field type.

Select Enable when Listagrow should populate the field.
Select Disable when you want the field to remain configured but prefer to manage its values yourself.
Select Edit instructions to add optional, field-specific AI guidance.
Select Remove to take the field out of this platform’s Listagrow configuration.

Use field instructions for rules that belong to one structured value, not your whole catalog. For example:

For a material field: Use the material stated in the source. Do not infer leather, wool, or solid wood when it is not stated.
For a care field: Give short care instructions only when the product material supports them. Leave the field empty for digital products.
For a list field: Return up to five shopper search phrases. Do not repeat the exact product title.

Add an existing platform definition

When the connected platform exposes definitions that are not yet configured, they appear under Available fields. Select Add beside a field to include it in the selected platform’s Listagrow field set.

Before adding a definition, check its platform label, namespace and key, and data type. A field should match a real destination in the connected store. Adding every available definition makes output harder to review and can encourage the AI to fill fields that are irrelevant to a product.

Add a custom field

Use Add custom field when the selected platform needs a field that is not available in the existing definitions list.

Provide:

Key: a stable machine-friendly name, such as material or care_notes. Spaces are converted to underscores.
Label: the customer-readable field name, such as Material or Care notes.
Type: choose the value shape that matches the destination: short text, long text, number, decimal, yes/no, list, URL, or color.
AI instructions: optional instructions for how the value should be produced.

Custom fields are best for a known catalog requirement. Confirm the destination field and expected type with the platform setup before relying on it in a production workflow.

Use Data Rules for verified values

Data Rules are optional. Use them when a structured value must be extracted from product text or supplied context instead of guessed. They run before AI generation for that field.

Enable Data Rules from a field’s expanded instructions panel, then configure the rule:

Choose what happens when the required product text is missing:
- Leave this field blank when accuracy is more important than completeness.
- Let AI fill the gap when an informed AI result is acceptable.
Enter a regular expression in Find the value (regex). Use parentheses around the part of the match you want to store.
Set the Capture group to save when your pattern has more than one parenthesized match.
Optionally validate the result, format it, restrict it to approved choices, or transform it.
Select Test rule, paste a representative product-detail excerpt, and confirm the resolved value before saving.

For example, to extract a stated material from a source line such as Material: Recycled nylon, use a pattern like ^\s*Material\s*:\s*(.+?)\s*$ and save capture group 1.

Validate and transform extracted values

Use Allowed output to control the values that can be saved:

Any value matching a format accepts values that pass your optional validation pattern.
Only these choices restricts output to a comma-separated approved list, such as New, Used, Refurbished.
Some platforms may offer store-option matching or creation controls when their field type supports it.

Transforms run in order after extraction and before validation. You can map values, convert measurements, or convert durations. Examples include mapping yes to true, converting a supplied measurement from centimetres to inches, or converting a warranty from months to years. Keep transforms simple and test them with real, anonymized input.

Category attributes

Some connected platforms show Category Attributes below their structured fields. This option lets Listagrow prepare category-specific values such as colour, material, or size.

Enable Generate category attributes only when you want Listagrow to produce these fields. When the selected platform provides namespace choices, choose the namespace where the category attributes should be stored. Leave the option off when your team manages category attributes manually or the platform does not support this workflow.

Review before publishing

Open a product in Review Products after generation or enrichment. Review every structured value with the same care as its title, description, pricing, and category.

The review label depends on the platform. For example, Shopify shows a Metafields section with the category and product metadata for that product, while other platforms can present their own fields, attributes, or features. Return to Structured Fields through the product’s management link whenever future jobs need a different field configuration.