Overview

Yellow Dog's 1-way interface with Focus pulls sales data to reduce inventory based on transactions.

Sync Approach

Yellow Dog Inventory will pull sales from the Focus server via XML files.

Sync Frequency

This sync can be scheduled to run at any frequency, however it should be scheduled to run after the daily sales export has been generated. Sales are exported 1x daily.

Requirements

POS Partner

Focus will need to configure the Daily Sales export to include:

DailyData

  • Configuration

    • Discount/Discounts --required to pull in Discount descriptions

    • Voids --required to pull in Void descriptions

    • Stations --required to pull in Register Names

  • MenuItems

    • MenuItemRecord --required to pull in unsold items to be used in POS Item Map

  • Checks

    • CheckRecord

    • Seats

    • Seat

    • CheckItemRecord

Responsibilities

Client

Client should identify the Revenue Center codes that match the stores in Yellow Dog. If needed, Client will also need to provide access to a location that can access the Daily Sales Export files.

POS Partner

In addition to configuring the sales export, Focus is also responsible for scheduling the sales export to run.

Yellow Dog

The sync can be ran from any location that has access to the Dailys Sales Export files.

Data Exchange and Mapping

Sales Data

Focus FieldYellow Dog Field
CheckRecord > RevenueCenterID Store
CheckRecord > IDTransactionNumber
CheckItemRecord > KeyTransactionLineNumber
CheckRecord > TimeClosed CheckClosed
CheckItemRecord > RecordNumberItemNumber
CheckItemRecord > RecordNumberItemNumber
CheckItemRecord > GuestCheckNameItem
CheckItemRecord > PriceItemRetail
CheckItemRecord > DiscountAmountItemDiscountAmount
Configuration > Discounts > Discount > Name DiscountDescription
CheckItemRecord > QuantityQuantity
CheckRecord > CloserNameEmployeeName
CheckRecord > CloserIDEmployeeNumber
CheckRecord > StationClosedIDRegisterNumber
Stations > Station > Name based on Checks > Check > CheckRecord > StationClosedIDRegisterName
Check > Seats > Seat > PaymentRecord > NameTender
Configuration > Voids > Void > Name based on CheckItemRecord > VoidIDReference

Additional Information

Limitations

TBD