Buylist
Use Buylist
Use Buylist to review customer sell-to-store submissions, adjust offers, and complete accepted buys.
Before you start
- Confirm buylist settings and payout rules.
- Have a staff process for condition review and offer approval.
What success looks like
- Submissions move through review and completed states.
- Accepted items and payout records match the final customer agreement.
- Customer history reflects completed buylist activity.
Quick start
The shortest path through this area.
- 1Open Sales > Buylist.
- 2Review incoming submissions.
- 3Open a submission and verify each item, condition, and quantity.
- 4Adjust accepted/rejected items and payout values as needed.
- 5Communicate the final offer to the customer.
- 6Complete the buylist transaction using the correct payout method.
- 7Confirm accepted items enter inventory if your workflow adds them automatically.
Common tasks
Open only the task you need.
Set what the store acceptsAcceptance settings are the outer rules; buylist price rules apply only inside them.
- 1Open Settings in Buylist and choose the accepted games, conditions, printings, and languages.
- 2Enable Cash, Store Credit, or both payout methods, then check for warnings on existing rules.
- 3Open Pricing Rules and create a named market-price range for the inventory you want to buy.
- 4Set the buy percentage and optional minimum and maximum market prices, then enable the rule.
- 5Test the customer buylist with one accepted and one rejected card.
Review a customer submissionInspect the actual cards before approving quantities, conditions, and payout.
- 1Open Pending and choose the submission.
- 2Match the customer or create their customer record if required.
- 3Review each card, correct received quantity or condition, and approve or reject it.
- 4Compare the final cash and store-credit offers, then confirm the customer’s payout choice.
- 5Complete the submission only after the cards and payout agree.
Process a counter buyUse POS Buy mode when a customer brings cards directly to the counter.
- 1Open POS, select the correct location and station, then switch to Buy mode.
- 2Search or scan each card and choose the exact version and condition.
- 3Review the calculated offer and adjust only when staff has permission and a clear reason.
- 4Choose cash or store credit, complete the payout, and verify the accepted cards entered inventory.
How this area works
Reference information for the choices on this page.
Reviewing submissions
- Compare submitted condition to the physical card.
- Reject cards that are missing, damaged beyond policy, or incorrectly identified.
- Adjust values before final acceptance.
Payout handling
- Use store credit when the customer wants credit on their account.
- Use cash or other payout methods only according to store policy.
- Complete the submission only after the customer accepts the final offer.
Actions on the Buylist page
- Use Pending to review new or unfinished customer submissions.
- Use Completed to look up submissions that have already been resolved.
- Use Pricing Rules to create, edit, enable, or delete market-price ranges and buy percentages.
- Use Settings to enable or disable buylist, choose cash and store-credit payout methods, and control accepted TCGs, conditions, printings, and languages.
- Use search to find submissions by customer, card name, or buylist/order number.
- Use bulk delete only when you are intentionally cleaning submissions and have confirmed the selected rows.
- If legacy draft lookup is enabled, search by customer email or BL-number to resume or create draft submissions.
Troubleshooting
Choose the symptom that matches what you see.
The submitted card is wrong
Correct or reject the line before completing the submission. Do not accept a line that does not match the physical card.
Customer store credit looks wrong
Check whether the buylist was completed, canceled, or paid by a different payout method.
Continue with a related guide
Still stuck?
Open a support ticket. We’ll include this guide so you only need to explain what happened and where you got stuck.
Sign-in is required to protect store information.