Commerce platform
Magento / Adobe Commerce
Catalogue in, galleries on every store view.
Import the catalogue, place galleries in a template or CMS block, and run one workspace across websites and store views. Orders can be sent to Idukki with Adobe Commerce Webhooks; API catalogue sync is still being finished.
- Connects in
- Products, Import (CSV or feed URL)
- Catalogue
- Magento product export or a feed on a schedule
- Orders
- Order webhook (beta), Adobe Commerce Webhooks 2.4.6+
Your Magento / Adobe Commerce catalogue in, shoppable galleries out.
Where the content starts, what Idukki does with it, and where it lands. The bar counts every capability in the ledger below, by status.
Magento / Adobe Commerce
Catalogue
Idukki
Collect · Tag to products · Clear rights
Your storefront
Shoppable galleries
5 live4 in progressSee each capability
What works today, and what is still being built.
Galleries, tagging, rights and click analytics are live, with the catalogue arriving by CSV or feed. The order webhook is in beta: it is the least field-tested of our order channels. Matching orders to gallery activity is rolling out, and API catalogue sync is in progress.
- Live
- In progress
- Planned
- Live
Catalogue by CSV or feed
System, Data Transfer, Export in Magento produces a CSV the import maps; a feed URL keeps prices current on a schedule.
- Live
Galleries in templates or CMS blocks
Loader once in the default layout; placeholder div in a .phtml template, a CMS block or Page Builder HTML.
- Live
Multi-website and store views
One workspace, one placeholder per store view, filtered by product id where the gallery sits on a PDP.
- Live
Hyvä and Luma themes
Plain HTML placeholder, no theme-specific module.
- Live
Add to cart from the gallery
The widget detects Magento 2 and adds to its cart. If an add fails, it opens the product page.
- In progress
Order webhook (beta)
Settings, Integrations gives you a per-store webhook URL and secret to subscribe an after-order event in Adobe Commerce Webhooks. The receiver always answers success, so it can never block a checkout.
- In progress
Matching orders to gallery activity
Rolling out. Uses the customer id, the quote id as the cart, and the visitor id when a store module adds it to the order.
- In progress
API catalogue sync
Replaces the CSV step with an integration token (Catalog read). Being finished.
- In progress
Idukki Magento 2 module
Early access: catalogue sync, a CMS gallery widget and product page gallery, and orders sent with the gallery visitor id, connected with a store connection key. Not yet run on a merchant store; see the install guide.
Set it up.
Where it lives in the dashboard: Products, Import.
Before you start
- Magento 2.4 or Adobe Commerce
- A product export CSV or a feed URL
- Theme-file or CMS-block access for the placeholder
- Step 1
Export the catalogue
System, Data Transfer, Export, entity type Products. Keep SKU, name, price, image and URL key.
- Step 2
Import it in Idukki
Products, Import: upload the CSV or paste a feed URL with a re-sync schedule.
- Step 3
Add the loader to the layout
In default.xml (or your theme’s equivalent) add the script once; Hyvä themes take it in the same place.
- Step 4
Place galleries per store view
A CMS block or .phtml template with the placeholder div; on PDPs add data-filter-pid with the product id.
- Step 5
Verify
Open the embed page in Idukki and confirm the install check passes for each store view.
The questions to ask before you connect it.
Do I need a Composer module?
No. The integration works today with a catalogue import and a script tag, with nothing to install in the codebase. An Idukki Magento 2 module that syncs the catalogue and sends orders with the gallery visitor id is in early access if you would rather have that.
Does it work with Hyvä?
Yes. The placeholder is plain HTML and the loader is a deferred script, so Hyvä’s Alpine and Tailwind stack is untouched.
When does order attribution arrive?
The order webhook is in beta now (Adobe Commerce Webhooks, 2.4.6 or later), and matching orders back to posts is rolling out. Product clicks and add-to-cart intent are tracked today.
Go deeper
Several store views and one content library?
That is the normal Magento shape. Import the catalogue, place one gallery per view, and the rights and moderation work happens once.