Allegro Returns
Allegro Returns
The Allegro Returns module automatically fetches customer returns registered on your Allegro seller accounts and turns each of them into an issue in Reklamator. Return status changes in Allegro (parcel dispatched, delivered, finished, etc.) are recorded in the issue history and can trigger business rules.
Configuration is available under Configuration → Modules → Allegro Returns.
Requirements
Managing the module requires the Allegro Returns settings permission (Allegro Returns permission group). The number of Allegro accounts you can connect depends on your subscription plan.
How it works
- You connect one or more Allegro seller accounts (sign-in happens on Allegro — Reklamator never sees your password).
- For each account you set the issue type, organization, an optional issue owner and the mapping of return data to issue fields.
- Every ~30 minutes Reklamator checks Allegro for new returns and creates issues from them — one issue per return.
- Each fetch also checks the status of open returns. A status change is recorded in the issue history, and fields mapped from changing data (status, waybill, carrier) are updated.
A return is tracked until it reaches a final status: Finished, Finished (Allegro Buyer Protection), Rejected or Commission refunded.
Connecting an Allegro account
- Go to Configuration → Modules → Allegro Returns and click Add Allegro account.
- You will be redirected to Allegro — sign in to your seller account and approve access for Reklamator.
- After returning to Reklamator the connection appears on the list. A new connection is paused — enable fetching once the configuration is complete.
Each Allegro account can be connected only once. If you try to connect an account that is already on the list, you will see "This Allegro account is already connected".
Connection list
For each account the list shows: connection name, Allegro login, status, last fetch date and last error. The row menu offers:
- Edit — connection configuration
- Fetch now — immediately fetches new returns and status changes (without waiting for the automatic cycle); a summary is shown afterwards: number of new issues, status changes and errors
- Returns preview — list of returns in Allegro (see below)
- Reconnect — renews access when Allegro has revoked it
- Delete — removes the connection; issues created from returns remain in the system
| Status | Meaning |
|---|---|
| Connected | Access to the Allegro account works |
| Needs reconnecting | Allegro revoked access (e.g. after a password change or removing the app in Allegro's "Connected applications") — fetching stops until you click Reconnect |
| Paused | Fetching is disabled in the connection settings |
When reconnecting you must sign in to the same Allegro account that was connected before.
Connection settings
| Field | Description |
|---|---|
| Name | Connection name shown in Reklamator (e.g. shop name) |
| Issue type | Type used for issues created from returns |
| Organization | Organization the issues are assigned to |
| Issue owner | User set as the owner of new issues (optional). Issues without an owner are visible only to users permitted to view all issues |
| Fetch returns created since | Date from which returns are fetched — at most 60 days back |
| Fetching enabled | Enables automatic fetching. Requires an issue type and organization |
Field mapping
The mapping defines which Allegro data goes into which issue fields. Each row is an issue field plus either:
- From Allegro — a value taken from the return or order, or
- Fixed — a constant value written to every issue from this account (e.g. a category or source)
You can map fields that are active and editable in the selected issue type. The lists only offer compatible pairs — a date field accepts only dates, a number field only numbers, a text field any data. Each issue field can be mapped only once. Select an issue type before mapping.
New connections get a default mapping: order number ← Order ID, purchase date ← Purchase date, description ← Items (summary).
Available Allegro data:
| Group | Data |
|---|---|
| Return | Return number, Return ID, Return status, Return creation date, Allegro marketplace, Waybill, Carrier, Refund account, Allegro account name |
| Buyer | Buyer login, Buyer email |
| Return items | Items (summary), Return reasons, Buyer comments, Serial numbers, Item names |
| Order | Order ID, Purchase date, Order total, First name, Last name, Full name, Company, Phone, Street, City, Postal code, Country |
Items (summary) contains one line per returned item in the format Name ×quantity: reason — buyer comment. Data from the Return items group is joined into a single text when a return covers several items.
Fields mapped from Return status, Waybill and Carrier are updated on every return status change. All other fields are filled only when the issue is created.
Order total and the Cost field
The Cost field accepts integers only, so the Allegro Order total cannot be mapped to it.
Customer
The Customer section defines whether and how the issue is linked to a customer:
| Mode | Behaviour |
|---|---|
| Match or create | Reklamator looks for a customer linked to the Allegro buyer, then by email; if none is found, a new customer is created from the mapped data |
| Match existing only | The issue is linked only to an existing customer; no new customers are created |
| No customer | The issue is created without a customer |
In create mode you can choose which Allegro data goes into customer fields (name, email, phone, mobile phone, address, tax number). Existing customer data is never overwritten.
Products
The Add return items as products option adds each returned item as an issue product — with quantity and serial numbers. Products are matched to the catalogue by Allegro offer or by the seller's product code (offer signature); if not found, a product is created automatically with the name from Allegro.
Returns preview
Returns preview lets you browse returns directly in Allegro, before (or regardless of whether) they are fetched into Reklamator. Set the creation date range and optionally a status, then click Show.
The table shows the return number, date, status, buyer, order number, items, waybill and the issue: an Open issue link, not imported or issue deleted.
The preview also works for paused connections and imports nothing — useful for checking the configuration before enabling fetching. Allegro returns a limited number of results per query — narrow the date range when there are many returns.
Issues created from returns
Issues created from returns have the Allegro return channel. Their issue card shows an Allegro return section with: return number, order, status, buyer, waybill, Allegro account and return creation date.
The issue history contains Allegro return entries:
- issue created from a return (return number, buyer login, account name),
- each return status change (previous → new status),
- issue field changes caused by a status change (change source: Change from Allegro).
If an issue created from a return is deleted, that return will not be imported again.
Return statuses
| Status | Description |
|---|---|
| Created | The buyer registered the return |
| Dispatched | The return parcel was sent |
| In transit | The parcel is in transport |
| Delivered | The parcel reached the seller |
| Delivered to Allegro warehouse | The parcel reached an Allegro warehouse (Allegro One Fulfillment) |
| Warehouse verification | The return is being verified in the Allegro warehouse |
| Commission refund claimed | A commission refund was requested |
| Finished | Return finished (final status) |
| Finished (Allegro Buyer Protection) | Return finished under Allegro Buyer Protection (final status) |
| Rejected | Return rejected (final status) |
| Commission refunded | Commission was refunded (final status) |
Business rules
Business rules offer an Allegro event group:
| Event | When |
|---|---|
| Issue created from Allegro return | After an issue is created from a return (in addition to the regular Issue created event) |
| Allegro return status changed | When a return status change is detected in Allegro |
The Allegro return status condition (equals / does not equal) lets you e.g. message the customer only once the return parcel reaches the seller (status Delivered). The Issue source condition has the value Allegro return for issues from this module.
Template variables
Message templates include an Allegro return variable section:
| Variable | Description |
|---|---|
{{allegro_return_number}} | Return number |
{{allegro_return_status}} | Return status |
{{allegro_return_reasons}} | Return reasons |
{{allegro_buyer_login}} | Buyer login |
{{allegro_waybill}} | Waybill |
The variables work in the message body and subject. They are empty for issues that do not come from an Allegro return.
Error messages
| Message | What to do |
|---|---|
| Allegro revoked access — reconnect the account | Click Reconnect on the connection |
| You signed in to a different Allegro account than the connected one | Sign in to the same Allegro account when reconnecting |
| The Allegro account limit of your plan has been reached | Delete an unused connection or change your plan |
| Set the issue type and organization before enabling fetching | Complete the connection settings |
| The start date can be at most 60 days back | Set a later date in Fetch returns created since |
| The mapping contains errors — fix the highlighted rows | Fix the highlighted mapping rows (e.g. field inactive in the type or incompatible data type) |
| Allegro request limit exceeded — try again in a minute | Temporary error — the next fetch will retry |
| Authorization in Allegro was cancelled | Authorization was interrupted in Allegro — try connecting the account again |
Fetch errors are also shown in the Last error column of the connection list and in the system log.
FAQ
How often are returns fetched?
Automatically every ~30 minutes. If you need a return right away, use Fetch now on the connection list.
Can I connect several Allegro accounts?
Yes, within your plan limit. Each account has its own configuration — issue type, organization, owner and mapping.
Can the same return create two issues?
No. Each return creates at most one issue — even after deleting and reconnecting the same Allegro account.
What happens when I delete a connection?
The connection and access to the Allegro account are removed and fetching stops. Issues previously created from returns remain unchanged.
Does Reklamator change anything in the return on Allegro?
No. The module only reads returns and orders — the return status is changed by the buyer, the carrier and Allegro.
Can I fetch older returns?
Yes, by setting the Fetch returns created since date — at most 60 days back.
What if a required field of the issue type is missing?
The issue is created from the return even if a required field is empty — fill it in manually or add it to the mapping.
Does a paused connection fetch returns?
No — neither automatically nor via Fetch now. Only Returns preview works for a paused connection.