> ## Documentation Index
> Fetch the complete documentation index at: https://docs.loopreturns.com/llms.txt
> Use this file to discover all available pages before exploring further.

# General Integration

<Warning>
  This guide assumes you have API access and the necessary permissions. For help
  enabling these features or to request sandbox/testing access, contact your
  Loop point of contact, Merchant Success Manager, or [support@loopreturns.com](mailto:support@loopreturns.com).
</Warning>

## 🧭 Overview

This use case shows how to connect your systems to Loop Returns and integrate at key points in the return lifecycle. The two guides below, when used together, provide the full picture for building an end-to-end integration.

<Tip>
  <b>Why integrate directly with Loop?</b><br />
  Connecting Loop to your ERP, WMS, 3PL, or other systems unlocks real-time data, advanced automation, and richer return workflows than relying on storefront or admin tooling alone. Direct integration enables:

  <ul>
    <li>Immediate event notifications and data sync via webhooks</li>
    <li>Access to detailed return and shipment data beyond what typical admin-only workflows expose</li>
    <li>Support for advanced flows like item grading & disposition</li>
    <li>Flexible integration with multiple systems and middleware</li>
  </ul>

  These options help you automate, customize, and scale your returns process as your needs evolve.
</Tip>

<Columns cols={2}>
  <Card title="Retrieving Return Data" icon="database" href="/integration-guides/return-data">
    Learn how to access, sync, and pull Loop return data.
  </Card>

  <Card title="Actioning on Returns" icon="clapperboard" href="/integration-guides/return-actions">
    See how to automate, update, and finalize returns via API.
  </Card>
</Columns>

## 🧠 Integration Mindsets

