Configuration Guide
Setup location: Returns Back-office → Settings → Price Setup → Return Addresses
Onboarding Requirements
What you’ll need:
Access to your Returns Back-office (admin permissions)
Complete address details for each warehouse (street, city, postal code, country)
Contact information for each facility (phone, email, department name)
Clear naming system for your return addresses (e.g., warehouse codes)
List of markets and products requiring specific routing
System requirements:
Active Ingrid Returns product
Returns Back-office access
Integration dependencies:
Price Setups configured to use your return addresses
Carrier accounts supporting your return address locations
Warehouse management system ready to receive returns at specified addresses
Your online shop integration active for product data (if using product-based routing)
Step-by-Step Setup Guide
Step 1: Navigate to Return Address Settings
Log in to your Returns Back-office
Go to Settings → Price Setups in the main navigation
Go to Return Addresses
Click the “Create Return Address” button
Step 2: Create Your Return Address Identifier
Enter a unique Name/ID that makes sense for your business (examples: “warehouse_london”, “returns_us_west”, “facility_main”)
Keep it simple and consistent - you’ll use this when setting up routing rules
Consider using location or purpose in the name for easy identification
Step 3: Fill In Address Details
Complete all address fields carefully
Select the correct Country Code from the dropdown
Add contact details so carriers and your team can coordinate
Use the Attention Name field to specify which department receives returns
Step 4: Save and Verify
Review all information for accuracy
Click “Submit” to save
Check that your new return address appears in the list
Make note of the Name/ID - you’ll need it for the next step
Step 5: Connect to Routing Rules
Go to Settings → Price Setups
Create or edit your routing configuration
Reference your return address Name/ID
Set up rules for which returns should go to this address (by market, product type, etc.)
Implementation Examples
Example 1: Multi-Region European Operations
Business scenario: A fashion retailer operates warehouses in the Netherlands (serving Northern Europe) and Spain (serving Southern Europe). They want to route returns to the nearest regional facility to reduce processing time and shipping costs.
Configuration:
Return Address 1:
Name/ID:
warehouse_nl_amsterdamAddress: Amsterdam facility complete address
Purpose: Northern Europe returns
Return Address 2:
Name/ID:
warehouse_es_barcelonaAddress: Barcelona facility complete address
Purpose: Southern Europe returns
Price Setup Configuration:
Price Setup 1: Markets SE, DK, NO, FI →
warehouse_nl_amsterdamPrice Setup 2: Markets ES, PT, IT →
warehouse_es_barcelona
Result: Swedish customers receive return labels with Amsterdam address, Spanish customers receive Barcelona address, optimising return logistics across Europe.
Example 2: Product Category Routing
Business scenario: An electronics retailer wants to route expensive items (laptops, cameras) to a secure facility with specialised inspection, while routing accessories to the main warehouse.
Configuration:
Return Address 1:
Name/ID:
facility_high_valueAddress: Secure inspection facility
Purpose: High-value electronics
Return Address 2:
Name/ID:
warehouse_mainAddress: Main distribution centre
Purpose: Standard products
Price Setup Configuration:
Price Setup 1: Product tags include “high-value” →
facility_high_valuePrice Setup 2: All other products →
warehouse_main
Result: Returns are automatically routed based on product value, ensuring appropriate handling and security measures for expensive items.
Example 3: Seasonal Pop-Up Facility
Business scenario: A retailer operates a temporary returns processing centre during Black Friday/ holiday season to handle increased return volumes.
Configuration:
Return Address:
Name/ID:
facility_seasonal_q4Address: Temporary facility address
Purpose: Q4 peak season processing
Price Setup Configuration:
Create time-bound Price Setup active November-January
Route all returns to
facility_seasonal_q4during this periodLower priority fallback rule routes to standard warehouse outside peak season
Result: Returns are automatically directed to the seasonal facility during peak periods, then revert to standard routing when the temporary facility closes.
