Eco Systems CRM & More

Integrations

Every connection, with its real status attached.

This is the whole list of loyalty CRM integrations we run — the registers that award points, the scanner that feeds the leaderboard, the carriers that deliver the texts, and the back-office systems the ops verticals post into. Each one says what it actually does and how far along it is. Early access means early access. Import means import. Nothing on this page is marked further along than it is.

01 — Point of sale

Where the sale happens.

A loyalty program that does not touch the register is a spreadsheet. These are the POS systems we award points from and push redemptions back into.

Shopify

One-click install, points on every order, POS redemption

The deepest integration we have. You install it from Shopify as an app — OAuth, no key-pasting. Paid-order webhooks award points automatically on web and POS orders, with refund reversal and retroactive matching for guest checkouts. Redemption lives inside Shopify POS checkout as a line item, so staff redeem where they already work. Member name and email write back to the Shopify customer record so the two systems stop disagreeing, and the storefront widget shows a member their balance on your own site. Full write-up: the Shopify POS feature page.

  • App install via OAuth
  • Order webhooks
  • POS extension
  • Refund reversal
  • Customer write-back
  • Storefront widget

Live

Clover

Register app + payment webhooks

Payment webhooks award points the moment a Clover order is paid, idempotent on the Clover order id so a replayed event never double-awards. Our register app runs on the Clover device itself and provisions by asking Clover who the merchant is — nobody types a credential into a terminal. Rewards push onto the open ticket: a dollar discount applies as a discount, and a free-item reward finds the item by SKU and zeroes one unit of it. If the item cannot be found, the register says hand it over manually instead of pretending it worked. Member name and email write back to the Clover customer record.

  • Register app
  • Payment webhooks
  • Discounts on the open ticket
  • Free-item rewards
  • Customer write-back

Live

Lightspeed R-Series

A Rewards button on the sale tab

A custom menu button on the Lightspeed register opens the rewards screen for the sale in front of you, resolving the member from the customer on the ticket — or from a kiosk check-in at that store in the last ten minutes, which is how the tablet-based competitors do it. Mapped rewards apply as your own Lightspeed discount; unmapped fixed-dollar rewards fall back to a negative sale line. Included in the platform at no extra cost, and because it is our newest POS integration we do the connection and reward mapping with you rather than handing you a setup doc.

  • Register button
  • Signed launch, no shared secret
  • Discount mapping
  • Open-sale write not yet verified live

Early access

02 — Body composition

The scanner your members already trust.

InBody / LookinBody

Scan ingest by webhook, attributed per scanner

Scans arrive from LookinBody by webhook and land on the member record, no staff transcription. A per-serial map attributes each scanner to a store, so a two-location operator gets scans filed where they happened instead of pooled. Those scans feed the leaderboard, the challenge engine, the member's own history in the app, and the in-store mirror screen. If LookinBody's API is not an option for your unit, scan photos can be uploaded and parsed instead — the paths and their requirements are laid out on the InBody integration page. Connecting your own LookinBody Web account takes six steps, written up in the LookinBody setup guide.

  • LookinBody webhook ingest
  • Per-serial store attribution
  • Feeds challenges + leaderboard
  • Member scan history
  • Photo upload fallback

Live

03 — Messaging & money

Delivery, email, and payments.

Twilio

SMS delivery, with A2P 10DLC filed for you

Every store texts through Twilio under its own registered A2P 10DLC brand and campaign, which we file during setup — the business-information collection and the sample-message paperwork carriers actually read. The platform adds the operating discipline: drip sending inside throughput limits, quiet hours, instant STOP handling, and a composer that shows text count and cost before you send. Credentials are write-only — never echoed, never logged. More: SMS marketing.

  • A2P 10DLC registration handled
  • Drip sending
  • Quiet hours
  • STOP handling
  • Write-only credentials

Live

Resend

Transactional and lifecycle email

