Skip to main content

How to Fix Listing Errors

Fix listing errors in Zentail: start on Listing Status, work down Top Fixes, and fill in values in Quick Edit.

Written by Dan Sugarman

Zentail shows you which listings aren't live on each channel, and which fixes would get the most of them live. This article walks you through fixing them, from Listing Status to a saved value. For what each status means, see Understanding, Managing, and Fixing Errors.

Step 1: Open Listing Status

In the top menu, go to Listing → Listing Status, then click the channel you want to work on. The bar at the top splits that channel's listings into Not Selling, Live, Needs Attention and Healthy.

Step 2: Start with Top Fixes

Top Fixes is a ranked list of the fixes that would get the most Not Selling listings live on this channel. The fix that frees the most listings comes first, so work down from the top.

Each row shows:

  • Fix: what to change.

  • What it means: why the channel is holding these listings back.

  • Effort: how much work it is. For example, one answer for your whole account, or a value for each SKU.

  • Can go live: how many Not Selling listings could go live once you make this fix.

There are three kinds of fix:

  • A catalog value. Click Open in QuickEdit to fill it in (step 3).

  • A SMART Type to assign. This also opens in Quick Edit.

  • A step outside Zentail, usually in the channel's seller tools. These rows show Help article and View SKUs instead.

The card shows your top 5 fixes. Click See all fixes to see the rest.

The lines under the list account for Not Selling listings that no fix in the list covers:

  • "aren't sent: product data is off" means Zentail isn't sending product data to that channel. Click the channel name to turn it on in account setup.

  • "Not in a fix" counts listings with an error no fix here clears (see step 4), listings Zentail never submitted (see Never Listed in Which statuses mean a listing isn't live), and listings waiting on the channel.

Note: "Can go live" is what this fix unblocks. A listing can still wait on another error or on the channel's own review.

Step 3: Fix it in Quick Edit

Click Open in QuickEdit on a fix. Quick Edit opens with just the SKUs that fix affects, and just the columns you need to fill. Cells with an error are outlined.

Enter the value in each cell and save. Zentail resends the products to the channel on its own.

Note: Zentail resends the product automatically after you save. Update & Push is just the fastest way to check one product.

If AI Suggestions has proposed a value, accepting it writes that value to your catalog. The listing goes live only once the channel accepts it.

Step 4: Fix errors no Top Fix covers

On the channel's Listing Status page, find a status row with an Attribute errors button, such as Listed with Attribute Error. Click it to see which attributes are failing, and how many SKUs each one affects.

  1. Tick the attributes you want to fix. They all start ticked.

  2. Click Fix in Quick Edit. Quick Edit opens with just the SKUs failing on those attributes.

To see the values the channel accepts, pick a single product type in the Product type filter at the top of the page, then click Download valid values.

Fixing one product at a time

To work on a single SKU, open the product in your catalog and click Errors in the product's sidebar to see its errors on each channel. Click the wrench icon next to an error. It opens the product's catalog edit page, scrolled to the attributes that error names. Values you enter there go to every channel. To send a different value to just one channel, see Listing Attributes and Overrides.

If New screens is switched on in the top bar, the product opens in a side panel instead. Click Open the old product page to reach the Errors tab.

Common required attributes that cause listing failures

Depending on your product's category and the channel you're listing to, different attributes may be required. Some of the most frequently missing ones include:

  • Label Image — Required for many categories, especially in Health & Beauty on Walmart. You must provide at least one valid label image URL.

  • Category-Specific Product Type — Many channels require a valid value from a predefined list (e.g., a specific "type" field for your product category).

  • Ingredients Statement — Required for consumable or personal care products.

  • Key Features / Bullet Points — Required for most categories across major channels.

  • Manufacturer / Brand — Must be filled in and match what the channel has on record.

  • Shipping Weight / Package Weight — Missing weights can cause channels to reject item setup.

  • Unit Count / netContent — This is a required field on Amazon and Walmart for most products.

Use Listing Prep to find valid values

For category-specific fields, channels often accept only values from a predefined list. Go to Listing → Listing Prep to look up the valid values for your product's category before entering them.

Important: if you can't find the attribute you're looking for, select All. Some attributes are only required depending on other data you send, so Only Required doesn't show them.

Why am I also seeing pricing and inventory errors?

Pricing and inventory sync errors are often downstream of product data errors. Channels won't sync price or inventory for an item that hasn't been fully set up yet. Fix the product_data errors first — once the item is live on the channel, pricing and inventory errors typically resolve on their own.

If they persist after the item is set up, check that your pricing rules and inventory are configured correctly in Zentail for that channel.

Still seeing errors after making changes?

If you've filled in all the required fields but errors persist:

  • Double-check that all attribute values are from the channel's approved list — use Listing Prep to verify

  • Make sure any image URLs are publicly accessible

  • Check for duplicate UPCs or EANs across multiple SKUs in your catalog — each barcode should only be used by one SKU

  • Reach out to Zentail support and share the full error text — this helps pinpoint the exact field causing the issue

Did this answer your question?