The Email Shipping Labels connector emails the shipping labels on a shipping request to the location that ships it, for example a warehouse or supplier that prints the labels and packs the order. It only sends email. Pipe17 doesn't read replies and doesn't change the shipping request status.
Note: To email the full shipping request (items, address and shipping method) and move it to Sent To Fulfillment, use the separate Email Fulfillment tile. See Connect Email Fulfillment to Pipe17. This article covers the Email Shipping Labels tile.
Setup
Before you begin
- The Email Shipping Labels tile has limited availability. Contact Pipe17 support to have it enabled for your organization.
- Shipping requests that reach Sent To Fulfillment status with shipping labels attached. Another integration sends the shipping request to fulfillment, and the labels come from a shipping label integration or the API. This connector doesn't create labels.
- The email address that should receive the labels, used as Default Recipient Email address. Pipe17 doesn't need a login or credentials for it.
- Optional: a different recipient for some locations. A location's email can't be set on the location page in the app. It's set through the Pipe17 API, or by Pipe17 support.
- A mailbox you monitor for replies, to use as the Reply To Email address.
- Only one Email Shipping Labels integration per organization.
Prepare locations and recipients
- Choose the address that should receive the labels, for example your warehouse's inbox. You enter it as Default Recipient Email address. It's used for every shipping request whose location has no email of its own.
- Optional: if some locations need a different recipient, set the email on each location's address. The location page in the app (Inventory > Locations) has no email field. Set
address.emailon the location with the Pipe17 API (Update Location), or contact Pipe17 support to set it. The location must be active. See Using Locations. - Choose any addresses that should get a copy of every label email, for example your operations inbox. You enter them as CC Email address(es).
- Decide which address receives replies. Without a Reply To Email address, replies go to a Pipe17 no-reply address and nobody reads them.
- Check that your shipping requests have their labels in the Shipping Labels section by the time they reach Sent To Fulfillment. PDF, PNG and JPG labels are attached with the matching file extension. See Shipping Requests in Pipe17.
- Decide which shipping requests should get label emails. By default, the connector emails labels for every shipping request in Sent To Fulfillment status that has labels, from any location and any fulfillment integration. To limit this, use the Fulfillment Integration ID or Order Source filters in the settings.
- Tell the recipients which address the emails come from. The email is sent through Pipe17 from your Merchant Support Email, or your organization contact email if that setting is empty. Ask the recipients to allow it so the emails don't land in spam.
Connect in the app
- Navigate to Integrations in the app and click Add integration.
- Search for Email Shipping Labels and select it. The tile shows Limited availability. If you can't select it, contact Pipe17 support.
- The Connect Email Shipping Labels pop-up opens.
- In Default Recipient Email address, enter the address that should receive the labels. It's used for every shipping request whose location has no email of its own.
- In CC Email address(es), enter each address that should get a copy. Leave it empty if you don't need copies.
- In Reply To Email address, enter the mailbox that should receive replies.
- Click Connect.
Note: If you don't have the addresses yet, click Add without credentials. Enter them later on the Connection Details tab and click Save. Push shipping labels is off when you add the integration. Don't turn it on until a recipient is set. With no recipient, no email is sent for that shipping request.
Confirm the connection
- On Integrations, check that the Email Shipping Labels integration shows Connected and that its switch is on.
- Pick one test order whose shipping request has a shipping label, is in Sent To Fulfillment status, and ships from a location without its own email, so the label goes to the Default Recipient Email address.
- On the integration's Settings tab, enter the exact order ID in Process only shipping requests with specific order IDs (regex). Turn on Push shipping labels and click Save.
- Wait about 5 minutes. The app checks for shipping requests every 5 minutes. Check that the recipient got the email with the labels attached, and that any CC addresses got a copy. The shipping request stays in Sent To Fulfillment. This connector doesn't change its status.
- If you don't want labels emailed for every shipping request in Sent To Fulfillment, set Process only shipping requests with specific Fulfillment Integration IDs or Process only shipping requests with specific Order Sources (regex) first.
- Remove the order ID from Process only shipping requests with specific order IDs (regex) and click Save.
Supported flows
| Shipping labels (Pipe17 to email) | Every 5 minutes, the app finds shipping requests in Sent To Fulfillment status that have shipping labels and match the filters. For each one, it sends one email with the labels attached:
|
The connector doesn't create locations, doesn't send cancellations, and doesn't pull tracking numbers back.
How it differs from Email Fulfillment
| Email Shipping Labels | Emails the labels of shipping requests already in Sent To Fulfillment, from any location. The recipient is the default recipient, or the location's own email if one is set. The status doesn't change. If the email can't be sent, the status still doesn't change. |
| Email Fulfillment | Emails the shipping request itself (items, address, shipping method) for shipping requests in Ready for Fulfillment at its own location, to fixed recipients, and moves them to Sent To Fulfillment or Failed. It can also attach labels and send cancellation emails. |
Settings
Flows
On the integration's Settings tab.
| Push shipping labels | Sends the shipping labels by email, every 5 minutes, for shipping requests in Sent To Fulfillment status. Default: off. |
Shipping labels
| Process only shipping requests with specific order IDs (regex) | Sends emails only for the order IDs you enter. Use it for testing, then clear it. Enter the exact order ID. Matching ignores case. |
| Process only shipping requests with specific Fulfillment Integration IDs | Sends emails only for shipping requests sent to fulfillment by the integrations whose IDs you enter. Empty: all integrations. |
| Process only shipping requests with specific Order Sources (regex) | Sends emails only for shipping requests from the order sources you enter. Enter the source name, or a pattern between slashes, for example /^shopify/. Matching ignores case. Empty: all order sources. |
| Merchant Name | The value of {{merchantName}} in the templates. If empty, the organization name in Pipe17 is used. |
| Merchant Support Email | The value of {{merchantEmail}} in the templates. The email is also sent from this address. If empty, the organization contact email in Pipe17 is used. |
| Merchant Support Phone Number | The value of {{merchantPhone}} in the templates. If empty, the organization contact phone in Pipe17 is used. |
| Email subject template | Subject of the label email. Default: Shipping Labels for Order {{extOrderId}} for {{merchantName}}. If empty, the default is used. |
| Email body template | HTML body of the label email. If empty, the default body is used. |
Email templates
The subject and body templates use Handlebars syntax: put a field name in double curly braces, for example {{extOrderId}}. Field names are case-sensitive. You can use the fields of the shipping request (the setting's help text links to the full list in the Pipe17 API reference) and the three merchant fields.
The default body has:
- The Pipe17 shipping request ID, the order number and the shipping request number.
- The shipping address, including email and phone when the order has them.
- The shipping method and the shipping note, when the order has them.
- A line saying your merchant name asks the recipient to ship the order with the attached labels, and to contact your merchant support email if they got it in error.
Unlike Email Fulfillment, the default body doesn't list line items. Fields used by the default templates:
{{extOrderId}} |
Order number |
{{extShipmentId}} |
Shipping request number |
{{shipmentId}} |
Pipe17 shipping request ID |
{{shippingAddress.firstName}}, {{shippingAddress.lastName}}, {{shippingAddress.address1}}, {{shippingAddress.address2}}, {{shippingAddress.city}}, {{shippingAddress.stateOrProvince}}, {{shippingAddress.zipCodeOrPostalCode}}, {{shippingAddress.country}}, {{shippingAddress.email}}, {{shippingAddress.phone}}
|
Shipping address |
{{shippingCode}} |
Shipping method |
{{shippingNote}} |
Shipping note |
{{merchantName}}, {{merchantEmail}}, {{merchantPhone}}
|
Merchant fields from the settings |
To go back to the default subject or body, clear the template field and click Save.
Troubleshooting
- No email is sent for a shipping request.
Check that Push shipping labels is on, that the shipping request is in Sent To Fulfillment status and has a label in Shipping Labels, and that the three Process only shipping requests filters are empty or include it. Each shipping request is emailed only once, so a shipping request that already got the email is skipped. - No email is sent, and no recipient is set.
Default Recipient Email address may be empty, and the location has no email of its own. The app has no recipient and sends nothing. Enter a default recipient on the Connection Details tab and click Save. - The email goes to the default recipient instead of a location's own address.
The location's email is used first, but only if the location is active andaddress.emailis set on it. The location page in the app doesn't show this field. Check it with the Pipe17 API (Update Location), or contact Pipe17 support. - No email is sent, and the shipping request status didn't change to Failed.
That's expected. If a label can't be loaded or the email can't be sent, this connector sends nothing and leaves the status as it is. Check that the label opens on the shipping request. If it does, contact Pipe17 support. - The email is in spam, or doesn't arrive.
The email is sent through Pipe17 from your Merchant Support Email or organization contact email. Ask the recipient to check spam and to allow that address. Delivery isn't guaranteed. - Replies to the email don't reach you.
Reply To Email address is empty, so replies go to a Pipe17 no-reply address. Enter your mailbox on the Connection Details tab and click Save. - The order ID filter doesn't pick up the test order.
Enter the exact order ID in Process only shipping requests with specific order IDs (regex), not a pattern. - Labels are emailed for shipping requests you didn't expect.
The connector emails every shipping request in Sent To Fulfillment that has labels. Limit it with Process only shipping requests with specific Fulfillment Integration IDs or Process only shipping requests with specific Order Sources (regex). - A template field shows up empty in the email.
Check the field name and its case, for example{{extOrderId}}, not{{extorderid}}. Fields that the order doesn't have stay empty. - The recipient needs the item list and address in the same email as the labels.
Use Email Fulfillment with Include shipping labels as attachments instead. See Connect Email Fulfillment to Pipe17.
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