The email leg: login links, staff invitations, document-signature requests, quote notifications to the owner, and the lifecycle sequence — welcome, we-miss-you, birthday, renewal notice. Lifecycle sends are ledger-marked before the send, so a retry cannot text or email the same member twice for the same reason, and marketing-flavored emails respect the email opt-out. There is a single kill switch if you want the automated ones to stop today.

  • Transactional email
  • Lifecycle sequences
  • Send ledger, no duplicates
  • Per-store kill switch

Live

Stripe

Your bill from us

The platform subscription, the one-time setup fee, and metered SMS overage all bill through Stripe. We never see or store full card numbers — Stripe holds the payment instrument, we hold the invoice history. Non-payment pauses campaigns first and never deletes member data. Pricing is published for retail; ops and construction are quoted per site and headcount.

  • Monthly subscription
  • Metered SMS overage
  • No card data on our side
  • Cancel anytime

Live

Stripe Connect

Your members' payments, into your account

For studios and gyms taking money through the platform: memberships, class packs, retail, and paid bookings run on Stripe Connect, so the money lands in the studio's own Stripe account, not ours. Checkout handles online purchases, Terminal handles the front desk, and webhooks mirror paid and failed invoices back into the billing ledger so dunning and late fees run off real payment events. Until a studio connects Stripe, booking simply runs in free mode — no plans, no packs, no payment gate.

  • Direct charges to your account
  • Checkout
  • Terminal
  • Invoice mirror + dunning

Live

04 — Back office & field

For the operations side of the product.

These belong to workforce ops and construction rather than the loyalty product. They are here because they are real, and because operators ask.

QuickBooks Online

Expenses, receipts, and an invoice mirror

Job expenses sync into QuickBooks coded to the right account and class. A receipt photographed by a crew member on site posts as a purchase with the image attached and the job already tagged. Company-card receipts do not post blind — because the card feed already brings that purchase into QuickBooks, we match the receipt to the feed line instead of creating a duplicate for a bookkeeper to clean up by hand. Invoices come the other direction: read-only mirror, QuickBooks stays the system of record.

  • Expense sync
  • Receipt posting with attachment
  • Card-feed matching
  • Invoice mirror (read-only)

Live

Autodesk Construction Cloud

Cost expenses, projects, and Daily Reports

Expenses post to the ACC cost module so the project budget sees them. Projects go both ways: import the existing ones to create jobs here, or create a new ACC project from a job with its number and address already filled in. And the end-of-day log a foreman fills out on their phone — crew, work, materials, equipment, photos — becomes an ACC Daily Report form, written once and retried against the same form if the fill fails. One caveat we will state plainly: creating projects requires an account admin to reconnect with write scope, and an account that has customized its Daily Report template may need the field mapping revisited.

  • Cost expenses
  • Project import
  • Project create
  • Daily Report forms

Live

Samsara

Fleet trips turned into travel pay

We pull trips per vehicle and turn drives to a job site into travel-pay lines at each person's own rate, by hours or by miles. Every trip is ledgered on a unique reference, so a re-run never re-pays and never overwrites an approval, and the amount freezes the moment it is approved. Setup-dependent, and we say why: many fleets do not assign drivers to trucks in Samsara, so a trip arrives with no driver on it. The fix is a one-time mapping of each truck to its usual driver, plus geofences on the jobs — without those, the trips still import but nobody gets paid for them.

  • Trip pull per vehicle
  • Hours or miles rates
  • Paid once, ledgered
  • Needs truck-to-driver mapping

Live — setup-dependent

Gusto

Payroll export, not a payroll API

Hours and tiered pay rates come out as a Gusto-shaped CSV you upload on payroll day. Deliberately a file and not an API connection: payroll is the one place an operator wants to look at the numbers before anything is submitted on their behalf. The hours behind it come from real clock punches and published schedules — see staff management.

  • Payroll CSV export
  • Tiered rates
  • Review before upload

Live

Kisi

Door access for 24/7 gyms

Membership standing decides door access: a lapsed member loses the door, a reinstated one gets it back, reconciled hourly instead of at a front-desk person's discretion. Honest status: experimental. The code is written and runs, but it has never been tested against a real Kisi organization, so we will not put it on a go-live plan. If you run Kisi and want to be the store that proves it, tell us on a demo call.

  • Standing-driven access
  • Hourly reconcile
  • Untested against a live org

