How The Integration Works
4 min
outline the integration runs in two directions refundid tells shipmonk what to expect, and shipmonk tells refundid what turned up creating the return in shipmonk when a customer lodges a return, refundid creates a return in shipmonk containing the refundid rma reference, so warehouse staff can match the physical parcel to the return a reference to the original order, so shipmonk can link the return to the sale the return tracking number, which lets the warehouse identify the parcel when it arrives one line per returned item, with the sku and the expected quantity a return reason, mapped from the reason the customer selected in the portal to the equivalent shipmonk reason code so size related returns, wrong item returns and change of mind returns are reportable in shipmonk a desired action of receiving the item back into inventory multiple warehouses and regions if you fulfil from more than one shipmonk warehouse, the return is created against the right one automatically the order's currency and region determine which warehouse and store the return is created against, so a us order goes to your us facility and a uk order to your uk facility without your team having to route anything receiving the return when your fulfilment centre processes the return, shipmonk notifies refundid with what was received for each item refundid checks two things quantity was the received quantity at least the expected quantity? disposition was the item returned to inventory, or dispositioned some other way for example held aside or returned to the merchant as unsellable? when everything matches if every item arrived in full and was returned to inventory, the return is closed in refundid automatically and the customer's resolution is processed your team doesn't need to touch it when something doesn't match if any item is short, or was dispositioned as anything other than returned to inventory, the return is not closed automatically instead refundid flags the return docid 5gmoihujts7quhdxhecde in your dashboard adds a note explaining exactly what didn't match for example "received 1 of 2 expected" or the disposition the warehouse recorded the return then sits in your dashboard for a person to decide on this is deliberate a short or damaged return is a commercial decision, not something an integration should make on your behalf you can find flagged returns quickly using a flagged filter on your dashboard