Bepoz – 1 Way Interface (Sales)
Last Updated: 8/24/2026
Overview
Yellow Dog gets daily sales data from BePoz via CSV file.
Sync Approach
BePoz provides a daily sales file to a shared SFTP folder.
Yellow Dog’s SalesFile application pulls that file from the SFTP and processes it to get the sales data into YD.
Yellow Dog’s ProcessSales application matches sales to items, adjusts on hands accordingly, and updates reports in YD.
Sync Frequency
BePoz provides their sales file once per day.
Configuration
The only configuration supported for this integration is a single instance of BePoz to a single Yellow Dog database with a 1:1 relationship of BePoz locations to YD stores.
Requirements
Client
Confirm which BePoz StoreID should be mapped to which Stores in Yellow Dog
POS Partner
Confirm time when daily sales export will be available
Complete necessary steps to enable the daily sales export and upload to SFTP
Yellow Dog
Provide SFTP credentials
Yellow Dog provides store names and corresponding revenue center codes to Bepoz.
Data Exchange
Sales Data from POS
Overview
BePoz provides a daily sales file to a shared SFTP folder.
Yellow Dog’s SalesFile application pulls that file from the SFTP and processes it to get the sales data into YD.
Yellow Dog’s ProcessSales application matches sales to items, adjusts on hands accordingly, and updates reports in YD.
Sales can be matched to items in YD by one of the following:
YD SKU to BePoz productID
YD UPC to BePoz productID
POS Item Mapping
We pull in the following sales data:
| Yellow Dog Field | Bepoz Field |
|---|---|
| TransactionNumber | TransactionNumber |
| TransactionLineNumber | [linePositionInFile] |
| CheckClosed | CheckClosed |
| ItemNumber | ItemNumber |
| SKU | SKU |
| Item | itemDescription |
| ItemRetail (always positive) | UnitRetail |
| ItemDiscount (always negative) | UnitDiscount |
| DiscountDescription | DiscountDesc |
| Quantity | QuantitySold |
| EmployeeNumber | EmployeeNum |
| EmployeeName | EmployeeName |
Modifiers
Modifiers are pulled in with the sales data for this integration, but are treated as separate line items.
Workflows - Where Performed
| Workflows | Done in YD | Done in POS |
|---|---|---|
| Create POS Item | x | x |
| Create Stand Item | x | x |
| Create Menu Item | x | x |
| Create Modifier | x | x |
| Modifier Assignment to Item | x | |
| Screen Placement for Item | x | |
| Discount Setup | x | |
| Discount Assignment to Item | x | |
| Tax Setup | x | |
| Tax Assignment | x |
| POS Actions | Result in YD |
|---|---|
| Item Returned | Quantity will be returned to inventory |
| Item Voided | n/a - voids are not supported in this integration |
| Previous Check Voided | n/a - voids are not supported in this integration |
| Item created in POS, not in YD | none until item is sold, at which time it will need to be matched to an item in YD in order to appropriately affect on hands in YD |
| Item deleted in POS | none |
| Item properties changed in POS, not in YD | none - unless SKU changed in BePoz, in which case sales would no longer match |
| Item sold at POS but is Removed in YD | Item's on hand will be updated and it will be automatically un-removed because the on hand is no longer zero |
| Item sold at POS but is Inactive in YD | Item's on hand will be updated and item will remain inactive |
| Menu item sold at POS | Populates in YD POS Item Mapping |
| Menu item created at POS but not sold | none - unsold items are not supported in this integration |
| Modifier created at POS but not sold | none - unsold items are not supported in this integration |
| Modifier sold at POS | Populates in YD POS Item Mapping |
| Image deleted at POS, not in YD | n/a |
Accounting Export:
| Integration Ability from POS | Supported | Details |
|---|---|---|
| POS Sales - Itemized | ||
| POS Taxes | ||
| POS Tender Type | ||
| POS Discounts | ||
| Total Net Sales | x | (Retail*Quantity-Discounts) |
Limitations
Multiple instances of BePoz's POS backend per Yellow Dog database is not supported in this integration, per BePoz.
Posting transactions from multiple POS locations to a single store in Yellow Dog is not supported in this integration, per BePoz.
Voids are not supported in this integration.
BePoz uses nested modifiers in some cases (a modifier on a modifier) and YD doesn't support this when concatenating modifiers in this integration
BePoz's files do not include a discount description for check level discounts.
BePoz's files include line item discount description, but they are whatever name that the POS terminal operator chooses to enter. This does not necessarily reflect an accurate description.
BePoz's files don't consistently present the item being modified before the modifier, therefore concatenate modifiers cannot be reliably used in this integration.
