Third party catalog feeds
A merchant or product catalog feed contains a list of products for retailers to upload and manage on different platforms. This feed typically includes attributes like product ID, title, description, price, and other relevant details. Third-party feeds can be used to integrate product catalogs into your MCM platform by mapping them to Moloco's catalog specifications.
Google Merchant feed
For the official Google Merchant feed specification, please refer to https://support.google.com/merchants/answer/7052112?hl=en
Recommendations
We recommend using your Google Merchant feed with our MSPI Multiple Sellers per Item catalog specification to reduce the need for complex feed file customization. You can simply create an additional ‘Seller catalog feed’ without changing your existing Google Merchant feed.
For more information on selecting the correct MCM catalog format, please see: Catalog Feed Specifications
Requirements
MSPI (Multiple Sellers Per Item)(Recommended)
When using MSPI, the original Google Merchant feed file remains unchanged; you should create an additional file called ‘Seller catalog feed’ to comply with the MSPI Catalog feed specification.
SSPI (Single Seller Per Item)(Not Recommended)
We strongly advise using our MSPI catalog specification instead of SSPI (Single Seller Per Item). MSPI allows you to use your Google Merchant feed file as is, while SSPI requires transformation to append new columns and populate them with the appropriate catalog information.
When converting the Google Merchant feed to the SSPI Catalog feed specification, if the
sale_price
field is empty or null,price
will be mapped tosale_price
.The
price
andsale_price
fields in the Google Merchant feed file are formatted as a numeric value followed by the currency code (e.g., "15.00 USD"). Only the numeric value is stored when using SSPI.
Currency
The default currency is set at the platform level during onboarding and should match the currency stored in the Google Merchant feed. You must convert all price fields to match the currency set on your platform, do not mix currencies.
Transformation Rules
The Google Merchant feed is automatically transformed into the canonical format listed in the tables below. The transformation rule indicates how Moloco transforms fields found in the Google Merchant feed into our specification.
Google Merchant Feed Mappings
Field | Type | Validation | Canonical Format Mapping |
---|---|---|---|
id | String | Max 50 characters | id |
title | String | Max 200 characters | title |
image_link | String | Max 200 characters | image_link |
seller_id | String | Max 200 characters | seller_id seller_title |
seller_id field requirements
The
seller_id
is required for Single Seller Per Item (SSPI) Catalog Feeds. Theseller_id
is a virtual column which is not supported by the Google Merchant feed format; you must include this field to meet the SSPI specification.The
seller_id
is not required for Multiple Sellers per Item (MSPI) Catalog Feeds.
Field | Type | Validation | Canonical Format Mapping |
---|---|---|---|
price | Float | Cannot be negative | price sale_price (Note: sale_price is used if price is not provided) |
sale_price | Float | Cannot be negative | sale_price |
currency requirements
Price fields such as
price
andsale_price
found in the Google Merchant feed are represented as Numeric + ISO 4217. Moloco uses the numeric section of this field along with the currency code set at the platform level. You must ensure the currency used in the catalog feed matches the currency set on the platform.
Field | Type | Validation | Canonical Format Mapping | Transformation Rule |
---|---|---|---|---|
product_type | String | Max 750 characters | category For more information please see Google Merchant product type documentation | product_type is used to fill the internal category field.If product_type is not provided, Moloco will fallback to google_product_category to fill the internal category field. |
google_product_category | String | Max 750 characters | google_product_category | Moloco will accept both the full path of the product category or the numerical category ID. If product_type is not provided, google_product_category will be used instead. In this case, we highly recommend using the full category path which provides better ML performance when compared to the numerical ID |
brand | String | Max 70 characters | brand | |
gtin | String | Max 200 characters | gtin | |
condition | String | ENUM: new, refurbished, used | condition | ENUM:new, refurbished, used |
adult | String | ENUM: Yes, No | adult | YES = Y NO = N |
description | String | Max 5000 characters | description | |
is_bundle | String | ENUM: Yes, No | is_bundle | YES = Y NO = N |
age_group | String | ENUM: newborn, infant, toddler, kids, adult | age_group | ENUM:newborn, infant, toddler, kids, teen, adult, all |
color | String | Max 100 alphanumeric characters | color | |
gender | String | ENUM: male, female, unisex | gender | ENUM:male, female, unisex |
material | String | Max 200 characters | material | |
pattern | String | Max 100 characters | pattern | |
size | String | Max 100 characters | size | |
item_group_id | String | Max 50 alphanumeric characters | item_group_id | |
availability | String | ENUM: In_stock, out_of_stock, preorder, backorder | availability | ENUM:In_stock, out_of_stock, preorder, backorder |
link | String | Max 2000 Characters | link | |
mobile_link | String | Max 2000 characters | mobile_link | |
additional_image_link | String | Max 2000 characters | additional_image_link | |
custom_label_0 | String | Max 200 characters | custom_label_0 | |
custom_label_1 | String | Max 200 characters | custom_label_1 | |
custom_label_2 | String | Max 200 characters | custom_label_2 | |
custom_label_3 | String | Max 200 characters | custom_label_3 | |
custom_label_4 | String | Max 200 characters | custom_label_4 |
Naver EP
For the official Naver EP feed specification, please refer to: https://join.shopping.naver.com/misc/download/ep_guide.nhn
Limitations
The Naver EP feed file supports conversion only to the SSPI (Single Seller Per Item) Catalog specification. MSPI (Multiple Sellers per Item) is not supported.
For more information on selecting the correct MCM catalog format, please see: Catalog Feed Specifications
Requirements
When converting the Naver EP feed to the SSPI Catalog feed specification, please note the following field mappings:
normal_price
will be mapped toprice
.
price_pc
will be mapped tosale_price
.
Note: If normal_price
is empty / null, price_pc
will also be mapped to price
.
Shipping Fields
When using the
shipping
field a value of-1
indicates pay on delivery, which is not unsupported by Moloco. If theshipping
field is set to-1
the field will be converted into an empty string in the SSPI catalog feed.Positive numerical values will be converted and used for the
shipping_charge
. Do not include any negative values.
Currency
The default currency is set at the platform level during onboarding and should match the currency stored in the Naver EP feed file. You must convert all price fields to match the currency set on your platform, do not mix currencies.
Transformation Rules
The Naver EP feed is automatically transformed into the canonical format listed in the tables below. The transformation rule indicates how Moloco transforms fields found in the Naver EP feed into our specification.
Naver EP Catalog Mappings
Field | Type | Validation | Canonical Format Mapping | Transformation Rule |
---|---|---|---|---|
id | String | id | ||
title | String | title | ||
image_link | String | image_link | ||
seller_id | String | seller_id seller_title | ||
normal_price | Float | price | ||
price_pc | Float | sale_price price (Note: normal_price is used if price is not provided) | ||
category_name1 | String | category (first level in the category) | See notes below | |
category_name2 | String | category (second level in the category) | See notes below | |
category_name3 | String | category (third level in the category) | See notes below | |
category_name4 | String | category (fourth level in the category) | See notes below |
category_name# transformation rules
category_name# fields will be transformed internally into a hierarchical structure with the category_name# fields separated with a greater than sign
>
as follows:
category_name1>category_name2>category_name3>category_name4
Field | Type | Validation | Canonical Format Mapping | Transformation Rule |
---|---|---|---|---|
review_count | Int | review_count | ||
brand | String | brand | ||
adult | String | adult | ||
update_time | String | updated_time | ||
link | String | link | ||
mobile_link | String | mobile_link | ||
add_image_link | String | additional_image_link | ||
shipping | Float | shipping_charge | -1 represents pay on delivery. Moloco does not support this feature, if the shipping field is set to -1 the field will be converted into null (empty) string. Positive numerical values will be converted and used for the shipping_charge . Do not include negative values. | |
point | String | reward_point | ||
gender | String | ENUM: 남자 여자 남녀공용 | gender | 남자 = male 여자 = female 남녀공용 = unisex |
group_id | String | item_group_id | ||
condition | String | ENUM: 신상품 중고 | condition | 신상품 = new 중고 = used |
age_group | String | ENUM: 유아 아동 청소년 성인 | age_group | 유아 = toddler 아동 = kids 청소년 = teen 성인 = adult |
class | String | class |
Updated 23 days ago