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

# Acumatica

> Connect Acumatica to Redo to create an RMA for each return and process returns once Acumatica completes them

## What is Acumatica?

Acumatica is a cloud ERP that manages orders, inventory, and warehouses. Redo's Acumatica integration creates an RMA sales order in Acumatica for each return, numbered with the Redo return number. When your warehouse completes the RMA, Redo processes the return. Acumatica restocks the items; Redo issues the refund, store credit, or exchange.

## What Does the Integration Do?

When a return is created in Redo (or approved, if it needs review), the integration creates an **RMA sales order** in Acumatica against the original sales order, populated with:

* **Order number** set to the Redo return number, which also prints on the packing slip and label so your warehouse can match the package to the RMA.
* **Customer** from the original sales order, with that sales order's number (for example SM326595) in **Customer Order**.
* **Return items only**, matched to the original order's lines by SKU (Acumatica inventory ID). Items the customer keeps (green returns) are left off.
* **Warehouse** set to your returns warehouse, or each line's original warehouse if you leave it empty.
* **Description** with the Redo return number and the return reasons, so warehouse staff see why items are coming back.

If an RMA with the return number already exists for the same order, Redo uses it instead of creating a second one.

Acumatica does not send webhooks. If you turn on **Process returns when Acumatica completes the RMA**, Redo checks Acumatica **every 15 minutes**. When your warehouse releases the RMA's receipt and Acumatica marks the RMA **Completed**, Acumatica has already restocked the items, so Redo **automatically processes** the return without restocking your storefront again.

### Other RMA Changes

* **Return reset or rejected in Redo**: an RMA still **On Hold** is deleted in Acumatica. Once your warehouse takes it off hold, Redo leaves it in place and notes on the return that it needs handling in Acumatica.
* **RMA canceled in Acumatica**: the return is flagged in Redo for your team to review.
* **RMA deleted in Acumatica**: the return is flagged in Redo for your team to review.
* **Return flagged or needing review in Redo**: Redo doesn't process it automatically, even after the RMA completes.

## How to Set It Up

### Prerequisites

Before you begin, make sure you have:

> **Acumatica User and Permissions**
>
> You need access to the **Connected Applications** screen to create the application. The Acumatica user who signs in when you click **Connect** is the user Redo acts as, so use a dedicated integration user if you can. That user must be able to view, create, and delete sales orders. Your instance must expose the **Default** endpoint version **24.200.001** (Acumatica 2024 R2 or later).

> **Orders Synced to Acumatica**
>
> Your store's orders must reach Acumatica as sales orders through a commerce connector, so Redo can find the original order. Redo matches the storefront order ID or order number against the sales order's **External Reference** and **Customer Order**.

> **SKUs Match Inventory IDs**
>
> Each product's SKU in your store must match its Acumatica inventory ID on the original sales order.

> **RMA Order Type with Manual Numbering**
>
> You need a sales order type for returns (Redo uses **RX** by default) whose numbering sequence allows **manual numbering**, because Redo sets the order number to the Redo return number.

> **Acumatica Updates Storefront Stock**
>
> Acumatica should push stock levels to your store. Redo leaves restocking to Acumatica.

### Configuration Steps

**1. Navigate to Integrations**

Go to **Settings** → **Integrations** and open **Acumatica**.

**2. Create a Connected Application in Acumatica**

On the **Returns** row, click **Connect** and copy the redirect URI shown. In Acumatica, open **Connected Applications**, add an application that uses the **Authorization Code** flow, add the redirect URI, and create a client secret. Note the client ID and secret.

**3. Connect Acumatica**

Back in Redo, enter your **Acumatica URL** (your tenant root, for example `https://example.acumatica.com`), the **Client ID**, and the **Client secret**, then click **Connect**. An Acumatica sign-in window opens. Sign in and approve access. The window closes and Redo shows Acumatica as connected.

**4. Choose RMA Settings**

Click **Set up** on the Returns row and choose:

* **RMA order type**, the sales order type Redo creates for each return (RX by default)
* **Returns warehouse** (optional), where returned lines go; leave it empty to keep each line's original warehouse
* **First return number**, where Redo return numbers start counting. Pick a number above any order number already used in the RMA order type.

**5. Turn On Returns**

