Discovery Playbook: Operations / Inventory Manager

Who this playbook is for

You’re talking to the Operations / Inventory Manager (often also Store Manager or Ops Lead) at a resale/consignment business. They live in the “messy middle”: intake volume, item accuracy, shopfloor readiness, omnichannel selling, and seller trust.

Your job (as an SDR): map their operational pain to Ribbn’s inventory lifecycle + tooling, qualify impact, and book a meeting with the right stakeholders (ops + ecom + finance as needed).

Ribbn’s core value narrative (Ops-friendly)

Use this when the Ops/Inventory Manager asks “what is Ribbn?”

• Ribbn is a resale commerce platform that helps secondhand stores run end-to-end operations: seller intake → digitization → lifecycle statuses → in-store POS sale → payout steps, with Ribbn as the system of record for one-of-a-kind inventory.
• Ribbn supports omnichannel: run in-store checkout (mobile app POS and web POS) and publish online via Ribbn webshop or commonly Shopify integration (Ribbn stays source of truth; Shopify is the storefront/order management for online).

30-second talk track (inventory + operations emphasis)

“Ribbn is built for secondhand operations. Sellers can submit items, your team reviews and prices them, then items move through a clear status lifecycle—draft, QC, listed, sold—and into payout steps after the return window. You can sell in-store with POS and keep online inventory in sync by publishing to Shopify while Ribbn remains your system of record.”

Operational pain → Ribbn capability map (what to listen for)

Use this to translate what they say into a qualified “why Ribbn.”

Ribbn’s inventory lifecycle (the mental model you qualify against)

Ribbn’s operations story is a lifecycle:

1. Seller submits inventory via Sell Request
2. Store Accepts/Declines, sets resale price, then Confirm Selection sends the seller a consolidated update
3. Item enters internal workflow using admin-driven statuses (Draft → QC → Listed, etc.)
4. Item sells via POS (app POS or web POS)
5. After sale, item moves through post-sale payout statuses (manual “to be paid” or self-pay in supported flows)

Discovery questions (Ops / Inventory Manager)

Use these for onboarding + daily call prep. Pick 6–8, don’t machine-gun all of them.

1) Intake & digitization (speed + quality)

• “How does inventory arrive—walk-ins, appointments, digital submissions, or a mix?”
• “What’s your biggest bottleneck today: getting items entered, getting photos, or getting listings accurate?”
• “Do you batch intake (e.g., 50 items at a time)? If yes, how do you keep them moving without losing track?”

2) Lifecycle discipline (statuses + handoffs)

• “Do you have a consistent lifecycle (draft → QC → listed → sold), or is it tracked in spreadsheets/messages?”
• “Where do items get stuck most often—post-dropoff, QC, pricing, or publishing online?”
• “How often do you need to update many items at once (QC → listed, clearance moves, etc.)?”

3) Inventory accuracy (audits, missing items, shrink)

• “How do you confirm what’s physically in the store vs what your system says—do you run stock takes/cycle counts?”
• “When something is missing, what’s your current investigation workflow and how long does reconciliation take?”

Optional: qualify with Ribbn’s tag-based stock take pattern (high level)

If they mention audits, you can sanity-check fit with Ribbn’s approach:

• “Would it help if your team could tag items found during a count, bulk-tag the ‘expected’ set, and then identify what’s still flagged as missing?”

(Keep it conceptual; don’t teach SOP on the call.)

4) Omnichannel execution (store + online + Shopify)

• “What’s your online model today—Ribbn webshop, Shopify, or something else?”
• “What’s the source of truth for product data and one-of-a-kind inventory today?”
• “Do you ever run into issues where something sells in-store but stays available online (or the reverse)?”

5) Seller trust (commissions + payouts)

• “Are you consignment, buy-out, or a mix?”
• “Do you pay sellers out manually after a return window, or do you have a seller cash-out/self-serve flow?”
• “What generates the most seller support tickets—pricing, status updates, returns, or payout timing?”

Quick product references (SDR-safe, ops-relevant)

Status Management (what it is)

• Statuses represent where an item is physically and digitally; Ribbn uses admin-driven statuses for internal workflow and system-driven statuses after events like a sale.
• Common admin-driven statuses include: DRAFT, QUALITY_CONTROL, optional PENDING_PUBLICATION, LISTED, AVAILABLE_IN_STORE, HOLD, ARCHIVED.

