Setting up a ManoMano feed

UI update: The settings for Feeds and the Feeds steps have been redesigned! Some visuals and instructions may not be up-to-date.

Important: To ensure you have the latest fields in your ManoMano feed, click the 'Update Mapping' button in the feed settings. For more details about fields, refer to this section of this article.

For ManoMano, Channable offers the option to integrate your products with a Feed. In this article, will guide you through the different steps of creating a ManoMano feed.

Step 1: Setting up your ManoMano feed

Follow these steps to set up your ManoMano feed:

1. Navigate to [Your project] > Channels.

2. Click +Create channel.

3. Search for "ManoMano" and select 'ManoMano'.

4. Next, fill in your Feed name

5. Select your Target country from the dropdown.

6. Select the Type of market, which is the specific category or sector of the retail market for your products.

7. Click on Advanced settings to edit more settings for your feed.

8. Once you have completed your feed settings, click Continue.

Step 2: Categorization

Start by assigning your products to the appropriate categories. You can do this by:

• Using AI product categorization, so your items can be automatically matched to the most likely product category.

• Utilizing the generate categories feature to create categories based on your product data

• Manually creating and assigning new categories if needed

Step 3: Rules

Create different Rules to optimize your product data. Once you have created all the rules to adjust your product information, you just need to assign the fields in the Mappingstep.

Step 4: Mapping

ManoMano has unique requirements when it comes to mapping fields. In this section, we will explain how field mapping works specifically for ManoMano.

• Mandatory fields: These fields are required for all items and are marked with the label ‘Mandatory’ (in blue) in the Mapping step of the feed setup.

• Optional fields: These fields are presented as optional in the feed, but depending on the category of the product, they could be required.

• Category-specific fields: ManoMano has fields that are tied to specific product categories. Most of these fields are shown as optional in the feed, but they can become mandatory depending on the category.

• Mandatory ‘under certain conditions’ fields: These fields are only required in specific situations based on certain criteria or conditions.

Below, we will explain the Category-specific fields and Mandatory ‘under certain conditions’ fields to provide you with enough information to work with.

Category specific-fields

ManoMano has specific requirements based on product categories. While most of these fields appear as optional in the feed, they may become mandatory depending on the category. Due to technical limitations, this cannot be displayed directly in the feed.

To ensure accuracy, we strongly recommend regularly checking ManoMano Seller Central for any attribute-related errors. Additionally, reviewing the attribute requirements in ManoMano can provide valuable insight into what ManoMano expects for each category.

Mandatory 'Under certain conditions' fields:

Some fields in the ManoMano feed are not always marked as mandatory by default. These fields become required only under specific circumstances, depending on the information provided.

Examples:

• EAN: Generally required, but if you're unable to provide an EAN, both the manufacturer SKU and brand fields must be filled in to uniquely identify the product.

• Carrier and Shipping Time: These fields are mandatory only when you're not using a carrier grid.

• ParentSKU and Parent Title: Required if you're grouping products as variations.

These conditional fields ensure that the system has all the necessary data to process your products correctly based on the specific setup and data available.

List of mandatory and optional fields

Below, we outline the fields, their specifications, and the conditions under which they are required.

Important: The information provided in the table below is sourced directly from ManoMano and may slightly differ from the exact wording used in the Channable ManoMano feed. However, the details remain accurate and reflect the requirements for setting up your product feed correctly.

