Summer Upsell requests the minimum scopes needed for each feature. No customer PII is read or stored.
| Field |
Description |
| read_products |
List products and variants in campaign builders, and sync the catalog cache that powers AI recommendations. |
| write_products |
Create the synthetic products used by Bundle / FBT discounts. |
| read_discounts |
List existing discounts in the admin to avoid conflicts. |
| write_discounts |
Create Shopify Function discounts for upsell offers. |
| read_orders |
Read paid orders so the orders/paid webhook can attribute a conversion and its revenue back to the campaign that produced it. This is what drives conversion rate and AOV lift in Analytics. |
| read_themes |
Detect the active theme to check whether the app embed and widget blocks are installed. |
| write_app_proxy |
Register the /apps/summer-upsell proxy used by the storefront widget runtime. |
| read_markets |
List market locales for translation overrides. |
| read_locales |
List shop locales for translation overrides. |
What we don't request
No read_customers, no write_orders, and no payment or financial scopes. Order data is read only to attribute conversions — we store the campaign ID, the line-item revenue, and the order timestamp. No customer names, emails, addresses, or payment details are read or stored.