FlavorCloud integrates with Loop Returns as a third-party label provider. By connecting your FlavorCloud account to Loop Returns, you can automatically generate return shipping labels through the Loop platform.
This guide walks you through the required setup:
Example:
If your Customer Key is 12345, your webhook URL will be:
https://loop.flavorcloud.com/api/customers/12345/webhooks
4. After creating all three webhooks, copy your Webhook Secret and share it securely with FlavorCloud.
To enable FlavorCloud return labels in Loop:
This will route return label generation through FlavorCloud for the countries you configure.
Here is an example of a set up rule for returns from the United Kingdom.
In the policy section you can create policies based on where you are receiving returns. For example, you can set up a return policy for the United Kingdom. In those marketed you can set up where the Return is meant to go back to in the Destination field, and Destination Address. These are necessary for an active policies.
Merchants can configure the following policy zone settings:
We recommend setting up the policy so you are able to review before committing to the return to make sure you are not losing on your margins with the cost of the return label. In order to estimate labels, you can use the rate quote tool in FlavorCloud for estimates.
Read more on Loop at Return Policy Settings.
All FlavorCloud return labels use DDU Express as the default rate.
This is the industry standard for international returns.
The customer or merchant will pay applicable landed costs on delivery (duties, taxes, or fees charged at import).
DDP (Delivered Duty Paid) is not available for returns.
Duties and taxes cannot be prepaid on return shipments.
In some cases, FlavorCloud can apply duty avoidance.
If the original order duties were already paid and the goods are being returned, you may avoid some landed cost items at import clearance in a process called duty avoidance.
Duty recovery (drawback) may be possible in specific cases — contact your FlavorCloud representative for more information.
Once setup is complete:
Learn more about generating and managing returns in FlavorCloud.
Tip: Keep your Customer Key, API Key, and Webhook Secret secure. If any credentials change, you will need to update them both in Loop and FlavorCloud to avoid disruptions in return label generation.
Why don’t I see the “External connector” option when editing return policies?
Make sure the API key has the correct scopes enabled. Missing “Labels” or “Label Generation Requests” permissions can prevent FlavorCloud from appearing as a provider.
My webhook URL isn’t working. What should I check?
Labels aren’t generating in Loop. How do I fix this?
What happens if I regenerate my API key or Webhook Secret?
If credentials are regenerated in Loop, you must update FlavorCloud with the new values immediately. Otherwise, return label requests will fail until the integration is re-authenticated.
Can I test my setup before going live?
Yes. We recommend creating a test return in Loop once webhooks and API keys are configured. Confirm that a FlavorCloud label is generated and attached to the return.