What Orbit Sales does.

A quick map of everything in the product. Grouped by what your team actually does with it, not by which integration it talks to.

Plan the day

• Route planning — order a list of stops, with or without traffic. Save a route per rep.
• Calendar integration — Google Calendar, two-way. Visits push to the calendar, events pull back as visits.

Run the visit

• Offline-first mobile App — installs on iOS and Android, your logo on the home screen, works when the signal drops.
• Capture what happened — configurable visit actions, feedback notes, order-on-the-spot.

Take the order

• Order form that knows your products — pulled from Shopify, WooCommerce, Square, or native inventory.
• Pay now with a card — Square Web Payments or Authorize.net. Tokenized in the browser; card details never touch our servers.
• Send a payment link — Square, WooCommerce, or QuickBooks payment link, emailed with a Complete Payment button.
• Offline payments recorded too — cash, e-transfer, check.
• Tax captured — sits on the order so the destination system can reconcile.

Serve your customers directly

• Marketplace App — a separate installable App under your brand. Installs on iPhone and Android with your logo on the home screen.
• Affiliate App — serves both casual word-of-mouth referrers and dedicated professional affiliates. Shareable referral links, native share to whichever Apps the user has installed — social, messaging, SMS, email — on mobile and desktop. Commission history, store credit issued as discount codes, and a read-only view of the orders each affiliate drove. The same App serves a customer who shares your store with a friend once and an affiliate who builds a business promoting it.
• Store App for B2B customers — a customer-facing ordering App your retailers use to place wholesale orders directly. Each retailer sees your catalog, places orders that land in your existing systems, and gets order confirmations and payment links back. Used today by Bob The Dog's retail accounts.

Keep your books

• QuickBooks invoicing — auto-create invoices on B2B orders, payment links, connections that stay active on their own.
• Transaction log — every charge, link, or offline payment recorded against the order.

Discounts, store credit, wholesale pricing

• One engine, every shape — percentage off, fixed amount off, fixed-price overrides for wholesale, store credit, free shipping, buy-X-get-Y. Same record, same audit trail. The mechanism is a column on the discount, not a separate product.
• Triggers, not categories — a discount can fire from a code at checkout, the identity of the user submitting the order (affiliate or wholesale rep), an order minimum, a quantity threshold, a customer tag, or always-on. Code-based and automatic discounts are the same record; only how they're triggered differs.
• Affiliates built in — when an affiliate submits an order on a customer's behalf, the customer's discount applies automatically and the affiliate's reward — store credit or cash commission — is logged in the same pass. No second ledger to reconcile.
• Wholesale pricing as price overrides — fixed prices per SKU per customer (or per price group). Stands outside the discount pipeline because it replaces the price rather than reducing it — standing agreements without per-order configuration.
• Store credit as a first-class ledger — every credit has a balance, a reason, an expiry, and a transaction history. Issued by a rep, awarded by the system as an affiliate reward, or applied on a return.
• Every discount is attributed — to the rep, affiliate, or admin who created it. No anonymous discounts. Every redemption logs the trigger type, the order, the customer, and the dollar amount.
• Stacking rules you can actually reason about — non-stackable by default; free shipping is the one exception that can sit on top of another discount. Two fields decide it: stackable and priority.

Notifications and reminders

• Reminders tied to a specific customer — "follow up with this account next Tuesday" or "check in with this buyer every 30 days." Each reminder is anchored to a customer record, so it shows up wherever that customer shows up.
• One-off and repeating — set a reminder for a single date, or a recurring cadence (weekly, monthly, custom interval). Repeating reminders keep firing on schedule until you close them out.
• Three channels — email, SMS, or in-App. Pick per reminder. Pick a combination if it matters. In-App alerts arrive live via websocket, so your reps see them on the phone while they're moving.
• On-my-way and running-late alerts — one-tap "on my way" or "running late +10 / +15 / +30" from the route runner. The customer gets the message. Dispatch sees the update at the same time.
• Store-level opt-in — each customer account decides whether they accept SMS and email from you. No bulk outreach without consent.
• Google Calendar sync — reminders that belong on a rep's calendar land there automatically and update when they change.
• Delivered on time — the scheduler runs as its own worker process, so reminders and alerts fire on schedule even when the rest of the system is busy.

Talk to your customers

• Email — Gmail for personal sends. Mailchimp (via Mandrill) for transactional — order confirmations, payment links, receipts. Brevo available as an alternative for teams not on Mailchimp.
• SMS — Twilio for transactional and operational messages, opt-in per store.
• Mailing lists — Mailchimp first — we import your lists and contacts, tie each D2C customer to their opt-in or unsubscribe status, and tag contacts based on actual purchase behavior. Brevo is available on the same shape, so moving between the two is a setting change rather than a migration.

Keep your systems in sync

• Cross-vendor customer identity — the same email in Shopify and Mailchimp = one person in Orbit Sales.
• Row-level source tracking — every record knows which system it came from.
• Vendor-role architecture — you tell us which system does which job (order destination, payment processor, mailing list, accounting) and we route accordingly.

Scale

• Multi-tenant — each business is isolated at the database level.
• Separate worker processes — API, scheduler, payments, and marketplace run independently.
• In production with teams of hundreds of reps today.

See the full integrations list · See the changelog