How to run the AI listing pipeline

The web form's Collection Names tab — the same internal collection needs a different name per marketplace; this generates, reviews, and saves it.

1. 1Pick one Marketplace — this page works one marketplace at a time, because "already has a name" and "collides with something" are both evaluated per marketplace.
2. 2Paste Model Numbers, one per line, and click Look up collections — the system looks up which internal collection each model belongs to in Supabase.
3. 3Models with no collection found (not imported yet, or the catalog cell was blank) are called out separately — they don't block the rest from continuing.

1. 4Every collection found gets its own checkbox — one that already has a confirmed name for this marketplace starts unticked, everything else starts ticked. Ticking an "already has one" collection anyway is how you ask for a fresh suggestion — it replaces the old one (the previously confirmed name is untouched until you confirm again).
2. 5Click Generate names — only the ticked collections get an AI call.

1. 6Results land directly in an editable table — the Name cell is a text box, so an AI suggestion you don't like can just be typed over. Already-confirmed collections (Bristol here) are listed too, so everything's visible in one place.
2. 7Click Save & confirm: the edited (or AI-given) name is saved to Supabase, status becomes Confirmed. A dialog opens first and asks you to pick the marketplace again — if your pick doesn't match the marketplace in the table, it can't be saved (re-pick or cancel); this applies to AI-generated and Excel-uploaded names alike. Before that, an AI suggestion only lives in this browser tab — it's never saved to Supabase; refresh or look up again and it's gone, as if it never happened.

Another way: upload an Excel (no AI)

Already have the names (say, a collection mapping sheet)? No need to ask the AI. There's a Generate / Upload slider at the top — click or drag it; switching clears the table below so the two sources never mix in one save.

1. 8Pick the Marketplace above, flip the switch to Upload, choose an .xlsx file and click Read Excel. Only the first sheet is read, with row 1 as the header.
2. 9Two dropdowns appear under "Match the columns": the internal collection name column (defaults to the first column) and this marketplace's name column (Home Depot pre-selects the header containing "homedepot"; for other marketplaces pick it yourself). Below them you see how many rows will be read and a three-row sample; rows with a blank name for this marketplace are skipped. Picking the same column twice is flagged and blocked.
3. 10Click Load names and they land in the same editable table — only staged for now, not confirmed and not occupying the name. Check and edit them, then Save & confirm (the same confirm-marketplace dialog appears first). The duplicate rules are the same as for AI names (see the expandable note below), except the "no word Collection" rule, which only ever applied to AI output.

The statuses that can show up in that table —

The web form's Generate tab — paste model numbers, pick a marketplace, one click.

1. 1Pick the right Marketplace — if it's a newly added one, check Section 3 first to confirm a prompt has actually been published for it. To test a new prompt without touching a real marketplace, use Other… — see Section 5.
2. 2Model Numbers — one per line, paste directly, no commas needed.
3. 3Click Generate. The page polls progress on its own; no need to watch it, it usually finishes in a few minutes.
4. 4Results land automatically in Airtable's Generation Items table — that's where people review, edit, and override.

Submitted the wrong thing, or it's been running long enough that it looks stuck — don't just wait it out, you can stop it mid-run.

1. 1Click Cancel next to the progress bar — a confirm dialog pops up, and it takes effect the moment you confirm.
2. 2Anything already generated is kept, untouched; whatever hasn't run yet gets marked stopped and won't consume any more OpenAI calls.
3. 3There's no "pause and resume" — cancelled models need to be resubmitted as a new batch.

Refreshed the page and lost the progress bar and Cancel button? You don't have to just wait it out.

1. 1Most of the time you don't need to do anything — refreshing in the same browser automatically reconnects to whatever batch is still running.
2. 2Switched browsers, cleared storage, or want to check in on someone else's batch — paste its Batch Code (the WF-... string next to the progress title, also in Airtable's Batches table) into the Resume a batch box at the top of the page and click Look up.
3. 3Once found, it behaves exactly like a batch you just started — same progress bar, same working Cancel button.

Reviewing copy happens in this base (editing prompts has moved to the Prompt Assistant) — worth a quick tour first.

Along the top are 5 tables —

airtable.com — Listing Content

Two more things worth knowing on the left sidebar of Generation Items —

airtable.com — Listing Content

