Return Shipping defines which carrier products Returnflows uses when your team generates return labels for claims.
It reuses your returns TMS connection, but this list is claims-only and is not shown to customers.
🔗 TMS connection
We use the same Return Label Provider (TMS) you configured for returns (e.g., Webshipper, Homerunner).
If you’re not connected yet, first connect your TMS via the standard returns shipping setup.
🗺️ Configure per country (claims)
In Return Shipping you create/maintain options for each country.
Click Manage options next to a country to add or edit options your team will use when generating a label on a claim.
✍️ Create/edit a shipping option (internal)
When you click Add Shipping Option within a country, set:
Name & Description
Internal labels to help staff pick the correct option.Carrier (TMS) → Returnflows Carrier
TMS/Carrier: select your exact contract/service in the TMS.
Returnflows Carrier: ensures correct handling/directions.
Service
Choose the exact return product (e.g., GLS: 15 – Shop return, PostNord: Return Drop-off, DHL: Parcel Connect Return).Important: Wrong service = label failure.
Carrier Add-ons (optional)
E.g., QR code / Labelless, Customs API, Liability/Insurance — provider dependent.Display Parameters
E.g., Labelless: Yes/No (affects label/QR generation, not customer UI).Status
Active: available to your team during claim handling
Draft: saved but not used
❓ FAQ
Are customers shown these shipping options in the claim flow?
No. The list is internal and used by staff when generating labels.
Is this configured per market?
No, per country. Maintain options under each country.
Can we keep multiple active options in one country?
Yes. Your team can choose the appropriate one when creating the label.
Label generation failed — now what?
Verify the Service exactly matches your carrier’s required return product and that any add-ons (QR/Labelless) are supported.
🙋 Need help?
Ping us in chat — we’ll help you validate your TMS setup, services and best practice.
Ask ChatGPT