Sometimes a part you've ordered turns out not to be needed — wrong fit, customer declined the work, or the car has a different issue than first thought. Pistonlog handles this with a two-step flow: flag for return on the jobcard, then process the return in the parts area.
Flag from the jobcard
Find the part on the jobcard
Open the jobcard, find the job containing the part, expand the parts table.
Open the return dialog
Click the part's status pill to open the status dropdown, then pick Return required. A dialog asks for a reason (e.g. "wrong size", "customer declined") — this becomes part of the audit trail and shows up when you process the return.
The part's order status moves
Confirming sets the part's order status to return_required and stores flaggedForReturn: true plus the reason. It stays attached to the job for the record but won't bill the customer.
Then process the return
When you've sent the part back to the supplier, mark its order status return_sent, then credited once the supplier has refunded you. See Parts returns for the parts-side admin flow.
Returns are a record, not just a tag
The flag + reason are stored on the part row, so even after the return is processed you can see why it was returned. Useful for spotting patterns — same part repeatedly returned suggests you're stocking the wrong reference.