If dispatch information is updated after the original dispatch is received by Omega you may need to link a new, updated dispatch in order for EDI validations to pass. The method for doing this depends on the sender of the dispatch.
GNCS
GNCS dispatches must be re-transmitted by GNCS. Please contact GNCS and request to have a dispatch resent if the information has been updated. The new dispatch will automatically replace the old one as long as the job in Omega has the same claim ID and is less than 90 days old.
SGC
SGC dispatches (referrals) are pulled from sgc.safelite.com. If information has been updated since the initial pull it may be necessary to refresh the referral from within the dispatch view. It may take up to 30 seconds for the new information to appear.
Lynx
Lynx dispatches must be re-transmitted in order for the information to update in Omega. You can request a dispatch be re-transmitted by contacting Lynx or by visiting www.lynxservices.com. The updated dispatch will automatically attach as long as the dispatch numbers match and the job in Omega is less than 90 days old.Older dispatches are not automatically imported into Omega when connecting Lynx Services. To include these dispatches, request Lynx to redispatch them. This ensures they are processed and appear in Omega.If a Lynx dispatch does not appear in Omega, you can manually create the job in Omega and upload the dispatch document as an attachment in the "Attachments" section. This allows you to proceed with the job even if the dispatch wasn’t auto-ingested.Ensure that the account is configured with the Lynx EDI integration. Do not use the Driven Claims EDI setting for Lynx dispatches. Update the EDI setting to "Lynx EDI" for the dispatch or account as needed.While waiting for a Lynx dispatch to appear in Omega, use the dispatch communication from Lynx to review approved parts or other details. This ensures you have the necessary information to proceed.