A checkmark to select/unselect all variants when setting up States
Currently, when setting up states based on 'Selected Variant', all the variants of all the selected products are checked by default. Sometimes it's time-consuming to uncheck so many variants. Like in this example, you can see that it's 128 variants and if I only wanted a few, I'd have to manually uncheck all of them. It would be helpful to have a 'Select All' checkmark to select or unselect all variants

An Anonymous User 1 day ago
💬 Replo
A checkmark to select/unselect all variants when setting up States
Currently, when setting up states based on 'Selected Variant', all the variants of all the selected products are checked by default. Sometimes it's time-consuming to uncheck so many variants. Like in this example, you can see that it's 128 variants and if I only wanted a few, I'd have to manually uncheck all of them. It would be helpful to have a 'Select All' checkmark to select or unselect all variants

An Anonymous User 1 day ago
💬 Replo
Metafield for replo video component placeholder
I create meta field in shopify backend for dynamic video placeholder, but now replo doesn't supporting this feature please can you apply this feature.

An Anonymous User 1 day ago
💬 Replo
Metafield for replo video component placeholder
I create meta field in shopify backend for dynamic video placeholder, but now replo doesn't supporting this feature please can you apply this feature.

An Anonymous User 1 day ago
💬 Replo
"Set as homepage" toggle and "publish page" steps
Hello there —We just tested that whenever we release a new Shopify theme, the theme push is causing the "set as homepage" toggle to turn off on its own. Every time we need to release a new theme, we need to do the following steps: 1) turn on that toggle back on, and 2) hit “publish page”. These steps are adding complexity onto a process that should be done quickly in order to don’t disturb users. Before, we didn’t need to do step 1, but now it has become clear in the latest theme releases that we need to do both steps in order for our homepage to be visible. It’s also concerning since our devs sometimes need to push new themes for hot fixes, and my team may not be around. If they do, because the toggle "set as homepage" is turning off automatically, this is going to cause the Homepage to go dead every time they do this when my team isn’t around to support them. I think these two steps in Replo are unnecessary and do not consider clients that new to release new themes quite often, like our company. I’d like to request that these two steps be eliminated so a smoother process can be in place. Ideally, any time a new shopify theme is released, Replo should stay as is and not break the connection to the homepage —just like it does with its other pages. All Replo pages are always fine when a new theme is pushed, except for the homepage, which is strange since it’s the most pivotal page. Thank you!

An Anonymous User 2 days ago
High Priority
💬 Replo
"Set as homepage" toggle and "publish page" steps
Hello there —We just tested that whenever we release a new Shopify theme, the theme push is causing the "set as homepage" toggle to turn off on its own. Every time we need to release a new theme, we need to do the following steps: 1) turn on that toggle back on, and 2) hit “publish page”. These steps are adding complexity onto a process that should be done quickly in order to don’t disturb users. Before, we didn’t need to do step 1, but now it has become clear in the latest theme releases that we need to do both steps in order for our homepage to be visible. It’s also concerning since our devs sometimes need to push new themes for hot fixes, and my team may not be around. If they do, because the toggle "set as homepage" is turning off automatically, this is going to cause the Homepage to go dead every time they do this when my team isn’t around to support them. I think these two steps in Replo are unnecessary and do not consider clients that new to release new themes quite often, like our company. I’d like to request that these two steps be eliminated so a smoother process can be in place. Ideally, any time a new shopify theme is released, Replo should stay as is and not break the connection to the homepage —just like it does with its other pages. All Replo pages are always fine when a new theme is pushed, except for the homepage, which is strange since it’s the most pivotal page. Thank you!

An Anonymous User 2 days ago
High Priority
💬 Replo
Native MoonBundles integration
We’re getting consistent demand from shared users to use MoonBundles directly inside Replo. MoonBundles is used by 5,000+ Shopify stores to increase AOV with: Bundles (multi-product, tiered offers, gift stacking) Cart upsells Post-purchase offers Right now, integration is manual (scripts), which limits flexibility inside Replo. Request: Add MoonBundles as a native component/block in Replo so users can place bundle offers directly in PDPs and landing pages. Impact: Better UX, higher AOV/CVR for merchants, and smoother workflows for shared users. Happy to support on our side if needed.

