> ## Documentation Index
> Fetch the complete documentation index at: https://help.owlery.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# EDI Onboarding

> Configure your carrier EDI connection, generate SFTP credentials, complete testing, and request production activation.

You set up and test your EDI connection yourself in Owlery, then contact Support when you're ready for production activation.

## Set Up Your Connection

**Where to find it:** `Dashboard → EDI Test`

<Steps>
  <Step title="Choose the Shipper">
    Select the shipper under **Owlery EDI Connection**.

    If the shipper is not listed or its ISA configuration is missing, EDI isn't enabled for that shipper yet. Ask your contact at the shipper to email [support@owlery.ai](mailto:support@owlery.ai) and request EDI enablement. The request must come from the shipper, not from you. You can start testing once it's enabled.
  </Step>

  <Step title="Configure Your Carrier ISA ID">
    Under **Carrier EDI Connection**, click **Configure ISA ID**.

    Enter your **ISA Qualifier** and **ISA ID**, then click **Save**. You can return here and click **Edit** if either value changes.
  </Step>

  <Step title="Generate SFTP Credentials">
    Under **SFTP Setup**, choose **Password** or **Public Key**, then click **Generate Credentials**.

    Save the connection details shown in Owlery. If password credentials already exist, you can click **Get 1Password Share Link** to retrieve them securely.
  </Step>

  <Step title="Configure Your Translator">
    Use the connection details and directory structure shown in **EDI Test** to connect your translator.

    Before you connect, check these settings:

    * **File names**: Every file you put in `inbound/` must end in `.edi`, for example `my_990.edi`.
    * **Owlery's ID**: Owlery uses a separate ISA ID for each shipper. Use the ID shown under **Owlery EDI Connection** for that shipper, and use the same value in the GS segment. The ID is the same for test and production.
    * **Test and production**: One SFTP account handles both. Set ISA15 to `T` for test or `P` for production. There's no separate production account or directory.
    * **Acknowledgements**: Owlery puts a 997 in `outbound/` for every file you send. Send a 997 back for every 204 you receive. This lets the shipper see that you received the tender before you accept or reject it.
      Follow the [EDI Guidelines](https://owlery.ai/open/edi-guidelines) for transaction requirements, file handling, identifiers, acknowledgements, and test-versus-production rules.
  </Step>
</Steps>

<Note>
  Missing carrier ISA or SFTP setup does not require Support. Complete those items directly in **EDI Test**.
</Note>

## Complete Guided Testing

**Where to find it:** `Dashboard → EDI Test → Test Plans`

<Steps>
  <Step title="Start a Test Plan">
    Choose the shipper and click **Start Test** for the required plan.

    If **Start Test** is unavailable, follow the message shown in Owlery. It tells you whether you can fix the issue yourself or the shipper needs to request EDI enablement. See [Choose the Shipper](#set-up-your-connection) for how the shipper requests it.
  </Step>

  <Step title="Follow the Active Step">
    Owlery shows the current test action, load, and sample for each step. Complete only the active step.
  </Step>

  <Step title="Review Validation Results">
    The Owlery platform validates each transaction automatically as soon as you send it. You don't need to wait on the Owlery team. When a step passes, the test moves to the next step right away. If a step fails, Owlery shows the result and a correction hint. Update your transaction and retry the step.
  </Step>

  <Step title="Complete Every Required Plan">
    Continue until each required plan shows **Passed**.
  </Step>
</Steps>

Use the [EDI Guidelines](https://owlery.ai/open/edi-guidelines) as the source of truth for transaction structure and field-level requirements.

## Request Production Activation

After every required test plan passes, email [support@owlery.ai](mailto:support@owlery.ai) to request production activation. The Owlery team verifies the connection and enables live EDI for the carrier-to-shipper relationship.

You continue using the connection credentials created in **EDI Test**. Follow the [EDI Guidelines](https://owlery.ai/open/edi-guidelines) for the production transaction requirements.

<Warning>
  Do not send live EDI until the Owlery team confirms that the connection is enabled for production.
</Warning>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.