Target Plus accepts only five basic HTML tags in the product description you send from Acenda: <b>, <i>, <br>, <ul> and <li>. Anything outside that list is likely to be stripped out by Target+, or can cause the item update to fail, so it’s worth checking your formatting before you save.

The short version: use HTML for structure and basic emphasis only, meaning bold, italics, line breaks and bulleted lists. Don’t use it for custom styling, links or images.

Which HTML tags does Target+ allow?

Target+ accepts only these five tags:

<b> – bold text.
<i> – italic text.
<br> – a line break. Use it to separate paragraphs.
<ul> – starts a bulleted list.
<li> – a list item inside <ul>.

Look-alike tags aren’t on the list. Use <b> instead of <strong>, <i> instead of <em>, and <br> instead of <p>. Target+ doesn’t accept numbered lists (<ol>), so use a bulleted list instead.

What else does Target+ expect in a description?

Where it’s required: Target+ requires a description on parent items and stand-alone items. A variant can carry its own description, but the parent’s text should apply to every variant.
Length: Aim for at least 50 words and stay under 4,000 characters.
No links: Don’t include website addresses or links to other sites.
Claims: Avoid unsupported claims such as “best on the market” unless you can name who awarded or certified it.

Tags and attributes to avoid

Acenda passes your description HTML through as entered. It’s Target+ that strips or rejects anything outside the allowed list. Avoid:

Look-alike formatting tags: <strong>, <em>, <p> and <ol>
Links: <a>, and plain website addresses typed into the text
Images: <img>. Don’t add an image tag inside the description text. Add product images on the item itself instead (see Where you edit descriptions in Acenda below).
Styling: <style>, <font>, and any inline style="..." attributes (color, font-size and so on).
Scripts: <script>
Headings: <h1>, <h2>, <h3> and so on.
Tables: <table>, <tr>, <td>
Structural tags: <div>, <span>, <iframe>

Example of a clean description

Sticking to the allowed tags still gives you a readable, well-formatted description:

Keep your kitchen organized with this <b>6-piece stainless steel</b> mixing bowl set.<br>
<ul>
<li>Nesting design saves cabinet space</li>
<li>Dishwasher safe</li>
<li>Includes airtight lids</li>
</ul>
A practical set for everyday prep or gifting.

Where you edit descriptions in Acenda

Click CATALOG > Items in the sidebar.
Find the item and click the eye icon to open it.
Edit the Description field on the Details tab. This is your catalog description, and it’s shared across channels unless you override it for one.
If your catalog also sends Target+ Bullet Feature fields, they usually live in the Additional Attributes section of the same Details tab (the exact field names depend on how your catalog is set up). They follow the same tag rules as Description.

Need a Target+-only description that’s different from the rest of your catalog? If Description is mapped as its own attribute on your Target+ posting template, you may be able to set a channel-specific value for one item in CATALOG > Attribute Overrides.

If what shows on Target+ doesn’t match the Description field, check how Description is mapped on your Target+ posting template (Value Type String, Property or Twig). See How to build a posting template for how mappings and formulas work.

To add or update product images, use the item’s Media section on the same Details tab, or update many at once with How to bulk update product images. Don’t add an <img> tag to the description.

Troubleshooting & FAQ

Why does my description look fine in Acenda but plain on Target+? Target+ only renders the allowed tags above. Other tags may be dropped, which can flatten your formatting without showing an error.
What if an item has an error pointing to Description or a Bullet Feature field? In CHANNELS > Item Issues, check the Attribute Path column. If it names Description or a Bullet Feature field, check that field’s HTML against the allowed list above first. For other listing errors, see How to fix marketplace listing errors.
Do Bullet Feature fields get more freedom than Description? No. They go through the same pipeline, so the same allowed and avoid lists apply.
Why does the item still show the old error after I fixed the HTML? Acenda re-sends the item automatically after a real content change, and marketplace errors can take a cycle to clear. Give it some time, then check Item Issues again.

Still stuck? Contact Acenda Support and tell Acenda support the item’s SKU and which field you’re working on.

Information current as of Oct 21, 2026. We do our best to keep this accurate, but mistakes can happen. Target Plus's official guidance always takes precedence.

Keywords

HTML tags, allowed HTML, HTML in description, strong tag, em tag, p tag, numbered list, ol tag, description length, 50 words, 4,000 characters, product description HTML, rich text, bold, bullet list, line break, unsupported tags, strip HTML, script tag, links not allowed, images in description, tables, headings, description formatting, Bullet Feature, Twig, Attribute Overrides, Target+ description, Target Plus description, description rejected, how to format a product description, how to use HTML in a Target+ description, how to add bold or bullets to a description, how to format target+ product descriptions with allowed html tags

How to format Target+ product descriptions with allowed HTML tags