When a marketplace can't accept one of your items, or Acenda finds a problem before sending it, the issue appears in Item Issues. This page shows every listing problem across all your sales channels, so you can see which SKUs are affected, what's wrong, and fix them one at a time or in bulk.
Where to find it: In the sidebar, under CHANNELS, click Item Issues. This page replaces the old Suggested Fixes page. You can also see the issues for a single item on that item's Channel Status tab.
Understanding error sources
The Source column tells you where each issue came from. Knowing the source helps you decide how to fix it.
Integration: Acenda found the problem before sending the item, usually a required marketplace field that is empty (for example Required field 'Package Weight' value missing). Acenda can't send the item's listing to that marketplace until these are fixed. š
Channel: The marketplace itself rejected or flagged the item (for example Target+ MINOR_DATA_VALIDATION: Item is missing required fieldā¦). These can appear when you first list an item, or later on a live item if the marketplace changes its requirements.
Channel Price, Channel Inventory and other channel sources: The marketplace rejected a price, stock or promotion update rather than the listing itself.
Step 1: Find the items with issues
In the sidebar, under CHANNELS, click Item Issues.
Narrow the list with the filters at the top:
Search Products: Pick ID or SKU from the small menu inside the box, then type a product ID or SKU.
Subscription: Show issues for one sales channel only.
Error Source: Show only one type of issue, such as Integration or Channel.
Click a column heading (Product ID, Date, Type, SKU or Source) to sort by it. Click it again to reverse the order.
To work in a spreadsheet, click Export CSV. The file includes every issue that matches your current filters, not just the page you're viewing.
Tip: reading the CSV. Sort by subscription_id (the sales channel) and then error_source to group your work. attribute_path shows which field is missing or wrong (or the type of marketplace error), and error_message gives the details. The file also includes sku, product_id and channel_name.
Step 2: Fix the issues
You can fix issues in bulk with a spreadsheet, or one item at a time in the admin.
Fix many items at once
For many SKUs, the fastest option is usually a Super Template: you download your item data with the marketplace's fields, fill in the gaps in a spreadsheet, and import it back in one go. Imports accept only .xlsx or .csv files. See How to Generate and Import a Super Template for the full steps.
Fix one item
On the Item Issues page, click the Product ID on the issue's row to open the item. You can also go to CATALOG ā Items, search for the SKU and open it.
Open the Channel Status tab. It shows each sales channel the item is mapped to, its issues on that channel, and the value Acenda sends for each marketplace field. For a full tour, see What is Channel Status?
Decide where to make the fix:
To fix it for every channel: Open the Details tab and find the field (use Ctrl+F or Cmd+F). Marketplace-specific fields are under Additional Attributes. Click the pencil icon āļø, enter the correct value, then click the disk icon š¾ (Save Changes). You'll see an Updated message.
To fix it for one channel only: On the Channel Status tab, click Override value next to the field. In the Manual Override window, enter the value (and a reason if you like), then click Apply Override.
Not sure what value the marketplace expects? Here's how to find the allowed values for a marketplace field.
Wait for the next sync. Integration issues usually clear once Acenda re-checks the item. Channel issues clear only after the marketplace accepts the updated listing, which can take longer while it reviews the change.
Important: A manual override replaces the value for that one channel and keeps doing so even if you later change the item's catalog data. You can see all your overrides under CATALOG ā Attribute Overrides, and remove one from the item's Channel Status tab with Undo manual override.
Get AI suggestions (beta)
Under CHANNELS, Item Issues (AI) shows the same issues grouped by sales channel, with values suggested by Acenda IQ where it has one. Filter by Channel, Source and Status (Unresolved, Pending, Resolved or Rejected), then accept or reject each suggestion. Always review a suggestion before you accept it. For the full walkthrough, see Getting Started with Acenda IQ: AI Suggested Fixes.
Common errors and how to fix them
"Required field 'ā¦' value missing": The marketplace needs this field and it's empty for this item. Fill it in on the Details tab, add an override, or include it in a Super Template. If you're sure you filled it in, check Mapped from on the Channel Status tab. The channel may read the value from a different field than the one you edited.
"Related SKUs have Error: ā¦": The parent item is held back because the variants listed in the message have their own issues. Fix the variants and the parent clears with them. Target+ shows the reverse as "This field is inherited from its parent and has errors": fix the parent item.
"Item is missing required fieldā¦" or "Attribute ā¦ is not valid": The marketplace wants a value from its own list. Check the field's allowed values (see the link in Step 2) and use one exactly as written.
Target+ "Item may not align with Target's merchandising strategy": See Troubleshooting Target+ Error: "Item may not align with Target's merchandising strategy.".
Target+ "Barcode released after 60 days": See Resolving Target+ Error: DATA_VALIDATION (Barcode Released After 60 Days).
Target+ "removed due to prolonged out-of-stock inventory": See Troubleshooting Target+ Error: "Item removed due to prolonged out-of-stock inventory".
Codes like "MCM-04000" or "MCM-04012" (Mirakl marketplaces such as Lowe's, Kohl's or Macy's): The message lists the specific fields the marketplace rejected. Fix each one it names, not just the first.
"Unmanaged" in the Product ID column: The marketplace reported an issue for a SKU Acenda can't match to an item in your catalog. Search for the SKU under CATALOG ā Items. If the item uses a different SKU on that marketplace, add it on the item's Aliases tab.
The issue is still there after you fixed it: Give it time to sync (see Step 2). If an Integration issue is still showing a day later, contact Acenda Support with the SKU and the error message.
No issues, but the item isn't live on the marketplace: Check that the item is mapped to the channel with the right listing action (see Channel Mapping & Listing Actions), then work through the Marketplace Listing Issues: Troubleshooting Checklist.
Related articles
Still stuck? Contact Acenda Support and tell us the SKU, the sales channel and the exact error message.