Bulk operations (why ops teams care)

• Ribbn supports updating many products at once via Bulk Edit in “All Products,” with action groupings (In-Inventory, Clearance, Liquidation, Post-Sale).
• Bulk Edit also supports operational actions like adding/removing tags, publishing online, and messaging sellers (useful for trust + transparency at scale).

POS reality (what to claim)

• Web POS: designed for high-paced retail; supports scanning and Stripe WiFi-based reader payments; also supports manual line items for simple fixed-price goods.
• App POS: scan (RFID/QR) or search, link to customer, complete payment (cash/manual or card reader in supported setups).

Shopify integration (system-of-record clarity)

• Ribbn commonly acts as source of truth for product creation/updates; Shopify receives synced/published products and handles online order management. Shopify edits don’t sync back into Ribbn.

Qualification checklist (book the meeting when…)

Aim to confirm 2+ of the following, then book.

• Intake + listing bottleneck: high volume, slow digitization, inconsistent quality
• Lifecycle breakdown: items stuck, unclear handoffs, inconsistent statuses
• Inventory accuracy pain: missing items, hard audits, shrink concerns
• Omnichannel complexity: in-store sales + online storefront sync needs
• Seller trust issues: payout questions, return-window gating needs, self-serve payout interest

Stakeholders to pull into the AE meeting

• Ops/Inventory Manager (required)
• Ecom lead (if Shopify/webshop is in play)
• Finance/owner (if payouts, fees, or reporting are a core pain)

First-line objection handling (Ops persona)

“We already use Shopify.”

Response: “Totally—Ribbn commonly complements Shopify. Ribbn stays the system of record for resale inventory and seller mapping. You create and edit products in Ribbn, then publish/sync to Shopify for the storefront. Shopify doesn’t sync edits back into Ribbn.”

“We’re worried things will get stuck or missed.”

Response: “That’s exactly what the lifecycle statuses are designed for—items move through defined stages like draft, QC, listed, sold, and into payout steps. And for real ops volume, teams can bulk update statuses to keep inventory moving.”

“Payouts are a pain.”

Response: “Ribbn supports clear post-sale payout statuses—often after a return period (typically 14 days)—including a manual ‘seller to be paid’ step, and a seller self-pay status in supported flows to reduce admin work. Your exact policy is still your choice, but Ribbn helps operationalize it.”

Pricing & packaging basics (SDR guardrails)

Use this as a conversation stabilizer, not a negotiation.

What’s safe to say (high level)

• Ribbn offers tiered plans with a monthly fee plus a transaction fee on physical store sales; online fees can differ by plan.
• There are add-ons for operational scale (examples below).

Quick packaging reference (from current pricing sheet)

Common add-ons Ops cares about

Escalation triggers (when to bring AE/SE in fast)

Escalate (book + flag) when you hear:

• Complex omnichannel: multi-location inventory, Shopify migration, strict “system of record” requirements
• Payout policy complexity: custom return windows, store-credit incentives, self-payout requirements, heavy seller dispute volume
• High audit/shrink pressure: they need a formalized stock take process, missing item workflows, RFID interest (could expand scope)
• Operational volume: batch updates are constant → Bulk Edit becomes central to success

Call prep: “Ops / Inventory Manager” 5-minute checklist

1. Choose your angle:
   • Intake speed (QuickList)
   • Lifecycle discipline (Statuses + Bulk Edit)
   • POS throughput (Web POS / App POS)
   • Shopify system-of-record clarity
2. Ask 2 “current state” questions + 2 “impact” questions.
3. Confirm:
   • intake volume (items/week)
   • staff involved (who touches QC/listing)
   • storefront model (Shopify vs Ribbn webshop)
4. Set the meeting bar: 2+ pains + right stakeholders.

Example: SDR-ready opener + transition to discovery

“Curious—when items come in, do you have a consistent workflow to move them from intake to QC to listed,
and then handle sold-to-payout steps without losing track?

The reason I’m asking: Ribbn is built around that lifecycle for one-of-a-kind resale inventory,
with bulk updates and in-store POS, and it can publish to Shopify while staying your system of record.”

Use the answers to steer into:

• “Where does it break today?”
• “How do you measure impact (time-to-list, missing items, seller tickets, checkout speed)?”
• “Who owns Shopify / payouts / reporting?”