Yellow Dog/Simphony2 w/Oracle Integration Overview

Yellow Dog/Simphony2 w/Oracle Integration Overview

This document will provide an overview of the Yellow Dog /Simphony 2Way integration 

Integration Approach

The Yellow Dog/Simphony integration is a 2Way integration
  1. Sales – pulled in from files provided by Oracle once per day 
  2. Codes – pulled from the Simphony API
  3. Items – pushed to the Simphony API 

Requirements for Items to Push to Simphony 

  1. The item must be active 
  2. The item must be available to the store 
  3. The item must not be POS Blocked - this can be checked in the interface codes as of sync view. From this view, users can also quickly identify that Publish is enabled, and that the item is available to the store in question.

  1. The item must be set to publish

  1. The item must have a Major Group set in interfaces
  2. The item must have a Family Group set in interfaces
  3. The item must have a Menu Item Class set in interfaces

Best Practices for Managing Items

Updates and edits to items should be made in Yellow Dog and allowed to push to Simphony. If updates are made directly in Simphony it will be overwritten by Yellow Dog the next time the integration runs.

What to check before calling support:

  1. Check that your items have all requirements set
  2. Confirm your scheduled sync time has passed, feel free to ask support when your sync times are or refer to the scheduled apps report in YD’s Standard Report section to review your sync times.
  3. Note any errors appearing at the POS when you try to scan. If your items are still not able to be rung up at the POS, these errors can help support identify the issue.

Limitations 

  1. Sales are only provided once per day
  2. Sales do not contain transaction specific details such as check closed or transaction numbers
  3. Before removing items from Simphony, users will need to turn the item to “No, push nothing” in the publish field to prevent errors in the sync
  4. This integration does not delete barcodes from Simphony, any barcodes deleted in YD will need to be removed in Simphony manually
  5. There is a 12 digit limit for all barcodes 

For additional information on the Yellow Dog/Simphony Integration visit https://help.yellowdogsoftware.com/micros-simphony-2x-oracle-hosted/



    • Related Articles

    • Yellow Dog/Roller Integration Overview

      This document will provide an overview of the Yellow Dog Roller Integration Integration Approach This integration can be set up as a 2Way - Pull sales & Push items or a 1Way - Pull sales Sales – Pulled from Roller Webhook Codes – Pull from Roller API ...
    • Yellow Dog/Resort Suite Integration Overview

      This document will provide an overview of the Yellow Dog Resort Suite Integration Integration Approach This is a two-way file exchange integration – we pull sales and push items Sales – pulls sales from a CSV file Summary: will provide sales as a ...
    • Yellow Dog/Toast Integration Overview

      This document will provide an overview of the Yellow Dog Toast Integration Integration Approach This is a 1Way Integration – Pull sales only Sales – Pulled from the Toast API Items – Can be matched on SKU Item management best practices Yellow Dog ...
    • Yellow Dog/Silverware Integration Overview

      This document will provide an overview of the Yellow Dog Silverware Integration Integration Approach This can be setup as a 2Way – Push items and Pull sales or a 1Way – Pull sales Sales – Pulled from the Silverware API Codes – Pulled from the ...
    • Yellow Dog/Revel Integration Overview

      This document will provide an overview of the Yellow Dog Revel Integration Integration Approach This can be set up as a 2Way – Push items and Pull Sales or a 1Way – Pull Sales Sales – Pull from Revel Webhook Codes – Pull from Revel API Items – Push ...
    • Recent Articles

    • Yellow Dog/Jonas API Overview

      This document will provide an overview of the Yellow Dog Jonas API Integration Integration Approach This can be set up as a 2Way – Items are pulled from us, and sales are pushed or 1Way sales are pushed. NOTE: Jonas controls the flow of sales and ...
    • Retail Best Practices for Physical Inventory Webinar

      Ready to crush your next physical? Check out our latest webinar for tips, tricks, and best practices to make it a breeze.
    • Email Invoice Processing – Error response received when processing unsupported file type

      Yellow Dog Inventory Troubleshooting: Email Invoice Processing – Error response received when processing unsupported file type Issue: User received the following unsuccessful processing response when sending an invoice for invoice staging: “The ...
    • Feature Overview: Client ID

      What is a Client ID? The Client ID is a unique identifier assigned to each Yellow Dog Inventory system. Who is it for? The Client ID will be used by any user that will access a Yellow Dog mobile or web app. What is it used for? A Client ID is ...
    • Feature Overview: Password Recovery

      What is Password Recovery? Password Recovery is a built-in feature that allows Yellow Dog users to securely reset their login credentials independently by answering predefined security questions. This self-service option reduces the need for ...