Getting Started
Getting started with Marketplace
Requirements
To be incorporated to the marketplace, product data needs to be delivered in a machine-friendly format. The product data specification outlines the requirements for product data.
Product data specification
Use this specification to format your product information for FashionUnited Partner programs, such as the B2B Marketplace. It is important to use the correct format, as we use this product data to create listings in the B2B Marketplace and respond to queries.
Feel free to follow the Google Shopping format if your system already supports it. Do you have a custom format and is it not easy for you to change it to our required format? Contact us, we can probably help you out.
- FashionUnited Marketplace format Specifications
- Google shopping format Specifications
Data format
- Delimited file format (CSV, TSV, tab, comma, semicolon, pipe) is preferred, JSON supported as well. XML on request.
Deliver your data
Send the url with your feed containing the product data to FashionUnited Customer Service or your account manager.
- HTTPS is mandatory
- Supported file formats
If you are unable to provide a url, only a file, contact FashionUnited Customer Service to provide you with Cloud bucket access where you can upload your product data.
Fields
Attribute | Format | Requirements |
---|---|---|
name | Required Example Syntax Schema.org property | |
brand_name | Required Syntax Schema.org property | |
source_product_id | Required Example Syntax Schema.org property | |
source_variant_id | Required | - Unique ID per variant - Variants are: sizes, colors etc. You can use your own, as long as we have have a unique ID per size/color variant. |
description | Example Schema.org property | |
short_description | ||
material | Your product’s fabric or material Example Schema.org property | |
season | Required The season your product belongs to. Example | |
category_path | Optional Syntax | |
category_main | Required Syntax | Use the FashionUnited categories or use your own. We can map your categories to ours, as long as they are used consistently. |
category_sub | Optional Syntax | |
category_three | Optional Syntax | |
url | Your product’s landing page (b2b webshop) Example Schema.org property | |
genders | Your product’s gender Example | |
age_groups | Your product’s age group Example | |
color_name | Your product’s color Example Syntax Schema.org property | |
sizes | Example | |
price_amount | Syntax | |
price_currency | Example Syntax Schema.org property | |
shipping_cost | Syntax | |
delivery_time | Your product’s delivery time. Example | |
delivery_days | Automatically populated Automatically populated, if delivery_time is set. You can override. | |
order_quantity | ||
gtin | Your product’s Global Trade Item Number (GTIN) Example Syntax Schema.org property | |
mpn | Your product’s Manufacturer Part Number (mpn) Example Syntax Schema.org property | |
image | Required Your product’s main image URL Example Schema.org property | For the image URL:
|
alternate_image | Optional Your product’s additional image URL Example | |
locale | FashionUnited internal use Example Syntax | |
public | FashionUnited internal use | |
market_public | FashionUnited internal use | |
market_id | FashionUnited internal use | |
stand_id | FashionUnited internal use |