Purpose
Learn how the In‑Store workflow works—from the moment an offer is created until the item is successfully added to your inventory or returned to the customer.
How's Default In Store Workflow
1. Manual Quote
Purpose: Used when Custom Quotes are created and your customer is waiting for your team’s review.
Sub-statuses:
Pending: Your team confirms the quote can be processed and enters prices.
Requires Review: Waiting for the customer to accept or decline the quote.
Next Step (based on customer response):
Accepted: Moves to Active Leads, and the customer is expected to visit your store.
Declined: Moves to Cancelled.
Also read: How Custom Offers Work in In‑Store
Note
Your customer will be informed through the Customer Portal.
2. Leads
Purpose: Where buyback offers land after being created from the widget.
Sub-statuses:
Abandoned buyback: Customers didn’t continue after generating a quote.
Cancelled: Customers explicitly cancelled the offer.
Active leads: Customers are engaged and plan to visit the store.
Action: Verify the customer’s information.
Next steps: When the customer arrives with their device, move the offer to Being Inspected.
Tip
Use clear internal notes to track visit dates, follow‑ups, or special instructions.
3. Being Inspected
Purpose: For offers where your team is actively inspecting the device(s).
Action:
Check the item thoroughly and update details based on the actual inspection.
(Optional) Add images and internal notes.
Next steps:
If the offer is ready for payment → move to Payout Processing.
If the device doesn’t match the description → move to Not as Described.
Tip
Add detailed internal notes so future reviewers can clearly see what was found during inspection.
4. Payout Processing
Purpose: For offers where all devices passed inspection and are ready to be paid out.
Action:
Pay the customer.
Record the Transaction ID (optional, for your internal records).
Next steps: Once payment is complete, move the offer to Completed.
5. Not as Described
Purpose: For offers where the device does not match the original description.
Actions:
Edit the item details (via the meatballs menu ⋮ → Update Item), including:
Internal notes for defects and inspection findings
Reason
Condition
Payout / price
(Optional) IMEI/SNNote
Notes
Updates appear in the Customer Portal.
Turn on Send Email to notify the customer about the changes.
Next step (based on customer response):
Accepted: Status moves automatically to Seller Accepted.
Declined: Status moves to Return.
Tips
Use clear language when explaining condition differences to avoid confusion.
Add images for stronger, more transparent confirmation.
5. Return
Purpose: For offers where the customer declines the buyback or requests their device back after inspection.
Actions: Prepared to give the devices back to the customer.
Next steps: After the devices are sent back, move the offer to Returned.
6. Completed
Purpose: For offers where the customer accepted the payout and the entire process is finished.
8. Returned
Purpose: For offers where devices have successfully been returned to the customer, finalizing the return process.
By following this In‑Store workflow, your team can move every buyback offer from quote to inspection, payout, or return in a clear and consistent way. Keeping your operations organized and your customers confident in every step.