POS & Checkout: App POS + Web POS

Why this matters (SDR talk track)

Ribbn POS is one part of the bigger “end-to-end resale commerce platform” story:

• System of record for resale: inventory + webshop + POS + order tracking.
• Omnichannel execution: sell in-store (App POS / Web POS) and online via Ribbn webshop (and where applicable, Shopify integration with Ribbn as the system of record).
• Operational trust: items move through clear lifecycle states (e.g., available → sold), orders are recorded, and customers get confirmation—reducing disputes and improving payout clarity.

Use this page to:

• Qualify POS needs (speed, store setup, tagging/scanning, payment methods, locations).
• Accurately describe checkout options and what’s required—without overpromising hardware.

Ribbn checkout options: App POS vs Web POS (quick positioning)

App POS (mobile)

Best when the store wants:

• A mobile-first checkout flow from the Ribbn app.
• Flexible item entry via RFID/QR scan or manual search.
• Payment via cash/manual (“Mark as Paid”) or card with a connected reader.

Web POS (browser)

Best when the store wants:

• A web-based POS for high-paced retail, ideal for tablets and POS setups.
• Fast item entry via barcode scanning, QR scanning (for tagged items), or manual product search.
• Card payments via a Stripe WiFi-based reader.
• Optional productivity boosts (e.g., Bookmarks for saved filters).

Capabilities & requirements (what you can safely say)

Supported payment methods (in-store)

Supported scanning / product lookup

What happens after checkout (operational trust drivers)

For App POS, once payment is completed:

• Product is marked sold
• Order is updated in the system
• Customer receives an order confirmation email

For Web POS, the flow confirms:

• Order is completed after payment capture and confirmation
• Linking a customer is recommended so they receive an order confirmation via email

SDR discovery: qualify POS needs fast

Core qualifying questions (ask early)

1. Where do sales happen?

   • “How much of your volume is in-store vs online?”
   • “Do you need a fixed checkout station, or mobile checkout on the floor?”

2. Speed & workflow

   • “Is checkout typically one item at a time, or multi-item carts?”
   • “Do you need barcode scanning for speed at a busy counter?”

3. Inventory identification

   • “Are items tagged today (QR/RFID), barcoded, or mostly untagged?”
   • “Do you want the option to sell untagged items by searching the catalog?”

4. Payments

   • “Are you taking mostly card, cash, or mixed?”
   • “Do you already use Stripe Terminal readers, or would you be starting fresh?”

5. Customer linking & receipts

   • “Do you need customer profiles tied to purchases for confirmations and tracking?”

6. Multi-location

   • “Do you have more than one store location that needs separate reporting?”

Qualification signals (what to listen for)

• App POS fit when they want: mobile checkout, staff moving around, occasional scanning, cash/manual support.
• Web POS fit when they want: tablets/checkout lanes, high transaction pace, barcode/QR scanning, WiFi reader payments.
• Omnichannel need when they mention: in-store + online selling, unified inventory/order tracking, reducing double-entry.

Talk tracks: how to position the two POS options

Talk track: “Mobile checkout in the Ribbn app” (App POS)

• “Ribbn’s App POS is built for in-store checkout from your phone—add items to a cart by scanning RFID/QR tags or searching the catalog, link the sale to a customer, and complete payment.”
• “If you take cash or offline payments, you can mark the order as paid. For card, you can use a connected reader.”

Talk track: “High-speed web checkout for busy counters” (Web POS)

• “Ribbn’s Web POS is a browser-based POS for high-paced retail—ideal on tablets and fixed POS setups.”
• “Teams can scan barcodes or QR codes to pull up tagged items fast, link to a customer for confirmation emails, and capture card payments with a Stripe WiFi-based reader.”
• “You can also save product filters as Bookmarks, so each staff member has a consistent workspace.”

Objection handling (first-line, SDR-safe)

“Do you support card readers?”

Yes—Ribbn supports Stripe Terminal readers:

• WiFi (example: BBPOS WisePOS E)
• Bluetooth (example: WisePad 3)

And the App POS flow references a Stripe/Zettle Reader option for card payments.

Follow-up qualifier: “Which reader are you using today—Stripe Terminal, Zettle, or something else?”

“Can multiple devices use the same terminal?”

There is a documented restriction:

• Due to Skatteverket regulations, only one device can be synced with the Stripe terminal at a time.

Use this to qualify staffing/checkout layout early (single station vs multiple).

“We have multiple store locations—will checkout reporting get messy?”

In Web POS:

• You select the correct location when creating a POS order.
• It’s explicitly important to choose correctly to keep reporting and records accurate.

Quick reference: checkout flows (high level)

App POS: Check Out In Store (mobile)

1. Log in to the Ribbn app
2. Add products to cart:
   • Scan RFID/QR, or
   • Search product name
3. Select items → Add to Cart → View Order Summary
4. Link to User (existing customer or create new profile)
5. Take payment:
   • Mark as Paid (cash/manual), or
   • Stripe/Zettle Reader (card)
6. Confirm transaction → item marked sold + order updated + confirmation email

Web POS: Capture orders (web)

1. Go to Orders > Create POS Order
2. Select location (if multi-location)
3. Connect Stripe Reader
4. Add items:
   • Scan via barcode/QR scanner, or
   • Manually search/select products
   • (Optional) Use Bookmarks for saved filters (e.g., “Listed items”)
5. Link to customer (recommended)
6. Capture payment via reader
7. Confirm completion → order complete

Hardware & setup guardrails (don’t overpromise)

Supported Stripe reader types (documented)

SDR “next step” meeting ask (tie POS needs to a qualified demo)

If they indicate real POS volume or pain, close with:

• “Let’s book 30 minutes to map your in-store checkout flow—mobile vs counter, scanning, and payments—and show both App POS and Web POS so you can see what’s fastest for your staff. Before that, can I confirm how many locations and checkout stations you run today?”

Related internal references (for SDR prep)

• Orders & POS → Store POS: in-app checkout + reader connection
• Orders → Web POS: capturing orders in Web POS
• Stripe reader setup: WiFi (Stripe Terminal) + Bluetooth syncing and device restriction