Processing Returns In Brightpearl

outline your team doesn't need to process returns in the refundid dashboard completing the sales credit in brightpearl is enough refundid picks up the change and processes the return for you how it works your warehouse or finance team inspects the return and completes the sales credit in brightpearl as they normally would brightpearl notifies refundid when the credit changes refundid checks that the record is one of its own sales credits and that it has reached a completed status sales orders, other credits and credits still in progress are ignored the quantities left on the credit decide the outcome per item accepting and rejecting items the quantity on each credit row is what refundid acts on quantity greater than zero that quantity is accepted and the resolution is processed for it quantity of zero the item is rejected, with a note recorded against the return explaining it was rejected during inspection this means a partial approval is handled simply by editing the credit zero out the row for the jumper that came back worn, leave the dress at one, and refundid refunds the dress and declines the jumper rows that aren't items such as the return shipping deduction row are skipped and never treated as a returned item things worth knowing the return is only processed once if the credit is edited again after completion, refundid recognises the return as already closed and takes no further action because the resolution is processed at the point the credit completes, the customer's refund, store credit or exchange is triggered by your brightpearl workflow there is no separate step in the refundid dashboard returns can still be processed in the refundid dashboard if you need to for example when an item never arrives and the credit will never be completed