New EDI Development
EDI (Electronic Data Interchange) can allow Yellow Dog Inventory to automatically communicate with third-party systems via text files, typically via FTP or network folders. For our purposes, EDI file formats can include X12, CSV, A2A or any custom layout.
Yellow Dog Inventory also has the capability to import and export data manually. That is not part of this document. Please see Generic Sync for more information.
We build a new "sync" for each EDI vendor. This is typically referred to as SyncYdiWithVendor internally. Creating a sync for a new vendor requires a development effort by Yellow Dog Software.
Yellow Dog Inventory EDI Implementation Questions
What document types does YDI support?
We can pull the following documents:
- Product Guides
We can potentially push Purchase Order information.
How are files transported?
Files are typically published to an FTP server by the vendor and pulled by YDI. We can use a vendor's FTP account or we can provide an FTP account. Each vendor/customer should have a unique FTP account.
We can use other transports, such as SFTP.
Does YDI require specific data formats?
No. We build each vendor's sync individually. Even X12 EDI syncs are customized per vendor. We simply require a specification of the file formats.
What are the steps to build a new EDI sync?
- One of Yellow Dog Inventory's implementation managers will work with the customer to determine if EDI is required.
- The implementation manager will facilitate a call between the customer and the vendor to determine requirements.
- A transport (such as FTP) will be agreed upon.
- The vendor will provide file specifications.
- The vendor will provide sample data or (ideally) immediately begin publishing the customer's documents.
- Yellow Dog Software will build a new sync and pull the data into Yellow Dog Inventory.
- The customer will review.
Specific Data that YDI Can Consume:
Yellow Dog Inventory Item Export
Please refer to our Generic Sync for information on how YDI can already export inventory data. If Yellow Dog Software will be building a custom export, all fields described under the "Exporting From Yellow Dog Inventory" section are available.
Yellow Dog Inventory Item Import
If item information is to be pushed into YDI as part of an Order Guide, EDI 832 Price/Sales Catalog, or Purchasing document, the following data fields should be present in the third-party data. If data is already available in a document header (Invoice Store, for instance) it is not necessary to place the data with each line item.
The column names below are only suggestions.
|ItemID||Yes||A code that uniquely identifies the item.|
|StoreID||Recommended||A code that identifies which store this item is assigned to.|
|SKU||REcommended||A user-friendly item code, if different than ItemID.|
|UPC||No||A UPC that also identifies an item|
|Description||Yes||Standard item description in plain text.|
|Size||No||Size of the item.|
|ChildCount||No||If the item is a case, this number indicates the number of units per case.|
|Color||No||Color of the item.|
|MatrixID||Yes||A code that uniquely identifies a group of items that are all the same item but may have different Sizes, Colors or Retail.|
|ItemCost||Recommended||Current cost or vendor price of item.|
|ItemRetail||Recommended||Current retail price of item.|
|ManufacturerID||No||A code that uniquely identifies the Manufacturer.|
|Manufacturer||No||The Manufacturer's description.|
|No||A code that the Manufacturer uses to identify the item.|
|VendorID||No||A code that uniquely identifies the Vendor.|
|Vendor||Recommended||The Vendor's description.|
|VendorSKU||Recommended||A code that the Vendor uses to identify the item.|
|DepartmentCode, DepartmentDescription||No||If a code or description can be provided that uses YDI's level scheme it will be matched on. Otherwise the user will need to fix each new item after it is added into YDI. We often have a second scheduled task that sends out email notifications when items need to be fixed.|
|CategoryCode||No||Same As Department|
Please refer to our Generic Sync for information on how YDI can already import sales data. If Yellow Dog Software will be building a custom sales import, all fields described under the "Transactions" section are available.
Receipts / Invoices
If Yellow Dog Inventory is to import Receipt and/or Invoice data, the following data fields can be used.
|DocumentID||Yes||A code that uniquely identifies the purchasing document. This can be an Invoice Number.|
|StoreID||Yes||A code that identifies which store this document is applied to.|
|PurchaseOrderID||No||A code that identifies a Purchase Order this receipt or invoice is related to.|
|Description||No||General Description of the document|
|InvoiceTotal||No||Total amount of the invoice.|
|InvoiceExpenses||No||This can include Taxes, Freight, Other. This can be broken into multiple fields or records.|
|VendorID||Yes||A code that uniquely identifies the Vendor.|
|Vendor||Yes||The Vendor's description.|
Line Item Detail:
|ItemID||Yes||A code that uniquely identifies the purchasing document. This can be an Invoice Number.|
|StoreID||Yes||A code that uniquely identifies the item.|
|Other Item Information||See "Yellow Dog Inventory Item Import", above.|
|Quantity||Yes||Quantity being received. This can be a decimal.|
|ItemCost||Yes||The unit cost per item. If only Extended Cost is available we will divide that by Quantity.|
|LineItemNotes||No||Any notes or custom line information|
In addition to all data fields described under "Receipts / Invoices", only the Target Store ID is required to build a transfer.
|SourceStoreID||Yes||A code that identifies which stores items will be deducted from.|
|TargetStoreID||Yes||A code that identifies which stores items will be added to.|
|ItemCost||No||Item cost is ignored by transfers within YDI. In the case of transfers, cost is always reported as Calculated Cost of Source Store.|
|Other Item Information||See "Receipts / Invoices" above.|
If Yellow Dog Inventory is to push Purchase Orders all data fields found under the "Yellow Dog Inventory Item Import" and "Receipts / Invoices" sections can be included, with the exception of invoice expenses.