Overview

Cliqbux has a 1-way integration with Yellow Dog in which Cliqbux posts sales data to Yellow Dog’s API to deplete inventory levels.

Sync Approach

Cliqbux posts transaction data to the Yellow Dog API.

The integration consists of two elements:

  • The Cliqbux process that posts sales data to Yellow Dog

  • Yellow Dog’s process sales application to process transactions and deplete inventory

Sync Frequency

The Cliqbux application can be scheduled to every 30 min, 1 hr, 3 hrs, 6 hrs, or daily and is configured in Cliqbux

Requirements

Client

Map Yellow Dog Stores to Cliqbux Establishments within Cliqbux. The Cliqbux team can assist with this step.

Next, confirm how sales will be matched to items in Yellow Dog. You can:

  • Map recipes and items using the POS Item Map

  • Configure the integration to match on Yellow Dog SKU

  • If matching sales on YD UPC, ensure that the appropriate setting has been enabled in the database

POS Partner

  • Assist customer with mapping Yellow Dog StoreIDs to Cliqbux EstablishmentIDs

  • Complete setup to post sales transactions to Yellow Dog's API

Yellow Dog

  • Provide API credentials to Cliqbux

  • Provide StoreIDs, along with corresponding Store Descriptions and Codes, to Cliqbux for mapping

  • If matching sales on YD UPC, ensure that the system setting to match on itemAlias has been enabled for the database in Collar


Data Exchange and Mapping

Sales Data from POS

Sales - TPTransaction Third Party Field Notes
ThirdPartyID Cliqbux_[transactionNumber] uniqueID for the transaction, provided by Cliqbux
Converted [thirdPartyId]_[lineNumber] uniqueID for the transaction line, provided by Cliqbux
TransactionNumber unique id It will never be repeated in the Cliqbux database for multiple locations.
TransactionLineNumber sequence
CheckClosed sale order time
ItemNumber productID/modifierID
SKU sku
Item product/modifier title
ItemRetail (always positive) price
ItemDiscount (always negative) unit discount
DiscountDescription n/a
Quantity total sold qty
EmployeeNumber employee id
EmployeeName n/a
Source "Fetch-API"
Tender payment id
Reference "Return to Stock" when line is a return
RegisterNumber establishment station id Where the order is created.
RegisterName establishment station name Where the order is created.
ParentNumber thirdPartyLineId of the item being modified by this modifier line

Modifiers are supported in this integration. 

Workflows- Where Performed

Workflows Done in YD Done in POS
Create POS Item x x
Create Stand Item x x
Create Menu Item x x
Create Modifier x x
Modifier Assignment to Item x
Screen Placement for Item x
Discount Setup x
Discount Assignment to Item x
Tax Setup x
Tax Assignment x
POS Actions Result in YD
Item Returned Quantity returned to inventory
Item Voided n/a - not supported in Cliqbux on closed checks
Previous Check Voided n/a - not supported in Cliqbux
Item created in POS, not in YD When sold, the POS will not have an item in Yellow Dog to match to automatically, but will be available in the POS Item Map
Item deleted in POS None
Item properties changed in POS, not in YD None, unless Cliqbux SKU is changed without ensuring that the same Yellow Dog SKU/UPC was also updated so that it can continue to match
Item sold at POS but is Removed in YD Item on hand will be adjusted in Yellow Dog and the item will be automatically un-removed because it will no longer have an on hand of 0
Item sold at POS but is Inactive in YD Item on hand will be adjusted in Yellow Dog and the item will be automatically un-removed because it will no longer have an on hand of 0
Menu item sold at POS Populates in YD POS Item Mapping
Menu item created at POS but not sold n/a
Modifier created at POS but not sold n/a
Modifier sold at POS Populates in YD POS Item Mapping
Image deleted at POS, not in YD n/a
Accounting Integration Ability from POS Supported Details
POS Sales - Itemized
POS Taxes
POS Tender Type
POS Discounts
Total Net Sales x (Retail*Quantity-Discounts)

Limitations

  • SKU must be populated in Cliqbux to match sales to a Yellow Dog SKU or UPC. If the SKU is not populated in Cliqbux, POS Item Mapping must be used instead.

  • Voids are not possible after a sale is completed in Cliqbux. Removing an item from a check after completion will appear as a return in this integration.