Your store may know which fabric a garment uses, yet your trading report still treats every garment alike. Shopify Sidekick analytics can now answer questions using supported metafields and metaobjects alongside sales metrics. That gives merchants a practical way to investigate assortment decisions without starting every question with a spreadsheet export. The payoff depends on the data underneath: here’s how we’d prepare it, test the answers and decide which findings deserve action.
What changed in Shopify Sidekick analytics?
Shopify’s November 17 update says Sidekick can now use store metafields and metaobjects to answer analytics questions. Shopify gives fabric, supplier and the designer linked to a product as examples of details merchants can explore alongside sales metrics.
There’s a specific requirement: Sidekick can use metafields with Filter or group data in Analytics turned on. Shopify also says some metafield types and reports aren’t supported yet. Don’t read the announcement as a promise that every custom field in your store is immediately reportable.
This is a useful, concrete development within the data and AI priorities covered in Shopify’s DTC growth trends overview. For a merchant, the opportunity is to ask commercial questions using the product distinctions that matter to the business, rather than accept only the categories in a default report.
Our view: start with a buying decision, not an AI demonstration. A fabric-level breakdown is useful if it helps you investigate a reorder. An impressive answer that nobody checks or acts on is another reporting distraction.
Metafields and metaobjects: the distinction that matters
A metafield stores custom information on a Shopify resource. A product might have a metafield for its fabric or a reference to a designer. These fields let you record information beyond Shopify’s standard fields in a structured form.
A metaobject groups related custom information into a reusable record. A designer record, for example, could hold details that several products reference. That differs from typing the designer’s name independently into each product description.
For analytics, consistency is the prize. If your team records the same fabric under several names, an analysis can split what should be a single group. If a field is empty on older products, the results may describe the recently maintained catalog better than the whole business.
Sidekick makes those fields easier to query. It doesn’t relieve the merchandising team of deciding what the fields mean.

Prepare Shopify Sidekick analytics around a real decision
Choose a question with an owner
Start with something a named person needs to decide. A buyer could ask which fabric groups generated total sales last quarter before reviewing a reorder. A merchandising lead could investigate sales by designer before changing collection prominence.
Write down the decision separately from the query. “Review the cotton assortment before placing the next purchase order” gives the analysis a purpose. “Explore our custom data” doesn’t establish what a useful answer would look like.
Keep the initial request narrow. Specify the metric and time period, then add the grouping field. Shopify’s own example asks for total sales by fabric for the previous quarter. Treat that as a sensible starting shape, not proof that every variation of the question will work.
Check the field before enabling it
Find the relevant metafield definition and check whether the analytics setting is available. If it is, enable Filter or group data in Analytics. If your field type or intended report isn’t supported, don’t spend the afternoon rewriting the same prompt. Check the current support limits and use an established reporting route instead.
Before relying on the result, review the field’s contents:
- Coverage: Is the field populated across the products included in the analysis, including older products?
- Vocabulary: Does the same material appear under different spellings or internal abbreviations?
- Meaning: Does “supplier” consistently mean the same business relationship, or does it sometimes mean manufacturer?
- Ownership: Who updates the field when product information changes?
Fix ambiguity before bulk cleanup. Combining “cotton blend” with “cotton” might make the report tidier while erasing a distinction your buyer needs. The goal is faithful classification, not a shorter list of values.
Test the answer before it reaches the buying meeting
A clear response can feel more trustworthy than a messy spreadsheet. That’s exactly why the first result needs checking.
Ask Sidekick for the breakdown, then inspect any report or supporting detail it provides. Confirm the sales metric and date range. Check whether filters exclude products you expected to see. Where those details aren’t clear, ask for clarification rather than assume the system chose your team’s usual definitions.
Compare the answer with a known Shopify report using equivalent settings. A total-sales question shouldn’t be validated against a net-sales report and declared wrong because the totals differ. Establish what each metric includes before comparing results.
Then examine products you know well. Does a garment appear in the fabric group you expect? What happened to products without a fabric value? If the grouped figures don’t reconcile with the comparable overall figure, investigate the gap before sharing a conclusion.
Historical interpretation deserves particular care. Ask whether a breakdown uses the product’s current custom value or a value preserved from the sale. The announcement doesn’t establish that behavior. If products have changed supplier or classification, verify the reporting behavior before using the output to evaluate historical performance.
We’d save the accepted query with its metric definition and validation notes. That gives the next person a repeatable question rather than a screenshot detached from its assumptions.
A fabric sales report is a starting point, not a reorder instruction
Consider a hypothetical apparel merchant comparing sales across fabric groups. Sidekick returns a breakdown, and cotton leads. The tempting conclusion is to buy more cotton.
But the result only establishes leadership on the requested sales measure. Cotton might also have had more products available or received more promotional exposure. Another fabric might have spent much of the period out of stock. Revenue alone can’t resolve those explanations.
Use the breakdown to decide where to investigate:
- Compare the assortment behind each group. A broad range has more opportunities to generate sales than a narrow range.
- Review availability before interpreting weak sales as weak demand.
- Check discounting and product costs before treating revenue leadership as a reason to increase purchasing.
- Review returns where reliable data is available. A strong sales result can still lead to a disappointing commercial outcome.
These are follow-up analytical tasks, not a claim that Sidekick can answer all of them from the newly supported fields. Use your existing reports or other systems when the question exceeds supported analytics.
The useful decision might be to restore availability in an overlooked fabric, rather than expand the current bestseller. Better questions help expose that possibility; the merchant still has to judge the evidence.

