Ribbn SDR Sales EnablementRibbn SDR Sales Enablement

Seller Sourcing: Sell Requests + Digital Consignment

What this talk track is for

Seller sourcing is where Ribbn earns the right to be the system of record for resale: you bring in inventory predictably, digitize it fast, and keep sellers informed with clear decisions and payout visibility.

This page equips you (SDRs) to:

  • Tell a consistent Sell Requests + Digital Consignment narrative
  • Run a simple qualification path for seller acquisition workflows
  • Set pricing/packaging guardrails without overcommitting
  • Handle first-line objections tied to “stuck requests,” payouts, and omnichannel reality
Scope reminder: this is **not** an operator/admin SOP. You’ll reference outcomes + decision points and use workflow-true language.

Ribbn narrative (seller sourcing → sell-through → payout)

The one-liner (use on calls)

Ribbn helps secondhand businesses run end-to-end resale commerce—seller sourcing, one-of-a-kind inventory, omnichannel selling, and payouts—through a clear lifecycle that keeps items (and sellers) from getting stuck.

The 30-second talk track (seller sourcing–anchored)

  • Seller sourcing starts with Sell Requests: sellers submit items digitally, the store reviews each item, sets a resale price, accepts/declines, and then confirms the selection to notify the seller in one consolidated update.
  • Digital consignment + commissions: items are linked to sellers with clear commission splits, so payout math is explicit and trackable.
  • Lifecycle control: after drop-off, the team moves items through admin-driven statuses (Draft → QC → Listed), and post-sale statuses support payout steps (manual or seller self-pay in supported flows).
  • Omnichannel: sell in-store via Ribbn POS flows, and for ecommerce Ribbn can sync products to Shopify while staying the source of truth for inventory and product data.

Core workflow concept SDRs must get right: “Confirm Selection”

Why it matters (in plain language)

Sell Requests are the front door for seller inventory. Ribbn’s key behavior is:

  • Accept/Decline updates internal status,
  • but the seller doesn’t get notified until the store clicks Confirm Selection.

This is both:

  • a seller experience “trust moment,” and
  • a common source of “why are sellers saying they can’t see anything?” confusion.
If a prospect describes “requests getting stuck” or “sellers not seeing decisions,” translate it directly to: **they’re missing the Confirm Selection step** (or don’t have a clean review discipline). Don’t prescribe ops steps—just connect the pain to the workflow reality.

Sell Request decision points (merchant lens)

Merchant decision pointWhat Ribbn supportsWhy the merchant cares
Do we accept/decline items before they arrive?Sell Requests with item-by-item Accept/DeclinePrevents low-quality inventory and wasted intake time
Who sets resale pricing—and when?Store sets resale price during review (with a suggested price shown)Protects margin + brand positioning; creates consistent seller expectations
How do sellers get the decision?Confirm Selection sends one consolidated updatePrevents messy back-and-forth and “I never heard back” friction

Digital consignment (what to emphasize in SDR language)

What “Digital Consignment” means (outcome-first)

Digital consignment in Ribbn is the set of workflows that lets a store:

  • Link items to sellers, with commission tracking per item
  • Let sellers submit items from home (Sell Requests)
  • Support seller payouts, including seller self payout in supported flows

Trust drivers to call out (without turning into SOP)

These are the operational “trust anchors” prospects care about:

  • Lifecycle status visibility: items move through clear statuses from request → prep → listed → sold → payout.
  • Return-window gating (typical): payout steps commonly happen after a return period (often referenced as ~14 days in support content).
  • Payout clarity: Ribbn supports post-sale payout statuses and (in supported flows) seller self-pay to reduce admin workload.
If a prospect pushes for “fully automated payouts,” “guaranteed compliance,” or country-specific identity verification, route to AE/SE. Keep claims to **workflow support** only.

Where AI QuickList fits (positioning for seller acquisition)

The SDR framing

When seller sourcing scales, the bottleneck becomes: intake speed + listing quality.

Ribbn supports AI-assisted item creation (“AI QuickList”) as part of digitizing items faster—so the store can say “yes” to more sellers without drowning in admin.

Discovery tie-in

Ask:

  • “When sellers submit items, what slows you down more—reviewing/pricing, or digitizing/listing once the item arrives?”

Qualification path: Seller Sourcing (meeting-worthy) in 6 questions

Use these to qualify fast and route correctly.

1) Seller acquisition motion (the sourcing model)

  1. “Are you running resale on consignment (seller payouts), buy-out, or a mix?”
  2. “How do sellers submit inventory today—digitally or mostly walk-ins?”

