Skip to main content

​
Online Ordering

  • Recommended Logo Specifications: Square, 512 x 512 pixels
  • Recommended Shop Image Specifications: Landscape, 2400 x 600 pixels
Create QR codes for mobile ordering:
  1. Go to the Web Dashboard → Settings → QR Codes
  2. Choose the QR code type and optionally a category to focus (e.g. “Drinks”).
  3. Generate the QR code and download it.
  4. Print or display the QR code in-store; customers scanning it go directly to your ordering site (and selected category, if set).
Customers are not able to use their own domain for the Dripos mobile ordering site.
You can use a dedicated mobile ticket type and a checkout prompt:1. Create a curbside ticket type
  • Go to the Web Dashboard → Orders → Ticket Types.
  • Click Create Ticket Type.
  • Name it something along the lines of “Curbside Pickup”.
  • Set Type to a pickup-type ticket.
  • Save.
2. Add a checkout prompt for car details
  • In Checkout Setup, create a checkout prompt tied to the Curbside Pickup ticket type.
  • Ask for details like car make, model, and color.
  • Mark the prompt as required if needed.
Note: Dripos does not currently have a built-in “check-in” button for curbside; staff will rely on the order info and any customer communication.
Setup and pricing:
  • Third-party ordering is an add-on feature.
  • Pricing: $50 per location per month.
  • You can connect multiple services (DoorDash, UberEats, Grubhub, etc.) under that flat fee per location.
  • Once enabled by Dripos, you’ll: 1) Map your menu to each third-party service. 2) Configure ticket types and routing for third-party orders. (Your sales or onboarding rep will walk you through the exact integration steps.)
Some third-party platforms don’t respect modifier dependencies, which can allow customers to get free items.Workaround for “free modifier” issues on third-party menus:
  1. Duplicate categories for third-party - Create separate categories specifically for DoorDash/UberEats/Grubhub (e.g. “DD - Lattes”).
  2. Split products by type - Instead of one “Latte” with hot/cold modifiers, create “Latte - Hot” and “Latte - Cold”. Attach only the appropriate modifiers to each product.
  3. Use these categories only for third-party - Keep your main POS/mobile menu unchanged. Use the “third-party-safe” categories when building your DoorDash/UberEats/Grubhub menus.
1. Turn on In-House Delivery
  • Go to the Dashboard → Shop Settings → Order System.
  • Set Enable In-House Delivery to Yes.
2. Set delivery hours
  • Go to Shop Settings → Shop Information → Hours → Delivery.
  • Set the hours when you offer delivery. (This section appears only after In-House Delivery is enabled.)
3. Set delivery quote time
  • Go to Shop Settings → Mobile Ordering.
  • Set your Delivery Quote Time (estimated prep + delivery time).
4. Create a Delivery Ticket Type
  • Go to Orders → Checkout Flow → Ticket Types.
  • Click Create Ticket Type.
  • Choose Type: Delivery.
  • Save.
5. Set up delivery zones and fees on the POS
  • On the POS, go to POS Settings → Delivery Options.
  • Click Add Delivery Zone.
  • Set: Minimum order amount, Delivery fee, Driver compensation (if applicable).
  • Click Edit Points next to the zone.
  • Draw your delivery area on the map by clicking multiple points around your service area, then Save.
6. To edit delivery fees at a later time:
  • Go to POS Settings → Delivery Options.
  • Click your delivery zone.
  • Adjust the delivery fee and save.
  1. On the POS, go to the Delivery tab and remove the employee as a driver.
  2. Go to the Time Clock tab and clock the employee out.

​
Payments

Billing Accounts:
  • Let you continue to attach tickets to an account and pay later.
  • You can use Billing as a payment method on the POS, or send a payment link to pay off the billing account balance.
  • Learn more about billing accounts here
Invoices:
  • Created separately from tickets.
  • Used to bill for one-off or scheduled charges (e.g., catering, wholesale, events).
  • Not directly tied to existing POS tickets.
Can tickets convert to invoices?
  • No. You cannot convert existing tickets into invoices.
  • You can add tickets to a Billing Account, then send a payment link for that account. But invoices themselves are created separately and do not pull in tickets.
Receive an email when a customer pays an invoice:
  1. On the Dashboard, navigate to Orders → Invoicing → Contacts.
  2. In the Invoice notification emails section, add the email address(es) that should receive payment notifications.
  3. Save your changes.
Any time an invoice is paid, those email addresses will receive a notification.
An uncaptured payment means:
  • The customer’s bank authorized the payment (approved it),
  • But the money has not actually been taken/collected yet.
This can happen due to a system error, a fraud review, or an authorization timeout or interruption during checkout.In these cases, a second payment attempt is usually needed to successfully complete the transaction. If you see uncaptured payments and are unsure whether to retry or refund, contact Dripos Support so we can review the specific payment details.Note: Customers may see duplicate pending transactions in their bank statement when doing the second transaction. The duplicate transaction will drop off the customers bank statement within three days.
No. Customers are not automatically notified by Dripos when you receive or respond to a dispute (chargeback).
  • The customer’s bank or card issuer controls any communication they receive about the dispute.
  • If you want to reach out to the customer directly, you’ll need to do that outside of Dripos (phone, email, etc.).
Ticket/transaction numbers get skipped whenever a ticket number is generated but the order isn’t completed — this is expected behavior, not a sign of missing revenue or lost payments.Confirmed causes include:
  1. Deleted saved tickets – if a ticket is fired and then deleted, it cannot be restored.
  2. Started-then-cancelled tickets – a ticket that gets created but is cancelled before completion.
  3. Failed card payment + retry – the ticket number is assigned at the start of the payment attempt (before it processes), so any failed payment followed by a retry consumes and skips a number.
  4. “Before payment” tipping + backtracking – if a store has before payment tipping on, and staff select card → choose a tip → then go back to add another item, switch to cash, redeem a reward, etc., a new ticket number is generated, effectively burning the original one.
  5. Certain fire-ticket settings – other workflow/settings-dependent paths can also cause skips

​
Shop Workflow

You can’t fully block cash sales without a drawer, but you can force a strong prompt to remind staff:
  1. On the POS, go to POS Settings → Cash Management.
  2. Turn on “Show Cash Drawer Required Prompt.”
  3. Save your settings.
Now, whenever someone selects Cash as a payment method and no drawer is open, a pop-up will appear reminding them to open a drawer first.