Type of field	Fields	Mandatory	Description
Product fields	sku	Yes	This is your seller SKU. It is only linked to your organization and not the market. The value must be unique for each product of your feed.
ean	Yes	This is the EAN-13 of your product, but you can also use UPC-12 or ITF-14 formats. Providing this information helps the ManoMano system accurately detect and link your product to the ManoMano catalog. The EAN is connected to the international market and is essential for product identification. You can associate multiple EANs with a single SKU by separating them with a hashtag ('#'). Although this field can be left empty if you provide the correct manufacturer SKU and brand, we strongly recommend including the EAN to speed up your time to market and improve the visibility of your product pages.
sku_manufacturer	Yes	This is the SKU of the manufacturer. This information is mandatory if you’re not able to provide an EAN. The association of this information with the brand (field “brand”) has to be unique for each product of your catalog.
brand	Yes	This is the brand of your product. We strongly recommend you to provide the registration name as value of this field. Additionally, avoid using terms such as “without brand” which could complicate and lengthen the creation of the product in ManoMano system. The association of this information with the sku manufacturer (field “sku_manufacturer”) has to be unique for each product of your catalog.
manufacturer	No	This is the name of the manufacturer. We recommend you to provide the registration name as the value of this field. Additionally, avoid using terms such as “without brand” which could complicate and lengthen the creation of the product in ManoMano system.
mm_category_id	Yes	This is the id of the targeted ManoMano category for your product. You can find the ManoMano category tree inside your Toolbox in the Catalogue section.
merchant_category	Yes	This is the breadcrumb based on your category tree where the product is associated in.
title	Yes	Title you want to display on the product page. Here are some recommendations: 1. Organize the information in the title by its importance. 2. Include the specific characteristics of your product (model, color, size, …). 3. Ensure readability and relevance! Avoid acronyms, unnecessary capital letters and special characters. 4. Separate words using a space rather than other characters (e.g.,a slash) to ensure they are understanable by search engines. 5. Create a title between 50 and 65 characters long (approximately 8 words).
description	No	Description of your product that will be displayed on the Product Page. Here are some recommendations: 1. Provide detailed and comprehensive information for a better conversion. 2. Include all technical attributes (color, weight, power, …) and advice on usage. It will strongly impact your conversion rate. 3. Incorporate keywords in paragraphs. 4. Use more familiar terminology. You can ideally use both if you want to be understood by all prospects but also by Google and ManoMano bots. 5. Ensure the text is at least 1000 characters long. 6. Use simple html tags, such as paragraphs and lists. 7. Avoid adding CSS style, as this may impact design and performance of the page without providing any additional benefits.
product_url	No	Valid URL of your product page.
image_1	Yes	URL of your product images that will be displayed on the product page. Images are an essential element in the promotion and conversion of your products. It is mandatory to provide us with at least one image url that the system can download to create the product. However, you have the possibility to provide up to 5 and we strongly recommend that you provide the most possible. According to our analysis, products with : 3 images have a 10% higher conversion rate compared to products with only one image 5 images have a 25% higher conversion rate compared to products with only one image Don't forget to allow our system to download them.
image_2	No
image_3	No
image_4	No
image_5	No
cross_sell_sku	No	You can specify several SKUs from your catalog that can be associated with your product in a cross-sell strategy. Add your targeted SKUs separated by an hashtag (example : 123_ABC#456_DEF#789_GHI). This link between your products will be processed by our algorithm to provide accurate product associations on the website.
Sample_SKU	No	You also have the possibility to indicate that you offer your potential customers a sample. To do so, you must create a specific product with a unique SKU and indicate the value "1" in this field. You will also have to propose a minimum price of 0.10 Euros in the "product_price_vat_inc" field. The value 0 will not be accepted by our system.
manufacturer_pdf	No	URL of your PDF document providing technical product information.
product_information_pdf	No	URL of your PDF document providing functional product information (in relation with the energy labelling).
repairability_index_pdf	No	URL of your PDF document providing how repairability index is calculated for your product.
product_instructions_pdf	No	URL of your PDF document providing notice of usage or installation.
safety_information_pdf	No	URL of your PDF document containing warning or safety information that must be affixed on the product, its packaging, or an accompanying document, in accordance with law, should be provided in a language that is easily understood by consumers.
refrigeration_devices_information_pdf	No	URL of your PDF document providing refrigeration devices information.
eu_energy_efficiency_class_url	No	URL of the image of the energy label of your product.
unit_count	Mandatory for ManoMano.de	Unit to consider for calculating the price per unit. The number provided must be a positive decimal.
unit_count_type	Mandatory for ManoMano.de	Unit type to take into consideration to calculate the price per unit. Check the accepted values in the Valid Values sheet of the document.
ParentSKU	No	A common identifier to all products that need to be grouped together, which must be distinct from the SKU. The individual SKUs can be selected from a dropdown menu.
parent_title	Mandatory if you send the field 'ParentSKU'	Parent title for child SKUs grouped using the field "ParentSKU". Must be completed if the "ParentSKU" field is used.
length	No	Indicate the length of your product using a decimal value (e.g., 2.59). Please use a dot (.) as the decimal separator.
length_unit	No	Please specify the units for the length field. Refer to the Valid Values sheet in the document for the accepted unit formats.
width	No	Indicate the width of your product using a decimal value (e.g., 2.59). Please use a dot (.) as the decimal separator.
width_unit	No	Specify the units for the width field. Please refer to the Valid Values sheet in the document for the accepted unit formats.
height	No	Please indicate the height of your product using a decimal value (for example, 2.59). Use a dot (.) as the decimal separator.
height_unit	No	Please specify the units for the height field. Refer to the Valid Values sheet in the document for the accepted unit formats.
weight	No	Please indicate the weight of your product as a decimal value (for example, 2.59). Use a dot (.) as the decimal separator.
weight_unit	No	Please specify the units for the weight field. Refer to the Valid Values sheet in the document for the accepted unit formats.
volume	No	Total volume of the product (units: L, etc.) Please use a dot (.) as a decimal separator.
volume_unit	No	Specify the units for the volume field. Refer to the Valid Values sheet in the document for accepted unit formats.
light_output	No	Product light output (units: lumens, lux, etc.) Please use a dot (.) as a decimal separator.
light_output_unit	No	Specify the units for the light_output field. Refer to the Valid Values sheet in the document for accepted unit formats.
power	No	Product power rating (units: W, etc.) Please use a dot (.) as a decimal separator.
power_unit	No	Specify the units for the power field. Refer to the Valid Values sheet in the document for accepted unit formats.
voltage	No	Product voltage (unit: V etc.) Please use a dot (.) as a decimal separator.
voltage_unit	No	Specify the units for the voltage field. Refer to the Valid Values sheet in the document for accepted unit formats.
battery_life	No	Product battery life (units: min, hr, etc.) Please use a dot (.) as a decimal separator.
battery_life_unit	No	Specify the units for the battery_life field. Refer to the Valid Values sheet in the document for accepted unit formats.
amperage	No	Product amperage (unit: A etc.) Please use a dot (.) as a decimal separator.
amperage_unit	No	Specify the units for the amperage field. Refer to the Valid Values sheet in the document for accepted unit formats.
rotational_speed	No	Rotational speed of product (unit: RPM etc.) Please use a dot (.) as a decimal separator.
rotational_speed_unit	No	Specify the units for the rotational_speed field. Refer to the Valid Values sheet in the document for accepted unit formats.
max._flow_rate	No	Maximum flow rate of the product (units: m³/min, L/hr, etc.). Please use a dot (.) as a decimal separator.
max._flow_rate_unit	No	Please specify the units for the max_flow_rate field. Refer to the Valid Values sheet in the document for the accepted unit formats.
noise_level	No	Product sound level (unit: decibels, etc.). Please use a dot (.) as the decimal separator.
noise_level_unit	No	Specify the units for the noise_level field. Refer to the Valid Values sheet in the document for accepted unit formats.
pressure	No	Maximum pressure rating (unit: bar etc.) Please use a dot (.) as a decimal separator.
pressure_unit	No	Specify the units for the pressure field. Refer to the Valid Values sheet in the document for accepted unit formats.
material	No	Product materials (values: wood, leather, steel, etc.)
colour	No	A list of colors according to the values specified below, separated by a hashtag '#' (for example, "blue#orange"). Please refer to the Valid Values sheet of the document for the accepted values.
finish	No	Product finish (values: chrome, smooth, velvet, etc.)
shape	No	Main shape of your products. Check the accepted values in the Valid Values sheet of the document.
ip_rating	No	Product Ingress Protection (IP) rating (values: IP15, IP16, IP17, etc.)
cap_fitting	No	Bulb base type (values: E11, E14, E27, etc.)
energy_efficiency_rating	No	Energy class of your product. Provide one of these values : A+++, A++, A+, A, B, C, D, E, F, G
size	No	Clothing size (values: S, M, L, etc.)
connection_type	No	For assembly (values: male, female)
pipe_thread_size	No	Pipe thread size imperial/metric (values: 1 1/2" (40x49), 1 1/4" (33x42), etc.)
working_width_/_diameter	No	Working diameter/width of product (units: cm, m, etc.) Please use a dot (.) as a decimal separator.
working_width_/_diameter_unit	No	Specify the units for the working_width_/_diameter field. Refer to the Valid Values sheet in the document for accepted unit formats.
disc_/_blade_diameter	No	Blade or disc diameter (units: cm, mm, etc.) Please use a dot (.) as a decimal separator.
disc_/_blade_diameter_unit	No	Specify the units for the disc_/_blade_diameter field. Refer to the Valid Values sheet in the document for accepted unit formats.
coverage	No	Maximum surface that the product can cover (units: m², etc.) Please use a dot (.) as a decimal separator.
coverage_unit	No	Specify the units for the coverage field. Refer to the Valid Values sheet in the document for accepted unit formats.
light_colour	No	Light colour emitted by the light source (values: cool, warm, red, etc.)
centre-to-centre_distance	No	Distance from the centre of one column to the centre of another column (e.g. tap distance) (units: mm, cm, etc.) Please use a dot (.) as a decimal separator.
centre-to-centre_distance_unit	No	Specify the units for the centre-to-centre_distance field. Refer to the Valid Values sheet in the document for accepted unit formats.
engine_capacity	No	Engine size (units: cc, m3, L, etc.) Please use a dot (.) as a decimal separator.
engine_capacity_unit	No	Specify the units for the engine_capacity field. Refer to the Valid Values sheet in the document for accepted unit formats.
number_of_seats	No	Total number of seats (units: seats, places, etc.) Please use a dot (.) as a decimal separator.
number_of_seats_unit	No	Specify the units for the number_of_seats field. Refer to the Valid Values sheet in the document for accepted unit formats.
power_source	No	Type of power supply (values: battery, mains, solar, etc.)
fixing_method	No	Method used to fit or install the product (values: screws, adhesive, freestanding, wall-hung, etc.)
maximum_load	No	Maximum weight that the product can sustain (units: kg, etc.) Please use a dot (.) as a decimal separator.
maximum_load_unit	No	Specify the units for the maximum_load field. Refer to the Valid Values sheet in the document for accepted unit formats.
power_supply	No	Type of power source used by the product (values: air-powered, electric, petrol, etc.)
style	No	Product style (values: chic, classic, industrial, etc.)
battery_technology	No	Type of battery technology (values: Li-ion, ni-CD, Ni-Mh, etc.)
number_of_batteries	No	It refers to the number of batteries sold with the product
number_of_batteries_unit	No	Specify the units for the number_of_batteries field. Refer to the Valid Values sheet in the document for accepted unit formats.
range	No	Maximum range of product (units: cm, m, etc.) Please use a dot (.) as a decimal separator.
range_unit	No	Specify the units for the range field. Refer to the Valid Values sheet in the document for accepted unit formats.
angle,_tilt	No	Degree measure of an angle, tilt of a product, etc. (unit: degree etc.) Please use a dot (.) as a decimal separator.
angle,_tilt_unit	No	Specify the units for the angle,_tilt field. Refer to the Valid Values sheet in the document for accepted unit formats.
pcs_per_pack	No	Indicate the number of units that the product contain. For example if the product to be sold is a pack of chlorine tablets, indicate the number of tablets the product contains.
pcs_per_pack_unit	No	Specify the units for the pcs_per_pack field. Refer to the Valid Values sheet in the document for accepted unit formats.
origin	No	Country where the product had been manufactured. Check the accepted values in the Valid Values sheet of the document.
warranty	No	Warranty in year provided by the manufacturer. It does not concern the minimum legal warranty
warranty_unit	No	Specify the units for the warranty field. Refer to the Valid Values sheet in the document for accepted unit formats.
availability_of_spare_parts	No	Number of years that spare parts will be available. The expected value is a positive integer or zero (example: 15)
availability_of_spare_parts_unit	No	Specify the units for the availability_of_spare_parts field. Refer to the Valid Values sheet in the document for accepted unit formats.
volume_in_litres	No	Product volume (for paint, sand, gravel, wood pellets, etc.) (unit: L etc.) Please use a dot (.) as a decimal separator.
volume_in_litres_unit	No	Specify the units for the volume_in_litres field. Refer to the Valid Values sheet in the document for accepted unit formats.
tank/collection_capacity	No	Tank or collection capacity (for vacuum cleaner dust canister, lawnmower grass box, etc.) (units: L, m3, etc.) Please use a dot (.) as a decimal separator.
tank/collection_capacity_unit	No	Specify the units for the tank/collection_capacity field. Refer to the Valid Values sheet in the document for accepted unit formats.
indoor_/_outdoor	No	Product suitability for indoor/outdoor use (values: indoor, outdoor)
type_of_electrical_installation	No	Type of installation of electrical product (values: screws, recessed, hanging, etc.)
environmental_certification	No	Environmental certifications associated with your products. You can communicate the list of certifications according to the accepted values separated by a hashtag '#' (example: “cekal#ecocert”). Check the accepted values in the Valid Values sheet of the document.
type_of_power_connector	No	Type of power connector (values: audio, coaxial, ethernet, etc.)
reparability_index	No	repairability_index value. This index informs via a note from 1 to 10 on the more or less repairability of the product you sell.
reparability_index_unit	No	Specify the units for the reparability_index field. Refer to the Valid Values sheet in the document for accepted unit formats.
paint_finish	No	Paint finish (values: matte, gloss, velvet, etc.)
colour_name	No	Mandatory information to broadcast the color palette. It represents the name of the product color.
colour_code	No	Colour code (hexadecimal code) (ex : #394392)
battery_capacity	No	Total energy that a battery can store (units: Ah, etc.) Please use a dot (.) as a decimal separator.
battery_capacity_unit	No	Specify the units for the battery_capacity field. Refer to the Valid Values sheet in the document for accepted unit formats.
max._energy_efficiency_rating	No	Maximum energy class of your product category. Provide one of these values : A+++, A++, A+, A, B, C, D, E, F, G.
min._energy_efficiency_rating	No	Minimum energy class of your product category. Provide one of these values : A+++, A++, A+, A, B, C, D, E, F, G.
main_material	No	Main material used in the manufacture of the product. Check the accepted values in the Valid Values sheet of the document.
%_main_material	No	Percentage of the main material used in the manufacture of the product. Indicate a numerical value between 0 and 100.
%_main_material_unit	No	Specify the units for the %_main_material field. Refer to the Valid Values sheet in the document for accepted unit formats.
accessories_included	No	List of accessories included with your main product. Provide the name of the accessories separated by a hashtag. (example : ACCESSORIE_1#ACCESSORIE_2#ACCESSORIE_3)
shoe_upper_material	No	In the case of shoes, please indicate whether the upper part of the shoe is made of leather, coated leather, textile, or other materials. If no single material accounts for at least 80% of the product, please specify the two main materials used.
shoe_lining_material	No	In the case of shoes, please specify whether the lining material is made of leather, coated leather, textile, or other materials. If no single material makes up at least 80% of the product, the label should indicate the two main materials used.
shoe_outsole_material	No	In the case of shoes, please indicate whether the outer material of the shoe is made of leather, coated leather, textile, or other materials. If no single material constitutes at least 80% of the product, the label should indicate the two main materials used.
opening_of_the_blades	No
opening_of_the_blades_unit	No	Specify the units for the opening_of_the_blades field. Refer to the Valid Values sheet in the document for accepted unit formats.
folding_thickness	No
folding_thickness_unit	No	Specify the units for the folding_thickness field. Refer to the Valid Values sheet in the document for accepted unit formats.
folding_angle	No
folding_angle_unit	No	Specify the units for the folding_angle field. Refer to the Valid Values sheet in the document for accepted unit formats.
box_length	No
box_length_unit	No	Specify the units for the box_length field. Refer to the Valid Values sheet in the document for accepted unit formats.
box_width	No
box_width_unit	No	Specify the units for the box_width field. Refer to the Valid Values sheet in the document for accepted unit formats.
box_height	No
box_height_unit	No	Specify the units for the box_height field. Refer to the Valid Values sheet in the document for accepted unit formats.
textile_composition	No	Indicate the textile composition.
energy_consumption	No	In the case of products that use electrical energy for their normal operation, indicate their energy consumption in kW per hour.
energy_consumption_unit	No	Specify the units for the energy_consumption field. Refer to the Valid Values sheet in the document for accepted unit formats.
Offer fields	product_price_vat_inc	Yes	The price of your product, including VAT, is mandatory if you wish to sell your product on ManoMano. We recommend using a dot as the decimal separator. A value less than or equal to zero will result in an error, and the product will not be available for sale until the issue is corrected.
sales	No	Put the value '1' in order to benefit from the promotion button on the ManoMano website. Your product will also have to be included in one of our commercial operation.
retail_price_vat_inc	Yes	Please indicate a crossed-out price in this field when you wish to apply a price reduction to your product. We remind you that, according to EU regulations, the previous price must be the lowest price applied by the trader during a period of no less than 30 days prior to the implementation of the price reduction. The value of this price must be higher than the value in the "product_price_vat_inc" field in order for it to be considered by our system.
eco_participation	No	The amount of the eco-participation is mandatory to sell in France. For this, you just have to indicate the amount in this field. We advise you to use the point as a decimal separator.
min_quantity	Yes	Indicate a minimum quantity to buy.
increment	Yes	Indicate the increment to take into consideration to manage additional quantities. This value must however be less than or equal to the value in the "min_quantity" field.
quantity_lower_bound_1	No	The minimum quantity expected to benefit from a first price reduction (quantity_price_1).
quantity_price_1	No	The minimum quantity expected to benefit from a first price reduction (quantity_price_1).
quantity_lower_bound_2	No	The minimum quantity expected to benefit from a second price reduction (quantity_price_2).
quantity_price_2	No	Percentage of price reduction between 0 and 100 if customer is purchasing at least the quantity indicated in quantity_lower_bound_2. For example, if quantity_lower_bound_2 contains the value 20 and quantity_price_2 contains the value 10, it means that the customer will have a price reduction of 10% from the product_price_vat_included if he is buying at least 20 quantities of the product.
quantity_lower_bound_3	No	The minimum quantity expected to benefit from a third price reduction (quantity_price_3).
quantity_price_3	No	Percentage of price reduction between 0 and 100 if customer is purchasing at least the quantity indicated in quantity_lower_bound_3. For example, if quantity_lower_bound_3 contains the value 50 and quantity_price_3 contains the value 15, it means that the customer will have a price reduction of 15% from the product_price_vat_included if he is buying at least 50 quantities of the product.
quantity	Yes	Quantity you want to sell on ManoMano.
use_grid	Yes	If to be used, enter 1. This activates the transport matrix, and 0 if you don't want to.
carrier	Mandatory if you do not send the field 'use_grid'	If you are not using a carrier grid, enter the name of your carrier in this field
shipping_time	Mandatory if you do not send the field 'use_grid'	The shipping time for flat shipping rate in number of days. Must be a number or a range separated by #. (1 to 3 days = 1#3)
shipping_price_vat_inc	Mandatory if you do not send the field 'use_grid'	If you are not using a carrier grid, enter your shipping price in this field. If you offer free shipping, you can enter a value of zero or leave the field blank. The system will consider the delivery as free.
shipping_price_supplement_vat_inc	No	If you are not using a carrier grid and you want to add an additional amount when a customer buys a second product from you, you can indicate the amount of the increment in the "shipping_price_supplement_vat_inc" field. The system will calculate the shipping price according to this logic: 1. It will select the most expensive shipping price between the two products 2. It will add the increment amount to the selected delivery price.
carrier_grid_1 carrier_grid_2 carrier_grid_3 carrier_grid_4 carrier_grid_5 carrier_grid_6	Yes if use_grid is 1	If you are using carrier grids, indicate the name of the carrier at least for one of these fields : carrier_grid_1, carrier_grid_2, carrier_grid_3, carrier_grid_4, carrier_grid_5, carrier_grid_6.
shipping_time_carrier_grid_1 shipping_time_carrier_grid_2 shipping_time_carrier_grid_3 shipping_time_carrier_grid_4 shipping_time_carrier_grid_5 shipping_time_carrier_grid_6	Mandatory if you send the field 'use_grid'	If you are using carrier grids, Indicate your delivery times at least for one of these fields : shipping_time_carrier_grid_1, shipping_time_carrier_grid_2, shipping_time_carrier_grid_3, shipping_time_carrier_grid_4, shipping_time_carrier_grid_5, shipping_time_carrier_grid_6. You must propose a time interval between your minimum and maximum time. To do so, you just need to fill in these values using the hashtag as a separator: [TIME_MIN]#[TIME_MAX] . For example, if your delivery time is between 3 and 5 days, you must enter the value: 3#5
DisplayWeight	Mandatory if you send the field 'use_grid'	If you are using carrier grids and you have price range based on the weight, you have to indicate the weight of your product in kg.

Step 5: Quality & Preview

In the Quality step, you can review any issues Channable detects that could cause problems based on the feed’s specifications.

Keep in mind that you may see errors related to mandatory fields. As mentioned earlier, some of these fields are conditionally mandatory, so not all flagged errors need to be addressed.

Once the feed setup is complete, you can proceed to the Preview step to review your feed. Here, you’ll also find the URL you need to integrate into your ManoMano account.

Additional requirements and information

This section outlines crucial considerations for managing your feed and product listings on ManoMano. From processing frequency to image requirements and how to handle discontinued products, it's essential to keep these details in mind for smooth integration.

Important notes

1. Discontinuing products: Each time you run the feed, the current catalog will not be cancelled but overwritten. However, discontinued products will still appear in the catalog, even though they will be deactivated and listed as offline. To avoid this, send the products with stock set to zero before excluding them from the feed.

2. Matching existing catalog: It’s possible to match a ManoMano feed with an existing catalog, provided that for each item, the new feed contains the same values for the EAN, SKU_manufacturer and brand

Processing frequency

ManoMano processes updates less frequently than other marketplaces, so it’s important to be aware of the timing for your changes to be reflected in your account:

• Offer updates (price/stock): Every 3-4 hours

• Content updates (product data): Once a day

• Image updates: Every 7 days, with up to 10 days of additional processing time

Be mindful of these intervals when making modifications to your feed, as they will impact when you see the changes in your ManoMano account and product listings.

Image requirements

When sending your catalog to ManoMano, follow these specific guidelines for images:

• Main image requirements:

  • Drawings or illustrations of the product are not permitted.

  • No additional or confusing objects should appear in the image.

  • The image must be sharp, well-lit, and show realistic colors with smooth edges.

  • The complete product must be visible within the frame.

  • The background must be pure white (RGB 255, 255, 255).

  • No additional text, graphics, or inserts should be present.

• Additional image requirements (image_2, image_3, image_4, and image_5):

  • The image must belong to the product being sold.

  • It should be sharp, professionally lit, and show realistic colors and smooth edges.

  • You may include other products or objects to demonstrate the product’s use or scale.

  • The product and accessories should fill at least 85% of the image frame.

  • Cropped or close-up images are allowed.

  • Backgrounds and environments can be included.

  • Text and demonstrative graphics are allowed.

Products that don’t meet these criteria may face reduced visibility or even suspension on ManoMano.

If you encounter any issues or need clarification, feel free to reach out to ManoMano for questions about product requirements or to our technical support team.