See every change before bulk-editing live listings
Keble AI Agent drafts old → new rows; Amazon previews each one.
- Store sync: Pro (1 store) or balance
- Keble accounts are invite-only for now
Bulk edits today
- Upload first, find out later
Errors return after the file is live.
- One wrong field, a broken listing
One wrong column breaks a selling listing.
- No undoNo undo button
Rollback means finding every old value.
Three ways to change 80 listings
| Spreadsheet upload | One by one | Keble list | |
|---|---|---|---|
| Old → new on every row | MissingNew values only | LimitedOne at a time | Yes |
| Amazon preview first | MissingErrors after the upload | MissingErrors after you save | YesEvery row |
| Apply chosen rows only | LimitedEdit the file to choose | YesEach edit separate | Yes |
| Roll back to the old value | MissingRe-upload them | MissingRetype them | LimitedFields exact |
Typical of each category, from their public pages, as of Oct 2026; individual tools vary.
The list you actually review
What changes, and what can be restored
- Previewed first
Amazon checks each row; hidden characters are blocked.
- Chosen rows only
The rest wait for later.
- Undo with the old value
Fields return to their exact old value.
- Removals and A+: best-effort undo
A new A+ document can only be detached; Amazon reviews every A+ change.
Nothing changes in your store until you approve it.
More
Approve it yourself or through an API key you created with write access. Keble AI Agent can only propose.
Questions
What does it cost?
Preparing the changes is free (0 requests). Store sync needs Pro (1 store) or a balance; Keble AI Agent needs a paid plan or balance.
What can't it change?
Brand, barcodes, variation links and category. A listing can't be removed while Amazon holds its stock.
What if Amazon refuses a row?
Its reason shows; fix or exclude it.
Your whole catalog, one reviewed list
- Store sync: Pro (1 store) or balance
- Keble accounts are invite-only for now
Use it from your own AI Agent
With the Keble MCP tools (artifect_create, kind AMZ_LISTING_CHANGES), build a change list for my connected store: one row per change, with a reason.