Integrations
Every system wants the product in its own shape.
Cernel connects to your PIM, your shop and your files, and builds each system's version of a product from one set of facts.
What connects
Shop, PIM and feed integrations: every way in and out.
Shopify, Struct PIM and inriver each sync both ways. Files, feeds and a REST API connect everything else. Open one to see what it carries and its setup guide.
Magento
Public APIYour side pushes products in through the API, picks up the enriched values from the changes endpoint and writes them into Magento with Magento's own API.
DocsWooCommerce, BigCommerce, Salesforce Commerce Cloud and other platforms
Files, feeds or the APIProducts come in as a CSV file, a Google Shopping feed or through the API. Results go back as a CSV export in the columns you choose, or through the API.
Docs
Syndication
Product content syndication: one set of facts, every channel's version.
Syndication means getting the same product to every place it is sold, in the shape each place needs. In Cernel the facts about a product live once. Each channel's version is built from them, in its own fields, format and wording, and you review per channel where you want to.
- Shopify
- Titles, descriptions, SEO fields, metafields and every Markets language, synced back automatically.
- Struct PIM
- The mapped attributes, Global List values and every language layer, written back in the background.
- inriver
- The mapped fields and shared-list values in every inriver language, written back in the background.
- Google Shopping
- Its feed fields and up to five custom labels, as a feed file for Merchant Center.
- Marketplaces and retailers
- A file in their own columns, from a saved export template.
- Your own systems
- Every approved change, ready to pick up through the Public API.
Shopify, Struct PIM and inriver get approved values back automatically. Feed and channel files are ready whenever you need them.
System by system
What Cernel does for each system you run.
Each system in your stack is built for one job. Here is what each one is for, and what Cernel takes off your hands there.
01 · PIM
Your PIM keeps the record. Cernel fills it in.
A PIM, a product information management system, is where your team keeps the master record of every product: its fields, its categories and its languages.
It holds the structure, and every empty field and every translation is still somebody's job. Connect Cernel and the PIM stays the system of record, with the gaps filled for you.
What Cernel takes over
- Classifies every product into your categories, so it gets the right fields.
- Fills the fields each category needs, with an agent per field working by your rules.
- Writes every language you sell in, and sends each one to the matching PIM language.
- Sends approved values back into the mapped PIM fields in the background, with no export step.
Struct PIM and inriver each connect natively, both ways. Any other PIM connects through the Public API or files.
Connects through02 · ERP
Your ERP runs the business. Cernel writes the product.
The ERP is where SKUs, prices, stock and purchasing live, and often the raw data suppliers sent with their products.
It is built for orders and stock. What it knows about a product is often a short supplier line and a few codes, and Cernel turns that into content a shop can use, without anyone retyping it.
What Cernel takes over
- Takes products in through the REST API, or as a CSV export.
- Starts enrichment by itself when new products arrive, through an automation.
- Turns raw supplier data into descriptions, meta titles and structured fields.
- Keeps every approved value ready on the changes endpoint, for your systems to pick up on their own schedule.
Your ERP connects through the Public API or files, and your team decides where the approved values go from there.
Connects through03 · Shop system
Your shop is what customers read. Cernel fills the gaps in it.
The shop system, the commerce platform behind your store, is where customers meet the product: its title, its description, its images and the filters they click.
Every gap shows there. A missing material is a filter that cannot find the product, and a missing translation is a market reading another language. The native shop connection runs both ways.
What Cernel takes over
- Writes descriptions, meta titles and meta descriptions, which go back to the shop once they are approved.
- Fills custom fields on products and variants, and creates the field's definition in the shop when it is new.
- Sends each language as the matching translation in the shop, so it lands in every market your store runs.
Approved values go back to Shopify automatically, typically within a minute. Other shop systems connect through the Public API.
Connects through04 · Feeds and channels
Every channel has its own categories and fields. Cernel maps them all.
Shopping channels, comparison sites and marketplaces each have their own category tree and their own required fields.
In Cernel you map out the category tree of every channel you sell on. Each product is placed in each tree and gets the fields that channel asks for, and you export each channel's version when you need it.
What Cernel takes over
- Maps every channel's category tree and places each product in it.
- Fills the fields each channel asks for, with an agent per field working by your rules.
- Writes each channel's titles and descriptions from the same facts, in the length and order the channel wants.
- Exports each channel's version: a Google Shopping feed, a file in the channel's own columns, or through the API.
Connects through05 · Supplier files
Suppliers send spreadsheets. Cernel maps every one.
Supplier files are how new products often arrive: a spreadsheet per supplier, each with its own columns, codes and language.
Before anything can be written or translated, somebody has to read each file and match it to your fields. That is the first job Cernel takes over.
What Cernel takes over
- Suggests how each column maps to your fields and identifiers, and reuses the mapping for the next file.
- Brings differently shaped supplier files together into one catalogue.
- Shows what will be created or updated before anything runs.
- Matches rows on SKU, GTIN, MPN or your own identifier, so the next file updates instead of duplicating.
Connects through
What you control
You decide what goes back, and when.
You choose which values go live automatically and which get a review step. Review steps check every value and only ask a person when something fails or needs a decision.
- Approve Before PushSettings, Platform
- When it is on, content Cernel generates waits for an explicit yes before it syncs to a connected shop system or PIM. Every run and automation starts from this setting.
- Require reviewOn one field
- Overrides the run for a single field. New values for a safety or compliance field wait until someone approves them. A field you trust can be set to Approve automatically instead.
- Field mappingOn each integration
- Map fields one by one as import, export or both. Each Cernel field takes its value from one source field, so every field has one source of truth.
- Service accountsSettings, Developer, API
- One per integration, each with its own keys, so you decide who can call the API. Rotate without downtime; revoking takes effect at once.
- Event LogSettings, Events
- Integration activity by level and domain. Values that could not be matched are logged there, never dropped silently.
FAQ
Questions about shop and PIM integrations and syndication.
How does Cernel work with a Shopify store?
Cernel connects through Shopify's own app authorisation and keeps every product with its category and fields. It enriches them and syncs approved values back to the store, metafields and every Shopify Markets language included. If you also run a PIM, Cernel works with both.
Does Cernel integrate with my PIM?
Struct PIM and inriver each have their own native integration, and both sync two ways: Cernel reads your products and your model, fills the fields and the languages, and writes approved values back to the mapped PIM fields in the background. Any other PIM connects through the Public API or files, with your side pushing products in and picking up the enriched values.
What is product content syndication, and does Cernel do it?
Product content syndication is getting the same product to every channel you sell on, in the format each channel needs. In Cernel the facts about a product live once, and each channel's version is built from them: written back to Shopify, Struct PIM or inriver, exported as a Google Shopping feed or a file in a marketplace's own columns, or picked up through the API. Some channel fields need their own wording or format, and you can review each channel's version where you want to.
Does Cernel work with WooCommerce, Magento, BigCommerce or Salesforce?
Yes, through files and the Public API. Products come in as a CSV file, a Google Shopping feed or through the API, and results go back as a CSV export or through the API. For Magento the usual pattern is the API: push products in, pick up the enriched values from the changes endpoint, and write them into Magento with its own API.
Do we need a PIM or a shop connection to start?
No. Cernel runs on files alone. Import a supplier sheet or a catalogue export, check the preview, and export the result. Connect Shopify, Struct PIM or inriver later, when you want values to sync both ways.
We have Shopify and a PIM. Which one should connect?
Both can, and both run two ways. What matters is which system owns which field, because each Cernel field takes its value from one source field. Let the PIM own the specifications and the store own the commercial fields, or the other way round.