TB.One > Value Mapping > FAQ - Value Mapping > What is the Difference Between Global and Category Mapping?

What is the Difference Between Global and Category Mapping?

In TB.One, value mapping is essential for aligning your product data with the requirements of various channels.

TB.One offers two levels of value mapping: global and category-specific. Choosing the right approach ensures data accuracy and streamlines your workflow.

Find the value mapping menu under "Channels > [Your Channel] > Value mapping".

Global Mapping

•Map values simultaneously across multiple shop categories to save time and effort.

•Best suited for channels where the properties used in different categories have a high amount of overlap (e.g. fashion categories).

•Not available for marketplaces with a broad product range (e.g. fashion, electronics, and home & living)

•For channels that offer global mapping, the individual categories are hidden by default. To display them, click on the + icon in the line "-- global mapping --"

Category Mapping

•Map values specifically for individual categories.

•Overrides global mapping (when both styles of mapping are used). This is useful when certain categories require unique property values.

•Some marketplaces ONLY offer category-specific mapping.

Global or Category-Specific - Which Style of Mapping to Use?

We generally recommend using global mapping whenever possible. This significantly reduces the time required for value assignment, as you can apply values and properties across all categories at once. With global mapping, individual category assignments are typically unnecessary.

EXAMPLE:
When assigning the value “black” for the “color” property on global mapping, it is automatically assigned for all products that contain a black variant, regardless of the category (e.g. a black t-shirt, a black dress, black trousers, a black jacket).

Category-specific mapping provides the flexibility to override global assignments. If you need to export different information for a specific property in a particular category, you can assign a specific value at the category level. In such cases, the values defined at the category level will be used in the export.

EXAMPLE:

1.You have assigned your color value "Black" to the corresponding marketplace value "Black" for all categories.

2.You now want the value “Black” in the Jeans category to explicitly be exported as “Stone-washed black” rather than “Black.”

3.In the Jeans category, you assign "Stone-washed black" to your "Black" value. The global assignment is being overwritten in the Jeans category.

4.Jeans with the value “Black” will be exported as “Stone-washed black". Products in all other categories are still exported as "Black" due to the global mapping.

 

TIP:

•Assigning values at both the global and category levels for the same property can easily lead to mistakes when mappings change. To prevent inconsistencies, we recommend choosing one method (global or category) and using it consistently, if possible.

•Category-level assignments always take precedence over global assignments. Use category mapping only when you explicitly and intentionally need to export different information for a property in a specific category.