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

By Rohin Aggarwal · 2026-10-31

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.

**Quick answer**

- **Share the library.** One moderation queue, one rights record, one product match.
- **Split the face.** Each storefront gets its own widget placement and Brand Kit.
- **Tag by store.** Every post carries a store or brand label before it goes live.
- **Do not reuse secrets.** Each store connection key stays scoped to that platform shop.
- We make Idukki. Growth covers 2 stores. Professional covers 5 stores.

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.

_Figure: One library behind two storefront widgets._

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

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

> **Name the filter first:** Create store labels before the first import. Retroactive tagging on a mixed queue is slow and error-prone.

## 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](/integrations/magento) notes.

> **Test the wrong filter:** Open storefront A and search for a post tagged only to B. If it appears, fix the collection filter before launch.

## 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](/blog/magento-order-review-invitation-api-pattern). On Shopify, Idukki can send a review request email after the order.

## Go-live checklist

1. Create store labels and Brand Kits for both faces.
2. Connect each shop with its own key. Do not reuse keys across platforms.
3. Import or collect ten posts per store and approve them in one queue.
4. Place filtered widgets on both themes and click every product tag.
5. Send one test invite per storefront and confirm from-name and locale.

**The rule to use:** Share the library and the moderation shift. Split widgets, invites and connection keys. Label every post before it goes live.

### Questions multi-brand teams ask

**Q: Can two Shopify shops share one Idukki account?**

A: Yes on plans that include more than one store. Growth covers two stores. Professional covers five.

**Q: Will Brand A’s reviews leak onto Brand B?**

A: Only if the collection filter is wrong. Tag posts by store and point each widget at its filter.

**Q: Do we need two moderation seats?**

A: Not for volume alone. One queue with store filters is the point of a shared stack.

**Q: What about Magento store views?**

A: One catalogue import and one gallery per view is the usual shape. Rights and moderation stay shared.

### Sources and related reading
- [Idukki pricing](/pricing) — Store counts per plan.
- [Idukki reviews](/reviews) — Collection, moderation and display.
- [Magento integration](/integrations/magento) — Store views and one content library.
- [Magento order review invitation API pattern](/blog/magento-order-review-invitation-api-pattern)
- [Book a demo](/demo)

---
Canonical: https://idukki.io/blog/one-reviews-stack-two-storefronts
Tags: reviews, multi-store, multi-brand, moderation, storefronts, ugc, strategy