Deep linking allows merchants or partners to direct customers to their order in Loop without requiring the customer to manually submit their order number or ZIP code for lookup. This provides a seamless customer experience and enhances automation opportunities. Common Use Cases for Deep Linking:
  • Customer Emails: Embed deep links in order confirmation or delivery emails.
  • Customer Portals: Add links within order history or account overview pages.
  • Customer Support Automation: Streamline workflows by integrating deep links into help desk systems.
  • Product Packaging: Include QR codes in product inserts that lead directly to the return portal.

​
Deep Linking Options

Loop offers three approaches for implementing deep links, depending on your needs and integration requirements. The Deep Link API enables you to create deep links programmatically using the Generate Order Link endpoint. This method requires:
  • A Loop shop ID
  • An API key
  • The Shopify order name
  • The order shipping ZIP code
This option is ideal for merchants with API access and the necessary order details. Designed for Loop partners, this API enables deep linking into multiple customer return portals without requiring:
  • Individual merchant API keys
  • Shipping ZIP codes
  • The customer portal domain (which may vary per merchant)
This method is ideal for third-party app developers building integrations with Loop. It simplifies access to customer portals across merchants. Learn more in the Deep Link Into Return Portal documentation.

​
3. Dynamic URL

If you have the customer return portal domain, order name, and shipping ZIP code, you can construct a deep link directly using a dynamic URL. Customers are taken directly to their return without needing to input their order details. URL Format: https://{return_portal_domain}/?order={order_name}&zip={zip_code}

​
Summary

Each of these options provides flexibility depending on your use case, ensuring seamless integration and a smooth customer experience. For detailed implementation steps, refer to the corresponding API documentation.