Integrations Troubleshooting

Overview

Corso supports a wide range of integrations across shipping providers, warehouse management systems, customer experience platforms, email and SMS tools, and subscription services.

This guide provides general troubleshooting steps for each integration category to help you quickly identify and resolve common issues.

If you work through the steps below and the issue persists, reach out to our team at [email protected] for deeper investigation.

Shipping Providers (EasyPost and Vesyl)

The most common issue with shipping provider integrations is the inability to generate a shipping label. When this occurs, an error displays directly on the claim.

Step 1: Verify Credentials

Ensure your EasyPost or Vesyl API credentials are correct and have not changed. Corso pulls all connected EasyPost accounts into the platform, so confirm the accounts configured in EasyPost match the accounts selected within Corso settings.

Step 2: Validate Addresses

Confirm both the customer return address and your policy return-to location are valid and correctly formatted. Incorrect country codes or unverified addresses are a common source of label generation failures.

If the customer address appears invalid, contact the customer to confirm the correct address.

Step 3: Verify Carrier Coverage by Region

If you accept international returns, ensure your EasyPost or Vesyl account includes the appropriate carrier accounts for those regions. For example, if accepting returns from Canada, your EasyPost account must have Canada Post configured and enabled.

WMS Platforms (Shiphero, Shipbob, IDF, XB Fulfillment, Logiwa, Two Boxes)

Warehouse management system integrations are designed to push RMA details from Corso to your WMS. These integrations are generally stable once configured, but occasional issues can occur.

Troubleshooting Steps

1. Verify all setup details are accurate, including the webhook URL, webhook token, and any API keys.
2. Confirm any field mapping configured on the WMS side is correct and up to date.
3. If the integration was previously working and has stopped, check whether any changes were made on the WMS side.

If issues persist, contact our team. We can review what data is being sent from Corso and help identify the source of the problem.

Customer Experience Platforms (Gorgias, Gladly, Zowie, Kustomer, Zendesk)

CRM and customer experience integrations are typically very stable. If something is not loading or displaying correctly:

1. Log out and log back in to your CRM platform.
2. Confirm the Corso app has been properly added and configured within your CRM.
3. Ensure both Corso and the CRM platform are running without errors on their respective sides.

If issues continue, reach out to our team for support.

Email and SMS Providers (Klaviyo and Others)

Email and SMS integrations rely on events fired from Corso. As long as those events are being sent correctly and your flows are configured to respond to the right triggers, these integrations should work without issues.

Troubleshooting Steps

1. Confirm Corso events are mapped to the correct triggers in your email platform (for example, Klaviyo flows).
2. Verify timing settings and flow conditions in your email platform align with the events Corso sends.
3. If events are not appearing, reach out to our team and we will verify events are firing correctly from Corso.

Subscription Platforms (Recharge and Skio)

Subscription integrations allow Corso shipping protection to be included alongside a customer subscription cadence.

Expected Behavior

1. When a customer subscribes, the Corso shipping protection product is added on the same schedule as other subscription items.
2. For Recharge: If a customer cancels their subscription or removes other products, the Corso protection product is canceled as well.
3. For Skio: The Corso protection product remains on the subscription until the customer removes it.

Troubleshooting Steps

If Corso is not being added to subscriptions as expected, contact our team and we will review the integration configuration.

Other Integrations (Stripe, Localize, IntelliGems, Bridge)

• Stripe: As long as your Stripe account is connected, fees process straightforwardly. If charges are not coming through, verify your setup against the Stripe integration article and reach out if needed.
• Localize, IntelliGems, and Bridge: These are custom integration partnerships. Our team works closely with brands on these setups and is happy to jump on a call to assist.

General Troubleshooting Checklist

Before reaching out to our team, run through these steps for any integration:

1. Confirm all API credentials, keys, and tokens are correct and have not changed.
2. Review setup against the relevant setup article to ensure all steps were completed.
3. Check for any recent changes on the third-party platform side that may have affected the connection.
4. If the issue is intermittent or started recently without any setup changes, contact our team.

Contact: [email protected]