Skip to content

Reuse widget across multiple positions

Reuse the same widget content across multiple scenarios: duplicate, change Placement or Display rules, publish each independently.

1. Find the widget to reuse on the home page

Section titled “1. Find the widget to reuse on the home page”

Widget list grid view or list view.

After success, bottom-right toast: “Duplicate created”.

Image: ⋯ menu “Duplicate” position + new row in list

Duplicate defaults to “My widget” — recommend immediately ⋯ → Rename to a recognizable name.

Image: rename modal

Enter the duplicate’s editor:

  • In Display tab change Placement or add finer rules
  • Content fields preserved (the point of reuse is identical content)

The duplicate and original publish, count stats independently.

When duplicating, the system (commit 189e7a9):

  1. Regenerates component IDs — avoids duplicate ID conflicts with the original
  2. Remaps locales keysconfig.locales translation map’s component ID references auto-remap to new IDs, so translations follow the duplicate
  3. Preserves all content fields — text / heading / button preset etc. fully copied
  4. Preserves placement — duplicate defaults to same placement; merchant must change manually
  • Widget ID (config.key) — regenerated
  • Publish status — duplicate defaults to “Pending”; needs “Publish” click to ship
  • Historical stats — doesn’t inherit original’s impression / click data; counts from 0

Cross-widget-type duplication (e.g. duplicating a complex widget as label) is not allowed — server rejects. Reason: label widget content schema is incompatible with others (see Widget types).

To change type → rebuild a new widget.

Will modifying the original sync to duplicates?

Section titled “Will modifying the original sync to duplicates?”

No. Duplicate and original are two independent configs; modifying one doesn’t affect the other. To unified-update multiple duplicates, edit each.

Currently the ⋯ menu is a single-widget operation; bulk duplication is not supported. To quickly build multiple variants:

  • Duplicate one → modify fields → duplicate again → modify fields
  • During duplication, placement / visibility is preserved, can serve as a template for further derivation