Objection: “We’re Shopify-first—why do we need Ribbn?”
What the prospect means (and how to respond)
When a prospect says, “We’re Shopify-first—why do we need Ribbn?”, they’re usually saying one of these:
- “Shopify is our storefront already—don’t make us rebuild it.”
- “We don’t want two systems managing products.”
- “We’re worried inventory will drift and we’ll oversell.”
- “We already have checkout—why add another tool?”
Your job is to agree with Shopify-first and then clarify the responsibility split:
- Shopify = online storefront + online orders
- Ribbn = resale operations system of record (inventory + seller mapping/commissions + lifecycle + in-store POS), and it can sync products to Shopify.
Approved talk track (30–45 seconds)
Use this verbatim when you can:
“Totally—Ribbn commonly complements Shopify. The simple split is: Ribbn is where you create and manage resale items—one-of-a-kind inventory, seller mapping, commissions, and lifecycle statuses—then you sync/publish those items into Shopify so Shopify can be your storefront. Shopify is where you turn products Active and manage online orders. Ribbn stays the operational source of truth, because edits made directly in Shopify don’t sync back to Ribbn.”
Why this works:
- It validates Shopify-first.
- It frames Ribbn as the behind-the-scenes system of record (not a storefront replacement).
- It anchors in a product-true workflow: Ribbn-first product setup → sync to Shopify → Shopify publishing + orders.
The “responsibility split” (quick reference)
Who does what?
| Responsibility | Ribbn owns (system of record) | Shopify owns (storefront) |
|---|---|---|
| Create/edit product data (incl. seller mapping + commissions) | ✅ | ❌ |
| Sync products to Shopify | ✅ (initiate from Ribbn) | ✅ (Ribbn app shows status/logs) |
| Publish product visibility (Draft → Active) | ❌ | ✅ |
| Online orders & fulfillment | ❌ | ✅ |
| In-store sales/returns (resale ops) | ✅ | ❌ |
Why Shopify-first teams still choose Ribbn (positioning pillars)
1) Ribbn is the resale “system of record” behind Shopify
Shopify is excellent at being a storefront. Ribbn is where resale teams manage the operational realities that make resale hard day-to-day:
- One-of-a-kind inventory + lifecycle control (intake → QC → listed → sold → payout statuses)
- Seller-linked items (owner/seller mapping)
- Commission splits per item (default + overrides)
- Post-sale payout steps (manual and supported self-pay flows)
Use this line:
- “Shopify is where customers buy online. Ribbn is where your team runs the resale engine that creates accurate listings and keeps seller economics clean.”
2) “Two systems” doesn’t mean “two sources of truth”
A Shopify-first prospect fears duplication. Reframe it:
- “You’re not managing the same job twice—you’re splitting responsibilities.”
- “Ribbn is the system of record for product + seller data; Shopify is the storefront and online order system.”
3) Inventory trust: sold in-store automatically removes online availability (key reassurance)
If they worry about overselling unique items:
- When an item is sold in-store and moves to a sold state in Ribbn, Shopify inventory quantity decreases.
- For unique items, when inventory hits 0, Shopify sets the product to Draft, removing it from online sale.
Use this line:
- “Ribbn helps protect one-of-a-kind accuracy: when it sells in-store, Shopify availability is reduced and the item comes off sale online.”
4) Data quality and speed: Ribbn digitizes items for resale workflows (and can sync rich fields to Shopify)
Ribbn can sync core product fields (title, description, media, price) and also pass additional resale attributes into Shopify as Meta Fields (taxonomy, brand, size, condition, seller info, commission, tags, RFID, etc.). This lets the ecommerce team build Shopify collections/filters without recreating the underlying product structure.
Use this line:
- “Ribbn is where resale data is captured correctly once, then Shopify receives it to merchandize and sell.”
Discovery questions that turn the objection into qualification
Ask 3–5, then route to meeting if you confirm 2+ “pain signals.”
Shopify-first fit questions (system-of-record)
- “If Shopify is the storefront, what’s your source of truth today for one-of-a-kind inventory and product data—Shopify, a spreadsheet, a POS, or something else?”
- “When an item is pulled for QC/repairs/hold, how do you ensure it’s not still purchasable online?”
Seller + consignment workflow (multi-seller complexity)
- “Are you taking inventory on consignment (seller payouts), buy-out, or a mix?”
- “How do you track seller attribution + commission splits per item today?”
Intake + listing speed (operational throughput)
- “How do sellers submit inventory—do you have a digital intake/request step, or is it mostly walk-ins?”
- “Where does listing slow down most—intake, photos, product data quality, QC, or pricing?”
Omnichannel execution
- “Do you sell in-store via POS today, and do you scan items (barcode/QR/RFID)?”
- “Who owns online operations vs in-store ops—and would both be on a 30-minute workflow call?”
First-line objection handling (approved responses)
“Does Ribbn replace Shopify?”
Answer: “No—Shopify stays your storefront. Ribbn runs the resale operations behind it: you create and manage products in Ribbn (including seller + commission), then sync them to Shopify to sell online.”
“We don’t want duplicate work—why not manage products only in Shopify?”
Answer: “For resale, the operational ‘truth’ includes seller mapping, commissions, and lifecycle control for one-of-a-kind items. Ribbn is designed to be that system of record. Shopify receives synced products for online selling—but edits in Shopify don’t sync back, so you avoid split-brain by keeping Ribbn as the product master.”
“What if something changes status in Ribbn—does Shopify update automatically?”
Answer (be precise and safe): “Product data is managed in Ribbn and synced to Shopify for already-synced products. One important nuance: if you change an internal status in Ribbn (like back to QC), you should also ensure the Shopify product visibility matches—because Ribbn status changes don’t automatically deactivate the Shopify listing.”
“Will we pay fees twice (Stripe/Shopify)?”
Answer: “No—fees apply where the purchase happens: Ribbn/Stripe applies to in-store purchases, Shopify applies to online purchases. You’re not charged twice for the same order.”
What to demo verbally (SDR “workflow demo” in 60 seconds)
Use a simple narrative that matches current product behavior:
- Seller submits items (Sell Requests) → store reviews/accepts/sets price → Confirm Selection notifies seller.
- Items move through statuses (Draft → Quality Control → Listed/Available) to keep ops clean.
- Team sells in-store via POS.
- For ecommerce, items are created/edited in Ribbn, then synced to Shopify (Shopify shows Draft first; Shopify sets Active when ready).
- When a unique item sells in-store, Shopify quantity drops and the listing moves to Draft when inventory hits 0—helping prevent oversells.
Quick “when Ribbn is still needed” checklist (for Shopify-first)
Book the meeting if any are true:
- They sell unique / one-of-a-kind items and struggle with inventory accuracy
- They have consignment / multi-seller complexity (seller attribution, commissions, payouts)
- Their intake/listing process is slow or inconsistent (QC, data quality, photos, batch operations)
- They need in-store + online execution with one operational source of truth
Escalation guidance (what SDRs should NOT promise)
- Exact payout automation, compliance outcomes, or country-specific identity requirements
- Detailed implementation timelines or project plans
- Pricing/packaging/discounting specifics (unless you’re using AE-approved, current pricing guardrails)
- “We’re better than Shopify” or negative competitor framing