Sign In
Book a Demo

EasyPost Integration for Rates and Labels

The EasyPost integration puts EasyPost’s shipping API behind Pipe17’s label requests. When a packer asks for labels, Pipe17 shows EasyPost’s carrier rates per carton, buys the one picked, and stores the label and tracking number.
Book a demo
EasyPost logo tile for the Pipe17 EasyPost integration

The Solution for EasyPost Integration & Carrier Labels

EasyPost Prices the Carriers and Issues the Label. Pipe17 Settles the Location and Buys It.

Wiring EasyPost into a store network by hand takes an iPaaS to move shipment data and a legacy OMS to choose the packing location. Pipe17’s Order Operations Platform carries both jobs. Its order routing settles the location, EasyPost prices the carton, and Pipe17 buys the packer’s pick, tracking number included.
iPaaS & Custom Builds Legacy OMS Pipe17
Native API-First Connectivity ✅ ❌ ✅
Pre-Configured Commerce Connectors ❌ ❌ ✅
Custom Integration Mappings ✅ ❌ ✅
Advanced Order Orchestration ❌ ✅ ✅
Exception Management & Alerts ❌ ❌ ✅
Unified Inventory Management ❌ ✅ ✅
Rapid to Implement & Go-Live ❌ ❌ ✅
Easy to Add / Swap Channels & Flows ❌ ❌ ✅
Low Total Cost of Ownership (TCO) ❌ ❌ ✅

Future-Ready Brands and Fulfillment Providers Run on Pipe17

Rate Choice, Labels, and Refunds, All Inside Pipe17

Two-tone calculator icon with buttons, representing cost calculation, pricing analysis, and operational accuracy

Pick the Rate, or Take the Fallback

EasyPost prices each carton's carrier options. The packer picks one, or Pipe17 falls back to the requested service, then the default carrier, then the cheapest.

Box with checkmark overlaid, representing a verified, completed or fulfilled order

One Label per Carton, Ready to Print

Each carton gets its own label as a thermal file, PDF, or PNG, stored in Pipe17 with its tracking number, ready to print.

Box with backward arrow, representing return order processing

Void a Label, Pipe17 Tracks the Refund

When a packer voids a label, Pipe17 files the refund with EasyPost, records the carrier's decision, and opens an exception on a refusal.

Automated EasyPost Data Flows

Pipe17 calls EasyPost for three things: rates, labels, and refunds. EasyPost replies to each in the same call, except a refund the carrier decides later, which comes back by webhook.
  • Ask EasyPost for Rates. For each carton, with its weight, any dimensions, the packing location, and the ship-to address, Pipe17 asks EasyPost for every carrier and service on offer with cost, currency, and delivery days. Nothing is bought at this step.
  • Buy the Label. Pipe17 buys the rate the packer selected. With no selection it buys the service named on the request, then the cheapest within the default carrier, then the cheapest on any carrier. The return address is the Pipe17 location that packed the carton, a store filling a ship-from-store order or a warehouse that labels through the Pipe17 API. Insurance is added when the request asks for it.
  • Void the Label. When a packer voids a label in Pipe17, the connector files the refund with EasyPost and holds the label as pending until the carrier answers. A voided label stays voided, and the packer requests a new label for the carton.
  • Rates per Carton. Carrier, service, cost, currency, and delivery estimate for every option EasyPost can price, shown to the packer cheapest first.
  • Label and Tracking Number per Carton. The label file, tracking number, carrier, and service for each carton bought, attached by Pipe17 to the shipment’s label record.
  • Refund Decision. Submitted, refunded, or rejected, in EasyPost’s reply or later by webhook, written by Pipe17 on the label. For a rejection, Pipe17 opens an exception that quotes the carrier’s reason.

Connect EasyPost on the Account Pipe17 Manages, or on Your Own

The EasyPost connector is Pipe17’s to build and maintain. Leave the API key blank and labels ship on the account Pipe17 manages. Paste your own production key and they bill to your EasyPost account instead.

Buy the Right Label While the Packer Still Has the Box

Book a demo of the StoreOps mobile app and watch a store packer pick from EasyPost’s carrier rates for a carton, then print the label with its tracking number already on the shipment.
Book a demo
EasyPost horizontal logo in black

is better with

Pipe17 horizontal svg logo black

EasyPost Integration FAQs

The EasyPost integration lets Pipe17 buy carrier labels through EasyPost's shipping API while a shipment is being packed. A packer in the StoreOps app, or a system calling the Pipe17 API, asks for labels on a shipping request. Pipe17 sends each carton's weight, dimensions, and addresses to EasyPost, buys the rate the packer picks, and stores the label, tracking number, carrier, and service on the shipment. Pipe17 maintains the connector.

Yes, before any label is bought, Pipe17 asks EasyPost for every carrier and service available for each carton, with cost and delivery date, and the packer sees them cheapest first. The rate the packer picks is the one Pipe17 buys. If nobody picks, Pipe17 falls back to the service named on the request, then the default carrier's cheapest service, then the cheapest rate from any carrier.

No, by default the connector runs on the EasyPost account Pipe17 manages, and there is no EasyPost signup on your side. To use your own carrier accounts and rates instead, paste your production EasyPost API key into the connection in Pipe17. Pipe17 tests the key against EasyPost before the integration connects, and from then on labels bill to your EasyPost account.

Two kinds of location buy EasyPost labels through Pipe17: a store packing a ship-from-store order in the StoreOps app, and a warehouse whose system requests labels through the Pipe17 API. In both cases the return address is the Pipe17 location that packed the carton. Each store can be pinned to its own label provider in its StoreOps settings, letting one store ship on EasyPost while another uses a different connector.

Pipe17 files a refund request with EasyPost and marks the label pending. The carrier's decision comes back in EasyPost's reply or later through a webhook, as submitted, refunded, or rejected, and Pipe17 records it on the label. For a rejected refund, Pipe17 opens an exception that quotes the carrier's reason. The voided label stays voided, and the packer requests a new one.

The EasyPost integration supports Zebra Programming Language (ZPL), PDF, and PNG labels. The format is set once per EasyPost integration to match the printers at your locations, with ZPL the default for thermal printers. Each carton gets its own label file, stored in Pipe17 beside its tracking number. A packer in the StoreOps app prints it at the packing station, and an API caller downloads it from the label URL.

Yes, an organization can connect more than one label provider, and each store either chooses one in its StoreOps settings or inherits the organization default. The Easyship integration is one such provider. Whichever provider a store uses, the packing screen in StoreOps does not change, because Pipe17 resolves the provider behind the request for labels.

Add the EasyPost integration in Pipe17, choose a label format, and set a default carrier and service. Leave the API key blank to stay on the managed account, or paste your own production key. Then select EasyPost as a store's label provider, or leave the organization default. With your own key, also copy the webhook URL Pipe17 shows into your EasyPost dashboard, and later refund decisions reach Pipe17.