An integration is the link between one Content Hub project and one shop. It holds the shop’s address and credentials, and it decides what Content Hub can read and write.
What is available today
Shoper is the implemented connector. Products, product groups, options and variants are read from Shoper, and prices and variants can be written back.
Other platforms are possible, but they are built, not configured: a new connector means new code on our side, not a setting you switch on. If you are evaluating a platform we have not connected before, treat it as a project with its own scope rather than a checkbox.
The shop’s API is the ceiling
Whatever we build, a connector can only do what the platform’s API exposes. This is the honest limit and it is worth setting expectations on early:
- If the platform has no endpoint for a field, that field cannot be written from Content Hub.
- If an endpoint exists but is read-only, Content Hub can display the value and not change it.
- If the platform rate-limits writes, bulk operations take longer. Content Hub already handles this for Shoper: it batches requests, respects the shop’s “retry after” instruction and backs off rather than hammering the API.
So “can Content Hub do X with my shop” has two halves: can Content Hub do X at all, and does your platform expose X. The second half is out of our hands.
Who can set this up
Creating and editing integrations is an Enterprise capability. Day-to-day work with the products a shop has already delivered is not: any user in the project can do that.
What to reuse
Troubleshooting
A field will not save to the shop
Check whether the platform exposes it for writing at all. A field that Content Hub shows is not automatically a field the shop lets us change.
Bulk changes are slow
That is the rate limit, not a stall. Content Hub waits the interval the shop asks for and continues; a large batch finishes later rather than failing.
