Prepare a catalogue, wholesale prices and XML / CSV product data
A catalogue explains the range. A wholesale price list explains the commercial offer. Structured product data supports comparison and, later, channel integration.
The short answer
Provide the catalogue and a wholesale price list separately, with price validity, currency, tax basis and supply terms. State whether you can provide XML, CSV, Excel or API data and update prices and stock. XML and CSV are formats, not a shared marketplace schema: the fields and update method must still be agreed.
1. Prepare the two commercial documents
In the brand form, attach the catalogue and price list or provide usable links. If they are available only on request, choose that status. An initial enquiry does not require sharing account passwords or API keys.
| Document | Useful contents |
|---|---|
| Catalogue | Brand, product names, variants, images, specifications and applicable product documents. |
| Wholesale price list | Stable SKU/GTIN, variant, net unit price, currency, validity date, minimum order and relevant quantity breaks. |
| Supply note | Stock location, lead times, shipping terms, target markets and marketplace or territorial restrictions. |
2. Use stable identifiers and explicit units
| Example intake field | Meaning |
|---|---|
| supplier_sku / gtin | Stable supplier code and genuine GTIN where assigned; keep identifiers as text and preserve leading zeros. |
| product_name / variant | A clear product name plus the exact size, colour or other variant. |
| unit_price_net / currency | Numeric net price per stated unit and a separate currency code. |
| quantity / unit | Available quantity and whether the unit is a piece, pack or another agreed unit. |
| condition / stock_updated_at | Actual condition and the date/time of the stock update, including time zone. |
| photo_url / document_url | Accessible product images and relevant document links; disclose restrictions separately. |
A small CSV example for an initial exchange
These columns illustrate an intake exchange with us. They are not a universal XML/CSV standard or a ready-to-upload marketplace feed. Use UTF-8, agree the delimiter and decimal convention, and quote fields where the format requires it.
supplier_sku,product_name,variant,unit_price_net,currency,quantity,unit,stock_updated_at
BD-DEMO-001,Example storage box,Green,12.50,EUR,80,piece,2026-11-09T09:00:00ZExample data, not a live product or accepted channel feed.
3. Describe how the feed actually works
For XML, share a safe sample structure and explain how its elements map to the agreed fields. For CSV or Excel, identify headers, encoding, units and available update frequency. For API access, describe its availability and arrange credentials later through an agreed secure process.
- State whether prices and quantities are updated and how often.
- Explain what a missing value or zero means; do not use them interchangeably.
- Identify discontinued items and changed variants without reusing product IDs.
- Check the exact target-channel schema separately. For example, Google Merchant Center specifies its own fields and supported file formats; it does not define our wholesale intake schema.
Preparation checklist
Use the checkboxes as a working list. They are not submitted or saved.
Download checklist (TXT) ↓Sources and further reading
Official references support the general rules. Our checklists describe the information we need for an initial commercial assessment.