Skip to content
NewProduct Q&A: shoppers ask on your product page and get your answers.See how it works
IdukkiIdukki
Reviews and ratings

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 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.

One library behind two storefront widgets.
One library behind two storefront widgets.

Architecture: what is shared, what is not

LayerSharedPer storefrontWhy
SourcesSocial accounts you own onceReview apps tied to each shopAvoids duplicate rights work
CatalogueMaster SKUs where products matchStore product ids and handlesMatching needs both
ModerationOne approve / hide queueOptional brand filters in the inboxOne person can cover both
RightsOne consent record per postReuse scope if a post is brand-specificLegal history stays central
WidgetsSame runtimeGallery GUID, theme, placementEach face keeps its look
InvitesTemplate libraryFrom-name, delay, localeBuyers see the right brand
A two-storefront reviews stack. Shared rows are done once. Per-storefront rows repeat per shop.

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.

One stack or two accounts?

Start here

Can both brands share staff access?

  • If no

    Keep separate accounts

    Staff access is the hard line.

  • If yes

    Check the legal wall

    Consent records decide the rest.

    • Legal needs a wall between consent records: Keep separate accounts.
    • One consent record per post is fine: One stack, two filtered widgets.
The fit tests in this section.

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

Two storefronts live in five steps

  1. 01

    Label

    Create store labels and Brand Kits for both faces.

  2. 02

    Connect

    Each shop gets its own key.

  3. 03

    Approve

    Ten posts per store through one queue.

  4. 04

    Place

    Filtered widgets on both themes. Click every tag.

  5. 05

    Test invites

    One per storefront. Check from-name and locale.

The checklist below.
  1. 1Create store labels and Brand Kits for both faces.
  2. 2Connect each shop with its own key. Do not reuse keys across platforms.
  3. 3Import or collect ten posts per store and approve them in one queue.
  4. 4Place filtered widgets on both themes and click every product tag.
  5. 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

  1. 1Idukki pricing · Store counts per plan.
  2. 2Idukki reviews · Collection, moderation and display.
  3. 3Magento integration · Store views and one content library.
  4. 4Magento order review invitation API pattern
  5. 5Book a demo
#reviews#multi-store#multi-brand#moderation#storefronts#ugc

More from Rohin Aggarwal