SSI PDQ – 2 Way Interface
Last Updated: 10/7/2025
Overview
SSI PDQ integrates with Yellow Dog’s Fetch API to post interface codes and sales, and get item data.
Sync Approach
SSI PDQ has their processes to post interface codes and sales, and get item data from Yellow Dog’s Fetch API.
Yellow Dog’s ProcessSales application is scheduled to run to ensure that sales are matched to items in Yellow Dog, on hands are adjusted, and reports are updated.
Sync Frequency
SSI PDQ posts sales data to Yellow Dog’s API daily at 9am.
SSI PDQ gets item data from Yellow Dog’s API every 15 minutes.
NOTE:
PDQ's terminals must be refreshed in order to see item updates/new items; this can be done manually but it is also done automatically nightly
new/updated barcodes will be scannable at the POS WITHOUT a refresh
Configuration
SSI PDQ can support multiple instances of their system (normally each Property in PDQ would be considered a separate instance) against a single Yellow Dog database.
Multiple Yellow Dog databases against a single PDQ instance is NOT supported.
SSI PDQ’s integration can support mapping multiple Yellow Dog stores to a single PDQ store for sales.
Requirements
Client
Confirm whether PDQ will be pulling retail prices from the interfaces store only or from the mapped non-interfaces stores
NOTE: SSI PDQ can either pull Retail1 from the designated interfaces store OR from the mapped non-interfaces stores; this requires additional setup on the PDQ side
Confirm Revenue Center mapping for sales data
Agree on designated interface ONLY store (separate from the stores mapped to revenue centers)
This will be the store where all interfaces for this integration are set; ALL items that should be pulled in to PDQ MUST be available to this store in YD and have a retail1 set there
Configure PDQ interfaces via Level in the designated interface store (after PDQ has posted their codes to Yellow Dog’s API)
Configure items that should be pulled into PDQ
POS Partner
Provide PDQ StoreIDs to be used as RevenueCenter codes in YD
PDQ posts interfaces to the designated interface store via ThirdPartyCodes in YD's Fetch API
PDQ completes their setup to pull items and post sales
Yellow Dog
Create API User for PDQ
Provide API creds to PDQ
Provide YD StoreID for designated interface ONLY store to PDQ
Complete Revenue Center mapping for sales data by assigning PDQ StoreIDs as Revenue Center codes in YD Stores
Data Exchange
Sales Data from POS
Each day at 9am, PDQ posts transactions to Yellow Dog’s Fetch API.
If sales are missing or incorrect, PDQ will need to update transactions via a PUT.
Sales are mapped to Yellow Dog items by Yellow Dog SKU and PDQ ItemNum.
Stores are mapped for sales by assigning the PDQ StoreIDs as Revenue Center Codes to the Stores in Yellow Dog.
We pull in the following sales data:
Yellow Dog Field Partner Field
Modifiers
Modifiers are supported in this integration: they are posted as part of sales data.
Item Data from Yellow Dog
SSI PDQ gets item data from Yellow Dog’s API every 15 minutes.
NOTE:
PDQ's terminals must be refreshed in order to see item updates/new items; this can be done manually but it is also done automatically nightly
new/updated barcodes will be scannable at the POS WITHOUT a refresh
Interface Codes
SSI PDQ posts the following interface codes to Yellow Dog’s Fetch API
Yellow Dog Item to POS Mapping is not supported in this integration; sales are mapped to items via SKU only.
SKU must not be changed in Yellow Dog; SKU is added to the list of UPCs for the item to ensure that it is scannable in PDQ.
No known limitations on UPC in this integration; multiple UPCs are supported.
Workflows - Where Performed
Accounting Export:
Accounting data will be available for Total Net Sales only.