This guide gives you a repeatable SOP for pricing and comps workflows so you can reduce backlog, protect margin, and keep your week predictable.
If you’re new, start here: Start Here.
Goal
Build a workflow that a busy reseller can run consistently without guessing, rework, or losing track of items.
Who this is for
- Intermediate resellers who second-guess prices or waste time comping
- Resellers who need a system they can reuse every week
- Anyone cleaning up process gaps before scaling inventory
When to use this guide
Use this when your workflow feels inconsistent, items are piling up between steps, or margin decisions are happening too late.
What “good” looks like
- Every item has a status
- You can explain what happens next for each item
- You can stop and restart the workflow without losing context
- You can spot bottlenecks before they become stale inventory
The SOP (Step-by-step)
1. Prep the work window (5 minutes)
Set one timer, one workspace, and one queue for this run. Do not mix intake, pricing, and listing tasks in the same pile.
2. Process items in status order (10-20 minutes)
Work oldest items first or use a simple rule like “anything in queue over 7 days goes first.” Example: one delayed pricing decision can stall an entire bin, so this SOP uses a hold rule instead of endless comping.
3. Apply decision rules before perfection
Use a decision rule for each item: list now, hold for research, clean/test, or skip. This prevents the same item from being handled multiple times.
4. Capture pricing and margin thresholds
Set a minimum margin target and a skip rule before you continue. A simple threshold (for example, net margin 30%+ or a minimum dollar profit) keeps pricing consistent.
This is where FlipFinds can reduce manual tracking if you want one place for item status, costs, and margin checks.
5. Close the loop and stage the next action
At the end of the run, every item should be listed, staged, or assigned to a dated follow-up queue. Nothing goes back into an unlabeled pile.
Decision rules (If X, then Y)
- If an item has no cost recorded, stop and capture cost before pricing or listing.
- If an item needs more than 5 minutes of research, move it to a dated research hold queue.
- If the expected margin is below your floor, skip, bundle, or relist with a better title/photo set before buying more similar inventory.
- If the queue is growing for two straight weeks, reduce new sourcing volume until the queue stabilizes.
- If the item condition is unclear, photograph and note the issue before writing the title.
Phase checkpoints (major workflow phases)
Intake checkpoint
Every item should have a status, cost, and source date before it enters pricing or listing. If you cannot answer those three fields quickly, the item is not ready to move forward.
Pricing checkpoint
Use one margin floor and one skip rule for the entire session. Do not change the rule halfway through because one item looks promising.
Listing checkpoint
Before publishing, confirm photos, title, and specifics agree with the actual condition. This reduces buyer messages, avoidable returns, and relisting work later.
Storage / queue checkpoint
Your listed inventory should be physically separate from anything still in process. Use labels, bins, or shelves that match your status names so you can restart the workflow without guessing.
Time and effort
- First setup: 30-45 minutes
- Weekly maintenance: 10-20 minutes
- Monthly cleanup/reset: 30 minutes
Tools and setup (keep it simple)
You do not need a complicated stack. You need a consistent way to capture status, cost, and next action.
Minimum setup:
- One intake surface (table, shelf, or bin)
- One status system (labels, bins, or app statuses)
- One place for costs and pricing notes
- One weekly review time
Optional upgrades:
- A dedicated photo spot with repeatable lighting
- A scale for shipping estimates
- A simple margin floor by category
- A dated research-hold queue so indecision does not clog the workflow
Setup checklist (one-time)
- Choose your status labels (for example: Intake, Research Hold, Ready to List, Listed).
- Pick one place to capture cost and one place to capture item status.
- Set a margin floor and a skip rule before the next sourcing run.
- Label your bins or shelves to match the statuses.
- Decide when the weekly maintenance review happens (same day/time each week).
Pitfalls and fixes
- Writing titles before basic condition notes. Fix: inspect first, then title.
- Keeping “maybe” items in the active queue. Fix: set a hold deadline.
- Re-doing the same comps twice. Fix: note your price band once.
Quality checkpoints
Quality checkpoint: every item has cost, source date, and one next action before it leaves intake.
- Pricing checkpoint: your threshold rule is written down before comping starts.
- Listing checkpoint: titles and photos match item condition notes.
- Storage checkpoint: listed inventory and unprocessed inventory are physically separated.
What to track in week 1 (baseline)
For the first week, do not optimize everything. Just collect a baseline so you know whether the SOP is helping.
Track:
- Number of items entering intake
- Number of items moved to listed
- Number of items moved to hold/research
- Average time to complete one session
- Count of items still sitting without a next action
After one week, tighten only one rule (for example, your hold deadline or margin floor).
Example workflow run (30-minute block)
Here is what one realistic block can look like:
- Minutes 0-5: Prep table, open queue, pull the oldest bin.
- Minutes 5-15: Intake and status assignment for every item in the bin.
- Minutes 15-23: Pricing decisions for the list-now items using one margin floor.
- Minutes 23-28: Queue anything delayed (research/clean/test) with a dated note.
- Minutes 28-30: Record counts and set the next session focus.
The point is not to finish everything. The point is to leave every item with a clear next action.
Common mistakes (and how to fix them)
- Trying to finish every item in one pass. Fix: move items by status and close one stage at a time.
- Letting research holds become permanent. Fix: set a hold deadline and a skip rule.
- Skipping weekly maintenance. Fix: run one short review to catch backlog before it compounds.
- Changing pricing rules mid-session. Fix: keep one margin threshold for the whole run, then adjust next week if needed.
- Treating photos as a separate project. Fix: retake only what blocks the listing right now.
One-screen implementation checklist
- Pick one queue and one status system
- Set your minimum margin/skip rule
- Process the oldest items first
- Capture next action for every item
- Separate listed vs unprocessed inventory
- Schedule the weekly maintenance review
Monthly reset (30 minutes)
Once a month, run a reset pass:
- Count items by status (intake, hold, ready, listed)
- Identify the oldest queue and clear or reclassify it
- Review your skip rule and margin floor
- Spot one recurring bottleneck (photos, comps, storage, shipping)
- Change only one process rule for next month
This monthly reset keeps the SOP useful as your volume changes.
How to adjust the SOP without breaking it
Change one rule at a time and test it for one week.
Good changes:
- Shortening the research-hold deadline
- Raising or lowering a margin floor by category
- Splitting one large queue into two smaller statuses
- Moving weekly review time to a day you actually keep
Bad changes:
- Replacing the entire workflow after one messy week
- Changing pricing, intake, and storage rules at the same time
- Adding new tools before the current process is stable
Weekly maintenance routine
Run a short review once a week: clear stale queue items, check recent pricing decisions, and confirm items still match your process rules. Keep it short and repeatable. Write down one bottleneck and one fix before you end the review so next week starts with a clear focus.
Next step
Use this SOP for one week, then adjust only one rule at a time. The goal is consistency first, optimization second.
If you want this workflow in an app, get FlipFinds on Google Play or download it on the App Store.
Related reading
Related reading for the same operating loop: