"Does Pango integrate with X" is the second most common question after price, and the integrations page answers it one logo at a time. This guide answers it by category: what each kind of integration does inside Pango, which systems are in the directory today, and how to check your own stack before a call.
Short answer: the integrations directory lists 128 integrations: 89 carriers, 19 operations tools (warehouse, ERP, fulfilment and 3PL systems), 9 marketing and messaging tools, 3 support desks and 8 store platforms. Pango connects to more than 100 carriers through prebuilt connectors. The store platform integration (Shopify first) brings in orders and customers; carriers take shipments out and return tracking events; operations tools keep inventory and fulfilment in sync; marketing and support tools receive logistics-aware messages and context. Pango also exposes an API and an MCP interface for teams that want to build on it directly.
The five categories and what they do inside Pango
| Category | Count in the directory | What the integration does inside Pango |
|---|---|---|
| Carriers | 89 | Rates, booking, labels in the carrier's format, pickup points, tracking events normalised onto one status set, return labels |
| Operations | 19 | Orders, inventory and fulfilment state from the WMS, ERP, order platform or 3PL, so routing and returns act on the real stock picture |
| Marketing and messaging | 9 | Delivery, delay and return events pushed into the brand's email, SMS and messaging tools, segmented by customer |
| Support | 3 | Order, shipment and return context inside the help desk, so an agent answers "where is my order" without leaving the ticket |
| Store platforms | 8 | The order and customer source; Shopify is the first-class install with guided setup |
The counts are from the directory on the date this page was published and change as connectors are added.
Carriers
The carrier list spans the Nordics (PostNord, Bring, Budbee, Instabox and Instabee, Posti, Posten Norge, Helthjem, Porterbuddy, Airmee, Best Transport, Early Bird, DAO, Matkahuolto, Wolt), the UK and Europe (Royal Mail, Evri is not listed but DPD group carriers are, DHL Express, Deutsche Post, GLS, Colissimo, Chronopost, Mondial Relay, La Poste, bpost, PostNL, Correos, Swiss Post, Posturinn, Schenker, TNT Express, Geodis), North America (UPS, USPS, FedEx and FedEx Freight, Canada Post, Purolator, Canpar, OnTrac, GLS US, LSO, Veho, UniUni, Roadie, DoorDash Drive, Uber Direct, Spee-Dee, Better Trucks, plus a set of final-mile and LTL carriers such as XPO, Estes, Old Dominion, Averitt, R+L, Ryder Last Mile, RXO Last Mile, J.B. Hunt Final Mile, Seko Home Delivery, AIT Home Delivery, CDL Last Mile), Asia-Pacific (Australia Post, Sendle, Allied Express, SF Express, Yun Express, Yanwen, Aramex) and cross-border specialists (Asendia, Global-e, Zonos, Amazon Shipping).
Two practical notes. First, what matters is not the count but whether your five carriers are native, maintained connectors; the carrier integration checklist is the script for confirming that. Second, every carrier publishes its own status vocabulary, and the point of the connector is that Pango maps all of them onto one set the customer and the support team understand, then uses a status as an operational trigger. Each carrier's raw vocabulary is documented in the tracking guides on this site, for example PostNord, Royal Mail and UPS.
Operations: WMS, ERP, fulfilment and 3PL
The operations category is where Pango differs from a tracking or returns app. Because Pango runs outbound routing and warehouse pick and pack as well as tracking and returns, it needs the inventory and fulfilment picture, and the directory lists the systems that provide it: warehouse and fulfilment platforms (ShipHero, ShipBob, Ongoing, Extensiv, Deposco, Fulfil), ERPs and operations platforms (NetSuite, Brightpearl), address and data tools (Loqate, Smarty, USPS address validation, Google Maps), and data plumbing (Jitsu). For a brand on a 3PL, the 3PL's system is the operations integration; for a brand with its own warehouse, the WMS is, or Pango's own pick and pack module runs the bench directly. The distinction between these systems is in OMS vs WMS vs TMS.
Marketing, messaging and support
Logistics events are the most-opened messages a brand sends, and the directory lists where Pango can send them: Klaviyo, Attentive, Postscript, Twilio, WhatsApp Business, Apple Messages for Business, plus reviews and loyalty tools (Yotpo, Okendo, LoyaltyLion, Rise.ai) and subscription platforms (Recharge, Skio). Pango can also send through its own email and SMS, and can segment by customer value. The support integrations (Gorgias, Zendesk, Kustomer) put shipment and return context inside the ticket. The messaging strategy itself, which events to send and when, is in proactive shipping notifications and reduce WISMO tickets.
Store platforms
Shopify is the first-class integration: Pango installs as a Shopify app ("Pango Delivery and Returns" on the App Store, free to install) with guided setup rather than a long integration project, and the Shopify listing states it works with Checkout and Shopify Admin. The directory also lists BigCommerce, WooCommerce, Magento, Salesforce Commerce, Shop app, Tapcart and Vajro. What Shopify does natively for returns, and where Pango takes over, is set out in Shopify returns management.
API and MCP
For teams that want to build on Pango rather than only use it, the developers page documents APIs for generating labels, retrieving real-time data, tracking shipments and verifying addresses, and Pango exposes an MCP interface so agents and internal tools can call the same capabilities. This is how a brand with its own front end or an unusual workflow uses Pango's carrier and returns layer without adopting the whole interface.
How to check your stack before a demo
- List your store platform, WMS or 3PL, ERP, help desk, and email and SMS tools.
- List your carriers per market, with the services you actually use.
- Check each against the integrations directory; note anything missing.
- For anything missing, ask on the call whether it is a native connector in progress, reachable through the API, or built to fit as part of onboarding. Pango builds per-merchant workflows and can scrape carrier data where an API is poor, so a missing logo is a question, not a wall.
- Bring five real orders that crossed several of these systems, and ask to see them run on one record.
The bottom line
Five categories, 128 integrations at publication, Shopify first, carriers as native connectors, operations tools so routing and returns see real stock, messaging and support tools so events reach the customer and the agent, and an API for everything else. Check your stack against the directory, bring the gaps to the call, and book a demo to see your own orders run across them.
