Skip to main content

How to find and fix listing errors in the new screens

Find a product's listing errors, fix them in one click or in bulk, and see what Zentail last sent.

Written by Matthew Thomas

When a channel rejects or warns about a product's listing, the new screens show the error next to the value it is about, and open the right editor in one click. This article covers where errors appear, how to fix one product or many, why an error can stay after you fix it, and the Debugging tab, which shows what Zentail last sent.

A storefront is one connected sales channel account, such as "Amazon US". You need New screens turned on. See How to turn the new product screens on or off.

Where errors show

  • Product panel. Each storefront row has a red count of its blocking errors. A variant chip with an orange dot has errors. A number on a Catalog section counts attributes there that need fixing.

  • Status symbol. Hover a storefront's symbol. Its card lists open errors and offers Fix in Errors.

  • Errors tab. The full list for one storefront. The tab shows a count of its blocking errors.

  • Listing preview. A mark beside each value that has an error.

  • Catalog view. A badge on the storefront's logo, on each attribute row that has an error.

  • Buyable switch. Before you make a SKU Buyable, Zentail lists the blocking errors the storefront may reject it for again.

  • Quick Edit. Needs you > With errors in the views sidebar lists every product with errors.

The Errors tab

Open the product's panel, click a storefront, and open Errors. Errors are split into Blocking · N and Warnings and notices · N. A blocking error stops the listing. A storefront with none says "No errors on <storefront>."

Each error shows:

  • the message;

  • the attribute it is about, by name, or "Listing level" when it is about the whole listing;

  • its source: "From <storefront>", "From Zentail's checks" or "Source unknown";

  • "Sent:" with the value Zentail sent, and "Allowed:" with the values the channel accepts, when known;

  • "First seen" and "Last seen". Hover for the exact time.

Show the channel's raw response shows the channel's own wording. Errors from <data type> sends opens the Debugging tab at that send.

Fix one error

  1. On the error, click Fix.

  2. An editor opens on the value this storefront sends. If the storefront has its own override, you edit the override. Otherwise you edit the catalog value. An override is a value set for one storefront that replaces the catalog value there. See Catalog values and overrides.

  3. Change the value and save.

Zentail saves your fix at once. The error stays until the channel checks again: "Saved. This error stays until <channel>'s next check or send picks up the new value." The list keeps checking every 15 seconds for 3 minutes, and updates by itself.

Relist a locked eBay listing

eBay locks the sizes of a listing it moved from its older format, and refuses every change to it. Ending the listing and relisting it is the one fix eBay supports. On some accounts, the first error of this kind on the Errors tab has a Relist on eBay button beside Fix and Fix in Quick Edit. Ask support to turn it on.

  1. Click Relist on eBay.

  2. Read "End this eBay listing and relist it?". It warns that the current listing ends and can't be brought back, and that the new listing gets a new eBay item number, so links, ads and promotions that point at the old one stop working. It also says the sold count and watchers don't carry over (your seller feedback stays), that sizes out of stock or archived are left off the new listing, and that if the relist fails part-way the listing can stay off eBay until it is fixed.

  3. Tick "I understand this can't be undone", then click End and relist.

The page then shows progress, such as "Relist requested. Zentail is checking the listing before ending anything.", "Ending the listing on eBay…" and "The old listing has ended. Publishing the new one on eBay…". It ends with "Relisted on eBay as item <number>." If eBay would refuse some values on the new listing, Zentail lists them and says "Nothing was ended." Fix them, then relist again. If you see that Zentail stopped checking, the relist keeps running. Reload the page later and the Errors tab shows the result.

Fix many products with the same error

Click Fix in Quick Edit on the error. Quick Edit opens in a new tab, filtered to every product with this error. Fix them there, in the grid. If nothing opens, you see "Your browser blocked the new tab." Allow pop-ups for Zentail and try again.

Error marks on the Listing preview

On the Listing tab, each open error sits beside the value it is about:

  • a red circle with "!" for a blocking error;

  • an amber triangle for a warning or notice.

Hover or focus the mark to read the error, such as "Color: error — …". The mark then turns into the edit pencil. Click it to open the same editor as Fix.

Errors that no value on the preview can take are listed at the top under "Errors not on a field · N". Each has See in Errors.

Error marks in the Catalog view

In the Catalog view, a storefront's logo on an attribute row carries a red or amber badge when that storefront has an error on the attribute. Click the badge to open the row's editor. If the row can't be edited there, the badge opens that storefront's Errors tab. Errors that no row can take are listed under "Errors not on a field · N" at the top. See Error marks on storefront logos.

Why an error takes time to clear

Your fix lands in Zentail straight away. The channel decides when the error clears. It clears after the channel's next check, or after Zentail's next send to it. On Amazon and Walmart, Zentail sends in feeds, and a feed's result applies to every SKU in it.

Shelved and archived products

While a SKU is Shelved on a storefront, or archived, Zentail doesn't send its product data or pricing there. Those errors aren't re-checked, so they may be out of date. The Errors tab says "While this SKU is Shelved, product data and pricing aren't sent…". In the Catalog view, the error reads "(not re-checked while this SKU is Shelved)" or "archived". Inventory errors are still checked.

Listing submission on the Listing tab

