How to stop bad product listings from going live on your Shopify store
A customer bought a sofa based on the wrong dimensions. You refunded it, paid return shipping, and spent two hours on the phone with them. The product had no dimensions field, and your team didn't notice. Here's the system that catches that before it costs you.
Key Takeaways
- Incomplete product listings cost real money: returns, customer service time, Google Shopping feed errors, lost conversion.
- Every product can be scored 0β100% on completeness. Below your threshold = don't publish.
- The score isn't the point β the publish gate is. A score without consequences is just a dashboard.
- Apimio Quality Guard is the only completeness-scoring-with-publish-gate system in the Shopify mid-market.
Table of ContentsβΌ
- TL;DR
- Why "we'll just review every product" doesn't scale
- Completeness scoring: what it actually is
- The three stages of Quality Guard
- Stage 1 β Score
- Stage 2 β Impact
- Stage 3 β Fix
- The publish gate (this is the moat)
- π‘ Image Guard
- What changes when the publish gate is on
- How to set up Quality Guard the first time
- How this connects to the rest of your catalog ops
- FAQ
- Will Quality Guard block products that are already live on Shopify?
- Can different product categories have different completeness rules?
- What if I genuinely need to publish an incomplete product (e.g., pre-order)?
- Does this work for products with hundreds of variants?
TL;DR
Bad product listings cost you returns, support time, and conversion you'll never see. Apimio Quality Guard scores every product in your catalog 0β100% on completeness, surfaces what's missing, and (the part that matters) blocks incomplete products from going live until they meet your threshold. The score is the dashboard. The publish gate is the value.
A furniture brand published a new sofa to Shopify last spring. The product had two of three required images, a great description, and a price. The dimensions field was empty. The team didn't notice β the product went live, ranked on a couple of long-tail searches, and started selling.
Two months in, a customer ordered the sofa for an apartment with a 30-inch doorway. The sofa is 36 inches wide. It didn't fit. Return, refund, return shipping. Two hours on the phone with the customer, who was reasonable but unhappy. A Google review that mentioned "no dimensions listed." Eight similar future customers reading that review and going elsewhere.
Total cost of one missing dimensions field, conservatively: $400 in direct refund/shipping, $300 in support time, an unknown number in lost future conversion from the review.
And here's the thing β that field was empty for a knowable, fixable reason. The product was imported from a supplier file where the supplier listed dimensions as a string in the description ("L 84" x D 36" x H 32""), not as a structured dimensions attribute. The team imported the product, didn't notice, and published it.
Multiply this by every "almost complete" product in a catalog of 500β15,000 SKUs. That's the cost of running a Shopify catalog without a publish gate.
Why "we'll just review every product" doesn't scale
Every team that hits this problem first tries manual review. Person X eyeballs every new product before it publishes. It works for the first hundred products. It breaks at the first seasonal restock of 800.
The reasons it breaks are predictable:
- Manual review is the bottleneck. New product velocity is constrained by reviewer bandwidth.
- Reviewers miss things. The dimensions field was empty because someone scanned a product page that looked fine and didn't notice the blank.
- Standards drift. The reviewer who started caring about dimensions on month one stops caring on month four because they have eight other things to do.
- Reviewers don't scale to multi-store. Each store has its own publishing standard. One reviewer can't hold five standards in their head.
The fix isn't more discipline. The fix is a system that doesn't require discipline.
Completeness scoring: what it actually is
Apimio Quality Guard looks at every product in your Catalogue Hub and computes a completeness score from 0 to 100%. The score is based on:
- Whether required fields are filled in (title, description, price, weight, dimensions, materials, primary image)
- Whether recommended fields are filled in (alt text on all images, SEO metadata, variant attributes, lifestyle images)
- Whether the data is plausible (e.g., dimensions in expected ranges for the category, descriptions over 50 characters)
- Whether per-category required fields are present (a sofa needs fabric and dimensions; a candle needs scent notes and burn time β different categories, different rules)
You set the threshold. The default is 80% β products below that are flagged but can still publish. You can tighten this to 90% or 95% and block products below from publishing entirely.
The three stages of Quality Guard
Stage 1 β Score
Every product, every variant, scored automatically as soon as it's created or updated. The score is visible in the Apimio dashboard, in the Shopify connected app view, and in the product editor itself.
Stage 2 β Impact
A score alone is just a number. Quality Guard ties the score to commercial outcomes β return rates, Google Shopping feed errors, conversion data from your Shopify Analytics. You see not just "this product is at 65%" but "products at 65% have an above-average return rate; here's what they're missing."
This is where the score becomes actionable. Your team doesn't care about "low completeness." They care about returns and refunds and customer service time.
Stage 3 β Fix
From the Quality Guard interface, you can fix products in three ways:
- Edit one product at a time (the normal Shopify-like flow, but with the score visible and the missing fields highlighted).
- Bulk-fix across many products: "every product missing dimensions, open the editor for that field only, paste the data in, save all at once."
- AI fill: products that have structured attributes but no copy can be auto-enriched by Apimio AI. 120 products missing descriptions becomes one click and a wait of a few minutes.
The publish gate (this is the moat)
Scoring and fixing are useful. The publish gate is what makes the system actually save you money.
You set a rule: "Products below 85% don't go live on the storefront." Apimio enforces it. New products at 70% sit in a queue marked "incomplete." Bulk imports that include below-threshold products surface those products for review before any of them hit Shopify.
No competitor in the Shopify mid-market has this. There are scoring tools. There are quality dashboards. There is no other tool that scores and enforces a publish gate. That's what makes Quality Guard the moat. /features/quality-guard.
π‘ Image Guard
Image Guard is the sub-feature within Quality Guard that handles image-specific rules: resolution thresholds, count requirements per product category (a sofa needs at least four images; a candle needs at least two), alt text presence, and primary-image quality. Combined with Apimio AI Vision (Wave 2), this also handles alt-text generation at scale for catalogs with thousands of unaltered images.
What changes when the publish gate is on
In the first few weeks, your team notices: "fewer products are going live than I expected." That's the system working. The products that aren't going live are the ones that would have caused the returned-sofa moment.
Over the next quarter, three downstream effects appear:
- Return rate drops. The specific category of returns caused by incomplete data (wrong size, missing material info, surprise about product details) shrinks.
- Google Shopping feed errors drop. The Merchant Center stops flagging your products for missing required fields.
- Conversion rate rises on the listings that do publish. Completer listings convert better β partly because of trust, partly because the listings themselves answer more buyer questions.
How to set up Quality Guard the first time
After installing Apimio and connecting your Shopify store:
- Look at the initial score distribution. Most Shopify catalogs come in with 30β60% of products below 80% completeness. That's the baseline of what you've been silently publishing.
- Pick a threshold. 80% is the default; we suggest starting there and tightening to 85% or 90% once your team has worked through the initial backlog.
- Turn on the publish gate for your most important category first (your bestsellers, or your most-returned category). Confirm the gate is catching real issues before you turn it on globally.
- Schedule a weekly "quality clear" β 30 minutes where someone clears the queue of below-threshold products by either completing them or marking them archive.
- Once AI Wave 2 ships, turn on bulk AI enrichment for the long tail of missing descriptions and alt text. Most teams clear 80% of their below-threshold backlog this way.
How this connects to the rest of your catalog ops
Quality Guard doesn't live in isolation. It connects to every other product in the Apimio stack:
- Store Sync β quality scores follow products across every connected Shopify store. A product that passes the gate is published everywhere; a product that fails sits in the queue.
- Supplier Bridge β new supplier imports get scored immediately. The Friday import of 200 products immediately shows you which 40 are below threshold before any of them go live.
- Apimio AI β invoked from inside Quality Guard. The "fix" action on a missing description button generates one from the product's structured attributes in seconds.
- Trade Portal β dealers only see products that pass the gate. Your wholesale customers never see incomplete listings.
Scan your Shopify catalog free
FAQ
Will Quality Guard block products that are already live on Shopify?
No. Existing live products are scored but not retroactively unpublished. The gate applies to new products and to updates to existing products. You decide whether to tighten that policy over time.
Can different product categories have different completeness rules?
Yes. A sofa's required fields are not the same as a candle's. You configure required fields per category, and the score is computed against the category-specific rules.
What if I genuinely need to publish an incomplete product (e.g., pre-order)?
Quality Guard supports per-product overrides. You can mark a product "publish despite low score" with a required note. The override is logged so you can audit it later.
Does this work for products with hundreds of variants?
Yes. Each variant is scored individually. You can require that 95% of variants meet the threshold for the parent product to publish, or set per-variant rules.
Zahwa Nadeem
Marketing Manager at Apimio
Zahwa runs marketing and content strategy at Apimio, focused on the multi-store Shopify operators who buy the product. She writes about vertical-specific catalog operations β furniture brands managing 148 variants per sofa, fashion drops with seasonal SKU velocity, beauty brands needing ingredient-heavy SEO content, home dΓ©cor brands juggling artisan suppliers across D2C and wholesale. Her work is built on interviews with operating teams at brands shipping real product daily; the content reflects what merchants face on the ground, not what tools want to claim about them.
Ready to streamline your product data?
See how Apimio can help you manage product information across all your channels.