An Anonymous User 2 days ago
bundle-builder
🔗 Integration Requests
Native MoonBundles integration
We’re getting consistent demand from shared users to use MoonBundles directly inside Replo. MoonBundles is used by 5,000+ Shopify stores to increase AOV with: Bundles (multi-product, tiered offers, gift stacking) Cart upsells Post-purchase offers Right now, integration is manual (scripts), which limits flexibility inside Replo. Request: Add MoonBundles as a native component/block in Replo so users can place bundle offers directly in PDPs and landing pages. Impact: Better UX, higher AOV/CVR for merchants, and smoother workflows for shared users. Happy to support on our side if needed.

An Anonymous User 2 days ago
bundle-builder
🔗 Integration Requests
Expand AI Agent Scope to Global Components
The core issue stems from a technical limitation where the Replo AI agent is sandboxed to individual page components, preventing it from applying necessary global changes, such as translating the cart drawer to French, even when it correctly identifies the solution. This creates a significant friction point for users who cannot manually edit these files themselves and are left with a partially localized store. Replo needs to grant the AI elevated "write access" to global components like slideout-cart.tsx or to provide a managed UI editor that allows users to safely apply AI-generated code snippets to global files.

An Anonymous User 5 days ago
💬 Replo
Expand AI Agent Scope to Global Components
The core issue stems from a technical limitation where the Replo AI agent is sandboxed to individual page components, preventing it from applying necessary global changes, such as translating the cart drawer to French, even when it correctly identifies the solution. This creates a significant friction point for users who cannot manually edit these files themselves and are left with a partially localized store. Replo needs to grant the AI elevated "write access" to global components like slideout-cart.tsx or to provide a managed UI editor that allows users to safely apply AI-generated code snippets to global files.

An Anonymous User 5 days ago
💬 Replo
Auto-scroll in Accordion Block
I don’t like the way the accordions block works, it pisses us off. We want to open it seamlessly without be needing to scroll up to see the first part. Thanks!

An Anonymous User 16 days ago
💬 Replo
Auto-scroll in Accordion Block
I don’t like the way the accordions block works, it pisses us off. We want to open it seamlessly without be needing to scroll up to see the first part. Thanks!

An Anonymous User 16 days ago
💬 Replo
Reviewed
Support for Multiple Instances of the same Theme Custom Section without Data-RID Synchronization
When a user adds multiple instances of the same Theme Custom Section (specifically in themes using nested blocks or "Custom Section" frameworks like Shopify Horizon), Replo assigns the same data-rid attribute values to both instances in the generated Liquid output. Because the data-rid is identical, Replo’s runtime treats them as a single entity. Any change made to the content, attributes, or nested blocks in one instance is automatically synced/mirrored to the other, making it impossible to have two unique versions of the same section type on one page.

An Anonymous User 20 days ago
💬 Replo
Reviewed
Support for Multiple Instances of the same Theme Custom Section without Data-RID Synchronization
When a user adds multiple instances of the same Theme Custom Section (specifically in themes using nested blocks or "Custom Section" frameworks like Shopify Horizon), Replo assigns the same data-rid attribute values to both instances in the generated Liquid output. Because the data-rid is identical, Replo’s runtime treats them as a single entity. Any change made to the content, attributes, or nested blocks in one instance is automatically synced/mirrored to the other, making it impossible to have two unique versions of the same section type on one page.

An Anonymous User 20 days ago
💬 Replo
Allow copying/pasting AI pages from one project to another
As we have on the classic landing page builder (Replo for shopify themes) the ability to copy/paste pages from one Project to another, it would be nice and useful to have this for the AI builder as well.

Andres Pachano 22 days ago
High Priority
💬 Replo
Allow copying/pasting AI pages from one project to another
As we have on the classic landing page builder (Replo for shopify themes) the ability to copy/paste pages from one Project to another, it would be nice and useful to have this for the AI builder as well.

Andres Pachano 22 days ago
High Priority
💬 Replo
Combine AI Feature & Replo Editor
Please make it possible to Edit KI based Landingpages via Chat also via Drag and Drop as in Replo Editor. Otherwise it doesnt help me in any way if I can either just edit a Landingpage via Chat OR need to build the website from scratch with Replo Editor.

An Anonymous User 29 days ago
High Priority
💬 Replo
Combine AI Feature & Replo Editor
Please make it possible to Edit KI based Landingpages via Chat also via Drag and Drop as in Replo Editor. Otherwise it doesnt help me in any way if I can either just edit a Landingpage via Chat OR need to build the website from scratch with Replo Editor.

An Anonymous User 29 days ago
High Priority
💬 Replo
Allow rendering of +250 variants inside of Replo pages.
At the moment, Replo’s limit is at 250 variants, meaning that variant 251 will “vanish” from the live page.

