Order Commander
Updated: 11/8/24
Overview
Yellow Dog's integration with Order Commander is a one way sales pull via CSV files processed through Yellow Dog’s generic Sales File sync.
Sync Approach
The Integration consists of two elements:
Order Commander’s process to export sales data to a csv file and post to an SFTP location.
Yellow Dog’s generic Sales File sync to pull the sales files from the SFTP location and process transactions in order to deplete inventory.
This integration supports
Multiple Order Commander Locations mapped to a single Yellow Dog Store.
Multiple instances of Order Commander against a single instance of Yellow Dog, as long as there are not any overlapping Revenue Center Codes in the different instances of Order Commander.
Sync Frequency
Yellow Dog can pull in sales data hourly by default, but the frequency of the sync will depend on the frequency with which Order Commander posts their files to the SFTP location.
Requirements
POS Partner
Order Commander is responsible for
Configuring and scheduling their sales export process and uploading to the SFTP location.
Providing Revenue Center codes from Order Commander, if the customer doesn’t have access to them.
Yellow Dog
Yellow Dog is responsible for
Ensuring that the minimum version of Yellow Dog Inventory is v376 or higher and hosted by Yellow Dog.
Providing the SFTP location and login credentials to Order Commander.
Installing, configuring, and scheduling the generic Sales File sync to pull and process sales data from the SFTP location.
Responsibilities
Client
The client is responsible for
providing a list of Revenue Center Codes from Order Commander (if they have access).
providing mappings of Revenue Center Codes from Order Commander to Stores in Yellow Dog.
mapping sales to recipes in Yellow Dog’s POS Item Map.
Data Exchange and Mapping
Sales Data
Order Commander controls the export of sales data to CSV files and the posting of those files to the SFTP location; Yellow Dog controls the pulling down and processing of the CSV files from the SFTP into Yellow Dog to deplete inventory, which is dependent on the client mapping the POS Items via the POS Item Map in YDInv.
Below are the corresponding data fields:
| Yellow Dog Field | Order Commander Sales File Field |
|---|---|
| Revenue Center | Location |
| TransactionNumber | TransactionNumber |
| CheckClosed | CheckClosed |
| ItemNumber | ItemNumber |
| Item | ItemDescription |
| Item Retail | UnitRetail |
| ItemDiscount | UnitDiscount |
| Quantity | QuantitySold |
| RegisterName | SellingArea |
| ParentNumber | ParentItem |
| IsModifier | IsModifier |
Additional Information
Limitations
We did not have any examples of the following types of transactions in test data, so cannot guarantee that they are supported: Returns, Voids, and Split Checks. (11/8/24)
Matching sales to items on ItemNumber is not supported; so POS Item Map will need to be utilized. (11/8/24)
Modifiers must be configured in a consistent way to support concatenating modifiers. (11/8/24)
For example, we saw parent item: Bud Light and modifier: Bottle with the retail price on the bottle; this would work with concatenate modifiers enabled and the modifier line mapped to the recipe.
