Skip to main content
Mirakl

Order already refunded in Mirakl Connector: when it appears and how to fix it

The message appears when you press Refund in Mirakl on an order whose Refund State is already Refunded. It is a brake: the action stops and no second refund is sent to Mirakl. What you need to do is check the amount and date the message shows, not press the button again.

FlexigoTech · Editor in charge: Víctor Gómez · Updated 5 November 2026

Key facts

Module
Mirakl
Versions
Odoo 17, 18, 19 and 20
Checked
in the connector's source code, version 20.0 · against the sources linked at the end
Reading time
4 min

What the message says and what it means

When you press Refund in Mirakl on an order, Odoo stops and shows this text:

Order … is already fully refunded (… refunded on …). Refunding it again would send a second refund to the marketplace.

The gaps are filled with three pieces of data. The first is the order name or, if it has none, its Mirakl identifier. The second is the amount already refunded. The third is the refund date, or a hyphen - if none is stored.

The meaning is straightforward: the order is recorded as fully refunded and the module will not send the refund again. It is an error that stops the action, so whatever that click was going to change is not saved.

Diagram of the already-refunded order message in Spanish, German, French, Italian and Portuguese
Diagram built with code from the module's published translations (not an Odoo screenshot): the same message in Spanish, German, French, Italian and Portuguese.

The message is in the published code of every branch: Odoo 17, 18, 19 and 20.

Same stock on every Mirakl marketplace, sent from Odoo
Video: Same stock on every Mirakl marketplace, sent from Odoo

Exactly when it appears

There is a single condition: the order's Refund State is Refunded. That field is visible on the Mirakl Orders form, in the Refund group, and also in the list under the same menu. Its values are Pending, Refunded, Partial, Error and Not Requested, which is the default. With any of the others the check does not trigger.

The Refund in Mirakl button is always visible in Odoo 17, 18, 19 and 20, including when the order is already refunded. The message is what stops the second click.

In Odoo 20.0 the button's method works in this order: first it checks that your user belongs to the Mirakl Manager group; then, order by order, it looks at whether the state is Refunded and, if so, raises the message. Only if it is not does it send the refund.

The code explains why the guard exists: a refund is money and the call to Mirakl is not idempotent. Without the check, a second click would have resent a full refund, because when the order carries no requested amount the module uses the order total.

Diagram with the menu Mirakl › Operations › Orders, the Refund in Mirakl button, the Refund State field and the already-refunded order message
Diagram built with code from the module's published code (not an Odoo screenshot): the menu, the button, the state field and the message, with the English labels from the code, for Odoo 17, 18, 19 and 20.

How to resolve it, step by step

  1. Open Mirakl › Operations › Orders and go into the order named in the message. Its name, or identifier, is the first gap.
  2. Look at Refund State in the Refund group of the form. If it says Refunded, the message is the expected one: it is exactly the condition that raises it.
  3. Compare the amount and date in the message with the refund you thought you had made.
  4. If they match, do not press again. The order is already recorded as fully refunded, and repeating it would send a second refund to the marketplace.
  5. If they do not match, your click has sent nothing new: the message stops the action. Review that refund before doing anything else.
  6. For other orders, check the state in the Mirakl Orders list before pressing the button: it is shown there too.

If the state is Pending, Partial, Error or Not Requested, this message will not stop you: the check only looks at whether the state is Refunded.

What happens when the message does not appear

With the order in any other state, the Odoo 20.0 method sends the refund to Mirakl through the order's instance. The amount is the one requested on the order and, if there is none, the order total. The fields of that instance are explained in The Mirakl Instance fields.

If the send succeeds, the module stores the state Refunded, or Partial if the amount sent is lower than the order total, together with the amount and the date. Those are the data this message later shows you.

If the send fails, Odoo shows you the error and the refund is not marked as done. The same applies if it is FlexigoTech Cloud that does not let the send through: the order is not marked as refunded. The connection to Mirakl goes through that service, which keeps the credentials encrypted and watches the synchronisation.

What to check afterwards

Once you have checked an order, go back to the Mirakl Orders list and look at the Refund State of the others: that field is in the list too. That way, before pressing Refund in Mirakl, you know whether the message will appear or whether the module will send the refund.

Remember that the button does not change or disappear when the order is already refunded: it is always visible, and what stops it is the message. If a different message appears when you press it, it is not this one: this one only appears with the state Refunded.

How FlexigoTech can help

FlexigoTech implements Odoo 17, 18, 19 and 20 and builds custom connectors and integrations. If you want to review how the refund flow looks in your Odoo, get in touch from the module page or see its Odoo Apps listing.

Keep reading

Mirakl Connector instance fields: a checklist for OdooChecklist for filling in the Mirakl Connector instance in Odoo: connection, settlement accounts and options, with what each field's help text says.Mirakl Instance fields in Mirakl Connector: what each means and what to setA side-by-side guide to the Mirakl Instance fields in Mirakl Connector for Odoo: what each help text says, the default value and what to set.
Checked in the connector's source code (version 20.0) and the linked sources

Sources