Product information (PIM)
Contentserv
The products below a folder of the product tree are read, in full or only those changed since the last run. They come out with their images as Commerce Bundle products and from there go into every shop; the folder tree becomes the category tree, hierarchy included.
Contentserv is connected in the cloud as well as as your own installation, through Contentserv's REST API.
If you wish, only the products changed since the last run are read.
- ContentservProduct information (PIM)
- ConFlowIOintegration platformRun active
- Shopware 6
- Shopify
- Adobe Commerce
- 4ready-made building blocks
- 21data models in the Commerce Bundle, one mapping for every target
Building blocks
Four building blocks for Contentserv
- Read productsRead
Reads the products below a folder of the product tree as Commerce Bundle products, with their images — in full or changes only. A mapping table sets which value fills which product field.
- Read categoriesRead
Reads the folder tree as the category tree, hierarchy included.
- Read
Reads files from the asset management into a freely chosen data model.
- Free request
For everything there is no ready-made building block for: a request to the API, with the stored credentials.
In practice
A workflow with Contentserv
Product data from the PIM
Contentserv maintains, the shop displays — with no export file in between.
- Triggerschedule
- Readthe folder tree as the category tree
- Readproducts from Contentserv, changes only, with images
- WriteShopware 6, Shopify or another shop
One mapping onto the Commerce Bundle; a second shop is one more target building block.
Good to know
What to know about Contentserv
- PrerequisitesWhat has to be set up on your side.
- In the cloud: an API key
- On your own installation: a user
- Not coveredSo you know where you stand.
- The integration reads — there is no ready-made building block for writing into Contentserv
- Writing into Contentserv goes only through the free request
- DurabilityApplies to this integration as to every workflow in ConFlowIO.
- Failed steps retry themselves
- Large reads are processed page by page, each page a step of its own
- A failed run is continued rather than started over
- Live logs per step, with credentials removed
Works well with
What works with Contentserv
Frequent partners
With the Commerce Bundle as the target, it is the same mapping for all of them.
- Shopware 6Products, categories and images into the shop
- ShopifyThe same mapping, another target building block
- Adobe CommerceThe same mapping, another target building block
- WooCommerceThe same mapping, another target building block
- Salesforce Commerce CloudThe same mapping, another target building block
- Tradebyte TB.OneThe catalogue to the marketplaces through TB.One
Contact
See Contentserv on your own data
We are glad to show ConFlowIO on your own data. Bring a real slice of your catalogue.
The difference shows at real volumes — not at five sample records.
Would you like to read our whitepaper? Just say so in your enquiry and we will send it to you.
Rather write directly?info@conflowio.com