Updated April 2025
RetailCloud – 2-Way Interface
Overview :
RetailCloud posts sales data and pulls item data from Yellow Dog’s Fetch API.
Sync Approach:
This integration consists of two main elements:
RetailCloud’s processes to sync data with Yellow Dog’s API
Yellow Dog’s ProcessSales application to match sales to items, adjust on hands, and update cost and reports data.
Sync Frequency:
RetailCloud
Posts Sales data to Yellow Dog’s Fetch API every 15 minutes
Pulls Item data from Yellow Dog’s Fetch API every 30 minutes
Configuration Options:
This integration supports a single instance of RetailCloud against a single Yellow Dog database, and one RetailCloud revenue center per Yellow Dog store.
This integration does not support multiple instances of RetailCloud against a single Yellow Dog database.
This integration does not support multiple RetailCloud revenue centers per Yellow Dog store.
Requirements
Client:
Determine which YD store will be the designated Interfaces store
Complete Revenue Center Mapping in RetailCloud
Complete any other setup with RetailCloud, including determining whether Taxes will be set via RetailcloudTax interface or via Level4 in YD.
Yellow Dog:
Provide API Credentials to RetailCloud
Ensure that SKUs in YD are 15 characters or less and that autonumber for SKUs is set to create SKUs < 15 characters
POS:
Pull Stores data from YD's API for Revenue Center mapping in RetailCloud
Post ThirdPartyCodes to YD's API to the designated Interfaces store
Get Items from YD's API
Complete setup on the RetailCloud side to get items from YD's API and schedule for every 30 min
Complete setup on the RetailCloud side to post sales data to YD's API and schedule for every 15 min
Data Exchange
Sales Data from POS
RetailCloud posts Sales data to Yellow Dog’s Fetch API every 15 minutes.
If sales are missing/missed, RetailCloud will need to post them to Yellow Dog’s Fetch API.
Yellow Dog Stores are mapped to RetailCloud revenue centers in RetailCloud.
RetailCloud’s ItemID matches Yellow Dog’s SKU.
RetailCloud posts the following sales data:
Modifiers
The two-way RetailCloud integration with Yellow Dog is focused on Retail items and not F&B items, but, in general, the sales data RetailCloud posts to Yellow Dog includes modifier data when applicable.
Item Data from Yellow Dog
RetailCloud pulls Item data from Yellow Dog’s Fetch API every 30 minutes.
Interface Codes
Yellow Dog Item to POS Mapping is not used for the two-way RetailCloud integration.
SKU & UPC Limitations
SKUs are limited to 15 characters
SKUs cannot be updated in Yellow Dog after the item’s data has been pulled into RetailCloud.
When updating UPCs on an item, RetailCloud will NOT remove UPCs that are assigned to the item in RetailCloud but are no longer assigned to the item in YD.
Workflows - Where Performed
Accounting Export : Total net sales only
Limitations
RetailCloud doesn't support online sales
ItemID is visible but cannot be modified in RetailCloud.
RetailCloud's ItemID field is limited to 15 alphanumeric characters
YD's SKU is used in that field, so note that SKU cannot be more than 15 characters
Store mapping must be 1:1 - multiple RetailCloud locations mapped to a single YD Store is NOT supported
SKU cannot be updated in YD after the item's data has been imported into RetailCloud (for a one-way integration) or pulled from YD's API into RetailCloud (for a two-way integration)
RetailCloud uses YD's SKU as their ItemID, which is visible but NOT editable in RetailCloud
RetailCloud pulls Retail1 from the designated interfaces store only
Per Store Retail prices aren't supported in this integration
When updating UPCs on an item, RetailCloud will NOT remove UPCs that are assigned to the item in RetailCloud but are no longer assigned to the item in YD.
Items pulled into RetailCloud are available to ALL locations; RetailCloud does not assign items to locations based on their store assignments in YD
Images are not currently supported by this integration