1. 1The view list on the left switches what you're looking at — click Wayfair / THD / Amazon / Overstock to see only that marketplace's rows, no manual filtering needed.

airtable.com — Listing Content

1. 2For a visual once-over, switch the left sidebar to ALL cards (or a marketplace's own ... cards view) — it turns into a card layout with the product photo next to the copy, easier for a final human check than the grid view.

All done in the Prompt Assistant page (the Prompt Assistant card on the home page): edit, then Push to save and Publish to go live at once — no Sync needed. The field names below are the fields behind each cell in the Prompt Assistant.

By default, one row calls the AI exactly once — filling in the fields under Call 1 is all it takes.

Create or edit a row, filling in these fields in order —

Publishing from the Prompt Assistant takes effect at once, so you normally don't need this button. It is a back-up: it sends out rows that are marked to publish but have not gone out (say a publish that failed half-way). The button lives in the Payload Viewer tab, which only an admin account can see.

1. 1Sign in with an admin account and switch to the Payload Viewer tab.
2. 2Only needed when a prompt is marked to publish but has not gone out: tick the matching marketplace(s) in the checklist here — you can tick several at once.
3. 3Click Sync Prompts. Each ticked marketplace is processed on its own — a failure on one doesn't block the others.
4. 4Each line below the button is one marketplace's result: publish Call 1 vX / Call 2 vY means both calls actually published (together, see above); error means that row did not go out; the reason is kept in the row's publish result (visible in the Prompt Assistant).
5. 5A failure retries once automatically; if it still fails, click Sync Prompts again — the error text usually names the field that's wrong.

Want to try a prompt change without touching a real scope like Wayfair's? The Marketplace dropdown's last option, Other…, is exactly for that.

A custom name like Wayfair-xingyuan needs setting up in three places, spelled identically in each:

1. 1Prompt Assistant: create or copy a prompt, then set its Marketplace to the new name (any name works as it is; no option to create first). Prompt Name is just a plain-text label, type anything; but that is not the field that matters here — if Marketplace still says Wayfair, the system treats this prompt as the real Wayfair.
2. 2Generation Items: this table keeps its own separate list of Marketplace options — add the same new name there too (field header › Edit field › Add option). Generated results get written into this table, and a missing option fails that write.
3. 3The web form: pick Other… on the Generate tab's Marketplace dropdown, and again in the Payload Viewer tab's Sync Prompts checklist — type the exact same name in both.

Taking a prompt down for good, with no new version published — also done in the Prompt Assistant.

1. 1Find the prompt you want to retire in the Prompt Assistant.
2. 2Use the page's retire function: it switches the Scope to REMOVE — retire this prompt (no new version) and publishes at once.
3. 3Confirm when asked.
4. 4It takes effect straight away: the prompt is no longer used for any product, and the versions published before are kept.

Only needed when product facts are missing or stale — grab the latest export, then upload it. The Upload Catalog tab only shows up for an editor or admin account; reviewer doesn't get this tab.

First, get the latest file from the Homelegance dashboard —

1. 1In the Homelegance dashboard: Item › Product Downloads › click Product Sheet Download to get the latest export.
2. 2On the web form's Upload Catalog tab, click Choose File and pick that file, then Read file — this only parses it in the browser, nothing is written yet.
3. 3Check the row count shown below, and whether a Bundle / Image Link sheet was found, then click Import all rows.
4. 4For a large file, try Try 25 rows first on a small batch before running the full one.

A Set model number that's never been in the catalog at all? — "Create a Set from the naming rule", at the bottom of Upload Catalog

A different case from the upload flow above: that one is for a master that's already in the catalog but not yet linked to its components; this tool is for a master that has no row in the catalog at all — it finds the components by a fixed naming rule, validates them, and creates the row directly. Same editor/admin-only visibility as the rest of Upload Catalog.

1. 1Fixed rule, not editable here: *2 = -2 + -3 (2pc: Love Seat + Sofa); *3 = -1 + -2 + -3 (3pc: Chair + Love Seat + Sofa); *2PW/*3PW the same, with each component model also carrying a PW suffix.
2. 2Paste the master model number(s) to create, one per line, and click Create.
3. 3Each input gets its own result row: Created — every component was found and they agree on department; the master row and its component links are built, and content rollup (bundle_components) plus Set classification already ran automatically — nothing else to do by hand.