Creating a Product Line
A Product Line carries shared context and default targets for a set of products. Find it under Product Lines, next to Connections and Users, and start with + Add Product Line.
Two things are worth knowing before you fill anything in: the text fields share one budget across the whole profile, and Target ACOS does not do what most people assume.
The seller description budget
Section titled “The seller description budget”Every seller profile gets 10,000 characters of description text, shared across all of its Product Lines and Groups. The form shows what you have spent as you type.
Only two fields draw on that budget:
| Field | Per-field limit | Counts toward the 10,000 |
|---|---|---|
| Agent description | 4,000 | Yes |
| Group note | 1,500 | Yes |
| Product Line name | 120 | No |
| Auto-assign naming pattern | 200 | No |
It is a real constraint on a large catalog: five detailed Product Lines will use it up. Spend it where it changes a decision — a line whose economics are unusual earns more words than one that behaves like everything else. If you genuinely need more, contact Vendlen.
General information
Section titled “General information”Product Line name
Section titled “Product Line name”What the line is, in a few words: Insulated bottles, Travel mugs. It appears wherever an ASIN
shows which line it belongs to.
Agent description (Markdown)
Section titled “Agent description (Markdown)”This is the field that matters most. It is the working context the AI Analyst reasons inside, and the difference between a Product Line that improves recommendations and one that just groups things.
The form suggests an outline, and it is a good one:
## Category## Product## Relevant keywords## Correct/incorrect patterns## Competitors## Seasonality · cycleThe last heading is the one people skip and the one that pays. Correct/incorrect patterns is where you say which searches genuinely belong to this product and which ones look related but are not — the queries you already know are wrong. That is knowledge the Agent cannot derive from your account, and it directly shapes what gets harvested and what gets negated.
Write it for someone who has never seen your product. Margins, competitive position, the variant that actually sells, the shopper you do not want: all of it changes what a good decision looks like.
Auto-assign by name (naming pattern)
Section titled “Auto-assign by name (naming pattern)”An optional regular expression matched against SKU or ASIN. ^BOT- catches every SKU
starting with BOT-.
It does not assign anything. It flags a suggested Product Line against products that are still unassigned, and a person confirms it. The SKU and ASIN list stays authoritative.
Worth setting if your SKUs follow a convention — it means a new variant shows up already pointing at the right line instead of sitting unassigned until someone notices.
Default Ads targets
Section titled “Default Ads targets”Three numbers that become the economic defaults for every ASIN in the line.
| Field | What it is |
|---|---|
| Break-even ACOS (%) | The ACOS at which this product stops making money |
| Target ACOS (%) | The ACOS you want it to run at |
| Max bid ($) | Required. The ceiling every other bid limit is derived from |
Target ACOS is not a jump
Section titled “Target ACOS is not a jump”This is the one people misread. Setting Target ACOS to 50% does not mean the next run drives every bid to whatever produces 50%.
A Bidding rule can be set to glide instead: each time it calculates, it closes part of the distance between the ASIN’s current ACOS and the target rather than going straight there. An ASIN at 90% ACOS with a 50% target gets an effective 82% on that run.
Glide follows the real ACOS, so it does not schedule a descent — an ASIN that stays at 90% keeps getting 82%, run after run. That is intended.
Glide is a per-rule setting, off by default. See Bidding rule.
Safety limits and Budget
Section titled “Safety limits and Budget”| Field | What it caps |
|---|---|
| Proposal/Harvest multiplier cap (×) | How far above the base ceiling a proposal or harvest may bid |
| Proposal Placement Δ cap (pts %) | The largest placement adjustment a proposal may make |
| Proposal Audience Δ cap (pts %) | The largest audience adjustment a proposal may make |
| Budget min ($/day) | The floor a budget decision may not go below |
| Budget max ($/day) | The ceiling a budget decision may not exceed |
Max bid is not the last word
Section titled “Max bid is not the last word”Max bid is required because the other ceilings are built from it — and both sit above it, so seeing a bid over your Max bid is not a fault:
A Max bid of $2.60 with the default 1.5× multiplier cap. Raise the Max bid and both ceilings move with it; raise the multiplier cap and only the upper one does.
These ceilings do not apply to everything. Direct edits you make yourself, Dayparting, and Amazon’s own Dynamic Bidding are all outside them. A Dayparting cell can put a bid above the ceiling, because it is a transient overlay rather than a rule-set bid.
Account default Product Line
Section titled “Account default Product Line”One line can be marked the account default. Unassigned ASINs use it for economic decisions, so nothing falls through to having no numbers at all.
Set one. Without it, an ASIN nobody has assigned has no break-even, no target and no max bid, and the decisions that need them cannot be made.
What to do next
Section titled “What to do next”- Let the Agent draft it for you: Drafting with the Agent.
- Group the variants underneath it: Creating a Product Group.
- Understand which number wins where: How the economics resolve.
VendlenPrivacy PolicyTerms of ServiceContact
© 2026 HELODA PTE. LTD. Not affiliated with or endorsed by Amazon.

