Loop offers the ability to make changes to returns that have already been submitted by customers. Edit actions can be taken on returns that are in an open state and have yet to be processed.
The following is covered in this article:
- General Edit Functions
- Removing Line Items
- Editing the Return Method for Returning Items
- Editing the Refund Method
- Editing Fees
- Regenerating Labels
- API Implications
General Edit Functions
Edit capabilities enabled by default. This functionality can be disabled by toggling the setting off in the Return management module in Settings > General
To edit a return, simply access an open, un-processed return within the Loop admin. Edit functions will appear contextually within the return view. Loop now includes a totals module that gives visibility into the financial breakdown of the return and allows for various edit actions.
Removing Line Items
Loop offers the ability to remove "returning" and/or "purchased" items from a return. To remove a returning item, simply action the Remove button on the applicable line item in the Return Credits section:
The same action can be done for purchased items selected by the customer as part of an exchange or Shop Now purchase:
Remove actions will create either an increased credit owed to the customer or an outstanding balance owed from the customer. The totals module will reflect the impact to the return and prompt the user to take required actions to get the return to a processable state.
For example, removing a purchased item from an exchange will result in a credit remaining on the return which can be refunded to the customer's original payment method or issued as store credit:
Note: Edit actions that result in an outstanding balance (amount owed by the customer) cannot be processed and must be modified to to reach an even exchange or refund outcome. Loop does not currently support payment collection from customers resulting from an edit action. An example is shown below:
Editing the Return Method for Returning Items
Loop's "Keep Item" functionality offers the ability to suppress return shipping on returning items. To modify the return method for a returning item, simply action the Change to keep or Change to returning button on the applicable line item:
Editing the Refund Method
Loop offers the ability to modify the refund method on a return. To edit the refund method and choose between Original payment method or Gift card, simply select the Edit button in the refund total section:From there, simply select the desired refund method:
Loop offers the ability to edit any existing fees on a return by selecting the Options button below the fee amount in the totals module. The following options are available:
- Waive all fees - remove any fees from the return and set the fee amount to $0
- Charge a new amount - assess a new fee amount
Note: the new fee amount cannot exceed the value of credit owed to the customer, as this would create an owed balance.
Removing returning items or changing the return method of an item will result in a change to the contents of the returning package. In some cases, it may be beneficial to regenerate the return label in order to get the most accurate rate and ensure properly delivery of returned items.
When a modification to a return results in a change to returning items, Loop will offer the ability to regenerate the label associated with the return. Simply click the Regenerate label button within the module on the right to create a new label with the updated contents.
The above actions may impact an existing integration with a third party system. When an edit is made to a return, Loop reflects the new return data within our APIs and webhook payloads.
For integrations that rely on Loop webhooks:
The addition of a new field titled
edited_at will contain a timestamp from the most recent change and will deliver new returndata from a return that has been edited. If the return has not been edited, this field will have a null value. The payload reflects the new return after an edit has been made and should overwrite any previous record created for that return. If a return has been edited more than once, the timestamp and payload will reflect the current return data after the most recent edit.
For integrations that rely on Loop’s rest API:
Return data pulled from the rest API will reflect the most current state of a return. If a return was edited, the rest API will display a timestamp in the
edited_at field and reflect the new return and all associated data. If the return has not been edited, this field will have a null value. If a return has been edited more than once, the timestamp and payload will reflect the current return data after the most recent edit.
Do I have to save edits before I can process a return?
Yes. Once an edit action is taken on a return the return goes into "edit mode". To finalize the edits and allow for processing simply click the Save button in the top banner.
Do customers receive a notification when a change has been made to a return? No. Currently, customers do not receive notifications for changes made to their return. We are working to define the most effective way to communicate changes to customers and will include this functionality in a future iteration of this feature.
Are edits reflected in the return timeline within Loop? Yes. Edits made to a return are reflected in the return timeline and include the action taken and the user who performed the edit.
Will the edit return updates be pushed to the API? Yes, edits are reflected in webhook and API payloads. See the above section titled API Implications or view our API documentation for more details.
Can I edit returns through the public API? Not yet, but this is currently in development and will be available soon.
Why can’t I charge a customer’s credit card for an owed balance created by making an edit? Currently, we cannot resolve a scenario in which an edit creates an owed balance by the customer. This will be part of a future iteration of this feature.
Why can't I use Keep Item? To leverage Keep Item in Edit Return, it needs to be turned on in the return policy under which the return was generated. If you would rather not have Keep Item on, we recommend turning it on in the return policy, with the value range set to $0 and manual processing, which will essentially keep it from doing anything, while opening up manual Keep Item functionality when editing a return.