4.1 SSPI Catalog feed specification
Note
There are two options for SSPI (Single Seller Per Item) Catalog Feeds, Common and Delivery. The Common Catalog Feed is designed for general e-commerce usage, while the Delivery Catalog Feed is tailored for food and grocery delivery companies.
Common catalog feed
The Common Catalog Feed guide is designed for commerce and marketplace platforms. For food and restaurant delivery, see the Delivery catalog feed guide.
This guide will help you format your catalog feed information to optimize your Retail Media Business, including sponsored ads and recommendations powered by Moloco. By submitting your item data in the correct format, you can ensure that Moloco effectively matches your products with the right queries, maximizing the success of your ads. Whether you're a large-scale marketplace or a growing commerce platform, this guide will provide the essential steps to create successful ads and drive your business forward.
Required fields
The following fields are required for each item in your catalog. If any required fields are missing or formatted incorrectly, items may not upload to your catalog and may be unavailable for ad serving.
| Field | Data Type | Note |
|---|---|---|
| id | String (up to 50 characters) | A unique identifier for the item Example: 039842 |
| title | String (up to 200 characters) | A specific, relevant title for the item Example: Brown |
| image_link | String (up to 2,000 characters) | The URL of the main image of the item. It should begin with https and follow RFC 2396 or RFC 1738.Example: https://www.molocostore.com/100/bag.png |
| seller_id | String (up to 50 characters) | A unique seller/vendor ID. It is an Ad account ID for ad servicing & campaign management. Example: 38840029 |
| seller_title | String (up to 200 characters) | Name of seller/vendor. It is used as an Ad account title for ad servicing & campaign management. Example: Moloco store |
| price | Number (up to 25 characters) | Item unit price Format: Decimal number with a period (.) as the decimal point. Up to two decimal places are supported. KRW and JPY: Must be entered as whole numbers (integers). Including decimals for these currencies will cause the feed to be rejected. Purpose: This price will be used for: - Selecting items within a specific price range for ads. - Ranking items based on their potential sales value in advertising. Missing Price: If the price field is left blank, your item may not be shown in ads. Examples: USD or EUR: 3.25 KRW or JPY: 3000 (no decimals allowed) |
| sale_price | Number (up to 25 characters) | Item unit price after discounts. If the item is not discounted, set this equal to the ‘price’ value. The format is same as that of price field. |
| category | String (up to 750 characters) | Category of the product. Choose the most granular categories that describe the item. Use > as a delimiter among depths and use; as a delimiter among multiple categories. Include the full path of the categories.Examples: Women>Clothing>T-shirts>V-neckCoffee & Tea;BakeryMen>Shoes>Running;Men>Shoes>Athletic>Track & Field |
Recommended fields
The following fields are recommended to boost ad performance or filter out undesirable results.
| Field | Data Type | Note |
|---|---|---|
| availability | String | The current availability of the item. It must be one of the following:in_stockout_of_stockpreorderbackorder |
| rating | Number (up to 4 characters) | The rating of the product. Use a scale of 5 or 10. Round it to one decimal place. Always use a period ( .) as the decimal point.Example: 4.7 |
| review_count | Number (up to 20 characters) | The number of product reviews (purchase reviews) Example: 3850 |
| brand | String (up to 70 characters) | The brand name Example: Moloco |
| brand_id | String (up to 50 characters) | The brand id Example: Moloco or 1AB234 |
| location | String (up to 750 characters) | Locations where the product is eligible to sell. Provide the most specific product location possible from the list. Use > as a delimiter among depths.Use ; as a delimiter among multiple locations.Include the exact locations. Include the full path of the location. Example: CA>Redwoodcity;CA>MenloparkSeoul>Gangnamgu>Yeoksamdong |
| adult | String | Whether the item is not allowed for minors or contains adult content. It must be one of the following:YN |
| created_time | String (up to 25 characters) | Created time of the item information. The format should follow ISO 8601, such as the following: YYYY-MM-DDThh:mm [+hhmm]YYYY-MM-DDThh:mmZExample: 2023-02-24T11:07+0100 |
| updated_time | String (up to 25 characters) | Last updated time of the item information. The format should follow ISO 8601, such as the following: YYYY-MM-DDThh:mm [+hhmm]YYYY-MM-DDThh:mmZExample: 2023-02-24T11:07+0100 |
Optional fields
You can also include many optional fields to share more item information with customers or control how items are displayed.
| Field | Data Type | Note |
|---|---|---|
| description | String (up to 5,000 characters) | A short, relevant description of the item. Example: Lightweight fabric and a relaxed cut. A comfortable jacket that slips on like a shirt. |
| link | String (up to 1,024 characters) | The link to your business’s website lets people learn more about or buy the item. It should start with https.It should formatted with RFC 2396 or RFC 1738. Example: https://www.molocostore.com/products/100 |
| mobile_link | String (up to 1,024 characters) | The mobile link to your business’s website lets people learn more about or buy the item. It should start with https.It should formatted with RFC 2396 or RFC 1738. Example: https://m.molocostore.com/products/100 |
| additional_image_link | String (up to 1,024 characters) | Additional image URL for the item. It should start with https.It should formatted with RFC 2396 or RFC 1738. Example: https://www.molocostore.com/product/100/bag.png |
| shipping_charge | Number (up to 25 characters) | Shipping charge. Use the same format as the price field.Example 16.00 |
| reward_point | String (up to 100 characters) | Enter if reward points are paid when purchasing a product Example: naverpaypoint^500 |
| google_product_category | String (up to 750 characters) | Google product category. Example Apparel & Accessories > Clothing > Outerwear > Coats & Jackets or 371 |
| item_group_id | String (up to 50 characters) | ID for a product group that comes in different versions (variants). Example: 1234AB |
| color | String (up to 100 characters) | The main color of the item. Example: Blue |
| gender | String | The gender your item is targeted towards. It must be one of the following values:unisexmalefemale |
| size | String (up to 100 characters) | The size of the item. Example: XL |
| material | String (up to 200 characters) | The material the item is made from. Example: cottonpolyesterdenim leather |
| pattern | String (up to 100 characters) | The pattern or graphic print on the item Example: StripedFloral |
| condition | String | The condition of the item. It must be one of the following:newusedrefurbished |
| age_group | String | The age group that the item is targeted towards. It must be one of the following:alladultteenkidstoddlerinfantnewborn |
| class (For Update Feed) | String | This field is only for the update feed. Enter whether the item is new, updated, or sold out. It must be one of the following: N - a new item.U - an item to be updated with the provided information.D - a deleted item. Only id and class fields are required. |
| delivery_option | String (up to 200 characters) | The delivery option that is offered for the item. It must be one of the following:one_daysame_dayregulardawn |
| is_bundle | String | Used if the item is sold in a bundle. It must be one of the following:YN |
| gtin | String (up to 200 characters) | The Global Trade Item Number (GTIN) assigned by the manufacturer Example: 1234560012 |
| blocked | String (up to 50 characters) | Fill with any value if you need to block the item being advertised. Leave it empty if not. |
| custom_label_0 | String (up to 200 characters) | Label that you assign to items to help organize bidding and reporting in sponsored ad campaigns. Example: Seasonal, Holiday, Black Friday |
| custom_label_1 | String (up to 200 characters) | Label that you assign to items to help organize bidding and reporting in sponsored ad campaigns. Example: Seasonal, Holiday, Black Friday |
| custom_label_2 | String (up to 200 characters) | Label that you assign to items to help organize bidding and reporting in sponsored ad campaigns. Example: Seasonal, Holiday, Black Friday |
| custom_label_3 | String (up to 200 characters) | Label that you assign to items to help organize bidding and reporting in sponsored ad campaigns. Example: Seasonal, Holiday, Black Friday |
| custom_label_4 | String (up to 200 characters) | Label that you assign to items to help organize bidding and reporting in sponsored ad campaigns. Example: Seasonal, Holiday, Black Friday |
Delivery catalog feed
The Delivery Catalog Feed is tailored specifically for food and grocery delivery companies. This comprehensive guide will assist you in formatting your catalog feed information to optimize your Retail Media Business with the power of Moloco. By submitting your restaurant/grocery data in the correct format, you can ensure that Moloco matches your delivery-related stores with relevant queries, enhancing the performance of your sponsored ads and recommendations. Whether you specialize in food delivery, grocery services, or both, this guide will provide the necessary steps to optimize your Delivery Catalog Feed and achieve success in the competitive delivery market.
Required fields
The following fields are required for each item in your catalog. If any required fields are missing or formatted incorrectly, items may not upload to your catalog and can be missing from your ads.
| Field | Data Type | Note |
|---|---|---|
| id | String (up to 50 characters) | A unique restaurant ID. If the seller has only one restaurant, use the same value as theseller_id.Example: 039842 |
| title | Syntax (up to 200 characters) | A restaurant title. If the seller has only one restaurant, use the same value with seller_title. Example: Brown |
| image_link | String (up to 2,000 characters) | Main image URL of the restaurant. It should start with https.The format should follow the RFC 2396 or RFC 1738. Example: https://www.molocostore.com/100/bag.png |
| seller_id | String (up to 50 characters) | A unique seller/vendor ID. It is used as an Ad account ID in the MCM. Example: 38840029 |
| seller_title | String (up to 200 characters) | Name of seller/vendor. It is used as an Ad account title in the MCM. Example: Moloco store |
| average_order_value | Number (up to 25 characters) | Average order value (AOV) of the restaurant. Format the price as a number. Always use a period (.) as the decimal point, which only supports up to two decimal places.For KRW and JPY, the value must be set as an integer. Example: 3.25 (for USD or EUR)3000 (for KRW or JPY) |
| category | String (up to 750 characters) | Categories of the restaurant. Provide the most specific restaurant category possible from the list. Use > as a delimiter among the depths.Use ; as a delimiter among multiple categories.Include the most relevant categories. Include the full path of the category. Example: Women>Clothing>T-shirts>V-neckCoffee and Tea;BakerySnack>Coffee and Tea;Snack>Bakery |
Recommended fields
The following fields are recommended to boost ad performance or filter out undesirable results.
| Field | Data Type | Note |
|---|---|---|
| availability | String | The current availability of the restaurant. It must be one of the following values:in_stockout_of_stockpreorderbackorder |
| rating | Number (up to 4 characters) | The rating of the product in a numeric scale. Use a scale of 5 or 10. Round to one decimal place. Always use the period ( .) as the decimal point.Example: 4.7 |
| review_count | Number (up to 20 characters) | The number of product reviews (purchase reviews). Example: 3850 |
| brand | String (up to 70 characters) | The brand name. Example: Moloco |
| brand_id | String (up to 50 characters) | The brand id. Example: Moloco or 1AB234 |
| location | String (up to 750 characters) | Locations where the product is eligible to sell. Provide the most specific product location possible from the list. Use > as a delimiter among the depths.Use ; as a delimiter among multiple locations.Include the exact locations. Include the full path of the location. Example: Seoul>Gangnamgu>YeoksamdongCA>Redwoodcity;CA>Menlopark |
| created_time | String (up to 25 characters) | Created time of the item information. The data format should follow the ISO 8601 following:YYYY-MM-DDThh:mm[+hhmm]YYYY-MM-DDThh:mmZExample: 2016-02-24T11:07+0100 |
| updated_time | String (up to 25 characters) | Last updated time of the item information.The data format should follow the ISO 8601 following:YYYY-MM-DDThh:mm[+hhmm]YYYY-MM-DDThh:mmZExample: 2016-02-24T11:07+0100 |
| delivery_fee_avg | Number (up to 25 characters) | The average delivery fee per week for each order. Example: 16.00 |
Optional fields
You can also include many optional fields to share more item information with customers or control how items are displayed.
| Field | Data Type | Note |
|---|---|---|
| description | String (up to 5,000 characters) | A short, relevant description of the restaurant. Example: Enjoy Korean cuisine, experience various fusion dishes (Korean + Chinese, Korean + Japanese). |
| link | String (up to 1,024 characters) | The link to the restaurant’s specific page on your business’s website where shoppers can learn more about the restaurant. It should start with https.It should follow the format of RFC 2396 or RFC 1738. Example: https://www.molocostore.com/products/100 |
| mobile_link | String (up to 1,024 characters) | The mobile link to the restaurant’s specific page on your business’s website where shoppers can learn more about the restaurant. It should start with https.It should follow the format of RFC 2396 or RFC 1738. Example: https://m.molocostore.com/products/10 |
| additional_image_link | String (up to 1,024 characters) | Additional image URL for the restaurant. It should start with https.It should follow the format of RFC 2396 or RFC 1738. Example: https://www.molocostore.com/product/100/bag.png |
| delivery_charge | Number (up to 25 characters) | Minimum delivery(shipping) charge of the restaurant. Use the same formatting as the average_order_value field.Example: 16.00 |
| menus | String (up to 20,000 characters) | List of all restaurant menus. Use ; as a delimiter among multiple menus.Example: Taco;Burrito;Coffee;Coke |
| reward_point | String (up to 100 characters) | Enter if reward points are paid when purchasing from the restaurant Example: naver_pay_point^500 |
| delivery_option | String (up to 200 characters) | The delivery option that the Platform offers for the restaurant. It must be one of the following values:one_daysame_dayregulardawn |
| custom_label_0 | String (up to 200 characters) | Label that you assign to items to help organize bidding and reporting in sponsored ad campaigns. Example: Seasonal, Holiday, Black Friday |
| custom_label_1 | String (up to 200 characters) | Label that you assign to items to help organize bidding and reporting in sponsored ad campaigns. Example: Seasonal, Holiday, Black Friday |
| custom_label_2 | String (up to 200 characters) | Label that you assign to items to help organize bidding and reporting in sponsored ad campaigns. Example: Seasonal, Holiday, Black Friday |
| custom_label_3 | String (up to 200 characters) | Label that you assign to items to help organize bidding and reporting in sponsored ad campaigns. Example: Seasonal, Holiday, Black Friday |
| custom_label_4 | String (up to 200 characters) | Label that you assign to items to help organize bidding and reporting in sponsored ad campaigns. Example: Seasonal, Holiday, Black Friday |
Updated 26 days ago