Seller Programs: Commissions & Ownership Tracking
Why this matters (SDR talk track)
Ribbn is an end-to-end resale commerce platform—inventory + webshop + POS + seller sourcing + commissions + payouts tracking—so stores can run multi-seller/consignment operations with clarity and operational trust.
Use this page to:
- Qualify whether a prospect’s commission + ownership tracking needs fit Ribbn’s current workflow
- Explain Ribbn’s approach confidently without committing to unsupported edge cases
- Set pricing/packaging guardrails and route deep admin details to a follow-up (AE/CS) when needed
Illustrative examples only. No legal, tax, or financial advice—SDRs should describe *documented product behavior* and defer compliance questions.
Ribbn’s core narrative (what we do)
One-liner
Ribbn helps resale stores manage multi-seller inventory and sell it omnichannel (in-store + online), while keeping seller attribution and commission splits tied to items so sales tracking and payouts are clear.
What to anchor in discovery
- Every item can be linked to a seller so sales/payout reporting stays accurate.
- Commissions can be set by default (for speed) and overridden per product (for flexibility).
- Seller onboarding can be self-service (recommended) or manual to unblock edge situations.
You’ll hear prospects describe this as: consignment, buy-sell-trade with payouts, multi-vendor retail, “seller accounts,” or “drop-off sellers.”
How seller identity & ownership tracking works (current workflow)
Sellers live under “Customers”
In Ribbn, sellers are managed under Customers. Once a customer begins selling, Ribbn automatically tags them with a green “Seller” label.
Quick talk track
- “In Ribbn, sellers are essentially customers with a seller status—so you get one unified directory.”
- “As soon as someone starts selling, Ribbn marks them as a Seller automatically.”
Seller onboarding options (what’s supported)
| Approach | Who does the work | Why it matters | SDR positioning |
|---|---|---|---|
| Self-signup in the Ribbn App (recommended) | Seller | Fewer typos/duplicates; seller controls their info | “Fastest + cleanest data.” |
| Manual creation in Ribbn Admin | Store staff | Useful when seller can’t self-sign up | “Good for assisted onboarding.” |
Self-signup basics (SDR-level)
- Seller downloads the Ribbn App
- Logs in via a one-time passcode sent to email
- Selects the store (first time selling)
Manual creation basics (SDR-level)
- Admin creates a customer record with name + email or phone
- Seller logs in using the entered email/phone (OTP via SMS or email)
If a seller’s email/phone is entered incorrectly, they may not receive their one-time passcode and could be blocked from logging in. This is a common operational failure point worth calling out early.
Commissions in Ribbn (what SDRs can safely promise)
Commission definition (plain English)
- Ribbn’s store commission represents the store’s earnings on an item.
- The seller receives the remainder of the split.
- If the store is the seller, Ribbn sets earnings to 100% automatically.
Commission configuration levels (the mental model)
| Level | What it does | When it applies | What SDRs should say |
|---|---|---|---|
| Default store commission | Sets the standard split | Applies automatically to new products created after it’s set/changed | “Set it once, Ribbn applies it going forward.” |
| Custom commission per product | Overrides default | Applies to that specific product | “Flexible for VIP sellers or special inventory.” |
| Bulk Edit | Updates many listings at once | Useful for changes across existing products | “You can update many products together.” |
Changing the default commission only affects **new products created after the change**. It does **not** update existing listings retroactively.
Ownership attribution: linking a product to a seller
What “linking” means
Linking (assigning) a product to a seller ensures accurate tracking and payouts by tying seller attribution to the item at the product level.
Where it happens (SDR-level reference)
- Admin Dashboard → Products → Product details → Accounting Settings
- Select the correct seller
- Verify commission %
- Confirm
Wrong seller or wrong commission can impact reporting and payouts. The workflow supports verification at the point of confirmation—call this out as a trust/controls feature.
AI-assisted intake/listing (where it fits in the narrative)
Positioning (don’t over-commit)
Ribbn supports AI-assisted listing via AI QuickList to help teams digitize items faster and improve listing quality.
SDR phrasing:
- “Ribbn can help speed up intake and improve listing consistency with AI-assisted listing (AI QuickList).”
- “The key is: items get digitized quickly, then you can ensure seller attribution + commission are correct in the accounting settings.”
If a prospect asks for exact AI behavior (fields, languages, confidence checks, etc.), treat that as an AE follow-up unless you have the current product spec in your enablement materials.
Omnichannel tie-in (why commissions/ownership tracking matters)
What to emphasize
- Ribbn supports in-store checkout via POS (app POS / web POS).
- Ribbn supports online selling via Ribbn webshop or Shopify integration with Ribbn as system of record.
- The value for commission programs: seller attribution and commission rules need to remain consistent wherever the sale happens.
Talk track:
- “Whether it sells in-store or online, you still want the seller attribution tied to the item so reporting and payouts stay clean.”
Operational trust drivers (SDR-safe, high level)
Use these to build confidence without going deep into admin workflows:
- Lifecycle status management: Items move through statuses so teams can manage intake → live → sold → payout.
- Returns / holding periods: Ribbn supports operational handling that helps stores manage when an item is considered final for payout.
- Payout transparency: Ribbn supports clear tracking and payout handling (often described as manual and self payout).
- GDPR deletion flow (high level): Ribbn supports GDPR-aligned deletion processes for customer data management.
If a prospect asks “Does Ribbn enforce my local holding-period law?” or “Does Ribbn guarantee tax compliance/VAT handling?” do not answer beyond product behavior. Capture requirements and route to AE/CS.
Discovery: qualify commission complexity (questions that map to Ribbn capabilities)
Baseline qualification (fit)
Ask:
- How many sellers do you manage (active per month)?
- Do sellers self-onboard, or does staff create profiles?
- Is commission mostly standard, or do you need exceptions (VIP sellers, categories, high-ticket items)?
- Do you need to bulk-change commissions across inventory?
- Where do sales happen: in-store, online, both?
- Do you need seller attribution/payout tracking across multiple channels?
Complexity flags (possible follow-up needed)
Ask and flag for AE:
- “Do you need different commissions based on seller tier + category + season + store location at the same time?”
- “Do you do splits across multiple sellers on one item?” (co-ownership)
- “Do you need automated payout scheduling, partial payouts, advances, or netting against fees?”
Ribbn clearly supports default commissions, per-product overrides, and product-to-seller linking. For multi-variable rules engines or multi-party splits, don’t commit—document the requirement and bring an AE in.
First-line objection handling (SDR-ready)
“We have lots of special commission deals—will Ribbn handle that?”
Answer (safe):
- “Ribbn supports a default store commission, and you can override commission per product—including updating many products via bulk edit. The key is that commission is tied to the item so tracking and payouts stay accurate. If you tell me how many exception cases you have, we can confirm fit in a working session.”
“What if a seller can’t onboard themselves?”
Answer:
- “Self-signup in the Ribbn App is recommended, but staff can manually create a seller as a customer record in Admin using name + email/phone. Then the seller logs in via one-time passcode.”
“We’re worried about payout mistakes.”
Answer:
- “Ribbn’s workflow emphasizes controls at the point of linking: you assign the seller at the product level and verify the commission before confirming. That item-level attribution is what keeps reporting and payouts consistent.”
Pricing & packaging guardrails (what SDRs should cover)
What to mention (high level)
- Plans typically include core platform capabilities.
- Expect transaction fees depending on package.
- Common add-ons include:
- RFID
- Extra terminals
- Tradera integration
Do not quote exact pricing, fee percentages, or contract terms unless you have the current approved pricing sheet. Offer ranges only if your team explicitly allows it; otherwise, book time with an AE.
Illustrative examples (use in calls)
Example 1: Standard commission with occasional VIP exceptions
- Store sets default commission (e.g., 60% store / 40% seller)
- VIP sellers get better terms on specific items via per-product custom commission
- Outcome: consistent defaults + controlled exceptions
Example 2: Clean attribution for payout reporting
- Seller is onboarded (self-signup or manual)
- Each item is linked to the seller in Accounting Settings
- Commission verified before confirmation
- Outcome: fewer payout disputes because seller attribution is explicit per item
What NOT to promise (unsupported / needs confirmation)
- Automated compliance guarantees (VAT/tax, local holding period enforcement)
- Complex multi-conditional commission engines (unless documented elsewhere)
- Multi-seller splits on a single item (unless confirmed in current product docs)
- Any legal interpretation of “ownership,” agency, or consignment agreements
The safe positioning is: Ribbn provides item-level seller attribution + commission configuration to support accurate sales tracking and payout workflows; policy and compliance rules remain the merchant’s responsibility.
Quick reference (what to say vs. where it lives)
| SDR need | What to say | Where it happens in product |
|---|---|---|
| Seller onboarding | “Self-signup is recommended; manual creation is available.” | App (OTP login) / Admin → Customers |
| Seller status | “Sellers are customers with a Seller label once they start selling.” | Customers directory |
| Link item to seller | “Seller attribution is set per product for tracking + payouts.” | Admin → Products → Accounting Settings |
| Commissions | “Default commission + per-product override; bulk edit for many items.” | Products settings + product accounting details |
Suggested meeting CTA (close)
“If I book 25 minutes with an AE, can you bring an example of your current commission structure—default split plus 2–3 exceptions—so we can map it to Ribbn’s default + per-item commission model and confirm how you’d run payouts across in-store and online sales?”