Map watch attributes to channel fields
How your watch data reaches each channel, most of it is automatic, plus the channel-specific options and custom field mappings you can set yourself.
Got a question about this guide? Use Open to continue it in Claude or ChatGPT.
When you publish a watch, its data has to land in the right fields on each channel. Most of that is automatic: here's what's handled for you and what you set yourself.
What's automatic
Your watch's core attributes (brand, model, reference, case size and material, movement, condition, and the rest) are sent to each channel's matching fields when you publish. You don't hand-map eBay item specifics; Worldwatch fills them from the watch record. Keep the watch's details accurate and complete, and the listing inherits them.
Channel options you set per listing
Some fields are yours to choose when you create a listing, in the channel-specific section of the listing form:
- eBay: your fulfillment, payment, and return policies, and the item location.
- Shopify: collections and a delivery profile.
- WooCommerce: categories and a shipping class.
Set these up once under Settings → Channels, then just pick them from the dropdowns each time.
Custom field mappings
For Shopify and WooCommerce you can push extra watch data into your own fields. Go to Settings → Channels → Attribute mappings and map a source field (a watch attribute) to a target key, for example, brand to a Shopify metafield such as wwm.brand, or to a WooCommerce product attribute. This is optional; the standard attributes already flow without it.
If something's missing
If a channel needs a field or policy you haven't set, publishing to that channel fails and the error appears on the channel's row in the listing. Open it to see what's missing, fix it, and publish again.