cx-listing-playbook 0.3.0 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,67 +1,31 @@
1
- # cx-listing-playbook
1
+ This playbook teaches cx how to work on your Amazon listings: creating new ones, seeing how each one is doing and why, proposing changes, and judging afterwards whether a change worked.
2
2
 
3
- A [pi](https://pi.dev) package for the work on an Amazon listing: creating it, how it performs and why, a log of each change, and how to judge whether a change worked. It is written for the assistant in a [ComChatX](https://comchatx.com) seller's box, and reads the seller's Amazon account through the box's `cx` command.
3
+ With it, cx:
4
4
 
5
- It is text and one script. Its changes are in [CHANGELOG.md](CHANGELOG.md). Every sentence of the skills ends with the research item it rests on, and the research is in [`research/`](research/README.md).
5
+ - Creates listings in the stores you name, from your own words and your product's data. It shows you what Amazon's own check says first, and writes to your store only after you say yes.
6
+ - Reviews a listing at each step from search to purchase, says what has changed since it last looked, and reads what Amazon itself reports about the listing.
7
+ - Proposes a change with its reasons and the figures behind them, and sends it only after you say yes.
8
+ - Keeps a record of every change: before and after, what was expected, and Amazon's receipt.
9
+ - Tells you, once enough time has passed, whether a change worked, did not, or cannot be told yet.
10
+ - Explains the Buy Box: whether your offer holds it, why not, and which causes you can fix in your store.
6
11
 
7
- ## What it holds
12
+ To have cx keep watching a listing for you, also install cx-listing-watch.
8
13
 
9
- | | What the model reads |
10
- |---|---|
11
- | `skills/listing-review` | The funnel and which element serves each stage, what Amazon's own answers show about a listing, the signals that something changed, which file carries each figure, how a write is validated (`references/writing.md`), and `scripts/report.sh` |
12
- | `skills/listing-change-log` | One file per listing change: before, after, what was expected and from which file, the words bet on, the seller's decision, the request as it would be sent, Amazon's receipt id and the observation window |
13
- | `skills/listing-create` | Creating a listing in the stores the seller names: new item or existing ASIN, the product type and each store's schema, identity, the request built from the seller's data, the preview (sent as a read, since it persists nothing), the write on the seller's word, the read-back until buyable and discoverable, and variation families |
14
- | `skills/featured-offer` | How Amazon picks the Featured Offer (the Buy Box), how to read whether the seller's offer holds it and why not, which causes a Listings Items write reaches and which sit in Seller Central, the Brand Registry portal or Amazon's own choice, and what the Support API reads |
15
- | `skills/effect-review` | Experiments, baseline and observation windows, controls, confounders, and the three verdicts: held, not held, cannot tell |
16
- | `prompts/listing-create.md` | `/listing-create <marketplaces> <your words, and where the product's data is>`: hands the seller's words to cx, e.g. `/listing-create US,DE 新品上架,数据在 /tenant/products/new-router/,FBA 发货` |
17
- | `prompts/listing-review.md` | `/listing-review <ASIN>`: the listing and its issues, the market since last time, a proposal with its reasons |
14
+ ## Try it
18
15
 
19
- Each skill's detail is under its `references/`.
16
+ - `/listing-create US,DE new product, data in /tenant/products/new-router/, shipped by FBA`
17
+ - `/listing-review <ASIN>`
20
18
 
21
- `/listing-watch` now lives in its own package, [`@comchatx/cx-listing-watch`](https://github.com/comchatx/cx-listing-watch), which uses this one. Guarding a listing's Featured Offer is [`@comchatx/cx-featured-offer`](https://github.com/comchatx/cx-featured-offer).
19
+ ## What it uses
22
20
 
23
- ## Files in the seller's tree
21
+ - **Amazon SP-API:** your Amazon seller account, connected on the Amazon SP-API plugin. cx reads your listings, offers and reports there, and changes them only with your yes.
22
+ - **Keepa,** where you have it: price and rank history, and your competitors' listings.
24
23
 
25
- | Place | Holds |
26
- |---|---|
27
- | `/tenant/listings/<ASIN>/watch.md` | The standing instruction `/listing-watch` (`@comchatx/cx-listing-watch`) writes |
28
- | `/tenant/listings/<ASIN>/changes/` | One file per listing change; changes made together are one change |
29
- | `/tenant/reports/<reportType>/<ask>/<n>/` | One report of that ask: `receipt.json` with the report id, Amazon's status and `createdTime`, each reply as Amazon gave it, and the document |
24
+ Each is its own plugin, and its page gives its price.
30
25
 
31
- ## The report script
26
+ ## Where cx keeps things
32
27
 
33
- ```bash
34
- scripts/report.sh <reportType> --origin <origin> --marketplace <id>[,<id>...] [--start <ISO 8601>] [--end <ISO 8601>] \
35
- [--option <name>=<value>]... --wait <seconds> [--every <seconds>]
36
- ```
28
+ - One file per change to a listing, in `/tenant/listings/<ASIN>/changes/`.
29
+ - Amazon's reports as they came, in `/tenant/reports/`.
37
30
 
38
- It asks Amazon's Reports API through `cx raw amazon-sp-api`: `createReport`, `getReport` until a terminal status or the `--wait` ceiling, `getReportDocument` and the document, decompressed, landed beside the receipt. Each run asks for a report of its own, except that it carries on the ask's report not yet landed: one still queued at the ceiling ends the run with its id and status (exit 3) for the next run to carry on. Earlier reports stay as they landed. It has no rate limiter and no retry of its own. Report types, their options and their periods are the `amazon-sp-api` skill's (`references/door.md`). It needs `bash`, `jq`, `curl` and `gzip`, which the box has.
39
-
40
- ## What it needs
41
-
42
- pi, and in the box the `cx` command with the Amazon SP-API source; Keepa where a skill names a Keepa field. It reaches no network itself except the one document link Amazon hands the script.
43
-
44
- ## Install
45
-
46
- ```bash
47
- pi install npm:cx-listing-playbook # for you, in ~/.pi/agent/settings.json
48
- pi install -l npm:cx-listing-playbook # for one project, in .pi/settings.json
49
- pi remove npm:cx-listing-playbook
50
- ```
51
-
52
- On ComChatX, a seller installs it from the Plugins page.
53
-
54
- ## Develop
55
-
56
- ```bash
57
- npm ci
58
- npm run typecheck
59
- npm test # pi at the pin loads the package and its tarball and expands every template; every text line cites a research item;
60
- # the script runs against a stub cx
61
- ```
62
-
63
- `TENANT_TREE` moves the script's tree from `/tenant` for a run outside the box, as the tests do.
64
-
65
- ## Licence
66
-
67
- MIT. See [LICENSE](LICENSE).
31
+ Every fact this playbook gives cx names its source; the sources are in [`research/`](research/README.md).
@@ -0,0 +1,31 @@
1
+ 这套方法教 cx 打理你的亚马逊 listing:创建新 listing,看每条 listing 表现如何、原因是什么,提出修改建议,事后判断修改有没有见效。
2
+
3
+ 装上之后,cx 会:
4
+
5
+ - 按你的描述和产品资料,在你指定的站点创建 listing。提交前先给你看亚马逊自己的检查结果,你同意后才写入店铺。
6
+ - 从搜索到下单逐步检查一条 listing,说明它比上次检查时有什么变化,并读取亚马逊对这条 listing 给出的信息。
7
+ - 提出修改建议,附上理由和依据的数据,你同意后才提交。
8
+ - 每次修改都留一份记录:改前改后、预期效果和亚马逊的回执。
9
+ - 等观察期足够后,告诉你这次修改已见效、未见效,还是暂时无法确定。
10
+ - 分析 Buy Box:你的报价有没有拿到、为什么没拿到,以及哪些原因能在店铺里解决。
11
+
12
+ 如果想让 cx 持续帮你盯一条 listing,再装上 cx-listing-watch。
13
+
14
+ ## 试一试
15
+
16
+ - `/listing-create US,DE 新品上架,数据在 /tenant/products/new-router/,FBA 发货`
17
+ - `/listing-review <ASIN>`
18
+
19
+ ## 用到的数据
20
+
21
+ - **Amazon SP-API**:你的亚马逊卖家账户,在 Amazon SP-API 插件里连接。cx 在这里读取你的 listing、报价和报告,只有你同意后才会修改。
22
+ - **Keepa**(如果你装了):价格和排名的历史,以及竞品的 listing。
23
+
24
+ 两者各是一个插件,价格见各自的页面。
25
+
26
+ ## cx 把东西放在哪
27
+
28
+ - 每次修改一个文件,放在 `/tenant/listings/<ASIN>/changes/`。
29
+ - 亚马逊报告的原件,放在 `/tenant/reports/`。
30
+
31
+ 这套方法给 cx 的每条事实都注明出处,出处在 [`research/`](research/README.md)。
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "cx-listing-playbook",
3
- "version": "0.3.0",
3
+ "version": "0.4.0",
4
4
  "description": "A pi package for the work on an Amazon listing: how it performs and why, a log of each change, and how to judge one.",
5
5
  "license": "MIT",
6
6
  "author": "ComChatX",
@@ -42,6 +42,14 @@
42
42
  "zh": "分析亚马逊如何分配 Buy Box、你的报价为何拿到或没拿到,以及哪些原因能在店铺里解决。"
43
43
  }
44
44
  }
