Integrations ยท PIM
TalkPod + inRiver
Enterprise PIM focused on cross-channel product experience, common in manufacturing, B2B distribution and brands with deep variant hierarchies.
No connector built pre-emptively. We scope and build it inside the pilot, using whatever the source supports.
What this connection does
Turn inRiver into a conversation customers can have.
- Variant relationships stay intact, so a customer asking about a compatible accessory gets a real answer rather than the parent product's spec
- B2B-specific attributes (lead times by region, MOQ, contract pricing fields) sit alongside the marketing attributes for the pod to use
- Technical documents and datasheets your team has uploaded come through as references the chat can offer
- Channel governance from inRiver translates into what the pod talks about, so a trade channel can answer differently from a consumer channel
How it connects
REST API or scheduled export.
Most inRiver work runs through the REST API. The entity model matters: families, variants and accessories stay related so the pod can answer compatibility questions properly rather than flattening everything into a single record.
- B2B attributes
- variant relationships
- compliance documents
- trade specifications
Example conversation
What a customer might ask.
Same shape as the chat on the homepage. Real reply from real data when inRiver is connected.
customer Which adapter do I need to fit this to a 22 mm pipe?
product The 22 mm reducer (part 4B-22R), which ships in the spares kit. It threads onto our standard G3/4 inlet.
Your turn
Connect TalkPod to inRiver.
We'll plug into inRiver, ingest the relevant product or vehicle records, and have a working pod for one supplier or one category live in a working day.