An Anonymous User about 1 month ago
publishing
💬 Replo
Allow rendering of +250 variants inside of Replo pages.
At the moment, Replo’s limit is at 250 variants, meaning that variant 251 will “vanish” from the live page.

An Anonymous User about 1 month ago
publishing
💬 Replo
Timeline Horizontal Line
I want a feature, like when scrolling the timeline section show a horizontal live line which ups and down with scroll bar

An Anonymous User 2 months ago
design-panel
💬 Replo
Timeline Horizontal Line
I want a feature, like when scrolling the timeline section show a horizontal live line which ups and down with scroll bar

An Anonymous User 2 months ago
design-panel
💬 Replo
Reviewed
Import Shopify "Per-Unit Cost"
As far as I know, this is a fairly recent feature in Shopify that allows you to set the number of units in the item being sold. Shopify then calculates a cost per unit, whether it’s in oz. or items, lbs, etc. It would be really useful if we could have this information imported into replo as dynamic information so that we could add it to our templates. Thanks.

An Anonymous User 3 months ago
💬 Replo
Reviewed
Import Shopify "Per-Unit Cost"
As far as I know, this is a fairly recent feature in Shopify that allows you to set the number of units in the item being sold. Shopify then calculates a cost per unit, whether it’s in oz. or items, lbs, etc. It would be really useful if we could have this information imported into replo as dynamic information so that we could add it to our templates. Thanks.

An Anonymous User 3 months ago
💬 Replo
Removing "Discount Box" from Cart Section
As a brand who doesn’t ever run discounts or coupons, the discount box and apply button right above the Checkout button are a huge distraction for us. This would be a huge helpful to have this “discount box” editable and removable in the Replo AI product page builder… This is essentially the difference between us using Replo AI for all of our product pages and building our pages elsewhere on other platforms.

An Anonymous User 3 months ago
💬 Replo
Removing "Discount Box" from Cart Section
As a brand who doesn’t ever run discounts or coupons, the discount box and apply button right above the Checkout button are a huge distraction for us. This would be a huge helpful to have this “discount box” editable and removable in the Replo AI product page builder… This is essentially the difference between us using Replo AI for all of our product pages and building our pages elsewhere on other platforms.

An Anonymous User 3 months ago
💬 Replo
Native Event Access in "Run JavaScript" Interactions
It would be great having feature that exposes the native browser event object within Replo’s On Click → Run JavaScript interactions to allow developers to access critical data like event.target. Currently, because this object is inaccessible, users struggle to isolate JavaScript actions when a page contains multiple identical or duplicated sections, such as in A/B testing scenarios. By allowing the script to identify exactly which element was clicked, developers could use simple logic like.closest() to ensure actions are "siloed" to the correct container, preventing accidental triggers in hidden or duplicated sections. Implementing this change would eliminate the need for cumbersome global event listeners in Custom HTML blocks and enable the creation of truly portable, "smart" components that function reliably regardless of where they are placed on a page.

An Anonymous User 3 months ago
High Priority
💬 Replo
Native Event Access in "Run JavaScript" Interactions
It would be great having feature that exposes the native browser event object within Replo’s On Click → Run JavaScript interactions to allow developers to access critical data like event.target. Currently, because this object is inaccessible, users struggle to isolate JavaScript actions when a page contains multiple identical or duplicated sections, such as in A/B testing scenarios. By allowing the script to identify exactly which element was clicked, developers could use simple logic like.closest() to ensure actions are "siloed" to the correct container, preventing accidental triggers in hidden or duplicated sections. Implementing this change would eliminate the need for cumbersome global event listeners in Custom HTML blocks and enable the creation of truly portable, "smart" components that function reliably regardless of where they are placed on a page.

An Anonymous User 3 months ago
High Priority
💬 Replo
Show or Hide Content Based on Product Price
I would like a feature that allows me to show or hide specific text or blocks when a product price goes over a selected amount. This would help create dynamic messages such as free-shipping notices or volume-based benefits. It improves customization and makes the page more relevant for each user.

An Anonymous User 5 months ago
💬 Replo
Show or Hide Content Based on Product Price
I would like a feature that allows me to show or hide specific text or blocks when a product price goes over a selected amount. This would help create dynamic messages such as free-shipping notices or volume-based benefits. It improves customization and makes the page more relevant for each user.

An Anonymous User 5 months ago
💬 Replo