Custom fields and workflow mappings
Add product and variant details
Section titled “Add product and variant details”Custom fields describe your merchandise, not the shopper. Avoid personal information and secrets.
- Find the item in Retail > Catalog. The Custom fields product selector uses the current catalog search results.
- Open Retail > Custom fields and select the item.
- Choose product scope for shared product information, or variant scope for SKU-specific information.
- Enter a stable key, type and value, then save.
| Scope | Key | Type | Example |
|---|---|---|---|
| Product | fabric | Text | Cotton |
| Variant | sleeve_length | Number | 25 |
| Variant | lined | Boolean | false |
Keys use 1-128 letters, digits, underscores, dots or hyphens; reserved keys such as constructor, prototype and __proto__ are rejected. Keys are exact and case-sensitive: Fabric and fabric differ. A key such as details.fabric is a literal key, not a nested path. Product and variant values are separate; there is no automatic fallback between scopes. Adding a product-level value does not automatically group other imported SKUs or copy that value to them.
Up to 100 custom fields per scope are supported; text values have a 4,000-character limit. Use text, finite numbers or booleans, not arrays, objects or null values. A mapped value must not be blank. Saving fields does not approve an image or make a product ready automatically.
Connect fields to the experience
Section titled “Connect fields to the experience”Adding a custom field alone does not change generation. Ask Aabhas to connect it to a supported variable in your assigned workflow. Store administrators do not need to edit workflow IDs or input wiring.
For example, product fabric = Cotton can supply the workflow variable fabric_type. A numeric sleeve_length can supply a text variable only when explicit conversion is configured. Standard product fields such as name/category and variant fields such as size/color can also be used.
A mapping supplies the selected product’s value in place of the matching default, before configured value normalization. An unmapped variable retains its normal behavior. Missing or incompatible mapped values block the try-on rather than silently substituting an unrelated default.
Preview and troubleshoot
Section titled “Preview and troubleshoot”Ask Aabhas to preview a representative product and verify the resolved values before enabling mappings for your store. Preview validates mapped values, not image quality, screen connectivity, available usage, or a complete generation.
| Symptom | What to check |
|---|---|
| Product missing from the selector | Search for it in Catalog first |
| Field saved but no visible effect | Confirm a workflow mapping exists |
| Missing mapped value | Exact key, correct scope, type and nonblank value |
| Numeric value rejected for text | Request explicit scalar-to-text conversion |
| Issue after changing workflows | Ask Aabhas to review mappings for the new workflow |
Mappings are specific to the organization and workflow. A different workflow does not automatically inherit them. Aabhas can remove mappings to return to the normal default behavior without deleting your custom fields.
Prepared-image reuse
Section titled “Prepared-image reuse”These mappings support eligible result-generation variables only. Variables that affect image preparation cannot be mapped through this feature because doing so could reuse an incompatible prepared image. Do not use a custom field to bypass that restriction.
Saving a field is not a cache invalidation action. Ask Aabhas to review preparation-version settings when preparation behavior changes. See Product readiness for preparation reuse.
Custom CSV columns are not automatically ingested. See Catalog import for the supported import workflow.