Revel Systems - 2 Way Interface
The integration with Revel is a 2-Way interface in which Yellow Dog pulls code data from and pushes new and changed items to Revel Systems via their API and receives sales via Revel’s webhook ability.
Yellow Dog's sync to push in new/edited items can be run at any interval, but will be scheduled at the top of each hour during business hours by default.
The following is required from Revel in order to ensure that item and sales data synchronizes correctly:
Revenue Center / Establishment Codes
User ID to be used for the sync
POS Button Colors, if desired
Data Exchange and Mapping
The Yellow Dog sync pulls sales data from the Revel Systems API
Yellow Dog pushes the following item data to Revel Systems via their API
|Yellow Dog Field||Revel Systems Field|
|POS Description 1||Name|
|UPC1/UPC2/UPC3/SKU||Barcode (limit 1 in Revel)|
|Generic Level A||Category (required)|
|Generic Level B||Product Class|
|Generic Code A||POS Button Color|
|Generic Code B||Tax Group|
If an item is made inactive or deleted in Yellow Dog, the item is set to “Not Active” in Revel.
The Yellow Dog sync pulls in the following codes:
Revel POS is limited to a single barcode per item, 4 digits or greater. Yellow Dog's sync will push UPC1 if it is populated with a code longer than 4 digits; if UPC1 is not populated with a valid UPC, the Yellow Dog sync will push UPC2, UPC3, or SKU, whichever has a valid code first.
Because of the way that Revel Systems receives images, we are unable to push images to Revel's API.
After updating items in Yellow Dog and running the sync, a Refresh is required to update the Revel POS.
After updating items, their placement on the Revel POS screens may change.
Revel has specific limitations to the number of API calls that can be made to their API per day; this can cause delays with initial item pushes into Revel PO
We can only push in items, not modifiers.
Yellow Dog's sync can be run from any location that can access the Revel Systems API.