2) Sell Request decision discipline

  1. “Do you have an approval step before items arrive—and who owns the accept/decline decision?”
  2. “When you accept items, who sets resale pricing and when does the seller get notified?” (Listen for delays / manual messaging / confusion.)

3) Payout expectations (and operational trust)

  1. “How do you handle payouts today—manual after a return window, store credit, or something else?”

4) Omnichannel reality (where inventory must stay accurate)

  1. “Do you sell in-store via POS—and is Shopify your storefront? What’s your source of truth for one-of-a-kind inventory?”

“What to listen for” (qualification signals)

Strong fit signals (book it)

  • They want/need a digital seller submission flow (or want to move there)
  • They’re overwhelmed by intake/admin work (need lifecycle + bulk discipline)
  • They struggle with one-of-a-kind inventory accuracy across in-store + online
  • Payouts are messy and they want clearer seller earnings + payout statuses

Risk / misfit signals (clarify before booking)

  • They expect Ribbn to replace Shopify as a full ecommerce storefront (depends on setup; position Ribbn as system of record + sync)
  • They want guarantees on compliance, taxes, or payout automation (route to AE)

Pricing & packaging (SDR guardrails)

Use this to stay helpful without overpromising.

What’s safe to say (high level)

Ribbn offers tiered plans and transaction fees, with add-ons commonly tied to:

  • Seller sourcing & inventory (AI QuickList, digital consignment, seller self payouts)
  • Ecommerce (Shopify app integration)
  • POS/checkout (mobile checkout, Web POS)
  • Hardware/add-ons (QR codes, RFID, extra terminals)
  • Marketplace integrations (e.g., Tradera integration add-on)

Plan snapshot (use for quick reference)

PlanMonthlyTransaction fees (per pricing sheet)Good fit shorthand
Starter$70 / month+1.5% on physical store salesEarly-stage / basic workflows
Business$295 / month (sheet shows $329 crossed to $295)+1.5% on store sales, 0% onlineMost established single-location resale ops
Commercial$595 / month (sheet shows $724 crossed to $595)+1% on store sales, 0% onlineHigher-volume / more complex ops

Common add-ons (only if asked)

Add-onPrice (per pricing sheet)When it comes up on sourcing calls
QR codes for checkout (1000 yearly)$30 / monthFast in-store scanning once inventory scales
RFID gun$100 / month (min subscription note on sheet)“We lose items / can’t locate inventory”
RFID tags$0.5 / tagSame as above; item-level tracking at scale
Tradera integration$100 / monthThey want more sell-through via marketplaces
Extra mobile terminal$80 / month per terminalMulti-register / busy intake + checkout periods
“Both POS + Shopify integration” bundle+$49 / monthThey need in-store checkout and Shopify sync
If a prospect asks for discounting, final packaging, or anything not explicitly on the sheet: don’t improvise—route to AE.

Objection handling (first-line)

“We’re worried requests will get stuck / missed.”

Response (SDR-ready): “Ribbn is built around lifecycle status management—from Sell Request review through draft/QC/listed and into post-sale payout steps—so teams can keep items moving consistently. One key detail: sellers only get notified after Confirm Selection, so the workflow is designed to send one clean update instead of noisy item-by-item pings.”

“Payouts are a pain.”

Response (SDR-ready): “Ribbn supports clear post-sale payout statuses. Teams often gate payouts behind a return period, and in supported flows there’s a seller self-pay status that reduces admin work. The store still controls the policy—Ribbn provides the workflow structure.”

“Does this replace Shopify?”

Response (SDR-ready): “Most commonly, Shopify stays the storefront while Ribbn is the system of record for resale inventory and product data. The team creates/edits items in Ribbn and syncs to Shopify when ready—edits in Shopify don’t sync back to Ribbn.”


Meeting bar: when to book AE/SE (seller sourcing edition)

Book when you confirm 2+ of the following:

  • Meaningful seller intake volume (they need consistent Sell Requests → review → notification)
  • Clear pain in intake/admin workload or items getting stuck (lifecycle + bulk ops relevance)
  • Consignment + payouts complexity (manual payouts, store credit incentives, self payout interest)
  • Omnichannel complexity (in-store POS + online storefront sync, often Shopify)

Quick “workflow map” you can say out loud

Use this as your verbal whiteboard:

  1. Seller submits items via Sell Request
  2. Store reviews each item, sets price, Accept/Decline
  3. Store clicks Confirm Selection → seller gets one consolidated update
  4. After drop-off: Draft → Quality Control → Listed (inventory becomes sell-ready)
  5. Item sells → Ribbn moves to sold/payout statuses (manual or self-pay in supported flows)