Why These Three Vendors Are Not a Shortlist
Three names sit on the evaluation page in front of you: Narvar vs Metapack vs Malomo. Two of them publish no price at any volume. The third runs off the end of its published ladder before it reaches your floor.
That is not a shortlist. It is three vendors built around three different problems, lined up because they surface against the same search.
Their own published materials say so. Narvar is a post-purchase suite serving tier-one retail, running Promise, Secure, Track, Shield, Notify and Assist, with no price stated anywhere. Metapack is a five-module platform built around shipping orchestration, also with no published price. Malomo is a tracking product owned by Redo, whose published rate card ends below the volume you run.
So the useful question is not which of the three wins. It is what each one asks you to assemble, from whom, and on what commercial terms.
At 10,000 to 50,000 orders a month you are not trialling software, you are writing a business case a finance partner will challenge on total cost of ownership. Two of the three vendors here will not give you a number until you are weeks into a sales cycle, and the third publishes one sized for a smaller operation than yours.
The mismatch shows up in the scorecard. Score three vendors built around three different problems on one weighted matrix and the weights decide the outcome before the demos start: weight carrier logic and you have chosen the delivery platform, weight the shopper-facing experience and you have chosen the experience suite. Neither tells you what your post-purchase operation looks like eighteen months after signature.
Solve for the shape of the stack first, then score the vendors inside it.
AfterShip belongs in that evaluation on the same terms: Enterprise is custom-quoted, and the self-serve tiers stop below your volume too. What differs is what sits behind the quote. Tracking, shipping and returns arrive from a single supplier, on a single post-purchase data model.
The Three Contenders: Where Each One's Depth Actually Sits
Every vendor here sells tracking, returns and analytics, so sorting them by what they lack collapses on contact with their product pages. Sort them by centre of gravity instead: what each is built around, who owns it now, and how it charges.
Two of the four entities below changed brand or parent inside the last eight months, so a procurement pack older than that describes a market that no longer exists. Ask every vendor to confirm its corporate parent in writing, and check it against the contracting entity on the paper you sign.
| Entity | Centre of gravity | Ownership | Commercial model |
|---|---|---|---|
| Narvar | Post-purchase customer experience and communications at tier-one retail scale, across a multi-product suite | Independent | Quote-based at every volume. No price published anywhere |
| Metapack | Delivery orchestration: checkout delivery options, carrier orchestration, tracking and returns across five modules | A ShipStation Global brand since 1 June 2026 | Contact sales. No rate published at any volume |
| Malomo (Redo) | Tracking-led post-purchase experience, inside Redo's returns, warranties, shipping and support stack | Part of Redo since 19 January 2026 | Returns, claims and warranties listed free to the merchant. Redo publishes $0.08 per tracked order, for tracking alone, before returns, claims or checkout add-ons are counted. Malomo's published ladder tops out at $400 a month |
| AfterShip | Tracking, shipping and returns on a single post-purchase data model | Independent | Published self-serve tiers, with enterprise volume routed to a custom quote |
Narvar. Narvar's published line runs Promise, Secure, Track, Shield, Notify and Assist, and the weight sits on the shopper-facing experience rather than the carrier layer underneath it. It sells to tier-one retail, and it prices by quote at every volume. Narvar and Malomo are primarily post-purchase customer experience solutions; of the two, Narvar is much the larger.
Metapack. Metapack is an enterprise delivery platform spanning checkout options, carrier orchestration, tracking and returns. The five modules are Delivery Options, Delivery Manager, Branded Delivery Tracking, Returns and Intelligence Hub, and the platform has carried the ShipStation Global brand since 1 June 2026. Metapack's published figures are 350+ carriers, 4,000 services and 1.3M+ PUDO points, captured 15 August 2026. Those are the vendor's own numbers, and the centre of gravity they describe is delivery orchestration.
Malomo, now part of Redo. The product is tracking-led, and since 19 January 2026 it has sat inside Redo, whose stack also covers returns, warranties, shipping and support, as a closer look at Malomo since the acquisition sets out. Redo lists returns, claims and warranties as free to the merchant and covers return label costs, a different commercial shape from a flat subscription, which changes who pays and when. Its published rate card ends at the tier shown in the table above, sized well below your volume, and its Shopify listing carries six reviews, which describes the size of operation it currently serves.
AfterShip. AfterShip unifies tracking, shipping and returns on a single post-purchase data model. One system, one schema, rather than three products wired together after purchase, and that is what the rest of this comparison tests.
Treat Narvar, Metapack, Malomo and AfterShip as four answers to one procurement decision: how much of the post-purchase layer arrives assembled, and how much you assemble yourself. On that measure, AfterShip is the one that arrives whole.
The Architecture Question: How Many Vendors Sit Behind Your Experience Layer
One question survives every demo: when you buy a post-purchase experience layer, how many companies are you buying it from, and how many contracts govern it?
Metapack's own documentation settles that for one vendor on your list. Its Product Description pages for Tracking and Notifications, sold as Engage, and Returns and Notifications, sold as Retain, route the reader to parcelLab's documentation. Engage and Retain are parcelLab's own product names, confirmed by both parties, including the partnership release of 10 October 2024.
Read the same pages for what is included by default. Exchanges, gift cards and store credit, fraud and abuse screening, cross-border returns, marketplace returns, orderless and in-store returns, and resale flows are each written as conditional, either on what the retailer's contract covers or on systems the retailer already runs. What the documentation states as included by default is the portal.
Three qualifications matter. Metapack sells both tracking and returns, under those module names, to enterprise retailers running them at scale, so the finding is about architecture and commercial scope rather than capability. parcelLab is a capable enterprise vendor with its own carrier network and returns product, and nothing here turns on the quality of what it builds. And AfterShip is not exempt: it partners too, for drop-off networks and carrier relationships. The scoped version is what matters to your business case: the experience layer is the thing you are procuring, and for one of these vendors it arrives from a supplier under a separate commercial scope, with its own renewal, support path and data-processing terms.
Parabola and StartOps surveyed 90 supply chain and operations leaders at director level and above in early 2025 for their Supply Chain Tech Stack Report: 60% named lack of integration between tools as their primary pain point, and 50% cited limited visibility or reporting. One caveat travels with it: the sample sits at $50m to $250m brands, below your scale, and Parabola sells workflow automation rather than observing the category from outside it. Treat the finding as directional, not as a modellable cost.
Four post-purchase stacks drawn by what each is built around. An orange solid boundary marks a layer supplied by a separate company; an orange dashed boundary marks capabilities gated by contract scope rather than a published tier. Grey boundaries are structural only. Partnerships outside the experience layer, which every vendor including AfterShip has, are not shown.
Count the suppliers, then count the contracts. On AfterShip, tracking, shipping and returns arrive under one of each.
Tracking and the Delivery Signal
Carrier logo counts are the wrong test. The question is where the delivery signal originates, and whether the number your shopper sees on the tracking page is the one your promise engine used at checkout.
AfterShip retrieves tracking data through direct carrier integrations with the carriers themselves, and AI EDD is trained on AfterShip's own shipment history.
Coverage is where that provenance shows up in your numbers. AfterShip's AI EDD produces a prediction on 80%+ of deliveries, against under 40% for typical carrier estimates, at up to 95% accuracy. Coverage is the figure worth interrogating in a vendor demo, because an accurate estimate on a minority of your lanes still leaves most of your shoppers with nothing to trust. The one-to-one version of that comparison is worked through in an honest look at AfterShip vs. Narvar for enterprise.
When those two numbers come from different vendors, a disagreement in front of a customer is architectural, and no amount of notification tuning closes it. Tracking, shipping and AI EDD run on one engine at AfterShip, so both resolve from the same source, and stay that way as you add carriers.
Shipping: Scope Against Scope
AfterShip Shipping is an API-first, multi-carrier parcel-execution product: rate shopping, carrier-certified label generation, rule-based automation and international commercial-invoice generation, natively wired to tracking and returns rather than integrated with them. Own carrier accounts are supported, and Enterprise carries unlimited carrier accounts.
Now the limits, plainly. AfterShip Shipping is parcel execution. Freight, LTL and pallet are not published scope, and neither are customs brokerage and clearance, PUDO and locker networks, or multi-warehouse dynamic allocation. Commercial-invoice generation is document generation rather than clearance.
If your lane mix depends on any of those, make it a hard gate in your requirements document and test it against every vendor. Where AfterShip competes is the join: a label decision, a delivery outcome and a return event describe one order rather than three, and that stays true as your carrier mix changes.
Returns, and What a Single Data Model Can See
All four platforms run returns. The question is what your returns data can be asked in the same breath as your delivery data.
Try this on a demo call: "For the SKUs and carrier or lane combinations currently running late against our EDD, what is the 30-day return rate, and is late delivery driving returns on specific products or routes?"
In AfterShip, tracking status, AI EDD predicted versus actual, the carrier and lane, and the return event for the same order sit in one data model, so that is a pivot and an action rather than a data pull: filter to the failing lane and change the promise, the carrier or the return policy from the same screen.
Where the experience layer comes from a different supplier than the carrier and delivery layer, the same question is two exports, a key-match on order ID across two schemas never designed to agree, and a reconciliation someone owns. It gets answered quarterly instead of on Tuesday, which usually means after the quarter whose numbers it would have changed.
What to get in writing. Metapack's own documentation gates a long list of returns capabilities on "contracted scope" rather than naming them inside a published tier. Ask every vendor to list, in the contract, which returns capabilities are included at your tier and which are separately scoped. The gap between the demo and the signed scope is where post-purchase projects lose their business case.
One honest limit on the AfterShip side. Running several storefronts under one organisation is supported; a single consolidated reporting view across those stores is not there yet. If your business case depends on one cross-store view, test that requirement early and directly rather than assuming it. The example above holds inside one store's data, where most of these questions get asked.
AfterShip's single record buys speed on the questions that change margin: which lanes are failing, which SKUs those failures convert into returns, and what to do about both before peak.
The 2026 Enterprise Verdict: A Use Case Breakdown
Seven criteria decide this evaluation, and none is a feature. They are what still matters in year three, when the renewal is on someone's desk.
| Criteria | AfterShip | Narvar | Metapack | Malomo (Redo) |
|---|---|---|---|---|
| Platform architecture | One record and one schema across tracking, shipping and returns, from a single supplier | A multi-product suite from one vendor, weighted to experience and communications; ask what joins across module boundaries | Five modules, and its own documentation routes the branded tracking and returns experience to a partner's product, so delivery data and experience data originate in different systems wherever that is in scope | A tracking product inside Redo's wider stack; ask how deep the join runs post-acquisition |
| Core functionality scope | Tracking and notifications, shipping, returns, AI EDD, and AfterShip Intelligence as the AI layer across them | Tracking, notifications, returns, delivery-date promises, fraud and protection | Checkout delivery options, carrier orchestration, tracking, returns and analytics | Tracking, with returns, warranties, shipping and support available from the parent |
| API and extensibility | One documented API surface spanning tracking, shipping and returns, with webhooks across all three | Developer documentation published; ask how far one integration reaches across the products you license | Developer documentation published; ask which APIs cover the partner-provided parts of the experience layer | Developer documentation published; ask whether one API surface spans tracking and the parent's returns products |
| Commercial model and price transparency | Published self-serve tiers, with enterprise volume custom-quoted | No price published anywhere | Contact sales, at every volume | Returns, claims and warranties listed free to the merchant, with a published per-order tracking rate |
| Implementation and support model | G2's User Insights band gives an implementation time of 1 month, described as an average across 311 reviews | G2's Value at a Glance band gives 3 months, with no sample size disclosed | No implementation figure published on its G2 profile, and 14 G2 entries in total | Not publicly documented |
| Data portability and exit | Documented APIs and webhooks support export; retention period and full-export terms are contract items to confirm, not published guarantees | Not publicly documented; ask for retention period and export format in writing | Not publicly documented; ask which party holds the experience-layer data where a partner product is in scope | Not publicly documented; ask which entity holds tracking data post-acquisition |
| Vendor consolidation potential | All three layers consolidate onto a single platform and a single record | Consolidates the experience layer; delivery execution stays elsewhere | Consolidates delivery orchestration; parts of the experience layer arrive from a partner | Consolidates into Redo's stack, sized for smaller operations than this reader runs |
Narvar is a post-purchase suite serving tier-one retail, and publishes no price at any volume. Metapack is a delivery-orchestration platform first; a buyer choosing it should establish in writing which parts of its post-purchase experience layer arrive from a partner, and under whose contract. Malomo sits inside Redo, on a published ladder and a review footprint sized for a smaller operation than this reader runs.
For an enterprise consolidating tracking, shipping and returns onto one data model and one commercial relationship, AfterShip is the 2026 choice: one supplier, and a single post-purchase record that answers cross-product questions without an export.
Aetrex runs AfterShip Tracking and AfterShip Returns together on Salesforce Commerce Cloud, an enterprise stack rather than a Shopify one.
“We can simplify our tech stack and leverage the data together.”
Rui Kojima, Senior Director of eCommerce
Read their story →Making the Business Case: Vendor Count, Contract Count, One Data Model
Start with a market observation, because the observation is the argument. What these four disclose about what they charge:
- Metapack directs buyers to contact sales. No rate is published at any volume.
- Narvar publishes no price at all.
- AfterShip publishes self-serve tiers, then routes enterprise volume to a custom quote. At your scale you are in custom territory by AfterShip's own segmentation.
- Redo, which owns Malomo, is the only one of the four that publishes a per-order rate at all, for tracking alone, before returns, claims or checkout add-ons are counted.
Three of the four will not give a finance partner a modellable number before a sales cycle, so your business case rests on the structure of what you are buying rather than on sticker prices.
One platform carrying tracking, shipping and returns is one implementation, one security review, one data-processing agreement, one support path and one renewal. Assemble the same capability from separate vendors and each becomes recurring work no invoice itemises, starting with the reconciliation between two schemas that someone on your team owns forever.
Consolidation concentrates risk, and a finance partner will say so before you finish the slide: less leverage at renewal, one supplier whose outage is your outage, and a larger migration if the relationship ends. Best-of-breed spreads that across contracts you can replace one at a time, which is a real advantage rather than a rhetorical one.
Two things change the arithmetic. How often your questions cross products is the cost best-of-breed charges weekly rather than once at renewal. And concentration risk is largely a contract problem: export format, retention period, notice terms and a tested exit are all negotiable before signature, and deserve more attention than the sticker price.
This article does not re-derive a returns cost-of-ownership model; our enterprise returns comparison already does that in detail. What a three-way comparison can say is narrower: the fewer suppliers and contracts behind your post-purchase layer, the fewer places your business case can spring a leak. On that measure AfterShip is one of each.
What to Ask Each Vendor Before You Sign
This is the part to forward internally. None of it is answerable from a website or a G2 profile, and every item changes the shape of a contract. Ask all four vendors the same questions.
Commercial.
- What is the price at our volume, and what is the charging unit? Per order, per shipment, per tracked parcel and per return produce very different bills at 50,000 orders a month.
- Which modules are bundled, and which are licensed separately? Get the answer as a list of line items, not as a plan name.
- Which capabilities are gated by the scope of our contract rather than named in a published tier? Ask for that list in writing before signature.
Architecture.
- How many companies and contracts sit behind the experience layer we are buying? If any part is a partner's product, ask whose paper it is on, whose support desk answers, and what happens at that partner's renewal.
- Are your AI features in production at a named customer today, or on a roadmap? Ask for the customer, the go-live date and the measured result.
Operational.
- Can we run this on our own domain with vendor attribution fully removed? Confirm whether that is standard or a paid tier.
- How do you administer multiple brands and multiple stores under one organisation? Ask specifically what reporting is available per store and what is available across stores.
- What does a new implementation take, in weeks and in named roles on both sides? Ask who does the carrier configuration and who owns data migration.
- How long is tracking data retained, and can we export it in full if we leave?
The implementation question has public evidence behind it, and the evidence is uneven. On G2, captured 15 August 2026, Metapack's profile publishes no implementation figure at all. Narvar's "Value at a Glance" band gives "Time to Implement: 3 months" with no sample size disclosed. AfterShip's "User Insights" band gives "Implementation Time: 1 month", described as an "Average based on 311 real user reviews". Three different instruments, so read them as three disclosures rather than one league table.
One procurement observation while you are on those profiles: Metapack's entire public review record is 14 entries on G2 and one on Capterra. For a platform sold to enterprise retail, that is a thin evidence base, so weight your own reference calls accordingly.
Run the list across all four and the pattern is the one this comparison started with. AfterShip answers it from a single supplier, against a single post-purchase record.
Tracking, shipping and returns on one platform, with one post-purchase record.
Book a demoFrequently Asked Questions
What is the difference between Narvar and Metapack?
They are built around different problems. Narvar is a post-purchase suite whose weight sits on the shopper-facing experience and communications for tier-one retail. Metapack is a delivery-orchestration platform spanning checkout delivery options, carrier orchestration, tracking and returns. Both sell tracking and returns, and neither publishes a price at any volume, so a commercial comparison requires a sales cycle with each.
Does AfterShip offer multi-carrier shipping?
Yes. AfterShip Shipping is an API-first, multi-carrier parcel-execution product covering rate shopping, carrier-certified labels, rule-based automation and international commercial-invoice generation, with support for your own carrier accounts. Freight, LTL, pallet and customs clearance are not published scope, so confirm those against your lane mix. What distinguishes it is the join: labels, delivery outcomes and returns describe the same order on one record.
Is a unified post-purchase platform better than best-of-breed point solutions?
Consolidation concentrates risk, and that is the fair objection to it. One vendor means less leverage at renewal, a single point of failure, and a larger migration if you leave; best-of-breed spreads that across contracts you can replace one at a time. Press any single-platform vendor, AfterShip included, on export format, retention period and notice terms before you sign. What consolidation buys in return is the join: on one data model, a question that crosses delivery and returns is a filter rather than two exports and a reconciliation.
How much does enterprise post-purchase software cost?
At enterprise volume, almost none of this category publishes a usable number. Metapack directs buyers to sales, Narvar publishes no price anywhere, and AfterShip routes enterprise volume to a custom quote. That makes commercial structure the thing to evaluate: how many contracts you sign, how many renewals you manage, and how many suppliers sit behind the layer. AfterShip answers those as one commercial relationship and one data model.
