If you run a print-on-demand store with real order volume, you already live in Shopify Analytics. Metafields reports are the newest reason to stay there — and also the newest way to draw the wrong conclusion if you read them at face value.
What Shopify metafields reports actually are
A metafield is a custom field you attach to a Shopify record — a product, variant, customer, or order — to store data Shopify has no standard column for. For a POD seller that's often the supplier (Printify vs. Printful vs. Gelato), the blank brand, the garment material, the design collection, or a customer's VIP tier.
Until recently that data sat in your store doing nothing for analysis. Shopify changed that: as of its February 2026 analytics release, you can use metafields as dimensions and filters across Reports and Explore. The feature covers metafields on products, variants, customers, and orders.
In plain terms: you can now ask "revenue by supplier" or "orders by garment material" without exporting anything to a spreadsheet first. This is the same underlying idea as building a custom calculation report in Shopify — you're bending the standard reports around data that's specific to your store.
How to turn metafields on for reporting
The data doesn't show up in Analytics automatically. You flip it on per definition.
- Go to Settings → Custom data (Metafields and metaobjects).
- Open the definition you care about — say, a product metafield called "Supplier."
- Enable Use in Analytics on that definition.
- Rebuild your report and add the metafield as a dimension or filter.
Per Shopify's changelog, the "Use in Analytics" toggle only appears on supported metafield types. A free-text note field or a complex JSON metafield usually won't qualify; single-value types like a product reference, a single-line text list, or a number tend to work. If the toggle is missing, the type is the reason.
Three reports worth building first
For an operating POD store, three metafield cuts pay for the setup time almost immediately.
Revenue by supplier or fulfillment partner
Store a "supplier" metafield on each product and you can finally see what share of revenue runs through Printify versus Printful versus Gelato. That matters because each one has different base costs, ship times, and reprint rates — so the split tells you where your fulfillment risk is concentrated.
Sales by product line or design collection
Group orders by a "collection" metafield to see which design families carry the store. Most POD catalogs are heavily bimodal: a handful of designs do the volume and a long tail does almost nothing. A metafield dimension surfaces that without you eyeballing hundreds of SKUs.
Customer segments by tier or source
A customer-level metafield — VIP tier, acquisition source, wholesale flag — lets you filter sales reports to just that segment. This is a solid starting point for the kind of segmentation covered in these ecommerce analytics use cases.
Where metafields reports stop — and why it matters
Here's the part the setup tutorials skip. Every native metafield report is built on revenue and units. None of them know your costs. For a POD store, cost is almost the entire story.
Say you sell at a $31 average order value and you're running roughly 340 orders a month. A metafield report groups your revenue by supplier and tells you Supplier A drove $6,500 last month and Supplier B drove $4,000. Supplier A looks like the winner.
Now walk one average order through its real economics:
| Line | Supplier A | Supplier B |
|---|---|---|
| Revenue (AOV) | $31.00 | $31.00 |
| − Blank + print (COGS) | −$14.00 | −$10.00 |
| − Shipping | −$5.50 | −$4.50 |
| − Payment processing (say 2.9% + $0.30) | −$1.20 | −$1.20 |
| − Pick/pack | −$1.00 | −$1.00 |
| = Contribution before ads | $9.30 | $14.30 |
(The line items above are example assumptions for this store, not published rates.) Supplier B earns you $5.00 more per order even though it posts less revenue. A metafield report ranks them the opposite way, because it can only see the top line. Multiply that $5.00 gap across a few hundred orders a month and the "losing" supplier is quietly funding the business.
The same blind spot hits every other cut. Revenue by collection tells you nothing about which collection survives ad spend. A VIP segment can be high-revenue and low-margin if those buyers only convert on discounts. This is the core limitation third-party reporting apps are built to patch — even Mipler's own metafield reporting page frames native metafield use in reports as "limited" and hard to analyze or export.
Adding the profit layer
To make metafield segments trustworthy, you have to pull cost data that doesn't live in Shopify at all. Your true per-order cost sits across your supplier (the blank and print charge), the carrier (shipping), your processor (fees), and — the biggest line for most POD stores — your ad platforms.
There are three ways to close that gap:
- Spreadsheet export. Export the metafield report to CSV, pull your Printify/Printful invoices, pull your Meta and Google spend, and reconcile by hand. It works, but it's a monthly afternoon and it's stale the moment you finish.
- A reporting app. Tools like Mipler or Report Pundit can merge cost columns into metafield-grouped reports and schedule exports. This is real automation of the math — it's still you reading a report and deciding what to do.
- An AI employee. This is where PodVector AI fits. Victor is an AI employee — not a dashboard and not a report — that connects your live data and does the profit math for you.
Victor connects Shopify (full store ops), Meta Ads, Google Ads, Printify, Printful, Gelato, and Klaviyo, then computes true per-order profit across all of them. He can deliver the resulting reports straight to your Google Drive. So instead of ranking suppliers by revenue, you can ask "which supplier actually earns the most per order after print, shipping, and ads?" and get the Supplier-B answer — the right one — without exporting anything.
Victor also drafts approval-gated customer-support email, and every write action he takes waits for your approval before it executes. Nothing happens to your store without your sign-off.
Metafields reports vs. a profit view, side by side
To keep it honest, here's what each approach can and can't tell you.
Native metafield reports answer which segment sells — revenue and units by supplier, collection, material, or tier. They're free, built in, and fine for spotting your long tail. They cannot tell you which segment earns, because they never see cost.
A profit view answers which segment earns — contribution and margin per order after COGS, shipping, fees, and ad spend. It requires pulling data from outside Shopify, which is exactly the work an ecommerce business intelligence setup is meant to handle. If you want to go deeper on reading those post-cost numbers, this breakdown of ecommerce performance analytics walks through the metrics that matter once cost is in the picture.
The two aren't rivals. Use metafields to define the segments you care about; use a profit layer to rank them correctly.
Want Victor to compute true per-order profit across your store, ad accounts, and POD suppliers? Start with PodVector AI.
FAQs
Do metafields reports work on every Shopify plan?
Metafields as dimensions and filters rolled out across Shopify Analytics, but the depth of custom reporting you get depends on your plan tier — higher plans unlock more report customization. The "Use in Analytics" toggle itself shows up per supported metafield definition regardless, so start by checking the definition type before assuming it's a plan limit.
Why doesn't my metafield appear as a reporting option?
Almost always because its type isn't supported. Per Shopify's release, the "Use in Analytics" option only surfaces for supported metafield types, and even then only after you enable it on that specific definition in Settings → Custom data. Free-text and complex JSON metafields typically won't qualify; single-value reference, text, and number types usually will.
Can metafields reports show me profit by supplier?
No. They show revenue and units by whatever metafield you group on, but they have no access to your blank cost, print fee, shipping, processing, or ad spend. To get profit by supplier you have to merge in cost data from outside Shopify — through a spreadsheet, a reporting app, or an AI employee like Victor that connects those sources and computes it for you.
Are metafields reports enough, or do I need a third-party app?
For spotting which segments carry volume, native reports are enough. The moment you need to know which segment is actually profitable — after COGS, fulfillment, and ads — native reporting stops short, and you'll reach for either a reporting app or an AI employee that pulls the cost side in automatically.
How are metafields reports different from ShopifyQL?
ShopifyQL is the query language underneath Shopify Analytics; once you enable a metafield for analytics it becomes a dimension you can query in ShopifyQL as well as use in the point-and-click report builder. Metafields reports are the friendlier surface over the same data — same revenue-and-units ceiling, same missing cost layer.
What metafields should a POD store set up first?
Supplier and product line on products, and a tier or acquisition-source field on customers. Those four cuts cover the questions most operators actually ask — where fulfillment risk sits, which designs carry the store, and which customers are worth keeping — and they're the same fields a profit layer needs to rank by margin later. If you plan to automate these reports to email, defining clean metafields now saves rework.