Turn on **Process returns when Acumatica completes the RMA** if you want Redo to process returns automatically, then click **Turn on**.

**6. Test the Integration**

Create a test return to verify it works end-to-end:

1. Create a return in Redo for an order that is in Acumatica
2. In Acumatica, open the sales order with your RMA order type and the Redo return number, and check it has the right items and warehouse
3. Release the RMA's receipt so Acumatica marks it **Completed**
4. Within 15 minutes, Redo processes the return

> [!NOTE]
>
> Acumatica does not send webhooks to Redo. **Returns are processed by Redo's 15-minute check**, so expect up to 15 minutes between Acumatica completing an RMA and Redo processing the return.

## How Long Does It Take?

### Setup Timeline

| Step | Time | Description |
| - | - | - |
| Create Connected Application | 5-10 minutes | Add the application and redirect URI in Acumatica |
| Connect Acumatica | 2-5 minutes | Enter the URL, client ID, and secret, then approve access |
| Choose RMA Settings | 5 minutes | Pick the order type, warehouse, and first return number |
| First Return Test | 10-15 minutes | Create a return, complete the RMA, and wait for the check |
| **Total Setup** | **Under 1 hour** | Plus up to 15 minutes for the first return to process |

### Operational Timing

**1. RMA Creation**

**Real-time (1-3 seconds)** after the return is created or approved in Redo.

**2. Return Processing**

**Up to 15 minutes** after Acumatica marks the RMA **Completed**.

**3. Warehouse Processing**

**Varies by warehouse**, from package arrival to releasing the RMA's receipt in Acumatica.

## Important Considerations

> [!WARNING]
>
> **Manual numbering is required:** if the RMA order type's numbering sequence doesn't allow manual numbers, Acumatica assigns its own number and Redo flags the return. Turn on manual numbering for the sequence, then retry.

> [!WARNING]
>
> **Redo processes the whole return at once:** a completed RMA means every item came back. If items are missing from the package, remove them from the RMA in Acumatica before releasing the receipt.

> [!NOTE]
>
> Redo doesn't send per-item grades or outcomes to Acumatica. Your warehouse decides what happens to each item in Acumatica, for example by receiving into a returns warehouse and transferring sellable stock.

> [!NOTE]
>
> Turning off Returns stops new RMAs but keeps the connection. Disconnecting removes the connection and its settings. Neither changes RMAs already in Acumatica.

## Troubleshooting

RMA creation failures show on the return in Redo with one of these messages.

> **No Acumatica Sales Order Found**
>
> Redo couldn't find an Acumatica sales order for the store order. Redo matches the storefront order ID or order number against the sales order's External Reference and Customer Order.
>
> **Solution:**
>
> * Confirm the order exists in Acumatica
> * Confirm it came in through your commerce connector
> * Wait for order sync to finish if the order is new, then retry

> **Returned SKUs Not Found on the Sales Order**
>
> A returned product's SKU doesn't match an inventory ID on the original sales order.
>
> **Solution:**
>
> * Check the SKU in your store matches the Acumatica inventory ID exactly
> * Check no SKU changed after the order was placed

> **Acumatica Numbered the RMA Differently**
>
> Acumatica gave the RMA its own number instead of the Redo return number.
>
> **Solution:**
>
> * Turn on manual numbering for the RMA order type's numbering sequence, then retry

> **Acumatica Already Has an RMA with This Number**
>
> An RMA with the Redo return number already exists for a different order, for example from another store sharing the same Acumatica tenant.
>
> **Solution:**
>
> * Raise **First return number** above the numbers already used in the RMA order type

> **Return Has No Redo Return Number**
>
> The return was created before Redo return numbers were turned on.
>
> **Solution:**
>
> * Create the RMA manually in Acumatica for this return; new returns get a number automatically

> **Refresh Token Rejected**
>
> Acumatica rejected Redo's access, for example after the Connected Application's secret changed or access was revoked.
>
> **Solution:**
>
> * Click **Reconnect** on the Returns row and sign in again

## Support

For issues with the Redo integration configuration, return processing, or data synchronization, contact **[support@getredo.com](mailto:support@getredo.com)**.

For issues with Acumatica access, API credentials, or warehouse operations, contact your Acumatica account manager or support team.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.