Above the preview on the Listing tab, the Listing submission card shows the last product data send.

  • A badge shows the channel's answer, or Listing off when listing data is off for this SKU.

  • Below it, "Listing data" (or "Not sending"), the steps the send reached, and a note such as "Live on <storefront> since <time>." or "<storefront> rejected it."

  • When the send was rejected or is still waiting, and there are blocking errors, See the error (or See the N errors) opens the Errors tab.

It reads the same row as Product data under Last sent on the Debugging tab, so the two agree.

The Debugging tab

The Debugging tab shows what Zentail last sent this storefront, and lets you send again. It replaces View Feed Messages on the classic product page.

Last sent

Last sent has one row for each kind of data: Product data, Pricing and Inventory. Each row shows:

  • how far the send got: Built, Prepared, Sent, then Accepted, Rejected, Waiting or No answer;

  • a result: "Accepted", "Rejected", "Pending", "Not sent", "No answer" or "Submission error";

  • when nothing is sent, the reason, for example "Not sending · Shelved", "SKU archived" or "listing data off";

  • for inventory, when it last sent out of stock.

View IDs, request and response shows the submission ID, the Zentail SKU, product and feed IDs, and the exact request and response. See the error (or See the N errors) jumps to the Errors tab. It counts only blocking errors, the same as the count on the Errors tab, so warnings are left out.

Send now

Changes go out automatically when you save, so you don't need to send by hand. To send again anyway:

  1. Under Send to <storefront> now, click Send now….

  2. In "Send <SKU> to <storefront>?", choose What to send.

  3. Under Which SKUs, choose Just <SKU> or Every SKU on this listing.

  4. Click Send.

You then see "Sent to <storefront>", "Still sending. Stay on this page." or "No answer yet…". Some channels keep no record of a send, so Zentail can't confirm it. An archived SKU can't be sent: "This SKU is archived. Unarchive it to send it."

Walmart shows a different quantity than Zentail: check the last send and resend

If Walmart shows a different quantity from Zentail, first check what Zentail last sent. If that was right, send it again from the product's Debugging tab. This section covers both steps, and what to check when Walmart changes the number again afterwards.

Step 1: Check what Zentail last sent

  1. Open the product, then click the Walmart storefront.

  2. Open the Debugging tab.

  3. Under Last sent, find the Inventory row. It shows how far the send got, and whether Walmart accepted it.

  4. Click View IDs, request and response to see the quantity in the request.

If the request holds the quantity you expect and Walmart accepted it, Zentail did its part. Go to step 2.

If the row says "Rejected", "Not sent" or "No answer", or the quantity is wrong, fix that first. Check your stock in Zentail and that inventory is on for this SKU. See How to Audit your Inventory in Zentail.

Step 2: Send the quantity again

  1. On the Debugging tab, find the card called Send to Walmart now.

  2. Click Send now….

  3. Under What to send, tick Inventory and clear the rest.

  4. Under Which SKUs, choose the one SKU, or Every SKU on this listing.

  5. Click Send.

The card then shows "Sent to Walmart". If it says "Still sending", stay on the page. An archived SKU can't be sent. Unarchive it first. For the other parts of this tab, see How to find and fix listing errors in the new screens.

Walmart usually applies a quantity within minutes. Look at the product on Walmart again after that.

If Walmart changes the number again

Zentail only writes the quantity it holds, and only when that quantity changes or you send it. If Walmart shows another number later, something else may be writing stock to your Walmart account. It may be another app connected to Walmart, or someone editing stock in Walmart Seller Center.

Walmart sellers can also have more than one fulfillment location, which Walmart calls a ship node. Zentail sends stock to your default location only. Stock on a second location was put there by something else.

To check:

  • In Walmart Seller Center, look at the product's inventory for each fulfillment location.

  • List the apps connected to your Walmart account that can update inventory.

  • Choose one tool to own Walmart stock. Turn off inventory updates in the other, then send again from the Debugging tab.

If the numbers still disagree, contact support with the SKU and what you see on the Debugging tab.

Frequently asked questions

Where do I see listing errors for a product?
In the product panel, click the storefront and open the Errors tab. Errors are split into Blocking and Warnings and notices.

How do I fix an error?
Click Fix on the error, change the value, and save. It clears after the channel's next check.

I fixed it, but the error is still there.
Zentail saved your fix. The error stays until the channel re-checks or Zentail next sends. The list updates by itself.

What are the red and amber marks on the preview?
Red is a blocking error and amber is a warning or notice on that value. Click the mark to fix it.

How do I fix lots of products with the same error?
Click Fix in Quick Edit on the error. It opens Quick Edit filtered to every product with that error.

How do I see what was sent to Amazon, like the old feed messages?
Open the storefront's Debugging tab and click View IDs, request and response.

How do I resend a listing now?
On the Debugging tab, click Send now…, choose what to send and which SKUs, then click Send.

What is the Listing submission card?
It sits above the preview on the Listing tab and shows the last product data send and what the channel answered.

My eBay listing is locked and every change is refused. What can I do?
If your account has it, click Relist on eBay on the error. It ends the listing and publishes a new one with a new item number.

Where did View Feed Messages go?
It's now the Debugging tab on each storefront.

Do I still need Update & Push?
No. Changes go out automatically when you save. Use Send now… only to resend.

Walmart shows 0, but Zentail has stock. What do I do?
Check Last sent on the Debugging tab. If Zentail sent the right quantity, click Send now… and send Inventory again.

Why does Walmart show a different number after Zentail sent the right one?
Another app or person may be changing your stock on Walmart. See "If Walmart changes the number again".

Did this answer your question?