Skip to content

Integrations

One provider integration serves every account you run on it.

Connecting a second Shopify store or a second Amazon marketplace adds a connection, not a deployment. Each entry below states what syncs, which way the data travels, and what it does not do yet.

An integration is listed Live only when a sync module for it exists. Planned entries have no connector.

Providers

Storefronts and marketplaces you sell on. One integration per provider, however many accounts you run on it.

Shopify

Live
What syncs
  • Products and variants
  • Orders and line items
  • Customers
  • Inventory levels
  • Payouts and transactions
Direction
Inbound. Scheduled synchronization plus signed inbound webhooks, with duplicate events discarded on arrival.
What it does not do yet
Pushing a product from the master catalog (title, description, price) is implemented but not yet in production use. Sellable quantity is not published back to Shopify.

Amazon

Live
What syncs
  • Listings and products
  • Orders and line items
  • Inventory, including FBA fulfillable, inbound and reserved
  • Fees and refunds
  • Shipments
Direction
Inbound, through SP-API, on a schedule. Amazon sends no inbound webhooks to this system, so freshness is bounded by the sync interval.
What it does not do yet
Pushing a listing from the master catalog is implemented but not yet in production use; listing and price changes are otherwise made in Seller Central. Sellable quantity is not published back to Amazon.

Walmart Marketplace

Planned
What syncs
Nothing yet.
Direction
Not connected.
What it does not do yet
No connector exists yet.

Temu

Planned
What syncs
Nothing yet.
Direction
Not connected.
What it does not do yet
No connector exists yet.

Google

Planned
What syncs
Nothing yet.
Direction
Not connected.
What it does not do yet
No connector exists yet. Product feed publication is the intended first scope. Order with Google, ordering from a Google Business Profile, is listed separately below.

Meta

Planned
What syncs
Nothing yet.
Direction
Not connected.
What it does not do yet
No connector exists yet. Catalog publication is the intended first scope.

Uber Eats

In development
What syncs
  • Payment details statements (CSV), uploaded by the restaurant
Direction
Inbound, by file. The restaurant exports its payment details from Uber Eats Manager and uploads the CSV; sales, fees, adjustments and payouts are recorded as reported and reconciled against payouts.
What it does not do yet
Statement import only. Nothing is read from Uber Eats directly: store status (open, paused, closed), orders and payouts are not fetched, and nothing is posted to an accounting system.

DoorDash

In development
What syncs
  • Transaction and payout reports (CSV), uploaded by the restaurant
Direction
Inbound, by file. Transaction and payout reports exported from the DoorDash Merchant Portal are uploaded, and each payout is reconciled against the transactions it settles.
What it does not do yet
Statement import only. Nothing is read from DoorDash directly: store status, orders and reports are not fetched, and nothing is posted to an accounting system.

Grubhub (incl. Seamless)

In development
What syncs
  • Transaction and deposit reports (CSV), uploaded by the restaurant
Direction
Inbound, by file. Reports exported from Grubhub for Restaurants are uploaded; Seamless orders arrive in the same Grubhub reports.
What it does not do yet
Statement import only. Nothing is read from Grubhub directly, and nothing is posted to an accounting system.

Slice

Planned
What syncs
Nothing yet.
Direction
Not connected.
What it does not do yet
No connector exists yet. Slice offers no public API, and its statements are PDF, so a file import is not possible either.

ezCater

Planned
What syncs
Nothing yet.
Direction
Not connected.
What it does not do yet
No connector exists yet. Catering orders are the intended first scope.

Order with Google

Planned
What syncs
Nothing yet.
Direction
Not connected.
What it does not do yet
No connector exists yet. Ordering from a Google Business Profile is placed through an ordering partner, not with this system.

FreshDirect

Planned
What syncs
Nothing yet.
Direction
Not connected.
What it does not do yet
No connector exists yet.

Operations

The warehouse. System of record for physical inventory.

TSmart Warehouse

In development
What syncs
  • Service-account authentication between the two systems
Direction
Outbound and inbound, over a machine token with an explicit audience and rotation, separate from the public API key mechanism.
What it does not do yet
Stock is not yet read from the warehouse into this system, and orders are not yet released to it. The warehouse is the system of record for physical inventory, so no warehouse stock figure is displayed until that link is running.

Figure POS

Planned
What syncs
Nothing yet.
Direction
Not connected.
What it does not do yet
No connector exists yet. Figure publishes no API; its own order aggregator connects delivery platforms to the point of sale, and whether it offers a data feed is not established.

Finance

The ledger and the cash view. System of record for accounting.

QuickBooks Online

Live
What syncs
  • Customers, vendors, employees and items
  • Invoices, estimates, sales receipts and credit memos
  • Bills, bill payments, purchase orders and vendor credits
  • Payments, deposits, transfers and journal entries
  • Accounts, classes, departments, terms, tax codes and tax rates
Direction
Inbound. OAuth connection with stored tokens and automatic refresh, then scheduled incremental synchronization per entity.
What it does not do yet
Writing back to the ledger from this layer is gated and not enabled. QuickBooks is the system of record for accounting, and the posting path is owned by the warehouse system today.

Bank reconciliation

Planned
What syncs
Nothing yet.
Direction
Not connected.
What it does not do yet
Payout data is available as a read-only cash-movement ledger. Matching payouts against bank records requires persisted reconciliation state and is not built.

Security and infrastructure connectors

Websites, hosting, cloud and developer tools. Every connector in this section is planned: none can be connected yet, and each page describes the intended design rather than shipped behaviour.

Websites and CMS

Content management systems and the plugins, themes and runtimes they report.

WooCommerce

Planned

Websites and CMS

Store-level inventory for WooCommerce sites, as a scope separate from WordPress.

Drupal

Planned

Websites and CMS

Core and module version inventory for Drupal sites.

Joomla

Planned

Websites and CMS

Core and extension version inventory for Joomla sites.

Hosting and infrastructure

Hosting control panels and servers: accounts, domains, runtimes and certificates.

Plesk

Planned

Hosting and infrastructure

Subscription, domain and PHP version inventory from Plesk servers.

DirectAdmin

Planned

Hosting and infrastructure

Account and domain inventory from DirectAdmin servers.

SSH / Linux

Planned

Hosting and infrastructure

Package and runtime inventory from Linux hosts reached over SSH.

Docker

Planned

Hosting and infrastructure

Container image and version inventory from Docker hosts.

Cloud and developer tools

DNS and edge configuration, cloud resources and source repositories, read-only.

AWS

Planned

Cloud and developer tools

Resource and configuration metadata from AWS accounts, read-only.

Microsoft Azure

Planned

Cloud and developer tools

Resource and configuration metadata from Azure subscriptions, read-only.

Google Cloud

Planned

Cloud and developer tools

Resource and configuration metadata from Google Cloud projects, read-only.

PHP and dependency intelligence

Not an account connection: a parser that normalizes dependency files supplied by other connectors.

Need a provider that is still planned?

Connector order is set by the accounts customers actually run. Tell us which one you need.

Request a demo