On this page
Before you start
METRO makro checks your content inside e-tailize before anything is sent. The check reads the METRO category definition of the category you mapped, so that category decides which fields are mandatory and which values it accepts. A message about a field is about your mapping or your product data, not about your METRO seller account.
You need a METRO makro connection, a PIM tab mapped to a METRO category, and validated products. Content goes first: "List content" puts the product in the METRO catalogue, "List offers" attaches your offer to it.
Steps
- Open the "Listing" page and pick the tile of your METRO makro connection.
- Select the products you want to send and click "List content".
- Open the panel "Offer response" above the grid when the run comes back with issues. It holds the columns "Ean", "Message", "Name" and "Value".
- Read the first row, which names the kind of problem, and then the rows under it, which name the product and the field.
- Correct each field from the "Name" column, in the mapping of the METRO category or on the product itself.
- Save the product with "Save & close" and let it validate again; a corrected product has to come back green before it can be listed.
- Click "List content" again for the same products.
- Click "List offers" once a content run comes back without violations.
What happens next
A submission that fails the check inside e-tailize opens with "Listing content does not comply with category requirements. Please update the mapping and try again!". Nothing reached METRO for those products, and the rows under that line are the fields to correct.
Content that passes goes to METRO makro as an upload. If METRO refuses something, its own report comes back per product: the EAN, the column, the message and the value it received.
The upload can also land on a hold: "Listing has been reserved for a manual review by MetroMakro Product Data Team. Please check back later by lising same content again!". It is a wait state, not a data error: METRO looks at the listing by hand. List the same content again later to see where the review stands.
Common problems
A missing mandatory value, for example "Field value 'Brand' is required for this product". The category marks that field mandatory and your product delivers nothing for it. Map a PIM field to it or fill the value on the product, then validate and list again.
A value outside the accepted list, for example "Values provided within 'Blue' does not comply with the expected list: 'Black,White'". The message ends with the values that are accepted, and the mapping page shows the same set under "Valid values for this field are:".
A value of the wrong type, for example "The type of 'twenty' does not comply with the expected type: 'Integer'". The mapped field delivers text where the category asks for a number, a true or false value, or a link. Two more of this family cover the length of a value and the number of values.
"No report file was generated for this product content upload!" METRO returned no report for the upload, so there is nothing on your products to correct. Push once more, and ask us in the chat when it keeps coming back.
FAQ
Is the manual review message something I did wrong?
No. It is a wait state. Your upload reached METRO and their Product Data Team looks at it by hand. Nothing in your data has to change, and e-tailize cannot skip that review.
Where do I see which values a field accepts?
On the mapping page of the METRO category, in the hint of the field: "Valid values for this field are:". The refusal message repeats the same set.
Our images from one METRO market show up on another. Why?
METRO takes the attributes that are not language bound, images among them, from the last successful upload and applies them to all its markets. Offers and orders stay with one connection: "Selecting a destination means that this connection will only process offers & orders generated in that destination."
Related
Was this useful?