EDI login test failed
Orders wait safely while the login fails. Re-enter your EDI username and password in Settings and select Test and save. If an order shows Problem, check EJD's portal before sending it again.
EDI is how the app sends your orders to EJD as files, and reads EJD's replies (see the glossary). It needs its own login to EJD's EDI server.
This article covers two alerts: the login test failed (EDI_LOGIN_FAILED), or an order didn't finish sending (EDI_UPLOAD_FAILED).
EDI_LOGIN_FAILED
The app couldn't log in to EJD's EDI server with the details you entered. Your details are saved, but the login shows Not connected. No orders are sent and no EJD replies are read until a test passes. Orders that come in meanwhile wait, and are sent once it works.
Your login is in Settings > EJD EDI login.
- Check the SFTP username. It's case-sensitive. Copy it exactly from EJD.
- Enter the SFTP password again. Watch for spaces at the start or end when you paste. If you leave it blank, the app keeps the saved one.
- Check the Trading partner ID matches the one EJD gave you.
- Sending to EJD doesn't affect the test: the test only lists folders and sends nothing.
- Ask EJD whether your EDI setup is complete. A login can exist before EJD finishes setting up your account.
- If you recently changed the password with EJD, enter the new one.
- Select Test and save again. The banner shows Connected when it works.
When the test passes, any orders that were waiting for the login are sent.
You can test 5 times an hour. After that the app says "That's 5 login tests in the last hour". Check the details with EJD, then try again an hour later.
"EJD's EDI server couldn't be found" or "refused the connection"
The app couldn't reach EJD's server at all. Your username and password weren't checked, so changing them won't help. EJD's server may be down, or there's a network problem. Try again in a few minutes. If it keeps happening, contact support.
"identified itself with a different key than before"
EJD's EDI server answered with a different identity key than the one the app saved the first time it connected. The app stopped without sending your password, because a different key is also what a server pretending to be EJD's would show. Nothing can be sent or read until it's sorted out. You can't fix this in Settings: contact support. Support checks with EJD that the key changed, then accepts the new key for you.
EDI_UPLOAD_FAILED
The app started sending an order to EJD but couldn't finish. It may or may not have reached EJD. The order's status is Problem and it's tagged EJD-Problem. The app doesn't retry by itself, because sending it twice could make EJD ship and bill it twice.
- Open the order in the app. The problem says what went wrong.
- Check EJD's portal for the order's PO number, or ask EJD whether they got it.
- If EJD has it, do nothing more. Don't send it again. When EJD's acknowledgement, ship notice or invoice for the PO arrives, the app marks the order sent and the problem and its alert clear.
- If EJD confirms they never got it, select EJD confirmed they didn't get it on the order, and confirm. The order goes back to Ready to send. (If the order was cancelled in Shopify meanwhile, it's closed instead.)
- If the failure was a login problem, fix it in Settings > EJD EDI login and select Test and save.
- Select Check again to re-run the order checks, then Send to EJD.
Check again isn't offered on a Problem order until step 4, because re-checking can't tell whether EJD got it. Only EJD can.
When nothing was uploaded
If the app could tell nothing reached EJD (it couldn't reach EJD's Inbound folder before uploading), the order isn't a Problem. It stays Sending soon and the app tries again by itself. You don't need to do anything.
Still failing?
Contact support with the time of the test and the message the app showed. Never send us your password.
Technical details
Show the exact rules, for the technically minded
- The login test connects to EJD's EDI server over SFTP and only lists its folders. Nothing is downloaded, moved or deleted.
- The first successful connection saves the server's identity key (its SHA-256 fingerprint). Every later connection must show the same key, or the app stops before sending the password.
- Tests are limited to 5 an hour per store, because every test reaches EJD's server from the app's one shared address.
- A send has a control number from the moment it starts. While a send with a control number hasn't been confirmed by an 855, 856 or 810 from EJD, it can't be re-checked or resent until someone selects EJD confirmed they didn't get it. That clears the control number, and a new one is used for the next send.