45
+ },
46
+ "prompts": {
47
+ "listing-create": {
48
+ "zh": "用你自己的话和产品资料,在你指定的站点创建亚马逊 listing,例如 /listing-create US,DE 新品上架,数据在 /tenant/products/new-router/,FBA 发货。"
49
+ },
50
+ "listing-review": {
51
+ "zh": "检查一条亚马逊 listing:表现如何、有什么变化、该改什么。"
52
+ }
45
53
  }
46
54
  },
47
55
  "homepage": "https://github.com/comchatx/cx-listing-playbook#readme",
@@ -65,7 +73,8 @@
65
73
  "files": [
66
74
  "skills",
67
75
  "prompts",
68
- "research"
76
+ "research",
77
+ "README.zh-CN.md"
69
78
  ],
70
79
  "scripts": {
71
80
  "typecheck": "tsc --noEmit",
@@ -1,5 +1,5 @@
1
1
  ---
2
- description: Create Amazon listings from your own words and your product's data — e.g. /listing-create US,DE 新品上架,数据在 /tenant/products/new-router/,FBA 发货
2
+ description: Create Amazon listings in the stores you name, from your own words and your product's data.
3
3
  argument-hint: "<marketplaces> <your words, and where the product's data is>"
4
4
  ---
5
5
  Create my listing in $1 from my words: ${@:2}
@@ -1,5 +1,5 @@
1
1
  ---
2
- description: Review one Amazon listing — how it is doing, what changed, and what to change
2
+ description: "Review one Amazon listing: how it is doing, what changed, and what to change."
3
3
  argument-hint: "<ASIN>"
4
4
  ---
5
5
  Review my listing $1: the listing and its issues, the market since you last looked, and your proposal with its reasons.
@@ -64,6 +64,7 @@ Every research file has one layout: what it covers; Amazon's rules; what practit
64
64
  | listing-create.md | creating a listing: stores, new item against existing ASIN, product type and schema, identity and GTIN exemption, the request, variations, preview, write, read-back, sandbox, Build International Listings | none (write path) | listing-create |
65
65
  | listing-policies.md | claims, restricted words, regulators' rules, post-acceptance issues | all (policy gate) | writing.md; listing-change-log |
66
66
  | listing-writes.md | schema conformance, preview, patch and put, feeds, deletes, recording a write | none (write path) | writing.md; listing-change-log |
67
+ | playbook-defaults.md | three lines the charter once held as rules and Jack moved into the playbook on 2026-08-27 as defaults: how a series is shown after a chart, A+ as conversion knowledge, the store's language as the default the seller's word overrides | none (method) | listing-review; listing-create |
67
68
  | report-lifecycle.md | report and Data Kiosk lifecycles: create, poll, terminal statuses, documents, pagination, schedules, cancels, rate limits, landed receipts | none (data path) | scripts/report.sh; effect-review |
68
69
  | seller-central-only-tools.md | MYE, RLC, VOC, Seller Assistant and other tools without an API; how handoffs are kept | all | listing-review; effect-review; /listing-watch |
69
70
  | sp-api-access.md | roles, rate limits, 429s, account identity | none (access) | scripts/report.sh; listing-review |
@@ -1,6 +1,6 @@
1
1
  # Creating a listing: the seller's stores, the product type, the schema, identity, the preview, the write and the read-back
2
2
 
3
- Read 2026-10-27 by the research seat for brief 2026-10-26-87. Tags: [official] Amazon's own page, model or staff post; [opinion] a named practitioner or a seller's report; [research] published research; [seat] the seat's own reasoning, never a skill position.
3
+ Read 2026-10-27 by the research seat for brief 2026-10-26-87. Positions P-listing-create-25 and 26, open question 10 and their three forum rows were added 2026-11-04 for brief 2026-11-03-54. Tags: [official] Amazon's own page, model or staff post; [opinion] a named practitioner or a seller's report; [research] published research; [seat] the seat's own reasoning, never a skill position.
4
4
 
5
5
  ## What this covers
6
6
 
@@ -335,6 +335,9 @@ None was found that bears on the create path. The catalog-reconciliation papers
335
335
  | Seller Forums: Listing Lounge: Your GTIN Exemption Was Approved, But Now You Received An Error Message. What's Next? | https://sellercentral.amazon.com/seller-forums/discussions/t/a1257c84-e37a-439d-9c04-d731a0783edc | "2 years ago" | 2026-10-27 | Exemption spelling and wait; 5665, 5461, 8541, 8542 |
336
336
  | GitHub: Cannot create new listings and ASINs (#2711) | https://github.com/amzn/selling-partner-api-models/issues/2711 | 2023-09-22 | 2026-10-27 | 8566 and 8572 after an accepted put |
337
337
  | sell.amazon.com/blog/upc-codes; sell.amazon.com/learn/upc-codes | as named | none | 2026-10-27 | Not pages: 404 |
338
+ | Seller Forums: Listings Lounge: Difference between 'Merchant Release Date' and 'Offer Release Date' in Listing Offer tab | https://sellercentral.amazon.com/seller-forums/discussions/t/72cc7098-459b-477c-aff6-b02df3c7d160 | "2 years ago" | 2026-11-04 | Answer by Michelle_Amazon: Merchant Release Date as the product's first release, blank for most products; offer release start date as the first day of delivery and orders |
339
+ | Seller Forums: Release Dates Decoded: Is Your Product Launch Set Up for Success? | https://sellercentral.amazon.com/seller-forums/discussions/t/470084dd-d5f5-4e40-be04-d00b2532e25b | "a year ago" | 2026-11-04 | Post by Michelle_Amazon: Offer Release Date as when pre-orders open; Merchant Release Date as the first day a pre-orderable product can be delivered, optional for most products |
340
+ | Seller Forums: What exactly is the "Product Site Launch Date" on the Listing Product Details Tab? | https://sellercentral.amazon.com/seller-forums/discussions/t/e9d4654d-8d93-4d16-afcc-33e0842d6324 | "2 years ago" | 2026-11-04 | A seller's answer only; the Amazon-named reply defines no date. No position rests on it |
338
341
 
339
342
  ## Open questions
340
343
 
@@ -347,6 +350,7 @@ None was found that bears on the create path. The catalog-reconciliation papers
347
350
  7. **The GTIN exemption page.** G200426310 was not read. *Settles:* the office's ruling on the content call, or a signed-in read by the seller or Jack.
348
351
  8. **WEEE and EPR in a listing.** Whether any EU store's schema names a WEEE or packaging-EPR attribute. *Settles:* `getDefinitionsProductType` for the seller's product type in each EU store named.
349
352
  9. **Children in the same request window as the parent.** Whether a child put sent before the parent's creation finishes processing is refused or held. The pages say only that the parent is created first. *Settles:* the first family creation, read back between the parent and the children.
353
+ 10. **The three release dates in a store's schema.** No product-type schema was read for this file (the OpenAPI models at the pin carry none; a product type's schema comes only from `getDefinitionsProductType`, which no seat called). So the attribute names behind Seller Central's Product Site Launch Date, Offering Release Date and Merchant Release Date, and each one's `title` and `description`, are not known here. No Amazon page read defines Product Site Launch Date, and the two Amazon-named forum posts disagree on which of the other two opens pre-orders. *Settles:* the first `getDefinitionsProductType` for the seller's product type and store, read at run time.
350
354
 
351
355
  ## Positions
352
356
 
@@ -374,6 +378,8 @@ None was found that bears on the create path. The catalog-reconciliation papers
374
378
  - **P-listing-create-22.** `getListingsRestrictions` is read by ASIN, so it applies to an offer-only listing, and a new item's approval requirement shows as a `QUALIFICATION_REQUIRED` issue on the preview or the write. Sources: listingsRestrictions_2021-08-01.json; Get listings restrictions for an item in the catalog; listingsItems_2021-08-01.json.
375
379
  - **P-listing-create-23.** Amazon keeps no history of a listing, so a creation is a change whose before is empty, and what cx sent and what Amazon answered are kept only in the change log. Sources: listingsItems_2021-08-01.json; Listings Items API (as cited in listing-writes.md).
376
380
  - **P-listing-create-24.** A conflict issue is answered as its own text says: `4005011` by changing the submitted value to the catalog's or by contacting Amazon to change the catalog's; `4005033` by reverting to the original value and resubmitting, with a support case to dispute the original; `101165` by making the SKU, external ID and ASIN unique and resubmitting, with support where the duplicate is in Amazon's catalog. Sources: Listings Items API Issues Troubleshooting.
381
+ - **P-listing-create-25.** An Amazon-named account in Seller Forums describes the Merchant Release Date as the date the product was first released, which "can be left blank for most products", and the offer release date as the first day the seller can deliver and buyers can order once the item is live. A second post by the same account says instead that the Offer Release Date opens pre-orders and the Merchant Release Date is the first day a pre-orderable product can be delivered. Neither post shows a staff badge or an absolute date. Sources: Seller Forums "Listings Lounge: Difference between 'Merchant Release Date' and 'Offer Release Date' in Listing Offer tab"; Seller Forums "Release Dates Decoded".
382
+ - **P-listing-create-26.** No Amazon page read defines the Product Site Launch Date. Amazon's Sales Rank FAQ names the release date and the product site launch date among the dates to keep accurate for the New Release badge. What a date attribute is called in a store, and what it governs there, is in that store's product-type schema: the attribute's `title` and `description`, read at run time. Sources: Sales Rank FAQ (G202059240 v2, as cited in badges-and-placements.md); Amazon Product Type Definitions Meta-Schema (v1); Retrieve a Product Type Definition.
377
383
 
378
384
  ### The seat's own (not for a skill)
379
385
 
@@ -0,0 +1,34 @@
1
+ # Playbook defaults: what the company's own rulings leave to the playbook
2
+
3
+ Read 2026-11-04 for brief 2026-11-03-54. Tags as in `research/README.md`. This file holds no Amazon rule of its own. It records three lines that ComChatX's charter once held as rules. On 2026-08-27 Jack moved them out of the charter and into the playbook as defaults the model may set aside. Where a line rests on Amazon's words, the Amazon item is named and the file that holds it.
4
+
5
+ ## What this covers
6
+
7
+ - How a series is shown after a chart.
8
+ - What A+ is for, and what Amazon has said of its text in search, as of the date read.
9
+ - Which language a listing's text is written in.
10
+
11
+ ## The ruling
12
+
13
+ The CEO office's worksheet `2026-08-27-ai-constraint-recut-worksheet.md`, section 二, lists five charter lines to recut, R1 to R5, with Jack's note under the table: 「以上全部都能删」 (all of the above may be deleted). Three of them belong to this playbook:
14
+ - **R2**, the charter's "after a chart, a key-timepoint table (≤ 6 rows) + insight". The worksheet's reading: how such an analysis is shown is the playbook's to say, and the model picks the form for the case.
15
+ - **R3**, "A+ serves conversion, never SEO". The worksheet's reading: Amazon's indexing of A+ text is a platform fact that changes. The playbook keeps it as knowledge, with its source and date, not as a ban.
16
+ - **R4**, "target-market language". The worksheet's reading: a playbook default that the user's own words override, for example a seller who wants both languages.
17
+
18
+ The worksheet lives in the office's tree, outside this repository.
19
+
20
+ ## Pages read
21
+
22
+ | Page name | Where | Date read | What it gave |
23
+ |---|---|---|---|
24
+ | AI 约束重裁工作表, §二 | `ceo-office/drafts/completed/2026-08-27-ai-constraint-recut-worksheet.md` (office tree) | 2026-11-04 | R2, R3 and R4 as they stood, the worksheet's restatement of each, and Jack's note |
25
+
26
+ ## Positions
27
+
28
+ - **P-playbook-defaults-1.** After a chart, a table of its key time points (at most six rows) and one insight is this playbook's default way to show a series. It is a default, not a format rule, and the model may choose another form that suits the question. Sources: worksheet 2026-08-27 §二 R2, with Jack's note.
29
+ - **P-playbook-defaults-2.** A listing's text is written by default in each store's own language. The seller's own word overrides that default, for example a seller who asks for two languages. Sources: worksheet 2026-08-27 §二 R4, with Jack's note.
30
+ - **P-playbook-defaults-3.** That A+ serves conversion is playbook knowledge, not a ban on what A+ text may say. Whether Amazon search reads A+ text is a dated platform fact, as funnel-and-search.md holds it. Sources: worksheet 2026-08-27 §二 R3, with Jack's note; P-a-plus-content-1; P-funnel-and-search-30.
31
+
32
+ ## Verification
33
+
34
+ Read 2026-11-04 from the worksheet file in the office tree. The three charter lines are quoted from the worksheet's table as written there.
@@ -32,6 +32,7 @@ Facts cite P-<file>-<n> in research/<angles|elements|method>/<file>.md; pointers
32
32
  - A creation is `PUT /listings/2021-08-01/items/{sellerId}/{sku}?marketplaceIds=<one>&includedData=identifiers,issues&issueLocale=<locale>` with a body of `productType`, `requirements` and `attributes` in the schema's names and shapes, one store per request (P-listing-create-7).
33
33
  - The request carries only truthful values that the seller's data or the seller supports, and compliance declarations are the seller's own, since Amazon cannot determine them (P-listing-create-9; P-listing-create-15; P-attributes-and-browse-nodes-16).
34
34
  - references/request.md holds identity, language, price, fulfilment, images and compliance.
35
+ - For a listing built before the product is on sale, references/request.md holds what is known of the three release dates.
35
36
 
36
37
  ## Preview and write
37
38
 
@@ -65,4 +66,4 @@ Facts cite P-<file>-<n> in research/<angles|elements|method>/<file>.md; pointers
65
66
 
66
67
  ## References
67
68
 
68
- [request.md](references/request.md): identity, language, price, fulfilment, images, compliance. [family.md](references/family.md): parent and children. [answers.md](references/answers.md): issues and the sandbox.
69
+ [request.md](references/request.md): identity, language, price, fulfilment, images, compliance, dates. [family.md](references/family.md): parent and children. [answers.md](references/answers.md): issues and the sandbox.
@@ -15,6 +15,7 @@
15
15
  - The tag is the one the store's schema allows under `$defs.language_tag`, written with an underscore, as in `en_US` (P-marketplaces-and-languages-7; P-title-30).
16
16
  - The schema's `locale` sets display labels only, not the language of the values written (P-listing-create-12).
17
17
  - Text is written for each store in that store's language, not copied across stores (P-marketplaces-and-languages-8; P-listing-writes-22).
18
+ - The store's language is this playbook's default, and the seller's own word, such as asking for two languages, overrides it within the tags the store's schema allows (P-playbook-defaults-2; P-marketplaces-and-languages-7).
18
19
 
19
20
  ## Price
20
21
 
@@ -42,3 +43,11 @@
42
43
  - The compliance attributes a store's schema names, GPSR in an EU store among them, are filled from the seller's own declarations, store by store (P-listing-create-15; P-marketplaces-and-languages-11).
43
44
  - Dangerous goods, battery, safety data sheet, Prop 65 and CPSIA values come from the seller, since Amazon cannot determine them (P-attributes-and-browse-nodes-16).
44
45
  - A Prop 65 warning goes on child SKUs, not the parent (P-attributes-and-browse-nodes-18).
46
+
47
+ ## Dates
48
+
49
+ - Seller Central's Product Site Launch Date, Offering Release Date and Merchant Release Date are date attributes whose name and meaning in a store are the `title` and `description` of that store's schema (P-listing-create-26).
50
+ - No Amazon page read defines the Product Site Launch Date, and Amazon's Sales Rank FAQ names it, with the release date, among the dates to keep accurate for the New Release badge (P-listing-create-26; P-badges-and-placements-3).
51
+ - An Amazon-named forum account describes the Offering Release Date as the first day buyers can order once the item is live, and the Merchant Release Date as the product's first release, which can be left blank for most products (P-listing-create-25).
52
+ - The same account's other post says the Offer Release Date opens pre-orders, so which date opens pre-orders is not settled by Amazon's words as read on 2026-11-04 (P-listing-create-25).
53
+ - No page read says what an empty Offering Release Date or Product Site Launch Date does (P-listing-create-25; P-listing-create-26).
@@ -38,6 +38,10 @@ It lands the document and `receipt.json` under `/tenant/reports/<reportType>/<as
38
38
  `CANCELLED` is no report (explicit cancel, no data, or a repeat inside the type's period), never zero sales (P-report-lifecycle-2).
39
39
  The amazon-sp-api skill's references/door.md holds report names, options and periods (P-report-lifecycle-7).
40
40
 
41
+ ## Showing a series
42
+
43
+ After a chart, a table of its key time points (at most six rows) and one insight is this playbook's default; the model may choose another form that suits the question (P-playbook-defaults-1).
44
+
41
45
  ## References
42
46
 
43
47
  [writing.md](references/writing.md): schema limits, titles. [write-path.md](references/write-path.md): validating writes. [funnel.md](references/funnel.md): stages, gates, rank. [good-listing.md](references/good-listing.md): element health. [signals.md](references/signals.md): triggers, offer, stock. [figures.md](references/figures.md): figure sources. [policy.md](references/policy.md): policy screens. [reports.md](references/reports.md): reports, feeds. [watch.md](references/watch.md): watching.
@@ -20,7 +20,8 @@ Each sentence ends with the research item it rests on: P-<file>-<n> is in the pa
20
20
  - Search terms serve exposure only (P-search-terms-1).
21
21
  - The main image serves click-through; secondary images, video and 3D serve conversion (P-images-and-video-1).
22
22
  - A+ and Brand Story are conversion-stage elements, and an A+ change is judged at conversion (P-a-plus-content-1; P-funnel-and-search-30).
23
- - Amazon states that A+ image alt text helps search; no Amazon page says whether A+ body text is searched (P-funnel-and-search-30).
23
+ - Amazon states that A+ image alt text helps search; no Amazon page read on 2026-10-14 says whether A+ body text is searched, a platform fact that can change (P-funnel-and-search-30).
24
+ - That A+ serves conversion is playbook knowledge, not a ban on what A+ text may say (P-playbook-defaults-3).
24
25
 
25
26
  ## Gates copy does not fix
26
27