Pango and Ingrid are both Stockholm-built platforms for the delivery side of e-commerce, and a Nordic brand shortlisting one will usually shortlist the other. The overlap is large and we say so below. The difference is not in the feature list; it is in what each system is for: Ingrid is a delivery intelligence platform that a retailer's team configures and operates, and Pango is an operating system that runs the operation, including the warehouse, with the team supervising.
Short answer: on delivery options at checkout, multi-carrier transport and labels, branded tracking, exchange-first returns, Nordic carrier depth and AI that adjusts delivery decisions, the two are close and Ingrid has years of head start. Pango does two things Ingrid's product list does not include: it runs warehouse pick, pack and dispatch on the same order record as routing, tracking and returns, and it lets the operator write rules and agents in plain language that are compiled into that merchant's own workflows. If your question is "which delivery checkout is more proven", Ingrid has the longer record. If your question is "which system will run delivery, tracking, returns and the warehouse as one operation", that is what Pango is built to do.
What Ingrid is
Ingrid describes itself as a delivery intelligence platform for multi-carrier retail that helps retailers design, test and execute delivery strategy across checkout, tracking, transport, returns and exchanges. It was founded in Stockholm in 2015 and states more than 100 employees, four offices and more than 250 active retailers. Its products, per its own site: Delivery Checkout, Delivery Tracking, Delivery Insights, Delivery Experiments, Transport Automation, In-store Fulfillment, Returns and Exchanges, and Ingrid AI.
The strengths are real. Checkout is Ingrid's origin and its core: delivery options, pricing and A/B testing of the delivery offer, with pickup points and localised address forms. Transport is a cloud-based TMS with automated booking rules, label generation in the carrier's formats and, by Ingrid's count, more than 300 carrier products, inside what it calls over 350 carrier integrations. Tracking is branded and proactive. Returns are AI-driven, with tiered return policies, exchanges, gift cards, return analytics and re-commerce. Ingrid AI orchestrates delivery windows, pricing and carrier optimisation from real delivery performance instead of static rules, and Ingrid positions it for agentic commerce. It is modular by design: a retailer can start with checkout, tracking or returns and expand.
What Pango is
Pango is an AI-native operating system for e-commerce logistics. On install it reads the merchant's data, schema and delivery and returns policies, proposes the operations worth automating, and runs them as agent workflows on one record of the order: delivery options and promises at checkout, carrier routing across more than 100 carriers through prebuilt connectors, warehouse pick and pack, branded tracking with proactive messages, and returns and exchanges to any product in the store. Rules are written in plain language and compiled into per-merchant workflows. Pango is not an order management system and not a carrier. The company is a Y Combinator company built in Sweden and the United States; the full description is in what is Pango.
Pango vs Ingrid, by area
| Area | Ingrid | Pango | Verdict |
|---|---|---|---|
| Delivery options at checkout | Core product: options, pricing, A/B tests, pickup points, address form | Checkout delivery options, prices, ETAs, carrier-failure fallback, A/B testing of options | Tie on scope; Ingrid has the longer record |
| Carrier transport and labels | Cloud TMS, automated booking rules, 300+ carrier products, labels in carrier formats | Multi-carrier routing, rate shopping, labels, shipping rules, multi-warehouse and 3PL | Tie on scope |
| Carrier network | Over 350 carrier integrations, by Ingrid's count | More than 100 carriers through prebuilt connectors | Ingrid lists more; check your own five |
| Branded tracking | Branded, proactive tracking | Branded tracking pages on the merchant's domain, proactive messages, status as an operational trigger | Tie on the customer-facing side |
| Returns and exchanges | AI-driven returns, tiered policies, exchanges, gift cards, analytics, re-commerce | Plain-language return rules, exchanges to any product, labels, cross-border documents, refund logic per country | Tie on scope; different mechanism |
| Nordic carrier depth | Stockholm-founded, deep Nordic coverage | Stockholm-built, Nordic carriers as native connectors | Tie |
| AI | Ingrid AI: delivery windows, pricing and carrier choice adjusted from real performance | Agents that act on order and tracking events across routing, warehouse, tracking and returns; rules written by the operator in plain language | Different: optimisation of delivery decisions vs agents running the operation |
| Warehouse pick and pack | Not in the product list; In-store Fulfillment is ship-from-store | Pick, pack and dispatch on the same record as the shipment | Pango only |
| Operating model | Modular platform the retailer's team configures and operates | One system that runs the operation, team supervises | The real choice |
The real difference: who does the work
Ingrid's model is that the retailer's team gets a powerful, well-integrated set of delivery tools and configures them, with Ingrid AI adjusting the delivery decisions inside that configuration. That is a good model for a retailer with a delivery team that wants control and a long list of carriers.
Pango's model is that the operation itself is run by agents the operator instructs in plain language, and that the operation includes the warehouse. A late scan is acted on by an agent that knows how the parcel was routed, what was promised, and what the return policy says if it comes back, because all of that is on one record. The warehouse is inside the loop, so a return is recognised at the dock by the label Pango issued, and an exchange can ship on the return scan.
Neither is wrong. They suit different brands.
Which fits which brand
Ingrid fits a retailer with an in-house delivery or e-commerce operations team, a large carrier roster, a strong need for checkout experimentation, and a warehouse system it is happy with. Its checkout is the most proven part of the comparison.
Pango fits a DTC brand that runs its own delivery, tracking and returns and wants them, plus the warehouse pick and pack, to run as one system rather than a stack, with rules the operator can write and agents acting on events. The Shopify-first install and guided setup matter for brands without an integration team. The one public example of the returns side is Switch Nails, a Nordic brand where 19% of returns are now kept as an exchange or store credit, 33% of exchangers reorder against 20% of refund-takers, and 99% of returns run self-serve.
Questions to ask both
- Show one order from checkout promise to refund without switching screens. How many systems does that take?
- Which of my five carriers are native, maintained connectors, and what happens when one fails a booking?
- Where does the warehouse sit: inside the system, or behind an integration?
- How is a new return rule added: configured from a menu, or stated in plain language and compiled?
- What does the AI act on: the delivery decision at checkout, or every event across the order?
- What is the pricing model: per order, per return, per module, or by volume?
The carrier integration checklist turns these into a longer script. The related comparisons are Pango vs nShift, Pango vs AfterShip and the wider Ingrid alternative page; the Nordic context is in the Nordic e-commerce shipping and returns guide.
The bottom line
Ingrid is a proven, modular delivery intelligence platform with a checkout that has been refined for a decade and a large carrier network. Pango is an operating system that runs the whole post-purchase operation, warehouse included, on one record, with rules and agents the operator writes. Compare them on the operating model, not the feature grid, and test both with one real order from promise to refund. Then book a demo.
