Shipped: package lookup across the network

Package lookup across the returns network is a search capability inside areturnz that lets an operator or partner find any parcel by tracking number, order ID, RMA, or SKU, regardless of which node received it. areturnz processes returns across multiple facilities including NJ-01 in East Hanover, New Jersey, and this update ties that receiving data together so lookup is not locked to a single warehouse view.

Before this shipped, a support agent or partner ops lead had to know, or guess, which node handled a given parcel before they could pull its status. That was fine when areturnz ran a single facility. It stopped being fine once volume passed 180K+ returns processed across a growing set of nodes and tenants, each with their own inbound queues.

What shipped

The update adds a network-wide search index that sits above per-node receiving logs. Any authorized user, whether that is an internal ops manager, a brand partner, or a white-label reseller, can now type a tracking number or order ID into one search field and get a result even if the parcel landed at a node they do not normally interact with.

Each result still respects tenant boundaries. A partner searching their own account sees full detail: photos, AI grade, disposition, and timestamps. Anyone outside that tenant's scope sees nothing, which keeps the isolation rules described in multi-tenant webhook isolation intact even though the search itself now spans the whole network.

Why cross-node lookup matters

Support tickets do not wait for the right node

When a customer or partner opens a ticket asking where a return is, the answer needs to come back in minutes, not after someone manually checks three separate node dashboards. With the median cycle from inbound scan to disposition sitting around 48 hours, a support delay of even a few hours looks disproportionate to the customer on the other end.

Multi-node partners needed one pane of glass

Partners running volume through more than one node, whether for geographic coverage or capacity reasons, were the ones who asked for this most. Their reporting already aggregates at the tenant level through per-tenant reporting, but reporting is a daily or weekly view. Lookup is the real-time complement: it answers where a specific parcel is right now instead of how last week looked overall.

How it works

Every parcel gets a unique identifier at inbound scan, tied to its outer label photo, opened-parcel photo, item photo, and any defect photos. That identifier now propagates into a shared index alongside the node ID, tenant ID, current A/B/C/R grade, confidence score, and disposition status. The lookup service queries that index first, then pulls full detail from the node of record once a match is confirmed.

This matters for node onboarding too. Any node joining the network, whether it is an areturnz-operated facility or a partner-operated one under the terms in the node spec, has to emit receiving events in a format the shared index can consume. That requirement was already part of onboarding; this update is the first feature that visibly depends on it.

What it means for partners and node operators

For partners reselling returns processing under their own brand, cross-node lookup removes a real friction point. A reseller's own support team can now trace a parcel without filing an internal escalation to areturnz ops, which shortens response time on the partner's side too. That is a small thing individually, but across a support queue it adds up.

For node operators, it means receiving accuracy matters more than it used to. A parcel that gets scanned into the wrong queue or logged with a mismatched order ID will not show up cleanly in cross-node search, which surfaces data quality issues faster than they would have appeared in a single-node view. Operators should expect mismatches to get flagged sooner now, not later.

What is next

The near-term plan is to expose the same lookup logic through the signed-JSON API, so partners can build it into their own support tooling instead of relying on the dashboard search box. Webhook events for cross-node matches are also on the roadmap, which would let a partner's system get notified the moment a parcel resolves at any node, not just their primary one.

This kind of change is exactly why we keep a running log on the product updates hub: small infrastructure shifts like a shared search index rarely make headlines, but they are what let the network keep its 99.6% AI-vs-operator match accuracy and 48 hour median cycle as node count grows instead of degrading.

Frequently asked questions

Does cross-node lookup change how disposition works?

No. Disposition rules, grading, and operator overrides work exactly as before. This update only changes how existing data is found and displayed, not how a parcel is graded or routed. See a real example of what a completed record looks like at the evidence sample page.

Can a partner see parcels that belong to another tenant?

No. Tenant isolation is enforced at the index level, not just the dashboard level. A partner's search results are scoped to their own account regardless of which node received the parcel.

Is this available on all pricing tiers?

Lookup is part of the standard dashboard experience. Details on tiers and what is included at each level are on the pricing page.

Does this require anything from node operators?

Existing nodes already meet the data format required, since it follows the same specification described in the node spec above. New nodes joining the network need to meet the same requirement as part of standard onboarding.

How does this help partner support teams specifically?

Partners running white-label programs, as described in the partner use case overview, can now resolve a parcel location question without an internal escalation, which shortens their own customer response time.

If your support or ops team needs faster answers on where a return actually is, contact areturnz to see the lookup tool in a live account.