OVERVIEW

Blue Cherry is a two-way integration with Loop. Blue Cherry owns and maintains this integration.

Important: The lead time on setup for this integration is ONE MONTH from when Loop receives the information below. It is a complicated integration to setup that requires manual engineering work and testing.

The following information will need to be provided to your Onboarding Specialist in order for Loop to initiate setting up the integration.

1. The merchant or Bluecherry needs provide Loop with the following credentials:

• Bluecherry API keys (must confirm merchant is using Bluecherry APIs, if they are not we cannot integrate)

• Merchant URL on Bluecherry (e.g. https://examplebcapi.azure-api.net/EXAMPL)

• Staging and production Bluecherry codes (these are appended to the URL during calls)

2. A Loop developer instance for testing will need to be setup if it has not been done already.

   • If you need assistance setting up a Loop instance for your Shopify dev site, please reach out to your Onboarding Specialist.

3. Align on what processing events will be used for each Loop outcome.

   Manual outcomes require additional setup, so it is important that Loop knows this upfront!

4. Check Loop return reasons make sure your return reasons are up to date

• Return reasons can be found in the Loop Admin (Settings > Reasons)

• Changes in return reasons will require a manual change to the Loop <> Bluecherry integration which requires dev prioritization from Loop.

5. Provide Loop with payload mapping details

• The Loop Return ID must be passed into an unused field so the merchant can store it as reference.

  • Example: route Loop Return ID to ref_num2 field

• Return tracking numbers can sent & also need to be passed to an unused field

  • Example: route the tracking number to aux_ref_num field

• Confirm if you want the UPC passed into each line item’s upc field.

  • Align on & communicate any exceptions to Loop. For example, do you need the SKU of the item in the same field?

6. Provide return reason mapping

• Provide Loop with the reason codes for each return reason

• Example of return reasons and corresponding codes that will be provided by the merchant can be found at the bottom of the article

Note: Once all the information above has been gathered, please send it to your Loop Onboarding Specialist. From there, we will pass this information to the engineering team to complete the setup. Again, this is a complicated integration to execute so it may take a few weeks to confirm the completion of the setup.

• Create test orders & submit returns via merchant’s Loop dev instance

  • If you have different processing events by outcome - make sure you test a return with each outcome.

• Review how the return flows into Bluecherry

• If all looks good - we will launch the integration on the merchant’s live instance.

• Create test orders & submit returns via merchant’s Loop dev instance

  • If you have different processing events by outcome - make sure you test a return with each outcome.

• Review how the return flows into Bluecherry

• If all looks good - we will launch the integration on the merchant’s live instance.