Cinchio 2-Way
Last Updated: 6/1/2026
Overview
Cinchio gets item data from and posts sales data to Yellow Dog’s Fetch API.
Sync Approach
This integration consists of 3 elements:
Cinchio’s process to get item data from Yellow Dog’s Fetch API
Cinchio’s process to post sales data to Yellow Dog’s Fetch API
Yellow Dog’s Process Sales application, which matches sales to items in Yellow Dog, then updates on hands and sales reports.
Sync Frequency
Cinchio gets item data from Yellow Dog’s API every 10 minutes
Cinchio posts sales data to Yellow Dog’s API hourly
Yellow Dog fully processes the sales data at least once daily
Configuration Options
This integration supports a single instance of Yellow Dog to a single instance of Cinchio
Multiple instances of either system to a single instance of the other is not supported
This integration supports mapping a single Yellow Dog store to a single Cinchio store
Mapping multiple stores from either side to a single store on the other is not supported
Requirements
Client
Map YD Stores to Cinchio Stores/Locations in Cinchio
POS Partner
Complete their process to connect and schedule item pull from and sales push to YD's Fetch API
Assist customer with mapping YD Stores to Cinchio Stores/Locations in Cinchio
Yellow Dog
Create and provide API credentials to Cinchio for the customer's db
Data Exchange and Mapping
Sales Data
Cinchio posts sales data to Yellow Dog’s Fetch API hourly and Yellow Dog fully processes the sales data at least once daily.
Yellow Dog SKUs are matched to Cinchio ProductCodes.
Yellow Dog Stores are matched to Cinchio LocationIDs via mapping in Cinchio’s system.
Cinchio provides the following sales data:
| Yellow Dog | Cinchio |
|---|---|
| ThirdPartyID (unique id for the check) | Cinchio_[LocationID]_[TransactionID] |
| Converted (unique id for the line) | Cinchio_[LocationID]_[TransactionID]_[LineNumber] |
| StoreID | YDStoreID |
| TransactionNumber | ExtTransactionID-CompanyID-SourceID |
| TransactionLineNumber | Sequential |
| CheckClosed | TransactionDateTime |
| ItemNumber | n/a |
| SKU | ProductCode |
| Item | ProductNameLong |
| ItemRetail (always positive) | Gross |
| ItemDiscount (always negative) | RRPGross |
| DiscountDescription | DiscountName |
| Quantity | Quantity |
| EmployeeNumber | ClerkID |
| EmployeeName | ClerkName |
| Tender | MediaName |
| Reference | OrderReference |
| RegisterNumber | TillID |
| RegisterName | TillName |
Modifiers are not supported in this integration
Item Data
| Yellow Dog | Cinchio |
|---|---|
| ThirdPartyID (unique id for the check) | Cinchio_[LocationID]_[TransactionID] |
| Converted (unique id for the line) | Cinchio_[LocationID]_[TransactionID]_[LineNumber] |
| StoreID | YDStoreID |
| TransactionNumber | ExtTransactionID-CompanyID-SourceID |
| TransactionLineNumber | Sequential |
| CheckClosed | TransactionDateTime |
| ItemNumber | n/a |
| SKU | ProductCode |
| Item | ProductNameLong |
| ItemRetail (always positive) | Gross |
| ItemDiscount (always negative) | RRPGross |
| DiscountDescription | DiscountName |
| Quantity | Quantity |
| EmployeeNumber | ClerkID |
| EmployeeName | ClerkName |
| Tender | MediaName |
| Reference | OrderReference |
| RegisterNumber | TillID |
| RegisterName | TillName |
SKUs are not scannable in Cinchio; they only allow UPCs to be scannable.
Workflows - Where Performed
| Yellow Dog Item Properties | Cinchio Item Properties | Notes |
|---|---|---|
| Store | Store/Location | |
| Description | ProductNameShort | |
| POS Description 1 | ProductNameLong | |
| Retail1, per store | SalePriceUnit | |
| SKU | ProductCode | SKU is NOT scannable in Cinchio |
| UPC(s) | Barcode | Supports multiple; no known limit |
| Matrix Items - Product/Variants | Treated as individual items in Cinchio | |
| Items are active/set pushed when | Has a SKU, a Description, a POS Description 1, and a Retail1 in each configured store the item is available to | UPC is optional and is not required for the item to be pulled into Cinchio |
| Additional configuration settings in the third party system | Tax categories and any other Cinchio-specific properties must be set in Cinchio directly | |
| Interfaces | n/a |
| YD Action | Result in POS |
|---|---|
| Item Creation | If the item has the required properties set in YD, Cinchio will pull the item into their system. |
| Item Edit/Update | If the item has the required properties set in YD, Cinchio will pull the item updates into their system. |
| SKU Edited | Will result in a duplicate item in Cinchio, since they use the SKU as a unique ID. |
| UPC Edited | Cinchio will pull in UPC(s) and update them in Cinchio. |
| Inactivated | None; Cinchio does not use YD's Active flag. |
| Removed | None; removed items don't appear in YD's API. |
| Level Is Changed | None; Cinchio does not pull Level assignments for items. |
| Item is configured to Push to POS | Item available to one or more YD stores configured for this integration and has a Retail1 in the store(s). |
| Publish set to "No" | None; Cinchio does not use YD's Publish interface. |
| POS Blocked | None; Cinchio does not use YD's POS Blocked flag. |
| Unchecked availability to one store/location | Cinchio will update location availability for the item in Cinchio to match store availability in YD. |
| No longer available to Any Store/Location | Cinchio will update location availability for the item in Cinchio to match store availability in YD. |
| Image added to item in YD | None; Cinchio does not pull images from YD. |
| Image removed from item in YD | None; Cinchio does not pull images from YD. |
| Item removed from Sales Channel | None; Cinchio does not use Sales Channel assignments from YD. |
| On Hand changed in Yellow Dog | None; Cinchio does not pull on hands from YD. |
| POS Actions | Result in YD |
|---|---|
| Item Returned | Item on hand will be positively adjusted based on the return quantity. |
| Item Voided | Not supported in Cinchio. |
| Previous Check Voided | Not supported in Cinchio. |
| Item created in POS, not in YD | None, but if the item is sold in Cinchio it will not match to any YD items. |
| Item deleted in POS | None. |
| Item properties changed in POS, not in YD | If any of the item properties that Cinchio pulls from YD's API are changed in Cinchio, those properties will be overwritten the next time the item is updated based on YD's API. |
| Item sold at POS but is Removed in YD | The item's on hand is adjusted in YD based on the sale, and the item is automatically un-removed in YD because it will no longer have an on hand of 0. |
| Item sold at POS but is Inactive in YD | The item matched to the sale will have its on hand adjusted in YD based on the sale. |
| Menu item sold at POS | Cinchio posts the transaction to YD's API; the sale matches to the item based on YD SKU to Cinchio ProductCode. |
| Menu item created at POS but not sold | n/a - retail only, and all items originate in YD. |
| Modifier created at POS but not sold | n/a - retail only. |
| Modifier sold at POS | n/a - retail only. |
| Image deleted at POS, not in YD | None; images are not used in this integration. |
Accounting Export :
Total Net Sales (Retail*Quantity-Discounts) from this integration can be exported from Yellow Dog
Limitations
Interface codes are NOT used in this integration; customer will be responsible for setting Cinchio specific item properties, such as tax categories, on items directly in Cinchio
Voids are not supported in Cinchio
SKU must NOT be changed in YD, as this will create a new (duplicate) item in Cinchio
Cinchio has a method of mapping store specific retail prices using their price level structure
SKUs are not scannable in Cinchio
Only UPCs are scannable; Cinchio chose not to add YD SKUs to the barcode list in their system.
