Concept 2-Way Interface
Last Updated 12/11/2023
Overview
The interface with Concept supports a 2-way integration. The 2-way interface is required for retail inventory needs.
There are two elements involved in the interface:
Yellow Dog Software Sync Application
Concept Import/Export Process
Sync Approach
Yellow Dog Software sync application generates a file on a scheduled basis for any new or changed items and places it in an agreed upon ftp location. The sync will also check for any new code and/or sales files from Concept and process them to update codes and reduce inventory/update sales data.
Concept has their process check for new files on a frequency set by the end client. If a file exists, Concept will process it and add or update items to the Concept POS.
Sync Frequency
The Yellow Dog and Concept sync applications can be run on demand and at any frequency. Our recommendation is to have the Yellow Dog sync run every 60 minutes.
Requirements
Client
A complete list of Revenue Center (Warehouse) numbers and descriptions will need to be provided.
POS Partners
Concept will need to ensure that the Client has API V. 204 and configures the import/export process for the client.
Yellow Dog will also need a starting number range for new Item Numbers.
All data on pre-existing Concept items to include:
Number
Family
Warehouse, Name
Search Group
Sales Price 1
Discount Condition
Tax, Unit
Observation
Control Stock
Situation, UPC
Sale Group
Yellow Dog
Yellow Dog version 362 and above is required.
Yellow Dog will set up an FTP location that is accessible by both parties.
Yellow Dog's sync application can run from any computer that can access the designated FTP folder and has .Net 4.6.2 installed.
Data Exchange and Mapping
Sales Data
Yellow Dog receives the following:
| Concept Field Name | Yellow Dog Field |
|---|---|
| 1 (A) | Revenue Center |
| 2 (B) | Sales Type (1=Sale, 2=Invoice (we treat as sale), 3=Void/Refund) |
| 4 (D) | Transaction Number |
| 5 (E) | Check Closed |
| 9 (I) | Employee (GUID) |
| 12 (L) | Concept Transaction GUID |
| 13 (M) | Tender |
| 28 (AB) | Item Code/SKU |
| 29 (AC) | Quantity |
| 30 (AD) | Unit Retail |
| 31 (AE) | Unit Discount |
| 36 (AJ) | Concept Transaction GUID of transaction being voided |
Item Data
Yellow Dog exports the following item data to Concept:
| Concept Field Name | Yellow Dog Field |
|---|---|
| Number (8 Digits) | Item Number |
| Family | Concept Family |
| Warehouse | Revenue Center |
| Name | Item Description |
| Search Group | Concept Search Group |
| Sales Price 1 | Retail 1 |
| Discount Condition | Concept Discount |
| VAT Inc 1 | Concept Tax |
| Unit | Concept Unit |
| Quantity Stock | On Hand |
| Control Stock | Count/No Count status |
| Situation | Active/Inactive status |
| Barcode (no limit) | UPCs, else SKU |
| Sale Group | Concept Sale Group |
System Codes
Concept provides separate files for their codes:
| Concept Field Name |
|---|
| Family |
| Sales Group |
| Search Group |
| Units |
| Color |
| Size |
| Tax (Tax Type) |
| Warehouse (Revenue Center) |
Additional Information
Limitations
1. Concept will only support an 8-digit Item Number. Yellow Dog Inventory will require all Item Number to be 8 digits. Note: Item Number is an internal identification number that is used to send/link sales from Concept. The Yellow Dog SKU is a separate number and does not have any numbering limitations.
2. Yellow Dog can push ALL UPC codes to Concept. If an item does not have ANY UPC codes, we will send the Yellow Dog SKU. If an item has any UPC codes, we will NOT send the SKU. Any bar codes that are printed from Yellow Dog need to respect the above rules.
3. New or changed items only appear in Concept after their Import/Export Process is ran.
Other Notes
Support
Each side will support their portion of the interface.
Implementation
Each of the two elements will be implemented separately by Yellow Dog and Concept.
