---
title: "Listing Audit: Find What Each Channel Is Missing | SKU.io"
url: "https://www.sku.io/what-each-channel-listing-is-still-missing/"
description: "I argued one description was enough, then couldn't list on TikTok without its own. Why a listing audit should find gaps per channel, not check for matches."
published: 2026-11-03
---

[Marketplace Listings](https://www.sku.io/category/marketplace-listings/)

# Don't Match Your Listings. Find What Each Is Missing

By [Kalvin Mizzi](https://www.sku.io/our-story/) · November 3, 2026

![Don't Match Your Listings. Find What Each Is Missing](https://www.sku.io/_astro/gaps-per-channel.3JtPxv4X_Z1wAj6N.webp)

In July I put one of my own products on TikTok Shop, from inside SKU.io, with the dev team on a screen share. I run the brand and I help build the tool, so this was supposed to be the easy case.

It stopped at the first screen. One of the developers said the TikTok form wants a description, and the product I’d picked didn’t have one. SKU.io has no description column on the products table. I told him it would map to an attribute. He said that attribute was empty on this product. I said, “You can’t list it if it doesn’t have it,” which was my own bug report, delivered to myself.

Then I defended it anyway. “The reason why we don’t have a dedicated description is because it’s not really useful.” Amazon doesn’t take HTML in a description. eBay does. Every channel has its own length limit. So there is no single description that fits, and I’d rather each channel have an attribute of its own. I still think that’s right.

What I couldn’t do was see what TikTok wanted. I hit refresh, then hard refresh. The developer said the requirement showed on his screen. It never showed on mine, and nobody on the call found out why. I couldn’t list anything on TikTok until a field I had argued didn’t need to exist had something in it.

I had no list of what each channel still wanted from that product. I’d found out one blocked screen at a time.

The listing template is that list. A product gets a classification. The classification gets one template per sales channel. Each template names the fields that channel requires. A table then shows every product against every channel, and a cell is flagged where a required field is empty.

![A product-by-channel grid where each missing field is one flagged cell](https://www.sku.io/_astro/gaps-per-channel.3JtPxv4X_1M40PD.webp)

On October 6 I told a prospect what came after. I’d been cleaning my own catalog with an agent for a week or two, working down the flagged cells, and the last stretch was the night before and that morning. For weight and dimensions I told it to search my Gmail archive for any supplier who ever emailed them. Nothing there, then our Amazon listing. Nothing there, then the manufacturer’s site. It also pulled the certifications each channel wanted out of old manufacturer emails. Descriptions and images follow almost the same order: my database, then my listings on other channels, then the manufacturer’s site. Only if all of that comes up empty does it draft an email to the supplier, with a Google Sheet listing every data point I need so they answer once. By then the table showed no open gaps.

The weights are the part I’m not happy with. A weight from the manufacturer and a weight Amazon estimated sit in the same field and look identical. On that call I said “I think we need a new feature” that marks which is which. Until then, I know where a weight came from only because I remember.

A few weeks later someone asked whether SKU.io compares images and descriptions across sites to check they’re consistent. I said no, and why: “We don’t compare images because there’s different rules for each platform.” My Amazon, TikTok and eBay descriptions differ on purpose. A check that flagged the difference would flag work I did deliberately.

The table doesn’t read the text either. If a field has anything in it, it passes. I haven’t gone back through mine to see how many I’d stand behind.

Single-channel sellers don’t need any of this. A spreadsheet with a column per required field does the same job.

![Kalvin Mizzi, founder of SKU.io](https://www.sku.io/_astro/the-story-of-sku.BNjQHdxV_Z4P6NF.webp)

Written by

[Kalvin Mizzi](https://www.sku.io/our-story/) Founder, SKU.io

Kalvin has run his own multi-channel e-commerce business since 2008 and built the system behind it, which became SKU.io. He still gives every demo personally.

-   [LinkedIn](https://www.linkedin.com/in/kalvinmizzi/)
-   [X](https://x.com/kalvinmizzi)

## Keep reading

-   [Should I sell my brand on Amazon?](https://www.sku.io/should-i-sell-my-brand-on-amazon/)Dec 6, 2020
-   [Optimizing Google Shopping: Why you shouldn’t use shopping cart plugins to feed to Google Shopping.](https://www.sku.io/optimizing-google-shopping-why-you-shouldnt-use-shopping-cart-plugins-to-feed-to-google-shopping/)Sep 6, 2020
