New product wizard (Autopilot)

The New product wizard enrolls one product under Pulse Pilot management: its name and ASIN, its goal and weekly budget, whether to bring existing campaigns with it, its SKUs, any extra keywords, and a review before the product is created. Nothing is written until the last step's Build product. Words such as ASIN, SKU, ACoS and match type are in the Amazon advertising glossary; Pulse Pilot's own words, such as goal, Seeding and harvest, are on Pulse Pilot Vocabulary.

Open Autopilot → Managed Products → + Add Product.

Required marks a field the wizard will not continue without. Optional fields may be left blank. Preselected fields carry a default you can change.

How the steps work

The step bar shows five steps, or six when you choose to migrate campaigns. Completed steps show a tick and can be clicked to go back; you cannot jump forward. ← Back and Next → sit in the footer; on the last step Next becomes Build product. Next stays active; if something is missing, clicking it marks the missing fields "*required" and the footer says what to complete. ← Cancel at the top returns to the list without saving.

Step 1 · Product

Product name. Required. The name Pulse Pilot shows for this product.

Amazon ASIN. Required. Ten characters starting with B0; the field upper-cases as you type. The helper says where to find it.

Step 2 · Goals & Budget

Goal. Required. One card: Launch, Grow, Optimize, Liquidate or Wind Down. Each card describes the goal and what to expect. The goal decides which of the next fields appear.

Target ACoS (%). Shown for Grow, Optimize and Liquidate; Required for Optimize. A percentage from 0 to 100.

Min CVR (%). Shown for Grow, Optimize and Liquidate; Required when shown. Preselected (15). The conversion rate a search term has to beat before it can graduate into its own campaign.

Weekly keyword budget ($). Required; must be above zero. The total weekly budget Pulse Pilot distributes across the product's campaigns. The lines beneath it explain the per- campaign minimum and what happens when the budget cannot cover it.

Weekly budget decline (%/week). Wind Down only. Optional; above zero and at most 90. How much the weekly budget shrinks each week; blank uses the default.

Representative sale price ($). Optional. Blank uses your listing's price and keeps it in sync; a value here is used instead.

What does one unit cost you? ($). Optional. With the ASIN and a price, a line shows what you keep or lose per sale at your target ACoS.

Step 3 · Existing campaigns?

Yes, migrate campaigns adds a Select campaigns step. No, start fresh skips it. Required: choose one.

Step 4 · Select campaigns (migrate path only)

Two panes. Available lists the profile's campaigns with a search box, Select all and Clear; Selected (N) shows your picks with its own Clear. Rows show the name, the ad type tag, the state and the campaign id. Optional: you can continue with none selected.

Step · Products (SKUs)

On the migrate path the SKUs in your selected campaigns are listed and pre-ticked. Otherwise, or in addition, add rows by hand: SKU (Required, at least one row) and ASIN (Optional, ten characters). × removes a row; the last row cannot be removed. + Add another SKU adds one. The step's note says why SKU is the required half.

Step · Additional keywords

Yes, add keywords or No, just harvest. Required: choose one.

With Yes: a keywords box, one per line or comma-separated, shown as chips with Clear all; Starting bid ($), Preselected (0.75), Required and above zero, applied to each keyword you add.

Competitor ASINs. Optional. Product pages your ads may appear on; entries that are not ASINs are listed as unusable.

Search terms to track. Optional, up to 10. The searches to watch your Amazon ranking on.

Step · Review & build

Campaign prefix. Required. The preview beneath it shows every campaign name the prefix produces. The cards below summarise the product, goal and budget, the campaigns to migrate, the seed keywords, and a map of how the campaign roles connect; What happens next says what building does.

Build product creates the product. A name that already exists is refused with a message to go back to Step 1.

After building

"Product created" confirms the setup is saved and that nothing runs or spends until the product is turned on. Finish → opens the product page. ▸ Advanced — conversion fallbacks folds open optional per-match-type figures with Skip and Save & finish.

Good to know

1. The product is not on until you turn it on. Building saves the setup; Go live on the Products page creates the campaigns.
2. Only Wind Down shrinks the budget. The decline field appears for that goal alone.
3. Migrated campaigns are adopted, not rebuilt. They join the product alongside the standard structure the prefix names.
4. You can change most of this later. Goal, weekly budget, price and tracked terms are edited on the product page; competitor ASINs are not editable there yet.