Skip to content
Rupert

How connections work

  • A workspace administrator sets up and authorizes each connection separately. Signing in to Rupert never connects anything on its own.
  • Saved credentials are encrypted. Most connections only read data into Rupert, and anything that would change another system asks for the owner’s confirmation first.
  • Rupert keeps each source’s numbers separate and never adds two systems’ stock together.

Available means it works today. Partial means part of the workflow works, as described. Planned means it is not available yet.

Stores and point of sale

Shopify Available
Reads products, stock by location and orders into Rupert. Rupert changes nothing in Shopify unless the owner confirms it.
Square Available
Reads the catalog, stock, sales and timecards. Read-only.
C-Trax Available
Reads daily orders, register reports, stock counts and staff punches. Read-only.
SwipeSimple Available
Reviewed imports of sales and register reports.

Card payments

Authorize.net Partial
Card checkout through Authorize.net hosted card fields, plus read-only transaction reporting. Live use depends on the merchant’s own Authorize.net account and its approval.
NMI Partial
Card checkout through NMI hosted card fields, on test accounts only. Live charging is switched off.
Processor deposit reports Partial
Reads deposit reports from supported merchant portals to check them against the register.
Dejavoo terminals and payment page Partial
Counter terminals (the card is read on the terminal and Rupert receives only the result) and Dejavoo’s hosted payment page, on Dejavoo’s test system only. Live payments are switched off until the merchant’s processor approves the account.
Card payments on a phone Planned
Taking an in-person contactless payment on an iPhone through the payment provider’s own app. Not available yet, and it will not work on iPad.

Books and files

QuickBooks Available
Imports QuickBooks data, and exports the ledger as QuickBooks IIF or CSV.
Google Drive Partial
Copies retained reports, statements and exports into a Google Drive folder the workspace connects.
Rupert API Partial
A read-only API for catalog and inventory, with scoped, expiring and revocable tokens. Write access and webhooks are planned.

Payments and security

Rupert never receives full card numbers. Providers are named only to say what Rupert connects to: Rupert is not endorsed by them, and the merchant’s own processor decides which businesses and products it accepts. How card payments are kept out of Rupert’s servers: Security and data handling. For a feature-by-feature list, see the product roadmap.

iPhone, iPad and Face ID are trademarks of Apple Inc., registered in the U.S. and other countries and regions. Other company and product names are trademarks of their owners. Rupert is an independent product: naming a company on these pages does not mean it sponsors or endorses Rupert.