Most integrations with Loop fall into one of two broad categories: [1-way](#➡%EF%B8%8F-1-way-integration) and [2-way](#🔁-2-way-integration). Many brands start with a 1-way integration and evolve to 2-way as their needs grow. Below are summaries and common use cases for each approach; the application of these concepts will be explored in more detail in later sections.

<Info>
  **Common integration patterns**

  * Loop ↔️ ERP (e.g., NetSuite, Microsoft Dynamics)
  * Loop ↔️ WMS (Warehouse Management System)
  * Loop ↔️ OMS (Order Management System)
  * Loop ↔️ 3PL (Third-Party Logistics)
  * Loop ↔️ Middleware/iPaaS (e.g., Celigo, Alloy, custom connectors)
  * Direct API integrations
</Info>

| Pattern                  | Benefits                                                             |
| ------------------------ | -------------------------------------------------------------------- |
| Loop ↔️ ERP              | Centralizes all data, familiar workflows                             |
| Loop ↔️ WMS              | Real-time warehouse updates, faster fulfillment                      |
| Loop ↔️ 3PL              | Enables item grading & disposition, direct carrier/warehouse updates |
| Loop ↔️ Middleware/iPaaS | Flexible, scalable, connects multiple systems                        |
| Hybrid (ERP+WMS/3PL)     | Best of both worlds, tailored automation                             |

<Info>
  <b>FAQ: Why not rely on my storefront or admin alone?</b><br />
  Loop provides richer return data, real-time events, and advanced workflows that storefront-native return tooling alone typically doesn’t support.
</Info>

### ➡️ 1-Way Integration

Loop pushes return data to your system—either instantly via webhooks or on a schedule via API polling. Your system listens for these updates and triggers downstream processes like RMA creation, warehouse prep, or reconciliation.

<Info>
  For a full list of available webhooks and API endpoints, see the [Retrieving
  Return Data guide](/integration-guides/return-data).
</Info>

**Common use cases**

* Trigger workflows in your WMS/ERP as soon as a return is created (using the [Return Webhook](/webhook-reference/topics/return-webhook)).
* Sync all return activity into a data warehouse for analytics (using the [Detailed Returns List API](/api-reference/latest/return-data/detailed-returns-list)).
* Power customer service dashboards by pulling all returns for a specific order (using the [Get Return Details API](/api-reference/latest/return-data/get-return-details)).

### 🔁 2-Way Integration

Your system not only receives updates from Loop, but also sends actions and decisions back—enabling full automation and bi-directional sync. This allows you to programmatically process, flag, close, or annotate returns based on your own business rules, so both Loop and your internal systems always reflect the latest status.

<Info>
  For a full list of available API endpoints, see the [Actioning on Returns
  guide](/integration-guides/return-actions).
</Info>

**Common use cases**

* Automatically process and finalize returns (refund, exchange, store credit) from your WMS/ERP using the [Process Return API](/api-reference/latest/return-actions/process-return).
* Grade and disposition returned items from your WMS/ERP, then push those decisions to Loop using the [Item Grading & Dispositioning APIs](/api-reference/latest/item-grading-and-disposition/grade-items).
* Add internal notes or comments to returns for audit trails and team collaboration (using the [Create Return Note API](/api-reference/latest/return-actions/create-return-note)).

<Tip>Start with 1-way, evolve to 2-way as business needs grow.</Tip>

***

## 📦 Return Lifecycle

The following sections walk through the key integration touchpoints throughout the lifecycle of a return. Each stage highlights a high-level event or milestone in the return flow, making it easy to see where and how your systems can connect with Loop at every step.

<Steps>
  <Step title="🆕 Return created">
    Customer submits a return request in the Loop portal.
  </Step>

  <Step title="📦 Customer Ships Items">
    Items are shipped or dropped off by the customer.
  </Step>

  <Step title="🔄 Return Review & Processing">
    Warehouse reviews, grades, and processes returned items.
  </Step>

  <Step title="✅ Return Concluded">
    Return is closed and outcomes are finalized in all systems.
  </Step>
</Steps>

### 🆕 Return Created

This stage begins when the customer submits their return request in the Loop portal.

**What Happens**

* Customer selects the items to return and why, the outcome (refund, exchange, etc.), and return method (if applicable).
* Return is created in Loop.
* Loop updates the original order record to reflect the in-progress return.

**Integration Opportunities**

| Use Case                                                    | Loop Resource                                                                                                                              |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| Receive real-time notifications when a return is created    | [Return Webhook](/webhook-reference/topics/return-webhook)                                                                                 |
| Pull new or updated return data on demand                   | [Get Return Details API](/api-reference/latest/return-data/get-return-details)                                                             |
| Trigger downstream processes (e.g., create RMA, update ERP) | [Return Webhook](/webhook-reference/topics/return-webhook), [Get Return Details API](/api-reference/latest/return-data/get-return-details) |

### 📦 Customer Ships Items

This stage begins once the customer has shipped or dropped off the items they are returning.

**What Happens**

* Items required for return are shipped or dropped off by the customer.
* (Optional) If you track RMAs/ASNs, your system can update their status to reflect items in transit.
* Tracking information for the return becomes available and can be updated.

<Tip>
  Returns can be [processed
  automatically](https://help.loopreturns.com/en/articles/1917249#processing_event)
  during this stage based on shipping label status (e.g., "in transit",
  "delivered"). Whether and when this occurs depends on your brand’s Loop return
  policy and workflow configuration.
</Tip>

**Integration Opportunities**

| Use Case / Opportunity                                        | Loop Resource                                                                                                                                                                                                                                                    |
| ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Get tracking updates and in-transit status for returned items | [Return.updated Webhook](/webhook-reference/topics/return-webhook), [Label Webhook](/webhook-reference/topics/label-webhook)                                                                                                                                     |
| Pull latest tracking and shipment info for a return           | [Get Return Details API](/api-reference/latest/return-data/get-return-details), [Detailed Returns List API](/api-reference/latest/return-data/detailed-returns-list), [Advanced Shipping Notice API](/api-reference/latest/return-data/advanced-shipping-notice) |
| Sync RMA/ASN status in your WMS/ERP based on shipment events  | [Return.updated Webhook](/webhook-reference/topics/return-webhook), [Label Webhook](/webhook-reference/topics/label-webhook)                                                                                                                                     |

### 🔄 Return Review & Processing

At this stage, returned items have arrived at the warehouse (or other destination) and are reviewed for quantity, quality, and eligibility for restock. Based on this review, returns can be processed (triggering automated outcomes in your commerce platform or connected systems), flagged for manual review, or otherwise updated in Loop.

<Tip>
  Due to automated processing events, some returns may already have been
  processed by the time items arrive at the warehouse. Review your Loop workflow
  configuration for details.
</Tip>

**What Happens**

* Warehouse or receiving team inspects items for correctness and condition.
* Items are graded, dispositioned, or flagged if issues are found.
* Return is processed, triggering Loop to automate outcomes such as refunds, exchanges, or restocks in your commerce platform or connected systems.

**Integration Opportunities**

| Use Case / Opportunity                             | Loop Resource                                                                                        |
| -------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| Programmatically process or finalize a return      | [Process Return API](/api-reference/latest/return-actions/process-return)                            |
| Grade items and push disposition decisions to Loop | [Item Grading & Dispositioning APIs](/api-reference/latest/item-grading-and-disposition/grade-items) |
| Flag a return for manual review or investigation   | [Flag Return API](/api-reference/latest/return-actions/flag-return)                                  |
| Add internal notes or comments for audit trails    | [Create Return Note API](/api-reference/latest/return-actions/create-return-note)                    |

<Info>
  For the full range of actions and automation available at this stage, see the
  [Actioning on Returns guide](/integration-guides/return-actions).
</Info>

### ✅ Return Concluded

At this point, Loop has completed processing the return and created the appropriate outcomes in your commerce platform or connected systems (refund, exchange, store credit, etc.). This is the final stage, where you can ingest final updates into your own systems to ensure all records are in sync.

**What Happens**

* Outcomes (refund, exchange, store credit) are recorded by Loop in your commerce platform or connected systems.
* The return is closed in Loop.
* Final updates can be sent to 3rd party systems to reflect the completed return.

**Integration Opportunities**

| Use Case / Opportunity                                | Loop Resource                                                                                                                                     |
| ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Receive notification when a return is fully completed | [Return.closed Webhook](/webhook-reference/topics/return-webhook)                                                                                 |
| Ingest final return outcome into 3rd party systems    | [Return.closed Webhook](/webhook-reference/topics/return-webhook), [Get Return Details API](/api-reference/latest/return-data/get-return-details) |

## ✔️ Conclusion

<Info>
  <b>How long does integration take?</b>

  <br />

  Implementation time varies widely based on your systems, integration depth,
  and internal resources. Some brands launch basic integrations in days, while
  others require weeks for more advanced workflows. Your Loop point of contact
  can help estimate effort for your use case.
</Info>

Integrating with Loop enables you to automate, monitor, and optimize every stage of the return lifecycle. By leveraging Loop’s APIs and webhooks, you can keep your systems in sync, streamline operations, and deliver a seamless experience to your customers and teams—from return initiation to final resolution.