Who should use this, and who should wait?
Sidekick is worth testing when your custom data describes meaningful commercial differences. Merchants with maintained fabric fields or consistent designer references have a clear starting point. The attraction is the ability to ask follow-up questions in the admin without commissioning a new reporting workflow for every idea.
Wait before using the answers for purchasing if your fields are incomplete or their meanings vary between teams. You can still test the feature, but label that work as validation. Don’t present an exploratory result as a settled recommendation.
Also keep established business intelligence workflows where they serve a different purpose. A finance model that joins purchase costs with warehouse charges needs more than a sales breakdown by product attribute. Shopify’s announcement doesn’t claim to replace those calculations.
We wouldn’t buy another analytics app solely to try this supported custom-data question. Test the native capability first. Equally, we wouldn’t remove a reporting tool because Sidekick produced a good answer during a demonstration. Judge each tool against the decisions it supports and the evidence it lets you inspect.
Make the result repeatable
Choose a field your team already maintains and a completed reporting period. Clean the relevant values, confirm support and run the question. Ask the person responsible for the commercial decision to review the output alongside the validation evidence.
If that works, document the approved field vocabulary and query. Give someone responsibility for keeping the data usable as products enter the catalog. If it fails, record whether the problem is unsupported functionality or poor source data. Those require different fixes.
The lasting benefit comes when a buyer can ask a precise question next month and understand why the answer changed. That’s a better test than how fluent the first response sounds.
Takeaways
- Sidekick now supports analytics questions using eligible metafields and metaobjects, with limitations on field types and reports.
- Enable the analytics setting on supported metafields and check the values before trusting a breakdown.
- Validate the metric and grouping against known reporting evidence.
- Use sales by product attribute to guide investigation, not as an automatic purchasing recommendation.
Sources
Want this handled for you?
We're a Shopify Premier Partner and this is the work we do every day: performance, CRO, and store builds that pay for themselves. Book a free store review and we'll show you the three fixes we'd ship first.
Frequently asked questions
Can Shopify Sidekick analyze metafields and metaobjects?
Yes. Shopify’s November 17 update says Sidekick can use supported metafields and metaobjects to answer analytics questions alongside sales metrics. Some metafield types and reports aren’t supported yet.
How do I enable metafields for Sidekick analytics?
Check the relevant metafield definition and turn on Filter or group data in Analytics where that setting is available. Then open Sidekick in the Shopify admin and ask a specific question using the field.
Can I use Sidekick to report sales by fabric?
Shopify explicitly gives total sales by fabric for the previous quarter as an example. Your fabric data must use a supported metafield with the analytics setting enabled. Check missing values and inconsistent fabric names before relying on the breakdown.
Why should I check a Sidekick analytics answer against another report?
A breakdown can mislead if it uses a different sales metric, unexpected filters or incomplete custom data. Compare it with a known report using equivalent settings, then inspect familiar products to confirm the grouping makes sense.



