Overview

1 Way Interface- RetailCloud posts sales data to Yellow Dog’s Fetch API every 15 minutes.

Sync Approach

RetailCloud has an import module where customers will import item and modifier data from Yellow Dog so that Yellow Dog is the source of record for items.

RetailCloud pulls store data from Yellow Dog for mapping Yellow Dog stores to revenue centers in RetailCloud.

RetailCloud posts sales data to Yellow Dog’s Fetch API.

Yellow Dog runs a process sales application to adjust inventory based on the sales data and ensure that the sales are visible in reports.

Sync Frequency

Every 15 minutes

Configuration

This integration does not support multiple instances of either system against a single instance of the other.

This integration does not support mapping multiple revenue centers in RetailCloud to a single Yellow Dog store; stores and revenue centers must have a 1:1 relationship.

Requirements

Client

  • Complete Revenue Center Mapping in RetailCloud

  • Complete Item import from YD into RetailCloud via the import functionality in RetailCloud

Yellow Dog

  • Create an API User for RetailCloud

  • Provide API Credentials to RetailCloud

POS

  • Pull Stores data from YD's API for Revenue Center mapping in RetailCloud

  • Complete setup on the RetailCloud side to post sales data to YD's API and schedule for every 15 min

  • Assist the customer with importing item data from YD into RetailCloud using the import functionality in RetailCloud

Data Exchange

Sales Data from POS

Overview

RetailCloud posts sales data to Yellow Dog’s Fetch API every 15 minutes; Yellow Dog processes sales to decrement inventory based on sales.

If sales are missed, RetailCloud will have to post them to Yellow Dog’s API.

Matches items on YD SKU/RetailCloud ItemID

The store match is done on RetailCloud’s side.

We pull in the following sales data:

(CHART)

Modifiers

Modifiers are supported in this integration. RetailCloud posts sales of modifiers and provides data on which items were modified.

Workflows - Where Performed

(CHART)

Additional Information

Limitations

  1. ItemID is visible but cannot be modified in RetailCloud. The workflow discussed was that the customer would have YD be source of truth and create items. They would then import the items into retailcloud. Items can be imported to RetailCloud to be created and modified in mass, or manually adjusted through the RetailCloud UI.

  2. 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

  3. RetailCloud doesn't support online sales.

  4. Store mapping must be 1:1 - multiple RetailCloud locations mapped to a single YD Store is NOT supported.

  5. SKU cannot be updated in YD after the item's data has been imported into RetailCloud. RetailCloud uses YD's SKU as their ItemID, which is visible but NOT editable in RetailCloud