Revel Systems

Revel Systems is a cloud-based POS platform for restaurants and retail.

Overview

Revel Systems is an iPad-based point-of-sale platform used by restaurants, quick-service chains, and retail operators. It tracks orders, customers, products, inventory, and employees across one or many establishments, and exposes a REST API for downstream integration with accounting, marketing, and ERP systems.

In Spojit workflows, Revel typically acts as the source of truth for POS transactions and customer data. Common patterns include pushing daily orders into NetSuite for revenue accounting, syncing customer profiles into Klaviyo for email marketing, and reporting on inventory or employee data.

What You Can Do

The Revel connector exposes these tools:

create-customer - create a new customer record.
create-order - create a new order.
create-product - create a new product.
get-customer - fetch a single customer by ID.
get-order - fetch a single order by ID.
get-product - fetch a single product by ID.
list-customers - list customers, with optional filters.
list-employees - list employees configured in Revel.
list-inventory - list inventory levels.
list-orders - list orders, typically filtered by date or establishment.
list-products - list products in the Revel catalog.
raw-api-request - call any Revel REST endpoint not covered by typed tools.

Authentication

Revel authenticates with an API key, API secret, and an establishment ID. Get these from your Revel administrator: in the Revel admin (Management Console), look under API settings for the key and secret, and find the establishment ID under the establishment configuration. Multi-location operators have one establishment ID per location - create one Spojit connection per establishment, or use raw-api-request to switch establishments per call.

Setting Up Your Connection

In the Revel Management Console, retrieve your API key, API secret, and establishment ID.
In Spojit, go to Connections in the sidebar.
Click + Add Connection.
Search for Revel Systems and select it.
Enter the API key, API secret, and establishment ID.
Give the connection a name (e.g. "Revel - Main Street").
Click Save.

Using in a Workflow

Add a Connector node and select your Revel connection. Use Direct Mode for scheduled exports - call list-orders with a date range on a daily schedule and push results into NetSuite or a database. Use Agent Mode for ad-hoc analysis where the agent decides whether to look at customers, products, or inventory. For endpoints not covered by typed tools (modifier groups, taxes, payments breakdown), use raw-api-request.

Tips

Filter list-orders by a narrow date range - establishments with high volume return many records.
One connection per establishment keeps the data scope predictable; alternatively keep one connection and switch establishment IDs in raw-api-request calls.
Cache list-employees and list-products where possible - these change less often than orders.
Pair Revel exports with Date & Time Tools to normalise timestamps to UTC before pushing into downstream systems.
For long-running sync workflows, write the last successful timestamp into a database and use it as the next run's lower bound.

Common Pitfalls

Establishment ID is required on most endpoints - calls fail silently or return wrong data if it is missing or wrong.
Revel timestamps are in the establishment's local timezone, not UTC - convert before joining with other systems.
Order totals include taxes and discounts in fields you may not expect - confirm the schema before pushing to accounting.
API throttling can occur on bulk calls; back off and retry on 429 responses.
Refunds and voids show as separate records linked to the original order - reconcile by parent order ID, not by listing alone.

Common Use Cases

For technical API details and field specifications, see the Revel Systems connector documentation.