Skip to main content

Meijer EDI Version Update: Required Action

As of now, Meijer will only support specific EDI standards. Read on to learn more!

Written by Support
Updated this week

Product(s): Foundry platform, Transaction Manager

Overview

Meijer has recently communicated that they will only support the following EDI standards moving forward:

  • UCS / VICS / X12 version 4050

  • UCS / VICS / X12 version 5010

Your company has been identified by Meijer as needing to migrate to one of these supported EDI versions. To remain compliant and ensure uninterrupted transaction processing, updates must be made within the TrueCommerce Foundry platform to align with Meijer’s requirements.


How to Identify the Required EDI Version

  1. Open a recently received Purchase Order from Meijer.

  2. Select the EDI tab within the transaction.

  3. In the Standard Information section, locate the Version field.

    If the version listed is 4050 or 5010, this is the version that must be used for all outbound transactions sent to Meijer.


Updating Transactions in Foundry

Follow the steps below to update your active transactions to the correct version: 

  1. In Foundry, open the Menu and select Transaction Manager. 

  2. Choose Trading Partners, then select Meijer from your list of trading partners. 

  3. From the top toolbar, select Preferences, then choose Transactions. 

Deactivate Unsupported Versions

  1. In Transaction Setup, locate transactions currently marked as Active. 

  2. If the Version column does not show 4050 or 5010, deactivate the transaction by unchecking the Active box. 

Activate the Correct Version

  1. Locate the transaction that matches the correct version (4050 or 5010, based on the Purchase Order). 

  2. Mark this version as Active. 

  3. Repeat this process for all transaction types previously sent to Meijer, ensuring they are updated to the supported version. 


Final Configuration Steps

  • Update all newly activated transactions to Production mode. 

  • If your organization uses an integration to generate these transactions, ensure the Import Document Type is correctly set. 

  • Save all changes. 

  • Before sending outbound transactions, review the transaction templates and hardcode any required static values as needed. 

  • If your team uses Scheduler, confirm that all related Scheduled Events are updated to reference the correct transaction versions. 


Additional Resources

Click any of the following links for further information and supplemental Transaction Manager Help Center articles:

Did this answer your question?