Metafields Guru
Spełnia najwyższe standardy Shopify w zakresie płynności, łatwości użytkowania i korzyści dla sprzedawcy
Recenzje (246)
Zawęź
-
Według oceny
I chose Metafields Guru after reading its promises of “one-click bulk management,” “Excel-like automation,” and “Shopify Flow integration that speeds up work.” After using the app and exchanging several emails with the team, here is the reality:
1. No real automation – Every metafield/metaobject value still has to be typed or pasted manually. Filters help, but they don’t auto-populate or predict data.
2. Feature overlap with Shopify – Shopify’s free admin already lets me bulk-edit metafields in a grid, copy/paste across products, and automate assignments with Flow. MG adds no time-saving logic beyond what I can do natively.
3. Paid tiers ≠ extra value – The “Excel-like editor,” “advanced editor,” and credit-based bulk actions are just alternative UIs for tasks Shopify covers for free. The advertised productivity gain is missing.
Because the delivered functionality does not match the marketing claims, I’m requesting a full refund of my subscription and any unused app credits.
Recently, Shopify updated its review publishing process to let developers preview reviews before publication. Yesterday, upon seeing a negative review from a merchant who briefly used our app without contacting support, our dev team investigated if the merchant could've encountered any technical issues and confirmed everything was fine. After I reached out to the merchant, we had a constructive dialogue where he pointed out disappointment from unfulfilled expectations of AI-powered automation, which had never been advertised. We also discussed other automation-related topics, which, despite being raised and quoted by the merchant, couldn't be found on our resources. Today, Shopify published an edited version of the review with unjustified accusations of misleading marketing. It surprised the entire team and contrasted with the conversation in a support ticket, where we appeared to come to a mutual understanding. As a team behind the category-leading app, we constantly improve our product, are open to suggestions, and are down to help our users even with issues that do not relate to our product. At the same time, we value the reputation we earned over the past 6 years and can't let a misinterpretation affect it. Hopefully, the additional context makes the situation clearer for the community.
- Sasha
While the app seems like a fantastic idea, the app is too far from perfect. The app does not allow for a full hands-on trial. You are only limited to the “Free Version” that in the essence is a useless tier. In order to really test drive the app you will need to purchase a paid plan, oh wait your store has too many products so you’ll need to be on the top paid tier. Wow… $60.00 just to test an app… Yikes. Turns out the app was not successful at editing our metafields and has now filled in $0.00, now causing other issues. When trying to talk with support they are not addressing our real problem, they keep trying to blame the user for the issues as well as keep touting how wonderful the app is. Too bad to say the least… I would review some other apps before working with Metafields Guru (not). All in all, we tossed out $60.00, so a pretty good win for the developer I suppose.
Well, today is the day - our first negative review 🙃. For the sake of justice, I’d like to share more details about this situation.
The merchant reached out to us and reported an issue with the data they imported from a CSV file using our app. Upon further investigation, I discovered that the data was imported correctly. However, even though the data was correct in the backend, it was not getting displayed on the storefront. Usually, this indicates a theme problem, so I offered help with checking this theory. The merchant provided me with access to their store and I checked the source code of their active theme. Turned out that there was a piece of code that converted string metafields into numbers before displaying them on the product page. The problem was that said code expected values to be formatted in a very specific way. The merchant accidentally used a slightly different format while populating values in their CSV file, which resulted in the code being unable to process the data. I offered two different options for resolving the issue, and it looks like the merchant ended up using one of them. But the merchant was still upset about the situation, so they decided to keep this review. It's a shame that a third-party issue ruined the experience of using our app.
- Sasha