BerryPath imports product data from CSV, XML and JSON. Your field names may differ from the examples, as long as you map them after import.
Where to use this
Use this page when you prepare a feed for Product data.
- Add or upload the feed in Product data -> create or open a dataset -> Source.
- Connect fields in Product data -> open a dataset -> Mapping.
- Check examples in Properties and Products after import.
Required fields
| Field | Purpose | Common names |
|---|---|---|
| Product ID | Stable product code for updates and matching. | id, sku, product_id, ean |
| Title | Product name on recommendation cards. | title, name, product_name |
| URL | Link to the product page. | url, link, product_url |
Useful extra fields
Add Image, Price, Sale price, Label, Review rating, Review count and Position when available.
For matching, include fields visitors choose on: category, brand, use case, size, color, material, compatibility, stock status or collection.
CSV example
sku,name,price,stock,category,url,image_url,brand
PLANT-001,"Monstera Deliciosa",34.95,42,"Indoor plants",https://example.com/monstera,https://example.com/monstera.jpg,Example Nursery
PLANT-002,"Ficus Lyrata",49.95,18,"Indoor trees",https://example.com/ficus,https://example.com/ficus.jpg,Example NurseryMap sku to Product ID, name to Title, url to URL, image_url to Image, price to Price and brand or category to Label.
XML example
<products>
<product>
<id>PLANT-003</id>
<title>Calathea Orbifolia</title>
<url>https://example.com/calathea</url>
<image_url>https://example.com/calathea.jpg</image_url>
<price>24.95</price>
<brand>Example Nursery</brand>
</product>
</products>Google Merchant fields such as g:id, g:title, g:link, g:image_link, g:price and g:brand are also supported.
JSON example
{
"products": [
{
"id": "PLANT-004",
"title": "Pilea Peperomioides",
"url": "https://example.com/pilea",
"image_url": "https://example.com/pilea.jpg",
"price": 18.95,
"brand": "Example Nursery",
"categories": ["Indoor plants", "Easy care"]
}
]
}Keep the structure stable so mappings do not need to be repaired after each import.
Translated and market feeds
Use translated feeds for local titles, labels and URLs. Use the same Product IDs as the source feed.
id,title,label,url
PLANT-001,"Monstera Deliciosa","Zimmerpflanzen",https://example.de/monsteraUse market feeds when a webshop needs local availability, pricing or product URLs. If Product IDs differ, create a separate source dataset.
Check after import
Check Mapping, Properties, Products and Import history. Missing images, prices or titles usually mean the mapping points to the wrong field.