> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wisepim.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Shops
> Decide which connected shops each product syncs to. Set sync per connection, override CCV visibility, and see every destination from the products table.
When you sell through more than one shop, not every product belongs everywhere. The **Shops** tab decides where a single product syncs: "Choose where this product syncs. Each connection keeps its own field mappings and languages."
**Where to find it:** open a product and pick the **Shops** tab in the product editor, or click the **Shops** cell in the products table.
## One card per connection
Every shop you have connected gets its own card, headed by the shop name with its platform and profile number underneath ("CCV Shop ยท #4821"). What you can set there:
| Control | What it does |
| --------------------------------- | --------------------------------------------------------------------------------------- |
| **Sync this product** | Whether this product is included in future exports to that connection. |
| **Visibility on next CCV sync** | CCV Shop only. Overrides the storefront visibility this product gets on the next sync. |
| **Connection and field settings** | Opens the connection itself, where field mappings, languages, and export behavior live. |
Change something and **Save settings** lights up, next to a discard button that puts the card back the way you found it. Nothing leaves the page until you save.
Saving controls future exports, not the past: "Turning sync off does not remove an existing listing. Start an export to apply visibility changes." If a product is already live in a shop, switch sync off *and* remove or hide the listing on the platform.
If a whole connection has exports switched off, the card says so: "Export is disabled for this connection. Enable it in the connection settings to resume syncing." Product-level sync still saves; it simply does nothing until the connection resumes.
## CCV Shop and multishop
CCV Shop connections get two extras, because CCV manages shop membership on its own side.
**Visibility on next CCV sync** takes one of three values:
* **Use product visibility** โ inherit whatever the product's own visibility says. This is the default.
* **Enabled** โ force the product visible in this shop.
* **Disabled** โ force it hidden, whatever the product says.
**Manage CCV shops** opens the multishop panel, with a switch per CCV shop for assigning this product. A few things to know before you use it:
"Assignments are managed by the multishop parent." Connect the parent, not a child shop. A child or single-shop connection shows: "This connection is a child or single shop. Connect the multishop parent to manage product assignments."
Flip one switch, read the line that appears ("Apply will assign this product to the selected CCV shop", or the matching removal wording), then click **Apply to CCV Shop**. The other switches stay locked until that change is applied or undone. Other shop assignments are preserved.
CCV processes multishop changes through a queue, so a successful apply means accepted, not finished: "CCV Shop accepted the change. It processes multishop changes in its own queue; reload to check the result." If a change is still unconfirmed, WISEPIM blocks the next one until you reload and check.
The parent connection needs `GET products/webshops` and `PUT webshops` under CCV's API settings. Per-shop field exceptions are set in CCV itself, under **My Webshop > Settings > General > Multishop settings**.
Turning the product's sync toggle off does not cut CCV's parent out: "CCV's parent can still update child shops when this sync toggle is off. Use the parent connection to manage CCV shop assignments."
## See destinations from the products table
Add the **Shops** column to your product table and you can read sync status without opening anything. Click **Columns**, search for "shops", tick it, and click **Apply**.
Each row then shows a chip per shop, with a **+2** style counter when a product goes to more than two. The icon carries the state:
| Chip | Meaning |
| ------------------ | --------------------------------------------------------------------------------- |
| Green with a check | **Sync on**. The product goes out on the next export. |
| Grey with a pause | **Sync off** for this product, or **Connection paused** for the whole connection. |
Hover a cell for the full list with each shop's status. Click it to jump straight to that product's Shops tab.
Pair the Shops column with a [saved view](/en/products/customizing-views) per channel. One glance tells you which products are missing from a shop you just launched.
## Who can change what
Two different permissions are at play, and the tab spells them out: "Project editors manage product destinations. Integration managers configure connections and field mappings."
So a project editor decides *which* products go to a shop. An integration manager decides *how* they get there. If you only have view access, the tab tells you: "You can view shop settings. A project editor must save changes."
If nothing is listed at all, there is nothing connected yet: "Connect a shop in Integrations to manage product destinations."
## Change many products at once
Setting sync product by product gets old fast. The [Shop sync bulk action](/en/essentials/bulk-editing/set-shop-sync) sets the same choice across an entire selection, one setting per shop, leaving the shops you do not touch exactly as they were.
## Related
Switch sync on or off for whole selections, shop by shop.
Send your catalog to the shops and files that are set to receive it.
Connect CCV Shop, including multishop setups.
Everything else in the product editor, tab by tab.