- Category mappings remember which marketplace category a catalog category goes to. You pick them in the listing wizard.
- Attribute mapping rules fill a marketplace parameter from a fixed value or from a field of the product.
Choose what you are working on
The two controls at the top of the page decide what the page lists, and what a new mapping or rule applies to:- The account list: All accounts (tenant-wide), or one marketplace account.
- The Filter by marketplace category id… box: empty, or one marketplace category ID. It applies when you leave the box. It affects only the rules.
Category mappings
A category mapping links one catalog category to one marketplace category. The list shows each mapping’s display name and its Marketplace category id, but not the catalog category or the account. With All accounts (tenant-wide) selected, it shows every mapping; pick an account to see only that account’s mappings.Save a mapping from the listing wizard
The simplest way to add a mapping is from the listing wizard, where Omnilinker fills in the marketplace category ID for you.1
Open a listing without a match
Open the listing in the wizard and go to the Category step. The product must have a category in your catalog.
2
Choose the category
Under Browse categories, click through to the final category. It appears as Selected category.
3
Save the mapping
Tick Remember this mapping for this catalog category and click Save mapping. Omnilinker says “Mapping saved.”
Add a mapping on this page
1
Choose the scope
In the account control, pick the account, or All accounts (tenant-wide).
2
Open the form
Under Category mappings, click Add mapping. The New category mapping dialog opens.
3
Pick the catalog category
Type in Catalog category and click the category in the results, shown with its full path. The dialog shows
“Selected: ” followed by the path.
4
Enter the marketplace category
- Marketplace category id: the marketplace’s ID of the category, up to 64 characters. Required.
- Display name: how the mapping appears in lists, up to 256 characters. Without it, the list shows the ID.
5
Save
Click Save.
How category mappings are used
In the wizard’s Category step, a listing without a product match shows Saved mappings: every mapping saved for the listing’s account, by display name, whatever catalog category it was saved for. Omnilinker does not pick the one for the product’s catalog category; you click the one you want, and the listing gets that category. Mappings are not applied anywhere else. New listings and the worksheet do not pick a category from them. Mappings saved for all accounts are not offered in the wizard either, so at the moment nothing uses them. On Allegro, a listing matched to an Allegro product takes the category from the match instead.Attribute mapping rules
A rule fills one marketplace parameter. Rules for the same parameter form a fallback chain: Omnilinker tries them from the top and uses the first rule that gives a value.Add a rule
1
Choose the scope
Pick the account, or All accounts (tenant-wide), and type the marketplace category ID in Filter by marketplace
category id… if the rule is for one category only. Leave the box empty for a rule that applies in every category.
2
Open the form
Under Attribute mapping rules, click Add rule. The New mapping rule dialog opens.
3
Name the parameter
Enter the marketplace’s parameter ID in Target parameter id, up to 64 characters. Required, and fixed once saved.
4
Choose where the value comes from
Pick the Rule type and fill in its fields; see Rule types.
5
Save
Click Save. A new rule goes to the end of its parameter’s chain.
Rule types
Source field takes one of these product fields. Capitals do not matter.
Any other field name gives no value.
Value translation table (optional) turns product values into marketplace values. Click Add row and fill in
From (the product’s value) and To (the marketplace’s value). With a table, a value is used only when it matches a
From exactly, capitals included; a value with no row gives nothing, and the next rule in the chain is tried. Without
a table, the product’s value is used as it is.
Multi-value separator splits the value into several values for a parameter that accepts more than one. The default
is
|, and it can be up to 8 characters.
A parameter with a list of choices needs the marketplace’s ID of the value, not its label. For example, Allegro’s
condition parameter has the ID
11323, with 11323_1 for New and 11323_2 for Used. Use the translation
table to turn your own values into those IDs. Omnilinker does not show parameter or value IDs; take them from the
marketplace.The list of rules
Rules are grouped into chains, each headed by its parameter ID. A chain holds the rules for one parameter at one scope, so the same parameter ID can head more than one chain, for example one for all accounts and one for an account. Each rule shows its type and its value or source field.- The arrows move a rule up or down its chain.
- The pencil opens Edit mapping rule. Everything but Target parameter id can be changed.
- The bin deletes the rule after you confirm “Delete this mapping rule?”.
Which rules apply to a listing
A listing uses every rule whose account is the listing’s account or all accounts, and whose category is the listing’s category or every category. When the listing picks up rules from more than one chain for the same parameter, for example an all-accounts rule and an account rule, Omnilinker does not guarantee which chain it tries first. Keep one chain per parameter where you can.When rules fill in values
Rules fill parameters at two moments:- New listings: when a listing is matched to an Allegro product, Omnilinker fills its parameters from the rules.
- The wizard’s Parameters step: when a listing has no parameter values yet, the step fills them from the rules.
Troubleshooting
“A tenant-wide category mapping already exists for this catalog category.”
“A tenant-wide category mapping already exists for this catalog category.”
The catalog category already has a mapping for all accounts. Edit that mapping, or add one for a single account.
“The mapping rule is invalid: …”
“The mapping rule is invalid: …”
The rule could not be saved. The text after the colon says why, for example a translation table Omnilinker cannot
read. Check the rule’s fields and save again.
A rule does not fill the parameter
A rule does not fill the parameter
Check that Target parameter id is the marketplace’s ID of the parameter, that the rule’s account and category
cover the listing, and that the product has a value in the source field. With a translation table, the product’s value
must match a From exactly. A listing that already has values is not filled again; see
When rules fill in values.
The marketplace rejects a value the rule filled in
The marketplace rejects a value the rule filled in
For a parameter with a list of choices, the value must be the marketplace’s value ID. Add a translation table that
turns your values into IDs.
My mapping does not appear under Saved mappings in the wizard
My mapping does not appear under Saved mappings in the wizard
The wizard offers only mappings saved for the listing’s account. Mappings for all accounts are not offered, and
a matched Allegro listing shows no Saved mappings at all, because it takes its category from the match.
Permissions
Create listings
Create drafts, complete them and publish.
Listing templates
Build the description from product data and parameters.
Categories in the catalog
Organize the catalog categories you map.
Manage listings
Follow listings once they are published.