What Shopify access does OrderBrief Atlas request?
OrderBrief Atlas currently requests the minimum order-read scope required for its workflow: read_orders.
Common questions about installation, order-note processing, billing, logs, and what merchants should expect from OrderBrief Atlas in daily fulfillment workflows.
OrderBrief Atlas currently requests the minimum order-read scope required for its workflow: read_orders.
OrderBrief Atlas reads the merchant-authored order note, order name, order ID, tags, and custom attributes that help fulfillment teams understand special handling requests.
The app applies a rules-based note parser to detect urgent, gift, date-sensitive, customization, and warning signals. It then generates a short internal brief, action text, and risk score for staff review.
No. Summary results and checklist state are stored inside OrderBrief Atlas only. The app does not write its brief output back into Shopify orders, tags, or metafields.
Checklist state is saved in OrderBrief Atlas and stays synchronized across the dashboard and supported Shopify Admin extension surfaces for the same order.
The Webhook Logs tab shows inbound Shopify events, processing status, and paged history so operators can inspect event flow without reading raw server logs.
Processing Rules lets merchants add shop-specific urgent, gift, date-sensitive, customization, and warning keywords. Those rules change how future briefs are classified, and the retention setting controls how long saved briefs and webhook logs stay in the app database.
No. Manual reprocess and checklist actions are limited by plan. Starter stores can review summaries, while paid plans unlock the manual workflow actions documented in the billing surface.
If Shopify has not yet approved the required protected customer data access, OrderBrief Atlas does not fail with a raw server error. Instead, order-level actions return a guidance message so merchants know the workflow is blocked by platform approval rather than store data loss.