The Orderful EDI 3PL connector links the app to a third-party logistics (3PL) warehouse that exchanges EDI documents through Orderful. The app sends warehouse shipping orders (940) to your 3PL. The 3PL sends back shipping advices (945) and inventory advices (846). The connector uses Orderful's Mosaic format, so one setup works with any 3PL partner and needs no partner-specific configuration.
With this connector, you can:
- Send shipping requests to your 3PL as EDI 940 warehouse shipping orders, including cancellations.
- Create fulfillments with carrier and tracking details from your 3PL's EDI 945 shipping advices.
- Update on-hand and available inventory from your 3PL's EDI 846 inventory advices.
- Create 3PL warehouse locations from your connector settings.
- Pull fulfillments again on demand by order ID or by date range.
Setup
Before you begin, make sure you have:
- An Orderful account with permission to create API credentials and communication channels.
- An active trading relationship in Orderful with your 3PL for 940 (outbound), 945 (inbound) and 846 (inbound).
- Your ISA ID and your 3PL's ISA ID.
- A decision on which document stream to use: Test for sandbox or certification, or Live for production.
Configure Orderful
- Sign in to Orderful and go to Settings > API credentials.
- Create an API token and copy it.
- Create a communication channel of type Inbound Poller and set its format to Mosaic.
- Route only your 3PL's 945 documents to this poller channel.
- Copy the poller bucket ID.
Connect the app
- In the app, go to Integrations and add the Orderful EDI 3PL connector.
- Open the Connection Details tab.
- Select your Orderful environment: Production (default) or Sandbox.
- Enter your Orderful token in API Token.
- Enter the bucket ID from step 5 in Poller bucket ID (Mosaic — fulfillments).
- Enter your ISA ID in Your ISA ID.
- Enter your 3PL's ISA ID in Partner ISA ID.
- Select the Documents stream: Live (default) or Test.
- Save your changes.
Set up locations and flows
- Open the Settings tab.
- Enter your 3PL warehouse in Locations in the format
ISAID:Location Name, one location per line. - Turn on the Locations switch under Connection Flow and save your changes.
- Wait for the next run, then copy the ID of the new location.
- Paste the location ID into Location ID for inbound inventory (846).
- Turn on the switches under Connection Flow for each flow you want to use: Shipping Requests (940), Fulfillments (945) and Inventory (846).
- Save your changes.
Each time the connector runs, it checks your Orderful token. If the token is invalid, the integration stops with an authentication error.
Settings
| Setting | Description | Options/Default |
|---|---|---|
| Select Orderful environment | The Orderful environment the connector connects to. | Production (default), Sandbox |
| API Token | Your Orderful API token. Required. | — |
| Poller bucket ID (Mosaic — fulfillments) | The Orderful Inbound Poller bucket that receives 945 documents. Required when the Fulfillments flow is on. | — |
| Poller bucket ID (EDI — inventory 846) | Optional. The connector reads 846 documents from the Orderful transactions API by ISA ID and stream. | Empty |
| Your ISA ID | Your ISA ID. It's the sender on 940s and the receiver on 945s and 846s. Required. | — |
| Partner ISA ID | Your 3PL's ISA ID. Required. | — |
| Documents stream | The Orderful stream the connector sends and reads documents on. | Live (default), Test |
| Connection Flow | One switch for each flow: Shipping Requests (940), Inventory (846), Fulfillments (945) and Locations. | Off until turned on |
| Push shipping requests only for specific status | The shipment statuses that the app sends as 940s. To send cancellations, add canceled and canceledRestock. |
readyForFulfillment |
| Exclude fulfillments created before this date | The earliest date for 945 fulfillment pulls. | Empty |
| Process only inventory items with specific SKUs | A list of SKUs to include from 846 documents. When empty, the app processes all SKUs. | Empty (all SKUs) |
| Location ID for inbound inventory (846) | The location in the app that receives every 846 inventory line. Required for the Inventory flow. | — |
| Locations | The 3PL locations to create in the app, one per line, in the format ISAID:Location Name. |
Empty |
You can review and edit how fields map between the app and Orderful on the Mappings tab for Shipping Requests, Fulfillments, Inventory and Locations.
Flows
| Flow | Direction | Notes |
|---|---|---|
| Shipping requests (EDI 940) | Pipe17 → Orderful | Runs every 5 minutes. Sends shipments that match the status filter. Canceled shipments go out as a 940 with purpose cancel. A 4xx error from Orderful marks the shipment as failed. A 5xx error is retried on the next run. |
| Fulfillments (EDI 945) | Orderful → Pipe17 | Reads up to 100 documents from the poller bucket per run. Matches each 945 to a shipment by shipping order number first, then by purchase order number. Unmatched 945s are skipped. Duplicate fulfillments are skipped. Pallet and carton structures become flat line items. |
| Inventory (EDI 846) | Orderful → Pipe17 | Updates on-hand and available quantities at the location set in Location ID for inbound inventory (846). The next scan runs 1, 4, 8 or 12 hours later, depending on how long the last scan took. |
| Locations | Settings → Pipe17 | Creates locations from the Locations setting. Doesn't call Orderful. Locations that already exist are skipped. |
Advance shipping notices (EDI 856) aren't supported. You can also pull fulfillments on demand from the Actions menu, by Order ID or by date (a start time plus a 1–24 hour window). On-demand pulls don't change where the scheduled pulls resume.
Troubleshooting
-
The integration stops with an authentication error
Your Orderful API token is invalid, expired, or for a different environment. Create a new token in Orderful, enter it in API Token, and check that Select Orderful environment matches where you created it. -
The integration fails to start after you turn on Fulfillments (945)
Poller bucket ID (Mosaic — fulfillments) is empty. Enter the bucket ID from your Orderful Inbound Poller channel and save your changes. -
Your 3PL sent a 945, but no fulfillment appears in the app
The 945 didn't match a shipment, so the app skipped it. Make sure the 3PL returns the 940's supplier order number (your external shipment ID, or the external order ID if there's no shipment ID) as the shipping order number on the 945. -
Documents disappear from the Orderful poller bucket without being processed
Document types other than 945 are routed to the Mosaic poller bucket. The connector approves every document it reads, including types it ignores, so they're removed from the bucket. Update your Orderful channel so that only 945s go to this bucket. -
Inventory doesn't update every 5 minutes
This is expected. The 846 scan reschedules itself every 1 to 12 hours based on how long the last scan took. If inventory never updates, check that Location ID for inbound inventory (846) is set and that your SKU filter includes the affected SKUs.
Need Help?
If you need additional assistance:
- Use Ask Pippen, our AI agent, located at the top of the app 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