How The Integration Works

outline returns are created in bundle when the customer lodges, then polled until the warehouse has finished with them creating the return in bundle when a return is lodged, refundid creates an order return in bundle containing the refundid return id , sent as the external request reference so the same return can be recognised on both sides the order number , used to resolve the original order in bundle the refundid rma reference , so warehouse staff can match the physical parcel one item per returned line , with the sku, the quantity and the return reason a restock disposition is only sent where the item is explicitly marked for restock at lodgement refundid deliberately doesn't infer "dispose of this" from the absence of a restock instruction that decision belongs to the warehouse when they inspect the goods the identifier bundle returns is stored against the refundid return, and that's what's used to track it from then on tracking the return refundid checks each open bundle return on a schedule returns still sitting at created , accepted or in progress stay pending and are checked again next time nothing is closed while the warehouse still has work to do closing the return once the bundle return reaches a final state, the refundid return is closed to match received items are accepted and restocked, and the customer's resolution is processed discrepancy, failed or cancelled the return is closed as cancelled by the merchant with no restock, and a note records the bundle outcome and reference items rejected or quarantined a return can be received overall while individual items still fail inspection where the warehouse marks an item as rejected, or sends it to quarantine rather than back into sellable stock, that item is cancelled even though the return itself was received notes on the return record which item failed and the action the warehouse took the rest of the return is unaffected items that passed inspection are still accepted and refunded returns bundle can't match to an order if bundle can't resolve the order reference to one of your orders, the return is held for review rather than closed either way it's surfaced for your team to look at, since it usually points to an order reference mismatch rather than anything the customer did returns already closed in refundid if your team has already processed the return in the refundid dashboard by the time bundle reports its outcome, the return is recognised as closed and left alone it's never closed twice or reopened