FlipStaff
Back to Blog
Reseller Outsourcing

How to Write SOPs for Your Reselling Business So a VA Can Run It Without You

July 4, 2026

A VA without an SOP is an expensive improviser. A VA with a clear SOP is a multiplier. Here's how to write SOPs for a reselling operation that a new hire can actually follow from day one.

How to Write SOPs for Your Reselling Business So a VA Can Run It Without You

The thing keeping most reselling businesses owner-dependent is not the staff they haven't hired. It's the documentation they haven't written.

An SOP — standard operating procedure — is the difference between a VA who follows your process exactly and one who invents their own version of it. In a reselling operation, invented process costs money: listings that don't rank, offers that are inconsistent, appointments that don't get confirmed.

Here's how to write SOPs that actually work.


What an SOP Is (and What It's Not)

An SOP is a written, step-by-step description of exactly how a task gets done in your business. It covers the what, the how, the in what order, and the what-to-do-when-something-goes-wrong.

An SOP is not:

  • A general description of the job
  • A list of things the VA should figure out
  • A training video where you do the task once and call it documented
  • Your mental model explained verbally on a call

The test for a good SOP: can a competent person who has never worked in your business follow it and produce the same output you would? If the answer is yes, it's an SOP. If the answer is "only after I explain what I meant," it's a starting point.


The Four Sections Every Reseller SOP Needs

1. Purpose One or two sentences explaining what this SOP covers and why it matters. "This SOP covers how to research sold comps and set listing prices on eBay. Accurate pricing against sold comps determines sell-through rate and margin."

The purpose section isn't fluff — it's the frame that helps your VA understand why each step matters, not just what it is.

2. Step-by-step process Numbered, sequential, specific. Not "price the item based on market value" — that's a vague instruction. Instead:

  1. Open eBay and search the exact model name + storage variant in quotes
  2. Apply the "Sold Listings" filter on the left sidebar
  3. Apply the "Condition" filter matching the item's grade
  4. Sort by "Most Recent" and scan the last 30 days of sales
  5. Remove any outliers (items with missing accessories, unusual bundles)
  6. Calculate the average of the remaining sales and set the listing price within 5% of that average
  7. Log the comp price and the listing price in the daily tracking sheet

That is an SOP. A VA can follow it.

3. Decision rules and edge cases Every task has edge cases. What does your VA do when there are fewer than 5 sold comps to average? What if the sold comps span a wide price range with no clear center? What if the device category has a comp from 90 days ago but nothing recent?

Document the answers. Make the decisions in advance. "Use your judgment" is not an edge case instruction — it's a gap.

4. Quality check criteria What does a correctly completed task look like? For a listing SOP: title is over 60 characters, item specifics are 100% complete, price is within 10% of comp average, condition grade matches the rubric. A VA who knows the quality standard self-checks against it. One who doesn't know what "good" looks like can't tell when they've hit it.


Which SOPs to Write First

Write SOPs in order of how frequently the task runs and how much it costs when done wrong.

Priority 1 — Daily, high-cost-if-wrong:

  • eBay listing process (title, pricing, item specifics, condition grading)
  • Lead pre-screening script and qualification criteria
  • Appointment confirmation process

Priority 2 — Daily, lower-cost-if-wrong:

  • Daily pickup log entries
  • Listing photo standards
  • Poshmark sharing routine

Priority 3 — Less frequent, but important:

  • Escalation process for edge cases
  • Stale listing review and reprice procedure
  • Driver communication protocol for dispatcher role

Common SOP Mistakes

Too vague — "Check prices and list accordingly" is not an SOP. It's a job description sentence. Every step needs to be specific enough that the output is predictable.

Written once, never updated — your processes evolve. An SOP for how you listed eBay items in 2024 may have wrong item specifics categories, outdated shipping logic, or platform changes that have since happened. Review SOPs quarterly at minimum.

Stored where no one can find them — SOPs that live in your Google Drive folder that you haven't opened in three months are not operational. Your VA needs a single, organized location where they can find every SOP they need without asking you.

No version control — when you update an SOP, archive the old version and date the new one. Your VA should always know they're working from the current version.


The Format That Works

Short paragraphs. Numbered steps. Clear headers. Screenshots where visual guidance helps (for interface-based tasks like eBay or Poshmark workflows, screenshots save a significant amount of description).

Loom videos as companions to written SOPs are useful during training — not as a substitute for written documentation. Video is hard to search, can't be scanned quickly, and becomes outdated faster than written steps.

The written SOP is the canonical source. The video can support it.


What Good SOP Infrastructure Looks Like

A fully documented reselling operation has a central repository — usually a shared Google Drive folder, Notion workspace, or similar — with SOPs organized by role:

  • /Listers/ — eBay listing, Poshmark listing, pricing, photo standards, cross-listing
  • /Appointment Setters/ — screening script, scheduling, confirmation, follow-up
  • /Negotiators/ — pricing sheet, objection guide, escalation rules, offer log
  • /Dispatchers/ — route confirmation, driver communication, daily log, tool access

Every SOP is dated, versioned, and accessible to every team member who needs it.

Building this fully takes 20–40 hours spread over 2–4 weeks. It's real work. But once it exists, every future hire is faster to ramp and more consistent in output.

For how to use SOPs during onboarding, see how to onboard a VA into your reselling business. For the bigger picture on building a remote team, see the complete guide to building a remote reselling team.


Let FlipStaff staff this for you — FlipStaff places staff who arrive with baseline reseller training so your SOP build starts on a shorter foundation, not from zero.