Every channel attachment has its own set of mappings — rows that connect a source field to a destination field, with an optional chain of transformation rules applied in between. Mappings are what turn raw source data into a clean canonical feed, and a canonical feed into the exact shape a destination expects.
from / to / transform
Each mapping row has three parts:
-
from— the source field. On an input channel this is the detected source column; on an output channel this is the canonical field. -
to— the destination field. On an input channel this is the canonical field it fills; on an output channel this is the attribute name the destination expects. -
transform— an optional, pipe-separated chain of rules applied to the value in order. See the transformation rule reference.
Default mappings
You rarely start from a blank mapping table. For an input channel, Product Feed Master pre-fills one row per detected source column, guessing a canonical target where the name matches. For an output channel, it pre-fills one row per canonical field, defaulting the destination name to the Google Merchant Center spec name. You only need to adjust the rows that need to be different.
Saving mappings
Saving a channel's mapping table replaces its full set of mapping rows for that attachment. Rows with an empty
from or
to are dropped, so a blank
row is a safe way to skip a field.