What we connect to, and what each connection actually does.
Our architecture treats every integration as a role: order destination, payment processor, accounting system, mailing list, and so on. You tell us which system does which job. We route the data accordingly. If you connect Shopify for orders and QuickBooks for invoicing, orders land in Shopify and invoices land in QuickBooks — not a mash-up of both.
Orders, products, customers, inventory
Shopify
Two-way: import your customers, products, and orders; place new orders from the field and they show up in your Shopify admin. Draft orders get a Shopify payment link for you to email. In production with our beta partners.
WooCommerce
Same shape as Shopify — customers, products, orders, inventory, payment links. WooCommerce has some well-known quirks around webhook delivery; we've handled those so you don't have to. In production.
Square
Customers, products, orders, inventory — and Square is also one of our direct payment processors (see below). A Square store can run full POS, or you can use Square for payments only while Shopify or WooCommerce holds your catalog.
Payment processing
Square Web Payments
Direct credit-card charges, tokenized in the browser. Card details never touch our servers. Used on both the rep-facing order form and the marketplace checkout.
Authorize.net
One of the oldest payment providers on the internet. Usually carries lower processing rates than Square and is more flexible about what merchants sell. Card details stay tokenized in the browser; they never touch our servers. If you already have an Authorize.net merchant account, we charge against it the same way we charge against Square.
Payment links (Square, WooCommerce, QuickBooks, Authorize.net)
For net-30 accounts, B2B customers, or anyone you'd rather not collect a card from in person. We generate a payment link and email it with a "Complete Payment" button. The customer pays on the provider's page; we record the transaction when it clears.
Accounting
QuickBooks Online
Connect your QuickBooks account once, sync customers and invoices, auto-create invoices on B2B orders, deliver payment links on QuickBooks invoices. Connections stay active automatically so they don't quietly drop. In beta with Bob The Dog, whose feedback drove most of this.
Email and SMS
Mailchimp
We import your lists and your contacts. Each D2C customer in Orbit Sales is linked to their Mailchimp opt-in or unsubscribe status, so a rep looking at the customer card sees whether they're on the newsletter. Opt-ins collected on your order forms flow the other way, into Mailchimp. Transactional sends run through Mandrill — order confirmations, payment-link emails, and reminders can all come from your Mailchimp account, with your branding.
Brevo
Same shape as Mailchimp — lists and contacts, opt-in linkage, transactional sends — but Brevo-backed. We included Brevo because it's often a less expensive alternative with newer technology underneath. Useful if you never ran Mailchimp, or if you want a path off it. Because both integrations write to the same underlying customer and identity tables, moving from one to the other is a connection change, not a data migration.
Gmail
Gmail can act as your transactional sender if you'd rather your customer emails come from your actual inbox. Connect your Google account once, per-business sender address.
Twilio
SMS notifications — on-my-way, running-late, reminders. Opt-in per store, so you don't blast every customer.
Scheduling
Google Calendar
Two-way. Visits push to the calendar as events. Calendar events pull back as visits. Reminder sync. Useful if your reps already live in Google Workspace.
On the field side
Google Maps
Route planning, address autocomplete on order and customer forms, geocoding on CSV imports.
Google Places
Prospecting — pull candidate stops from Places data and tag them so you can track which leads came from where.
CRM — what we don't do
We don't replace HubSpot, Pipedrive, Zoho, Keap, Close, Microsoft Dynamics, or any of the other dedicated CRMs you might be running. The plan is to write field data back to them, on the same row-level source-tracking model we use for orders and customers today.
Many smaller teams don't run a dedicated CRM at all — the customer list inside Square, WooCommerce, or Stripe is doing the job well enough. That works the same way on our side: we keep a normalized customer record in Orbit Sales that stays in sync with whichever tool is actually holding your book of business. Tell us what you're using — it helps us prioritize.
Under the hood
Every record in our system carries a source_integration tag: shopify, woocommerce, square, quickbooks, mailchimp, brevo, native, csv, google_places. That tag drives sync direction, conflict resolution, and which system gets the authoritative version of a given field. If you ever disconnect an integration, we don't orphan the data — it just stays tagged with where it came from.
See what we shipped this quarter · Talk to us about an integration not on this list