One reviews stack for two storefronts: shared queue, separate widgets
Share one moderation queue across two brands or markets. Keep separate review and UGC widgets per storefront. Architecture table and checks. We make Idukki.
You open the reviews inbox on Monday. Brand A’s hoodie photos sit next to Brand B’s serum selfies. Two themes, one tired queue. The fix is not two full review stacks. It is one library with two storefront faces.
In this article
We make Idukki. Multi-store plans exist so two front ends can share one content layer. This piece is the architecture. It is not a migration checklist.
Architecture: what is shared, what is not
| Layer | Shared | Per storefront | Why |
|---|---|---|---|
| Sources | Social accounts you own once | Review apps tied to each shop | Avoids duplicate rights work |
| Catalogue | Master SKUs where products match | Store product ids and handles | Matching needs both |
| Moderation | One approve / hide queue | Optional brand filters in the inbox | One person can cover both |
| Rights | One consent record per post | Reuse scope if a post is brand-specific | Legal history stays central |
| Widgets | Same runtime | Gallery GUID, theme, placement | Each face keeps its look |
| Invites | Template library | From-name, delay, locale | Buyers see the right brand |
If a row is shared by accident, Brand A’s serum shows on Brand B’s PDP. Tag every import and every invite with the storefront it belongs to.
When one stack fits two faces
- Two brands share a parent team and one moderation shift.
- Two markets sell the same catalogue with different themes.
- A DTC site and a marketplace brand page need the same photo set.
- You outgrew one login per tool and kept pasting the same hide decision twice.
One stack is a bad fit when the brands must never share staff access. Or when legal needs a hard wall between consent records. In those cases, keep separate accounts.
Per-storefront widgets without a second queue
Place a gallery or review layout on each theme. Point each widget at a collection filtered by store label. Brand Kit colours and fonts stay local. The approve button stays global.
On Magento, several store views often share one catalogue. Import once. Place one gallery per view. Moderation still happens once. That shape is the normal Magento case in our Magento integration notes.
Review invites per brand
Invites must look like the brand that shipped the order. Shared templates are fine. From-name, reply-to and delay are not. Route Magento or Shopify order events with a storefront id into the invitation call.
For the Magento webhook shape, see Magento order review invitation API pattern. On Shopify, Idukki can send a review request email after the order.
Go-live checklist
- 1Create store labels and Brand Kits for both faces.
- 2Connect each shop with its own key. Do not reuse keys across platforms.
- 3Import or collect ten posts per store and approve them in one queue.
- 4Place filtered widgets on both themes and click every product tag.
- 5Send one test invite per storefront and confirm from-name and locale.
Questions multi-brand teams ask
Can two Shopify shops share one Idukki account?
Yes on plans that include more than one store. Growth covers two stores. Professional covers five.
Will Brand A’s reviews leak onto Brand B?
Only if the collection filter is wrong. Tag posts by store and point each widget at its filter.
Do we need two moderation seats?
Not for volume alone. One queue with store filters is the point of a shared stack.
What about Magento store views?
One catalogue import and one gallery per view is the usual shape. Rights and moderation stay shared.
Sources and related reading
- 1Idukki pricing · Store counts per plan.
- 2Idukki reviews · Collection, moderation and display.
- 3Magento integration · Store views and one content library.
- 4Magento order review invitation API pattern
- 5Book a demo
More from Rohin Aggarwal
- Strategy
Finding the micro-influencers hiding in your customer list
Your best creators already bought from you, tagged you and reviewed you. Mine the customers who advocate already: the cheapest, most credible pipeline you own.
- Strategy
Gifting and seeding programs that actually produce content
Untargeted gifting mails free product into a void. A seeding program is designed: chosen recipients, a light expectation, and a rights path to usable UGC.
- Strategy
Ambassador tiers: structuring a creator community
A flat ambassador list treats a one-video customer like a year-long advocate: give the community tiers with clear criteria, real rewards, and a path to climb.