This guide shows how Field Mappings power your listing builder, how to configure per-field rules, and how mapping templates are created, saved, and reused. Learn with short tutorials, practical how-to steps, in-depth explanations, and a reference you can keep open while working.

🧪 Tutorials

Create a channel & auto-generate its default mapping template

Goal: See how a default listing mapping template is created for a new channel.

Scenario: You add a Shopify Store channel and want the template grouped by Variant (top) and Parent (bottom), both A→Z.

1. Go to Channels → Add Channel and select your storefront (e.g., Shopify Store).
2. After creation, open Field Mappings. A default Listing Mapping Template is created automatically.
   • Variant fields appear first, alphabetically.
   • Parent fields appear next, alphabetically.
   • Required fields are locked (cannot be unmapped).
3. Toggle a sample field to observe state changes: Mapped ↔ Not Mapped.
4. Make one change—notice the save bar appears at the top. Click Save.

Configure rules for Variant → Title

Goal: Build a clean Variant Title using Parent Title + UPC.

1. In Field Mappings, find Variant → Title and ensure it’s Mapped.
2. Click Configure Rules to open the flyout.
3. Select Always apply.
4. Add Rule #1: Set to Field → Parent → Title.
5. Add Rule #2: Postfix Field → UPC, Separator → Space.
6. Optional: Add Rule #3: Set Casing → Title case.
7. Click Save Rules. Then use the page Save bar to persist the template.

Use the mapping template during Create Products/Listings

Goal: Access the template in a new tab while creating products and listings.

1. Go to Catalog → Create and Link Products.
2. In Listings, select one or more channels. Click Field Mapping ↗ to open the template in a new tab.
3. Adjust mappings/rules as needed, Save Rules and click the page Save bar.
4. Return to the flow and continue. Listings are built in batches using the saved template.

🛠️ How-to Guides

A. Map or unmap a field

1. Open Channels → [Channel] → Field Mappings.
2. Use the toggle to set a field to Mapped or Not Mapped.
3. Required fields cannot be unmapped.
4. Click the top Save bar to persist.

B. Configure rules for a mapped field

1. Click Configure Rules on a mapped field. (If unmapped, rules can’t be edited; existing rules are preserved.)
2. Choose Always apply or Only when field is empty.
3. Add up to 5 rules (see actions below). Rules can be deleted but not reordered.
4. Click Save Rules, then use the page Save bar.

C. Manage mapping templates

1. Each channel has a universal template that is opened from Field Mappings or from the Create Listings step.
2. When you click Save Rules, changes are stored with the template. If the page’s Save bar is not clicked, changes can be lost in the current tab.
3. If multiple templates are created by design, the system will keep the most recent and cleanup unused (15+ days) templates automatically.

D. Batch-build listings with the template

1. From Create Listings, select channels and proceed.
2. The batch uses the latest saved template (per channel) for field outputs and rule evaluation.
3. Reopen Field Mapping ↗ if you need changes; save before continuing the batch.

🔍 Explanation

Key concepts

• Grouping & order: Variant fields display first (A→Z), then Parent fields (A→Z). Labels are prefixed as Variant → or Parent → inside the rules flyout.
• Required fields: These cannot be unmapped (channel requirements). Their toggles are disabled.
• State: Mapped = the field has a source mapping. Not Mapped = the field will not be sent.
• Rules availability: Rules can only be edited when a field is mapped. If you later unmap the field, its rules are kept but inactive.
• Rule limit: Up to 5 rules per field. Rules execute from top to bottom at save time; you can delete a rule but not reorder.

Rule actions & options

• Prefix/Postfix value — add a literal value. Choose Separator: Underscore (_), Dash (-), or Space.
• Prefix/Postfix field — add the value of another field with a separator.
• Set to field — replace the field entirely with another field’s value.
• Set to value — replace the field with a literal value.
• Set casing — normalize to Uppercase, Lowercase, Sentence case, or Title case.
• Run conditions — Always vs Only when field is empty determine when the rule set applies.

Saving behavior

• Save Rules commits rule changes to the template instance loaded in the flyout.
• The page-level Save bar persists the template to the channel. You should use both to avoid losing work when the template opens in a new tab.
• Template lifecycle may keep older versions; unused templates older than 15 days are eligible for cleanup.

Access points

• Channels → Field Mappings (primary)
• Create & Link Products → Listings → Field Mapping ↗
• Create Listings → Field Mapping ↗

📚 Reference

Field states & UI behavior

Quick FAQ

• Why can’t I edit rules? Ensure the field is Mapped. Unmapped fields disable rule editing (existing rules are kept).
• Do I lose changes if I close the tab? If you only clicked Save Rules but didn’t confirm the page Save bar, your latest changes might not persist to the channel.
• Can I reorder rules? Not at this time; delete and re-add in the desired order.
• How many rules per field? Up to five.