Getting started3 min read
Outlined's Shopify Integration: What It Can and Cannot Do
Understand Outlined's read-only Shopify customer and order context, connection checks, identity limitations and the order actions that remain in Shopify.
Published
Outlined
Practical guidance for ecommerce teams · AI-assisted writing
Outlined's Shopify integration provides customer and order context for internal support work. It is read-only: it does not issue refunds, cancel orders, edit purchases, or change inventory. Use authorised Shopify workflows for those actions.
This guide covers the integration's supported purpose and a practical evaluation checklist, as of 30 October 2026. Available context depends on store permissions, historical access, connection health, and customer matching. Check those conditions with your own authorised examples before relying on the integration.
What the integration is intended to support
Support agents can use available Shopify customer and order information alongside conversation context. This can help establish which purchase a request concerns, understand relevant items, and investigate the customer's question.
Product data also supports identifying catalogue items in the broader customer-intelligence workflow. A product reference still needs sufficient evidence: an informal description or image does not guarantee an accurate catalogue match.
Keep these boundaries clear
| Task | Outlined boundary | Appropriate next step |
|---|---|---|
| View available customer/order context | Supported read-only purpose, subject to access and matching | Verify the relevant customer and order |
| Use product context during investigation | Supported purpose where data and evidence are available | Review ambiguous matches |
| Refund or cancel an order | Not performed by this integration | Use authorised Shopify controls |
| Edit items, fulfilment or inventory | Not performed by this integration | Use the responsible commerce workflow |
| Access all lifetime order history | Not guaranteed | Check permissions and historical availability |
| Identify every social account as a customer | Not guaranteed | Follow approved identity verification |
Connect the correct store
In Outlined, go to Settings and the Shopify integration. Follow the setup and connection flow with an authorised store administrator. The integration requires read access for customers, orders, and products. Use the in-product flow for current installation details rather than treating this article as a permanent set of Shopify developer-screen instructions.
Shopify's scope documentation explains that permissions control data access. It also describes approval requirements for some capabilities. Granting access is necessary for the relevant data, but does not by itself prove every record is available.
Never paste store tokens into a support conversation, a screenshot, or a shared evaluation sheet. Use the intended secure connection controls.
Verify with an approved example
Use an authorised test customer with a known order. Confirm that the intended store appears and the available order context matches the source record. Repeat the check with an ordinary team member who should have access.
Record what fields are present and what is missing. A pass should establish the task your team needs, not merely that a store card displays “connected.” If the agent cannot identify the order safely, stop the disclosure and investigate.
Understand identity and freshness limits
A social username may differ from a checkout email. Similar names can belong to different people. Follow the normal verification policy before associating accounts or revealing order information.
Information may also be absent because of granted access, historical availability, connection state, or an unmatched identity. Do not translate “no order visible” into “this person has never purchased.” Check the authorised source system when needed.
If the displayed order state conflicts with the customer's report, verify freshness and underlying records. A support response should explain what has been checked and what remains uncertain.
Keep remedies in the right system
A fictional replacement request illustrates the distinction. The agent uses order history to understand the purchase. An authorised colleague approves the remedy. The responsible Shopify or operations workflow performs it. The agent then confirms the actual outcome to the customer.
Record those as separate steps. “Replacement approved” should not become “replacement shipped” unless dispatch is confirmed. This matters even when all participants work inside one company.
Decide whether the integration fits
If your essential requirement is read-only context, test representative identities, orders, roles, and missing-data cases. If you require refunds or edits from the inbox, the current integration does not satisfy that requirement.
Use the Shopify context workflow to train agents on responsible use, and include the verified integration boundary in your purchase decision.
Written by Outlined
Tools and perspectives for turning customer conversations into better decisions.
