Open Source inriver Alternatives
A curated collection of the 1 best open source alternatives to inriver.
The best open source alternative to inriver is UnoPim. If that doesn't suit you, we've compiled a ranked list of other open source inriver alternatives to help you find a suitable replacement.
inriver alternatives are mainly E-commerce Platforms. Browse these if you want a narrower list of alternatives or looking for a specific functionality of inriver.
An open source product information management system on Laravel, for businesses centralizing and enriching large product catalogs.
UnoPim is a product information management system built on Laravel 13. Product data that would otherwise be scattered across spreadsheets, an ecommerce backend and a supplier feed lives in one central repository, where it can be enriched before it goes anywhere downstream.
The project targets high-volume catalogs and documents how it scales past 10 million products. Import and export run on a queue with real-time progress tracking, pipeline visualization and job-specific logging.
Recent releases put most of their weight on catalog structure and downstream delivery.
- AI agent chat: search, create, update, bulk edit, export and categorize products through conversational multi-step tool calling.
- Magic AI: content, image and translation generation across 10 plus providers, with encrypted credentials and connection testing.
- Product completeness: every product scored against the attributes its family marks required per channel.
- Digital Product Passport: build passport templates, attach QR carriers and publish per-product passports behind a dedicated permission.
- Publication channels: enriched payloads pushed to downstream destinations on a queue, with per-channel payloads and delivery records.
- Webhooks: product events notify external systems asynchronously so subscriber calls never block a save.
The rest is what a PIM is expected to carry. Multi-channel and multi-currency support, 33 languages out of the box, configurable products with multi-level variant axes, version history on product data, and a documented REST API.
Requirements are specific. PHP 8.4.1 or later, Node 20 LTS, Composer 2.5, and MySQL 8.0.32 or PostgreSQL 16, plus a queue worker covering the webhooks, system, completeness and publication queues, without which those jobs pile up unprocessed.
