Definition sync
Pull every metafield definition your store already has — products, variants, collections and customers — straight from Shopify. Re-sync any time you add one.
Metafields
Metafields you can finally see all of
Fieldra pulls every metafield definition Shopify holds for your store into one searchable list, lets you describe a change across products, variants, collections or customers, and answers the question the admin never does: exactly how many resources match, and what each one holds right now.
- Every definition Shopify holds for your store, in one list
- Target products, variants, collections or customers
- A real match count and real current values, from live data
This release reads your store and saves the operations you build against it — it does not write metafield values, and rules do not fire on their schedule yet. Fieldra also has no Shopify App Store listing yet, so the link above goes to XCO Agency's published apps.
The problem
Metafields are the part of Shopify you cannot see all of
The admin shows one resource at a time. Past a handful of products there is no view that answers the two questions that matter: which definitions exist, and what is actually in them?
No single list of the metafield definitions a store has accumulated
One sync pulls every definition Shopify holds for your store into a searchable list
Pickers so long that the four fields your team actually uses are buried
Enable and pin the ones you work with, and they become the only ones the editors offer
Guessing how many products a filter would really hit before committing to anything
A preview that asks your store for the exact number of matching resources
No way to check what a field holds across live resources without opening them one by one
Real sample rows: each resource's current value beside the value your operation specifies
Features
What Fieldra does today
An embedded admin app that reads the Shopify Admin API. Nothing is added to your theme and nothing runs on your storefront.
A shortlist you control
Turn on the definitions you actually work with and they become the only ones the editors offer. Turning one off just hides it from Fieldra; your store data is untouched.
A change, described once
Pick the resource type, narrow it with Shopify's own search syntax — tag:sale, vendor:Nike, status:active — then choose the metafield and whether to set or clear it. Fieldra saves that operation so you can come back and edit it.
A preview built from live data
Fieldra asks your store for the exact number of matching resources and shows real rows: the resource, the value it holds now, and the value your operation specifies.
Read-only, by construction
This release writes nothing back to Shopify. Every screen reads your store and saves Fieldra's own records, so no preview can turn into a change you did not intend.
Operations you can revisit
A saved operation keeps its resource type, filter, metafield and action. Edit it, or delete it, without rebuilding the whole thing from the first step.
How it works
Three screens to a change you can size
The onboarding checklist walks a new install through exactly these steps.
Sync your definitions
One click pulls every metafield definition Shopify holds for your store into Fieldra. Until you do, the rest of the app has nothing to work with.
Choose what you work with
Enable the definitions that matter and pin the ones you reach for daily, so the pickers in the editor stay short instead of listing everything.
Build an operation and preview it
Pick the resource type, the optional filter, the metafield and the action. Fieldra returns the live match count and real before-and-after rows, then saves the operation.
Use cases
What merchants reach for it for
Taking stock after a migration
An import or an agency handover left definitions nobody on the team created. Sync once and read the whole list, instead of hunting through Settings one namespace at a time.
Sizing a change before you commit
How many products really match tag:sale and carry that field? The preview answers with a count from your store, not an estimate from a spreadsheet.
Spotting a bad import
Point an operation at the metafield a migration touched and read the sample rows — the value sitting on real resources right now, beside what you meant it to be.
Making the pickers usable
A store with hundreds of definitions gets a shortlist of the dozen a team actually edits, pinned to the top of every picker.
Pricing
Three tiers, none of them live
These are the plans Fieldra ships in its config. There is no App Store listing, so nothing is billable — and nothing is gated either: the app enforces no per-plan limit anywhere today, so listing one here would be selling something that does not exist.
Free
Free
Where every install sits today, with nothing withheld.
Pro
$9.99/month
A configured price point. No limit in the app separates it from Free.
Advanced
$19.99/month
The top tier in the config. It unlocks exactly what Free unlocks.
FAQ
Questions worth asking first
Can I install Fieldra today?
Not from the Shopify App Store — Fieldra does not have a listing yet. The apps XCO Agency has already published are on its partner page, and Fieldra will join them there once its listing is live.
What can it actually do right now?
It syncs your metafield definitions from Shopify, lets you shortlist and pin the ones you use, and builds an operation you can preview against live data — the true match count and real rows showing each resource's current value. What it does not do is apply that operation: writing metafield values is the job of a backend service that is not deployed, so an operation you run stays in progress and nothing on your store changes.
Do the automation rules run on their schedule?
No. You can build a rule, give it a recurring UTC schedule or your own cron, pause and resume it, and Fieldra records the next run it would have — but nothing fires it. The same backend that would apply a bulk change would run a rule, and it is not deployed. The builder ships so the rules are ready the day it is; this page does not sell them as working.
Which resources can it read and target?
Products, product variants, collections and customers. Those are the resource types the bulk editor and the rule builder target, and they match the product and customer access the app asks your store for.
How do I narrow which resources an operation covers?
With Shopify's own search syntax in the filter field — tag:sale, vendor:Nike, status:active. Leave it blank to cover every resource of that type. Variants are the exception: Shopify does not let them be filtered, so a variant operation covers every variant in the store.
Does it add anything to my theme?
No. Fieldra is an embedded admin app and works entirely through the Shopify Admin API. There is no storefront script, no theme snippet, and nothing to remove from your theme later.
What happens to my metafields if I uninstall?
They stay exactly where they are. Metafield values live on your Shopify resources, not in Fieldra — and this release never writes them in the first place. Uninstalling ends the app's access and removes its own records, and leaves every value on your products, variants, collections and customers untouched.
See your metafields before you change them
Fieldra is built and running as a read-only view of your metafields. Its App Store listing is not live yet — in the meantime, XCO Agency's published Shopify apps are one link away.