The Follett EDI integration exchanges EDI files with your drop-ship vendors through an SFTP server. The app sends shipping requests as purchase order files (850) and reads acknowledgments (855), ship notices (856), and inventory (846) back into Pipe17. It can also add store details to vendor invoices (810), and it keeps a product catalog that translates your SKUs into the identifiers your vendors use.
Setup
Before you begin
- Make sure the Follett EDI integration is available in your account. If you don't see the tile, contact Pipe17 support to enable it.
- Get the SFTP server details from your EDI provider or trading partner setup: host, port, username, and a password or private key.
- Agree on the folder structure with your EDI provider. You need at least an inbound folder (files for Pipe17) and an outbound folder (files from Pipe17).
- Confirm which EDI documents each vendor exchanges: 850 purchase orders, 855 acknowledgments, 856 ship notices, 846 inventory, and 810 invoices.
- Collect the ID each vendor uses in its files (for example, a vendor code such as
ABCor the sender ID in its 846 files). You enter these as locations. - Ask your EDI provider for the product catalog file. It's a CSV file with a header row that lists your SKUs and their vendor identifiers (UPC, ISBN, and similar).
- You can add only one Follett EDI integration per organization.
Prepare your SFTP server
- Create the folders the app uses. For example:
-
/inbound: your vendors' 855, 856, 846, and 810 files. -
/outbound: 850 files and updated 810 files from Pipe17. -
/catalog: product catalog files (optional). -
/catalog-export: the nightly product catalog export (optional). - A separate inbound and outbound folder for 810 invoices (optional).
-
- Give the SFTP user read, write, update (rename), and delete permissions on these folders.
- Test the account with an SFTP client. Create a folder, upload a file, download it, rename it, and delete it.
- Decide how the app signs in:
- Password: use the SFTP user's password.
-
SFTP key: generate a key pair with an SSH tool (for example,
ssh-keygen). Upload the public key to the SFTP server, usually into~/.ssh/authorized_keys. You paste the private key into the app.
Note: The app removes each file from the inbound folders after it downloads it. This includes files it doesn't recognize. Don't share these folders with other systems.
Connect in the app
- Navigate to Integrations and click Add integration.
- Search for Follett EDI and select it. The Connect Follett EDI pop-up opens.
- Enter the connection details:
- Host: the SFTP host name or IP address, without the protocol.
- Port (optional): the SFTP port. Leave it empty to use 22.
- Username: the SFTP user.
-
Password/Key: the password or the private key. Paste the whole key, including the first line (
-----BEGIN ...-----) and the last line (-----END ...-----). The app uses these lines to tell a key from a password. - Inbound path: the folder the app downloads incoming files from.
- Outbound path: the folder the app uploads generated files to.
- Click Connect.
Note: If you click Add without credentials, the app adds the integration but doesn't sync. Enter the credentials later on the Connection Details tab and save. You turn on the flows later on the Settings tab.
Confirm the connection
- Open the integration. Check that the status is Connected.
- On the Settings tab, add your vendors under Specify locations (warehouses) as ID:NAME pairs and save. Within about 5 minutes, the new locations appear in your locations list.
- Make sure your order routing sends a test order to one of these locations. See Creating Order Routing Rules.
- In Process only shipping requests with specific order IDs., enter the external order ID of the test order.
- Turn on Push shipping requests to the remote system and save.
- Wait about 5 minutes. Open the order's shipping request. Its status changes to Sent to fulfillment, and an 850 file appears in the outbound folder.
- When the test works, clear Process only shipping requests with specific order IDs. and save. Otherwise the app sends only that order.
How the EDI flow works
The app checks the SFTP server and Pipe17 about every 5 minutes. It picks the document type from the file name. The name must contain 810, 846, 855, or 856 (for example, ABC846IN_0001.txt or order.856). The app also treats file names that contain "inventory" as 846 files.
| Document | Direction | What the app does |
|---|---|---|
| Locations | Settings to Pipe17 | Creates one location per ID:NAME pair, plus one default location named after the integration. |
| 850 Purchase order | Pipe17 to SFTP | Writes one file per shipping request to the outbound folder. |
| 855 Acknowledgment | SFTP to Pipe17 | Marks the shipping request as sent to fulfillment, cancels it, or rejects some of its lines. |
| 856 Ship notice | SFTP to Pipe17 | Creates one fulfillment per package, with the tracking number and carrier. |
| 846 Inventory | SFTP to Pipe17 | Updates inventory at the vendor's location. |
| 810 Invoice | SFTP to SFTP | Adds store details to each invoice and uploads the updated file. |
| Product catalog (CSV) | SFTP to Pipe17 | Stores your SKUs and their vendor identifiers for this integration. |
| Product catalog export (ZIP) | Pipe17 to SFTP | Uploads the stored product catalog once a day or on demand. |
Locations
Your vendors don't send location data, so you list them in Specify locations (warehouses) as ID:NAME pairs. ID is the vendor's ID in its EDI files. NAME is the location name in Pipe17. For example, ABC:Vendor ABC. The app creates each location once. Editing a NAME later doesn't rename the location. Edit it on the locations page instead. See Using Locations and Merging Locations.
Shipping requests (850)
- The app sends shipping requests with the status Ready for fulfillment that are routed to this integration's locations.
- The 850 is a fixed-width text file. Its name is
OMS_850_followed by the shipping request's external shipment ID. - The PO number in the file is the shipping request's external shipment ID. The app saves it as the shipping request's reference and uses it to match the 855, 856, and 810 files that come back. Keep this ID unique.
- The file identifies the vendor by the location's Company (in its address) or, if that's empty, by the location name.
- Line items use the vendor identifier from the product catalog (vendor part, UPC, or full ISBN) when one exists. Otherwise they use the SKU.
- After the upload, the status changes to Sent to fulfillment. If the upload fails, the status changes to Failed.
- The app sends each shipping request once. To change the file content, see Customizing mappings in Pipe17.
Acknowledgments (855)
The app reads 855 files when Push shipping requests to the remote system is on. It matches each 855 to a shipping request by PO number, then by order ID.
- Accepted: if Don't mark shipping requests as 'sent to fulfillment' until an acknowledgment file is received from the remote system is on, the status changes to Sent to fulfillment now. If the setting is off, the status already changed when the 850 was sent.
- Rejected (the whole order): the app cancels the shipping request.
- Some lines rejected (line status R4 or IR): the app adds a rejected fulfillment for those lines only. The rest of the shipping request stays open.
- If a rejected line doesn't match any line on the shipping request, the app doesn't apply it. It raises an exception on the shipping request instead. See Event Logs and Exceptions.
Ship notices (856)
- The app matches each 856 to a shipping request by PO number, then by order ID.
- It creates one fulfillment per package. Each fulfillment gets the package's tracking number, the carrier, the ship date, and the package's items.
- A package needs a tracking number. The app skips packages without one and packages whose tracking number already has a fulfillment.
- If the 856 has no carrier, the carrier is "Unknown".
- The app matches 856 lines to shipping request lines by line number, SKU, or vendor identifier.
Inventory (846)
- The app reads 846 files when Pull inventory from the remote system is on. It accepts X12 846 files and some CSV inventory layouts.
- It finds each item's SKU through the product catalog. Items that aren't in the catalog are skipped.
- It picks the location in this order: the sender ID in the file, the vendor code before
846INin the file name (for example,ABCinABC846IN_0001.txt), then the default location. - The quantity in the file becomes the on-hand and available quantity. If a SKU appears twice in a file, the last line wins.
- If the product catalog marks a product as unavailable or purged, the app skips its inventory and sets it to 0 at this integration's locations. When the product is available again, the app restores the last quantity it received.
- Track missed zero quantities for files with the following prefixes: some vendors send only the SKUs they have in stock. For files whose name starts with one of these prefixes, the app compares the file with the previous file that has the same prefix. SKUs that were in the previous file but are missing from the new one get quantity 0. The first file with a prefix only sets the starting list.
Invoices (810)
- The app processes 810 files when Process invoices is on and the file name starts with one of the prefixes in Process invoices from vendors with the following file name prefixes.
- It matches each invoice to a shipping request by PO number, then by external shipment ID, then by order ID.
- It adds the store's SAN, name, and address. The store is the location in the shipping request's
OrigStoreLocationcustom field. - It uploads the updated file, with the same file name, to the outbound path or to Outbound path for 810 invoices (optional).
- Invoices that don't match a shipping request are left out of the updated file. If any invoice in a file has no store location, the app doesn't upload that file.
- The app doesn't create invoice records in Pipe17.
Product catalog
- The app downloads catalog files from Product catalog path. Leave the path empty to skip the catalog.
- Each file is a CSV with a header row. The app stores the products for this integration only. It doesn't create products in Pipe17.
- Later files update the stored products. The catalog is used for 850 line items and to find SKUs in 855, 856, and 846 files.
- With Nightly export product catalog on, the app uploads the full stored catalog once a day as a ZIP archive with one CSV file. It goes to Product catalog export path.
- To export now, run the Export product catalog to file action on the integration.
Settings
You enter the connection settings in the pop-up or on the Connection Details tab. You find the other settings on the Settings tab.
Connection
| Setting | What it does | Default |
|---|---|---|
| Host | SFTP host name or IP address, without the protocol. | Empty |
| Port (optional) | SFTP port. | 22 |
| Username | SFTP user. Needs read, write, update, and delete permissions. | Empty |
| Password/Key | Password or private key for the SFTP user. | Empty |
| Inbound path | Folder for incoming 855, 856, 846, and 810 files. | A preset folder. Change it to match your server. |
| Outbound path | Folder for 850 files and updated 810 files. | A preset folder. Change it to match your server. |
Product catalog
| Setting | What it does | Default |
|---|---|---|
| Product catalog path | Folder for product catalog files. Leave it empty to skip catalog sync. | A preset folder |
| Nightly export product catalog | Uploads the full stored catalog as a ZIP archive once a day. | Off |
| Product catalog export path | Folder for the export archive. | A preset folder |
| Timestamp the packed file name | On: the CSV in the archive is named products-<timestamp>.csv. Off: products.csv. |
On |
| Timestamp the archive name | On: the archive is named products-<timestamp>.zip. Off: products.zip, and each export overwrites the last one. |
On |
Locations
| Setting | What it does | Default |
|---|---|---|
| Pull locations | Creates locations from the ID:NAME pairs and a default location. | On |
| Specify locations (warehouses) as ID:NAME pairs | One entry per vendor. ID is the vendor's ID in its files. NAME is the location name in Pipe17. | Empty |
Inventory
| Setting | What it does | Default |
|---|---|---|
| Pull inventory from the remote system | Reads 846 files and updates inventory. | Off |
| Process only inventory items with matched SKUs (regex) | Not applied in the current version. Leave it empty. | Empty |
| Track missed zero quantities for files with the following prefixes | For files whose name starts with one of these prefixes, SKUs missing from the new file get quantity 0. | One preset prefix. Check it with your EDI provider. |
Shipping requests
| Setting | What it does | Default |
|---|---|---|
| Push shipping requests to the remote system | Sends 850 files and reads 855 files. | Off |
| Process only shipping requests with specific order IDs. | Sends only shipping requests for these external order IDs. Use it for testing. Leave it empty to send all. | Empty |
| Don't mark shipping requests as 'sent to fulfillment' until an acknowledgment file is received from the remote system | On: the status changes to Sent to fulfillment when an accepting 855 arrives. Off: it changes as soon as the 850 is uploaded. | Off |
Invoices
| Setting | What it does | Default |
|---|---|---|
| Process invoices | Adds store details to 810 invoices and uploads them back. | Off |
| Process invoices from vendors with the following file name prefixes | The app processes only 810 files whose name starts with one of these prefixes. | One preset prefix. Check it with your EDI provider. |
| Inbound path for 810 invoices (optional) | Separate folder for incoming 810 files. Leave it empty to use the inbound path. | Empty |
| Outbound path for 810 invoices (optional) | Separate folder for updated 810 files. Leave it empty to use the outbound path. | Empty |
Fulfillments
| Setting | What it does | Default |
|---|---|---|
| Pull fulfillments from the remote system | Reads 856 files and creates fulfillments. | Off |
File locations and naming
| File | Folder | Name |
|---|---|---|
| 855, 856, 846 | Inbound path | Contains 855, 856, or 846 (or "inventory" for 846) |
| 810 (incoming) | Inbound path for 810 invoices (optional) or Inbound path | Starts with an invoice prefix and contains 810
|
| 850 | Outbound path |
OMS_850_ plus the external shipment ID |
| 810 (updated) | Outbound path for 810 invoices (optional) or Outbound path | Same name as the incoming file |
| Product catalog | Product catalog path | Any CSV file with a header row |
| Catalog export | Product catalog export path |
products-<timestamp>.zip or products.zip
|
The app removes each file from the inbound and catalog folders after it downloads it. If a file's type isn't recognized, or its flow is off, the app still removes it and doesn't process it.
Troubleshooting
-
The integration status is Error.
The app couldn't reach the SFTP server for about 2 hours. Check the host, port, username, password or key, and firewall rules. Update them on the Connection Details tab and save. -
The private key isn't accepted.
The key is missing its first or last line. Paste the whole key, from-----BEGIN ...-----to-----END ...-----. -
Files disappear from the inbound folder, but nothing changes in Pipe17.
The file name doesn't contain the document number, or the flow for that document is off. The app removes these files without processing them. Fix the file name or turn on the flow, then ask your vendor to resend the file. -
A shipping request isn't sent.
The shipping request must be Ready for fulfillment and routed to one of this integration's locations. Also check Process only shipping requests with specific order IDs.. The app doesn't send a shipping request that it already sent. -
A shipping request has the status Failed.
The 850 upload failed. Check that the outbound folder exists and that the SFTP user can write to it. -
A shipping request stays Ready for fulfillment after the 850 is sent.
Don't mark shipping requests as 'sent to fulfillment' until an acknowledgment file is received from the remote system is on, and no matching 855 arrived. Check that the vendor sent the 855 with the PO number from the 850. -
An 855 or 856 isn't applied.
The PO number doesn't match a shipping request, or several open shipping requests share the same order ID. Make sure each shipping request has a unique external shipment ID. -
An exception says the 855 rejects lines that match no line of the shipping request.
The vendor rejected an item that isn't on the shipping request. The app didn't apply the rejection. Check the item with the vendor and update the shipping request manually. -
A package from an 856 has no fulfillment.
The package has no tracking number, or a fulfillment with that tracking number already exists. Ask the vendor to send a tracking number for each package. -
Inventory isn't updated for a SKU.
The SKU isn't in the product catalog, or the catalog marks it as unavailable. Check the latest catalog file. -
Inventory lands on the default location.
The sender ID or vendor code in the 846 doesn't match an ID in Specify locations (warehouses) as ID:NAME pairs. Add or fix the pair. -
A SKU's inventory drops to 0 unexpectedly.
The file name starts with a prefix in Track missed zero quantities for files with the following prefixes, and the SKU was missing from the latest file. Remove the prefix if this vendor sends partial files. -
An updated 810 file isn't uploaded.
An invoice in the file points to a shipping request without a store location in itsOrigStoreLocationcustom field, or that location isn't active. The app skips the whole file. Fix the shipping request and ask the vendor to resend the file. -
A large product catalog file isn't imported.
The app skips catalog files of 15 MB or more by default. Contact Pipe17 support to allow large files. -
A location name didn't change after you edited the ID:NAME pair.
The app creates each location once and doesn't update it. Rename the location on the locations page.
Need Help?
If you need additional assistance:
- Use Ask Pippen, our AI agent, located at the top of the platform page.
- Submit a support request with as much relevant detail as possible. Learn how to submit a request.
We’re here to help you succeed with your operations.
Comments
0 comments