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. The pairing connection in settings and order webhooks are still being finished in the backend.
- Connects in
- Products, Import (CSV or feed URL)
- Catalogue
- Magento product export or a feed on a schedule
- Orders
- Planned (plan F9)
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 pairing connection in settings is in progress; order attribution follows the WooCommerce and BigCommerce webhooks.
- 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
Opens the product page. In-gallery cart writes are Shopify only today.
- In progress
Pairing connection with catalogue sync
The Magento tab in settings takes the store URL and an admin email for a pairing link; the backend sync behind it is being finished.
- Planned
Order webhook attribution
Plan F9. Analytics stop at add-to-cart intent until it ships.
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. Today the integration is a catalogue import and a script tag for the storefront. There is nothing to install in the codebase.
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?
After the WooCommerce and BigCommerce order webhooks, per the product plan. 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.