Experimental

05 — Address tooling

Two small ones that save retyping.

Google Places

Address type-ahead at the counter

Address fields on the counter kiosk autocomplete instead of being typed out by an associate with a customer waiting. Proxied through our worker, so the key is never in the page.

  • Address type-ahead
  • Key stays server-side

Live

USPS address verification

Standardize before it prints on a label

Written and wired, and currently dormant: it needs USPS API credentials to be set before it does anything. Until then, address capture runs on type-ahead alone. We would rather list it as dormant than let you find out later it was never turned on.

  • Address verification
  • Dormant until credentials are set

Dormant

06 — Import paths, not integrations

These move your history in. They do not stay connected.

The distinction matters, so read it before anyone on a sales call blurs it. An integration is live: data moves on its own, daily, in both directions. An import runs once, from the file your old system exports, and then the old system is out of the picture. The four below are imports. Nothing keeps syncing.

Mindbody

Import — clients, balances, schedule

We read a Mindbody export and land clients, outstanding package balances, and the class schedule so a studio opens on day one with its people and its timetable already there. Imported members arrive with SMS consent marked pending, never opted in — you do not inherit consent you cannot prove. There is a dry-run pass first so you see what would land before anything is written.

  • Clients
  • Package balances
  • Class schedule
  • Consent stays pending
  • Dry run first

One-time import

TapMango

Import — members and point balances

Members and their point balances come across from a TapMango export, so nobody loses the points they earned when you switch. Same consent rule: imported contacts are pending until they opt in here. The honest comparison of the two products is on the TapMango page.

  • Members
  • Point balances
  • Consent stays pending

One-time import

Buildertrend

Import — crew and subcontractor lists

A Buildertrend export gives us users and subs: crew records, inactive people marked terminated rather than deleted, and the whole subcontractor and vendor list, deduplicated by name. Worth knowing before you plan around it — Buildertrend's export does not include schedules, daily logs, or to-dos, so those modules start empty here and get built forward, not backfilled.

  • Crew records
  • Subcontractors and vendors
  • No schedule or daily-log history

One-time import

Deputy

Import — employee roster

A Deputy export brings the roster over, store codes and all, which is how a multi-store franchise moves off Deputy scheduling and time clock in one weekend instead of retyping several dozen employees. After the import, scheduling and punches run here.

  • Employee roster
  • Store codes preserved
  • Scheduling and punches move here

One-time import

Public API

For stores with their own tooling

Still not shipped, and still on the public roadmap alongside additional POS integrations. If an API or a specific POS is the one thing standing between your store and switching, say it on a demo call — build order here is set by stores asking, not by us guessing.

  • Public API — roadmap
  • More POS integrations — roadmap

Roadmap

07 — Questions

Straight answers.

What is the difference between an integration and an import?

An integration is a live connection: data moves both ways on its own, every day, with no one pressing a button. An import runs once, at migration, from a file the old system exports. Mindbody, TapMango, Buildertrend and Deputy are imports on this platform — we read their exports and land the records here. Nothing keeps syncing with them afterward, and we do not claim it does.

Do you have a public API?

Not yet. It is on the public roadmap alongside additional POS integrations. If an API is the thing standing between your store and switching, say so on a demo call — build order is set by real stores asking, not by us guessing.

Who handles the A2P 10DLC registration for SMS?

We do, during setup. Your store texts through Twilio under its own registered brand and campaign — we file the business information and the sample-message paperwork carriers actually read, so your texts are not sending from a shared, unregistered number.

What happens to integration credentials you store?

POS, Twilio and accounting credentials are write-only: you can set them and replace them, and no API response or log ever echoes them back. Card numbers never touch our systems at all — Stripe holds the payment instrument, we hold the invoice history.

08 — Next step

Bring your stack to the call.

Book a 20 minute demo and name your register, your scanner, and your accounting system. We will tell you which of the three is a live integration, which is an import, and which is not built.

Book a demo See it live

$200/mo platform · 5,000 texts included · no contracts