Skip to main content

Price Posting Templates

Distributor steps for adding Price Posting Templates in Encompass to send scheduled EDI 832/888/879/889 price files to retailers, plus fixes for missing prices or products. Requires v22.01+.

B
Written by Bailey Naas-Thornton

Minimum Version Required: 22.01

Pre-Conditions

  • An Exchange Configuration with an 832, 888, 879, or 889 is already created with Production set to True. A customer with correct pricing is identified.

Steps

How to Add Price Posting Templates
​
​
1. Using Universal Search, navigate to the Price Posting Templates table.
​
2. Click the Add Price Posting Template button.
​
3. Enter values to all required and applicable optional fields displayed in the Add Price Posting Template form.
​
a. Price Posting Template - unique name of the posting Template.
​
b. Customer - indicates a Customer to pattern pricing file after, used as a template to create the pricing file.
​
c. Posting Interval - cadence for creating and sending Price Posting files.
​
d. Pricing Days in Future - How far in the future pricing is generated for. Example: If Same Day, the prices listed are for the same day the file is generated. If 1 Week Out, prices listed are for pricing that is available between the day the file is generated and a week from the file generation date.
​
e. Best Price - Determine if only the best price for each product should be posted, or all available pricing.
​
f. Next Run Date - Next Run date is the next time pricing will begin to generate on the posting interval set above. Note: Next Run Date should always be set for today or the future to ensure the pricing file is generated automatically.
​
4. Click the Add Record button when complete.
​
5. Click the Sub Tables button, and add the Exchange Configurations PostingTemplate subtable.
​
6. Enter the Exchange Configuration ID to the form to connect the Price Posting Template to an Exchange Configuration and confirm the Price Posting Template is correct.
​
​

Fields And Definitions

Need to set a Price Posting EDI, but not sure which one? Below are some key functionalities of each!

EDI 832 - also known as a Price/Sales Catalog: EDI 832 is usually sent periodically (quarterly, for example), and offers price and product information for an entire catalog of items.

EDI 888 - also known as an Item Maintenance document. It carries details about a specific product or product. Much like how product information management provides consistency across digital channels, EDI 888 makes it easy to alert trading partners to new product details, as well as changes to existing products.
​
​

EDI 879 - is the EDI transaction associated with electronic Price Information. This document is used by vendors to alert retailers or resellers to new product pricing or product price updates.
​
​

EDI 889 - also known as a Promotion Announcement, is an EDI transaction set used by a business to let their trading partners know about new promotions or discounts, as well as changes to existing promotions. This document is multidirectional, meaning it can be used by a variety of supply chain businesses, but is most commonly used by sellers and brokers.

The awesome thing about EDI is that there is so much online help to troubleshoot, here is one for EDI transaction codes.

Best Practices

Best Practice naming convention: [Retailer's name]+ [Location] + [Company Name] + [Functional Type] + [Cadence]
​
​
EXAMPLE: Loves 649 Brush Pioneer 879 Weekly
​
If an exchange Configuration is not setup, Creating a Task for our EDI Team to setup will help maximize the setup process and ensure everything runs smoothly.

Pricing Issues:
​
​

  1. Check the most recent price posting for the product in question on the price posting template. Filter to the product in Price Posting Trans to see if the pricing/promotion is being posted. If it is not posted, the user will want to make sure the customer is tied to the correct promotion zones and location to ensure they qualify for the pricing.

Product Issues:
​
​

  1. Check the most recent price posting for the product in question on the price posting template. Filter to the product in Price Posting Trans to see if the product is being posted. If it is not posted, the user will want to make sure the customer is able to purchase this product by looking through the standard product controls such as: Product group, Brand family areas, supplier family areas, product authorizations, allocations, product status and seasonality. For more detailed information on product controls please view the help resources under 'Product Controls' in the order management section.

Did this answer your question?