Key takeaways
Order scopes carry customer data: grant read access to the last 60 days, ask the protected-data level, refuse name, address, phone and email unless the report needs them, add read_all_orders only beside an orders scope for older history, and check retention, subprocessors, model training and deletion before install.
Decline optional scopes the report does not need.
Order access already includes customer data
Grant read access to recent orders, not a customer file. On Shopify, that split is not a switch you can flip.
Shopify's documentation on access scopes says more scopes reach protected customer data than you would expect. Customer scopes are the obvious case. Orders, draft orders, fulfilments, abandoned checkouts and store comments carry customer data too.
The GraphQL order object is the current picture of an order: customer details, line items, financial data and fulfilment status, in the same record. The REST order resource, the older API, says order access requires protected customer data, and that the data should be used only if the app's functionality requires it. Shopify will restrict scopes when an app has no legitimate use for the data. That is a control on the developer. If the install screen still offers a scope, the grant is yours to make or refuse.
Protected customer data is divided by level. Level 1 is customer data excluding name, address, phone and email. Level 2 includes name, address, phone or email, and it includes a requirement to participate in data protection reviews. Access to each level can vary by app type. Shopify describes these requirements as the minimum acceptable handling of protected customer data. Treat that as a floor. It does not show you how this vendor stores orders after the token is live.
Ask which level the app uses, and whether it reads name, address, phone or email. A margin report can usually be made from totals, line items, discounts, refunds, product identity and cost, which is a Level 1 argument. It does not need the four direct-identifier fields. If an AI analytics pitch wants those fields, ask what the output does with a name or email that it cannot do with order and product figures. A personalisation or audience job is a larger grant. Do not hide it inside a margin install.
What should you grant for a margin report?
Match the scopes to the report, then stop.
For orders, start with read_orders. By default that is read access to orders created in the last 60 days. write_orders is read and write for that same window. Write access comes from the write scope. read_all_orders does not grant write access, and it does not grant order access on its own. You add it beside read_orders or write_orders only if you need older orders.
A write scope includes the matching read. write_products includes read_products. Do not accept write_orders so the app can see orders properly. For a read-only margin or AI analytics job, do not install if write_orders is required. Ask the vendor to drop it, or decline it only if the app requests it as an optional scope.
Also decline scopes that carry customer data and do not serve the report. On Shopify's own list, that includes customers, draft orders, fulfilments, abandoned checkouts and store comments. A customers scope is a separate grant from order access. Do not accept it because the listing says analytics.
Cost belongs in a margin figure. This article does not name the scope that exposes cost per item. Ask which product or inventory field the app reads, then allow only the scope that matches that field. If the app reads the cost stored on the product, a wrong cost becomes a wrong margin. Check that figure in Shopify before you treat the chart as a decision.
Scopes you grant at install are the required set. Optional scopes are requested later, and you can decline them. A later prompt for customers, write access or full history is a new decision.
Useful for
- read_orders for a recent margin view
- Product access limited to fields the vendor names
- Optional scopes you can decline later
Watch for
- write_orders for a report that only reads
- Name, address, phone or email without a job for those fields
- Customers, draft orders, fulfilments, abandoned checkouts or comments by default
The default window is 60 days
The scope docs and the order object docs agree. By default, only the last 60 days of orders are accessible. Older records need access to all orders.
Zoho has described that limit for its own Shopify connector: with read_orders, Zoho Analytics can fetch only the most recent 60 days of order data. That is one vendor speaking about its connector, not a measure of every analytics app. It is a clear picture of what the default scope does.
A developer on Shopify's community forum reported a quieter failure. Orders older than 60 days stay hidden unless the token making the call has read_all_orders, and the query tends to fail silently, with no error. That is a reported experience, not an official guarantee. The rule next to it is official: without the extra scope, the app is not meant to see the older orders. If a chart stops near 60 days and the sales page promised a year, check the granted scopes before you trust the shape of the trend.
Request the longer window only when the decision needs it, for example a seasonal comparison, and only beside read_orders or write_orders. Shopify restricts scopes that lack a legitimate use. You do not have to open the archive on the first install. Sixty days is enough to see whether the report is worth the access.
What should you check in the privacy terms first?
Shopify calls the protected-customer-data requirements the minimum acceptable handling. Meeting that floor, or clicking install, is not the same as knowing how long this vendor keeps a copy, who else processes it, whether your orders train a model, or what uninstall deletes. Read the privacy terms, and any processing addendum, in the same sitting as the scope screen. If a point is missing, treat it as unanswered.
The questions below are for the vendor's contract, not a conclusion under UK GDPR or US state privacy law. If you need a legal sign-off, take the written answers to counsel.
Retention. How long are order and customer fields kept, what is removed on a schedule, and what is kept for the life of the account? A rolling window is a different risk from identifiable orders with no end date.
Subprocessors. Who else receives store data, and which fields does each party see? A host that stores the app is not the same grant as a model provider that receives raw orders.
Model training. Is store data used to train or improve models, including models offered to other merchants? Ask whether that use covers identifiable orders, aggregates, or neither. Silence is not a no. Get the sentence in writing. Nothing here states a platform rule that bans or permits training.
Deletion on uninstall. Ask what is deleted, from which systems, and on what timeline, after you remove the app. Do not assume uninstall wipes the vendor's copy. Do not assume a platform deadline. None is stated here.
Role. Ask whether they process store data only on your instructions, and whether they will sign a processing agreement if you want one. File that answer with the scope list. It is not, on its own, a ruling on who the law calls controller or processor.
Read the install screen against the job
The screen in your admin is the grant you are making. Scope descriptions here follow Shopify's developer documentation. If the screen and a sales page disagree, believe the screen, then ask the vendor to explain the extra line.
- Write the job in one line: a margin view on recent orders, or a named AI report.
- Allow read_orders. If write_orders is required, do not install, or ask the vendor to drop it. Decline write_orders only if it is an optional scope. An analytics report should not need to change orders.
- Ask which protected-customer-data level the app uses. Refuse name, address, phone and email unless the report needs those fields.
- Decline read_all_orders only if the app requests it as an optional scope and you do not need more than 60 days. If it is required and you do not need older orders, do not install, or ask the vendor to drop it. Use it only beside an orders scope.
- Match product or cost access to the fields the vendor names. Do not add a scope on a guess.
- Read retention, subprocessors, model training and deletion on uninstall. If a term is vague, get a written answer before you install.
- Decline a later optional scope that fails the same test.
A checklist cannot see the vendor's systems. Shopify's requirements are a stated minimum, and a tidy privacy policy can still be wrong in practice. What you can do is refuse scopes the job does not need, keep history short until you have a reason, and keep the vendor's answers beside the install record.
If the app will not say which level it uses, or will not say whether your orders train a model, do not install it to preview a dashboard. The dashboard is the small part. The token is the grant.
Sources
- Shopify API access scopes shopify.dev By default, read_orders provides read access and write_orders provides read and write access to orders created within the last 60 days.
- Shopify: Manage access scopes shopify.dev More scopes reach protected customer data than you'd expect. Customer scopes are the obvious case, but orders, draft orders, fulfillments, abandoned checkouts, and store comments all carry customer data too.
- Shopify: Order object, GraphQL Admin API shopify.dev The order object provides access to customer details, line items, financial data, and fulfillment status.
- Shopify: Order resource, REST Admin API shopify.dev Order access requires access to protected customer data.
- Shopify: Work with protected customer data shopify.dev Level 1 is customer data excluding name, address, phone, and email fields. Level 2 is customer data including name, address, phone, or email fields, and includes participation in data protection reviews.
- Shopify Developer Community: orders not returned when queried community.shopify.dev Practitioner report, not official Shopify documentation: orders older than 60 days are hidden unless the app has read_all_orders granted on the token making the call, and it tends to fail silently with no error.
- Zoho Analytics community notice about the Shopify connector help.zoho.com Vendor description of its own connector, illustration only: if the Shopify connector uses the read_orders scope, Zoho Analytics can fetch only the most recent 60 days of order data.



