78 lines
6.2 KiB
Markdown
78 lines
6.2 KiB
Markdown
# CartMyList + CartMySupply — Complete Response to All 18 Investigation Concerns
|
|
|
|
---
|
|
|
|
**Hi Anita and advisory team,**
|
|
|
|
Both trackers were reviewed line by line. Every one of the 18 concerns is answered in this document, with the critical findings up front. After the analysis was written, it went through two independent conductor reviews (Claude Sonnet 5 and Claude Opus 4.8) that stress-tested the technical claims, the math, and the blind spots. Their findings are folded in below.
|
|
|
|
### The Three Most Important Findings
|
|
|
|
**1. The "showstopper" is not a showstopper (Concern #4).**
|
|
|
|
The tracker flagged that the Amazon cart endpoint "silently drops items beyond ~3" and proposed testing PA-API as a workaround. We tested both claims:
|
|
|
|
- The PA-API workaround is dead on arrival. Amazon removed cart operations entirely in PA-API 5.0. The official FAQ: *"Cart API support is removed with PA API 5. You can use Add to Cart form."*
|
|
- The documented limit is 10 items per URL, not 3. Amazon's FAQ: "you can specify multiple item ids (up to 10)."
|
|
- Our live test of the endpoint from a datacenter IP redirected to the Associates sign-in flow. This is consistent with the "~3 item drop" being an unauthenticated-session artifact, not a hard platform cap. The drop itself was never observed because a cart was never built.
|
|
|
|
**Action:** a 10-minute logged-in test with 10 ASINs settles it. That test is now a hard gate on the architecture choice for this weekend's build, not a deferred item.
|
|
|
|
**2. The real legal risk was missed: Amazon Associates Section 2(g) (Concern #1).**
|
|
|
|
The automation itself is defensible: parents click real cart links, and emailing links is explicitly permitted when the parent opted in. The landmine is Section 2(g) of the Participation Requirements:
|
|
|
|
> "You will not offer any person or entity any consideration, reward, or incentive (including any money, rebate, discount, points, donation to charity or other organization, or other benefit) for using Special Links."
|
|
|
|
"$1 per cart donated to PTA" is arguably a donation to an organization for using your links. That is a real account-termination risk, and it pairs with Concern #18 (charitable solicitation). Both conductors flagged this as the single most important finding, and the $100/school guaranteed floor actually makes the 2(g) exposure worse, not better, because a guaranteed payment for link use sits closer to the prohibited text.
|
|
|
|
**Action:** the donation-to-PTA feature is parked behind a legal review. We ship the free tool; we do not ship "$1 per cart to PTA" until counsel clears the structure.
|
|
|
|
**3. Link expiry is resolved (Concern #8).**
|
|
|
|
The tracker's "Links Stay Active" tab is correct: the cart URL never expires, the tracking cookie window is 24 hours, and cart retention is 89 days per the Operating Agreement. We will still ship the regenerate-cart button for good UX, and the FAQ will be worded correctly.
|
|
|
|
### Verdict Summary on All 18 Concerns
|
|
|
|
| # | Concern | Verdict |
|
|
|---|---|---|
|
|
| 1 | Amazon TOS / automation | Addressed. Automation defensible; Section 2(g) donation model parked behind legal review |
|
|
| 2 | Privacy Policy / ToS | Addressed. Template 80% done; needs company details and one legal read |
|
|
| 3 | Wrong ASIN accuracy | Addressed. Confidence-tier framework + explicit verification workflow; needs 20+ real lists to benchmark |
|
|
| 4 | Cart item drops | Investigated. Likely false alarm; documented cap is 10/URL; 10-min test gates architecture |
|
|
| 5 | Seasonality | Addressed. CartMySupply peaks Jul-Aug; CartMyList peaks Aug-Oct/Feb-May; they smooth each other |
|
|
| 6 | Free-to-paid psychology | Addressed. Free is permanent; paid tiers are additive, no bait-and-switch |
|
|
| 7 | Stripe micro-fees | Addressed. $4.99 = 8.9%; $5.99 = 7.9%; $19.99 Family Pass = 4.4%. Price at $5.99+ |
|
|
| 8 | Cart link expiry | Resolved. URL never expires; 24h cookie; 89-day cart retention |
|
|
| 9 | Support at scale | New gap, scheduled. Scriptable scenarios + FAQ + refund policy within 48h |
|
|
| 10 | TeacherLists moat | Addressed honestly. No structural moat; funnel is the only advantage, and it is unproven |
|
|
| 11 | Amazon native feature | Addressed. Pivot documented: value moves to the school relationship layer |
|
|
| 12 | Amazon-only positioning | Addressed. "Amazon-first" framing; survey data to settle marketing language |
|
|
| 13 | PTA pitch math | Addressed. $8/school is real and thin; floor design conflicts with 2(g) and must be resolved by legal |
|
|
| 14 | PTA decision cycle | Addressed. CartMySupply bypasses PTAs entirely (direct-to-parent); CartMyList pitches in spring |
|
|
| 15 | Parser format variety | Needs data. Digital-first scope + manual fallback; needs 20+ real lists |
|
|
| 16 | Family Pass value prop | Addressed. Multi-kid angle is the killer feature; margin math verified |
|
|
| 17 | Domain and branding | Addressed. Register CartMySupply.com, branded landing before any pitch |
|
|
| 18 | Charitable solicitation | Addressed. Co-venture statutes (CA, NY, PA) are the precise lens; review before any donation |
|
|
|
|
### What This Means for the Weekend
|
|
|
|
- **CartMySupply build: green light**, with two hard gates: the logged-in 10-ASIN test, and the donation feature parked behind legal review. Ship the free tool.
|
|
- **CartMyList: scope as design plus legal prerequisites this weekend, not launch.** It is a much bigger surface: student cards, Stripe, COPPA/FERPA, 39-state solicitation registration. The analysis is honest enough to plan against, not yet sufficient to authorize launch.
|
|
- **The timing is actually good:** August 5 is peak supply-list season. This weekend's build lands CartMySupply in its natural window.
|
|
|
|
### What We Need From the Team
|
|
|
|
One thing, and it is the only item on the whole tracker that requires a human: **20+ real school supply lists** from different schools and states, typed and handwritten. Schools publish them publicly; an afternoon of collecting covers it. Everything else is built or scheduled.
|
|
|
|
---
|
|
|
|
Anita, one note before I sign off: the accuracy framework and the support-at-scale scenarios in your tracker are exactly the kind of discipline that separates a real product from a demo. The committee caught things that a purely technical review would have missed. That is why this response is as solid as it is.
|
|
|
|
*Am I the meanest?*
|
|
|
|
**Sho'Nuff Brown**
|
|
Germaine's AI Ops Engineer
|
|
(833) 545-4425
|
|
shonuff@germainebrown.com
|