Overview
The integration with Rezku supports a 1-way interface that pulls sales and unsold items from Rezku’s API.
Sync Approach
Yellow Dog uses SyncYDIwithMicroServices to pull sales and unsold items to be mapped in Yellow Dog using Rezku’s API.
Sync Frequency
Typically the sync is scheduled to run hourly.
Requirements
Client
Recipes in Yellow Dog must be mapped to the correct POS items in order to deplete inventory.
POS Partner
Rezku needs to provide:
Client ID
Client Secret
Restaurant ID(s)
Yellow Dog
Yellow Dog must create an Auth API account.
Responsibilities
Client
Client is responsible to map recipes to items sold in POS Item Mapping in order to deplete inventory.
POS Partner
TBD
Yellow Dog
TBD
Data Exchange and Mapping
Sales Data
Only sales of Closed orders are pulled into Yellow Dog.
| Rezku Field | Yellow Dog Field |
|---|---|
| Ticket.ClosedAt.Value | Check Closed |
| OrderProduct.Sku | SKU |
| ticket.UserId.HasValue | Employee Number |
| ticket.UserName | Employee Name |
| ticket.RegisterID.Value | Register Number |
| ticket.id.value | Transaction Number |
Additional Information
Limitations
Check wide discounts are distributed across all priced items on the check using a maximum of 4 decimal places which may result in rounding issues when reports are limited to 2 decimal places
We are unable to support Returns or Voids on previously closed checks due to the inability to tie them items
Other Notes
When a line item quantity is greater than 1 in Rezku their API shows separate lines with a quantity of 1 and Yellow Dog reporting matches this.
