Mapping
Summary
Explains how Flxpoint's mapping templates, mapping rules, and mapping sets work together to align and transform data between an integration and your catalog.
Mapping is how Flxpoint moves and reshapes data between an integration and your catalog. It works in three layers: a mapping template aligns fields, while mapping rules and mapping sets are applied inside a template to transform individual field values.
- Mapping templates: the field map. Takes values from one side (incoming) and translates them to the other (Flxpoint or the channel).
- Mapping rules: mini workflows applied to a single field: conditional or tiered transforms that run after the template maps a value.
- Mapping sets: simple value-to-value lookups (for example, translate "new" to "1"), applied to a field within a template.
- Default templates: generate a default template to auto-populate the recommended field configuration as a starting point.
The three layers
| Layer | What it does | Where it lives |
|---|---|---|
| Mapping template | Maps incoming fields to Flxpoint fields (or Flxpoint to a channel), with per-field operations. | Settings → Mapping → Templates |
| Mapping set | Replaces a given value with another via a lookup table. | Settings → Mapping → Sets, then applied to a field in a template |
| Mapping rule | Conditionally modifies a field value after mapping (if/then or tiered). | Created in a template, or built separately and added to a field |
Mapping template operations
Each field in a template uses one operation to decide how its value is set.
| Operation | What it does |
|---|---|
| Field | Use an available data point from the integration or event. |
| Value | Set a fixed value (hard-code it). |
| Option | Choose from predefined options. |
| Direct Copy | Automatically map matching values across. |
| Mapping Set | Apply a value-to-value lookup set. |
| Rules | Apply conditional or tiered transforms. |
| Don't Map | Leave the right-hand field untouched. |
| Set To Empty | Clear the field on every sync. |
Rule types
Rules run after the template maps a value. Two rule types are available.
- Conditional: if/then logic. Input types: String, Number, Boolean, Option Field. Example: if Brand = XYZ, set Title to Original Value.
- Tier: applies values from a tiered list that can be marked up or marked down, useful for pricing.
| Term | Meaning |
|---|---|
| Incoming Value | The value being manipulated. Because rules can be chained, this value passes through each rule in turn. |
| Original Value | The value first mapped from the field: use it to back out of a change. |
Mapping sets
A mapping set is two columns: Convert From Value (the incoming value) and To Value (the output). Populate it by hand or with a bulk CSV upload. Apply the set to a field inside a mapping template.
Post-mapping workflows and custom fields
Post-Mapping Workflows (PMWs) can add or update variant custom fields even if those fields are set to Don't Map in your mapping template. Custom fields created or modified by a PMW will persist on the product or variant regardless of the template configuration. To verify these updates, run the workflow and then refresh or reopen the product in the Product Builder or Inventory variant detail screens. Note that recent updates ensure PMW behavior remains consistent across different sources, so it is recommended to perform a full QA check when deploying new workflows to confirm fields like Preferred flags update as expected.
Note: When mapping the Ship By field in order or shipping workflows, Flxpoint supports specific date formats including YYYY-MM-DD HH:mm:ss (full timestamp) and YYYY-MM-DD (date only). Ensure your mapping rules or source data align with these formats to maintain valid date parsing during sync.
Custom field mapping options are missing: only Direct Copy is available on Get Inventory [Primary]
Some accounts report the block for product options, attributes, images, and custom fields disappearing from the inventory import template, leaving only Direct Copy for custom fields. This is a known open issue under investigation: if you can no longer set specific custom field keys/values that you could set before, capture before/after screenshots and raise it with support rather than rebuilding the template.
"Something went wrong and we were unable to process your request" when creating a new mapping template
This is a known error some accounts hit when creating a template. Retry, and if it persists, send support the account and the integration you are creating the template for: it needs a backend fix rather than a configuration change.
A mapping rule is not applying
Confirm the rule is actually added to the field (a rule built outside a template must be added manually). Use Test Rule with sample data to verify the condition passes. Note that rebuilding a product from the Edit screen may not apply template rules the same way an inventory-view build does: build from the inventory/product view to confirm the rule fires.
A field is mapped but the data is not populating
Check that the field is mapped on both templates in the flow (for example, the channel Order template and the Fulfillment Request template), that the operation is not left on Don't Map, and that the source actually provides a value for that field.
Listings fail with "Missing title for creating Shopify Product"
The Title field is set to Don't Map on the channel template, so no title is sent and the listing cannot be created or linked. Map Title to your product title field, save, and re-publish or re-link the affected listings.
Onboarding file mapping persistence
When onboarding via manual file upload, you can access and update your mapping templates multiple times without losing your configuration. Ensure you save your updates before exiting the screen to verify the template displays correctly upon your next access.
Mapping complex fields during setup
The onboarding mapping interface supports full configuration for product options, images, attributes, and both parent and variant custom fields. If you are using the Standard platform, these templates are managed under the Catalog menu for Inventory, Products, or Listings.
Seawide products showing $0.00 MAP or MAP violations?
For Seawide source integrations, the vendor feed may provide MAP values in a field named MAPRetail rather than the standard MRP field. If you encounter MAP violations or see zeroed values, verify your Get Inventory mapping template and ensure the MAPRetail field is mapped to the Flxpoint MAP field to capture the correct vendor-provided pricing.
What is the difference between a mapping template, a rule, and a set?
A template is the overall field map. A set is a value-to-value lookup applied to one field. A rule is conditional or tiered logic applied to one field. Rules and sets both live inside a template.
When should I use a rule versus a set?
Use a set for straightforward one-to-one value swaps (translate "A" to "Alpha"). Use a rule when the change depends on a condition or needs tiered logic (if Brand = XYZ, apply sentence case to the title).
Do rules run before or after the template maps a value?
After. A rule modifies the value the template has already mapped.
Can I chain multiple rules on one field?
Yes. The Incoming Value passes through each rule in sequence, so the order of the rules affects the result.
How do I undo a change a rule made?
Reference the Original Value in a follow-up condition: it holds the value as it was first mapped, before the rule ran.
Can I bulk-load a mapping set?
Yes, via CSV upload. Header names are case-sensitive, and each Convert From Value must match the incoming value exactly to convert.