Buyer consent does not replace Williams Sonoma’s permission for AI shopping agents

Measurement technique

How to read this report

1. 01Synthesize the saved evidence packet only. This is not a new collection, access test or experiment. The bounded scope is U.S. consumer browsing, delegated account access, purchasing and account-based post-purchase workflows at the six named retailers, with selected official integration exceptions.
2. 02Plan an evidence_matrix with retailer rows and columns for browsing, account access, checkout, post-purchase actions and documented integration routes. Each cell should retain its supporting source, contractual scope and uncertainty. Use expressly permitted within scope, permission-required, prohibited or indeterminate; missing evidence must not be coded as permission or prohibition.
3. 03Williams Sonoma: record written authorization requirements for account and purchasing delegation, express authorization for computer-use automation, and the explicit distinction between buyer consent and retailer permission. Do not infer detailed post-purchase permissions beyond the supplied evidence.
4. 04Amazon: record the general license exclusions for extraction tools and third-party-benefiting account-information use separately from Agent Terms requiring identification, compliance with restrictions and cessation requests. Leave action-specific authorization boundaries indeterminate where the supplied summary does not settle them.
5. 05Walmart: mark automated materials gathering as requiring express prior written consent and systematic downloading or storage as separately prohibited. Leave distinct delegated login, checkout and return approval requirements indeterminate in the examined sections. Record the company-described ChatGPT purchasing route separately from its planned embedded Sparky transition.
6. 06Target: record approved-agent requirements for delegated autonomous shopping. Note that authorized functions may include login, carts, orders and returns; this does not authorize arbitrary agents.
7. 07eBay: mark automated browsing, account access, purchasing and post-purchase access as requiring prior express permission. Record the separate prohibition on third-party credential sharing. Treat Buy API approvals and contracts as a scoped integration route, not a browser-automation exception.
8. 08Etsy: separate ordinary-term permission requirements for crawling, scraping and spidering from API-agreement approval and written-authorization requirements. Leave non-scraping browser login, checkout and returns indeterminate under ordinary terms alone. Record selected partnered guest checkout and specified linked-order functions without extending them to arbitrary account control.