Reselling returns under your own brand
For 3PLs, fulfillment providers, and commerce platforms, returns are a layer you can resell under your own brand without building a warehouse. White-label returns means your customers see your name, your dashboard styling, and your markup, while areturnz runs the receiving floor, photographs every parcel, grades condition, and pushes evidence back through the API you already integrate. You add a revenue line; we absorb the labor, the square footage, and the reverse-logistics complexity.
This is the embedded returns model. Instead of routing your merchants to a third-party portal or turning away returns work because you lack the dock space, you fold reverse logistics into the same relationship you already own. The end customer never leaves your brand, and you keep the margin between what we charge you and what you charge them.
How white-label returns actually work
The split is clean. You bring the customer relationship, the pricing, and the brand. We bring facility NJ-01 in East Hanover, New Jersey (about 130,000 sq ft), a median cycle time near 48 hours, roughly 99.6% match accuracy, and 180K+ returns already processed. Every parcel is photographed at receiving and gets an evidence bundle: photos, an A/B/C/R condition grade, a confidence score, tags, and a full custody chain, delivered by dashboard and by signed-JSON API with webhooks.
Under the hood, areturnz is multi-tenant. Each of your merchants becomes an isolated tenant or sub-account with its own rules, its own webhooks, and its own evidence packages. API tokens are scoped per sub-account, so one brand can never read another brand's returns. Billing rolls up to you as the partner, while usage breaks down per brand, so you get one invoice and a clear per-merchant breakdown to reconcile against what you bill each of them.
What each isolated tenant controls
- Disposition rules - each merchant sets how grades map to actions (restock, liquidate, recycle, return to vendor). See how grades become decisions for the mechanics.
- Webhooks - each tenant subscribes its own endpoints, and delivery is isolated so one merchant's outage never blocks another's. This is the core of our multi-tenant webhook isolation design.
- Evidence packages - photo sets, grades, and custody chains are scoped to the tenant that owns the return.
- API tokens - scoped per sub-account so integrations stay compartmentalized.
Build your own returns op vs resell areturnz
The strategic question is whether returns is worth building in-house. For most 3PLs and platforms, the answer is that reselling gets you to a resellable service in weeks instead of quarters, without capital tied up in racking, labor, and grading tooling.
| Dimension | Build your own returns op | Resell areturnz |
|---|---|---|
| Time to launch | Quarters: lease space, hire, build grading and evidence tooling | Weeks: connect the API, brand the surface, onboard merchants |
| Capital | Warehouse, racking, labor, software, insurance | None: usage-based per return |
| Margin | Wide in theory, thin after fixed costs and idle capacity | Predictable spread between your price and ours |
| Evidence and trust | You must build photo capture, grading, and custody from scratch | Photo, A/B/C/R grade, confidence, and custody on every parcel |
| Accuracy | Ramps slowly as staff and process mature | ~99.6% match accuracy from day one |
| Multi-brand isolation | Your engineering problem | Built in: per-tenant rules, webhooks, tokens, billing roll-up |
Margin, time-to-launch, and trust
Margin. You resell at your own price. Because usage breaks down per brand while billing rolls up to you, your cost basis is transparent and per-merchant, so you can price by volume tier, by SKU category, or as a flat per-return fee and keep the spread. Our pricing is usage-based, which means your margin scales with adoption instead of being gated by a fixed facility cost you carry whether returns come in or not.
Time-to-launch. Standing up a returns operation is a real estate and hiring project. Reselling is an integration project. If you already push fulfillment events to our API, adding returns is mostly configuration: create the sub-accounts, set each merchant's disposition rules, subscribe their webhooks. The receiving floor is already running.
Trust. The reason returns damage merchant relationships is disputes: the customer says the item was fine, the merchant says it came back broken, and nobody has proof. We close that gap with proof on every return - a timestamped photo set and grade attached to each parcel. You can show your merchants the evidence sample so they see exactly what lands in their dashboard. When a chargeback or a not-as-described claim comes in, the evidence bundle settles it.
Keeping areturnz invisible to the end customer
Your merchants should experience the service as yours. Evidence today is served through the API and dashboard you control, and partner-CNAME evidence is on our roadmap: it will let you serve evidence links from your own domain, so the shopper or brand clicking through to a photo set never sees a third-party hostname. Combined with your branded surface and per-tenant isolation, the end customer stays inside your world while our floor does the physical work.
Who this fits
- 3PLs and fulfillment providers already handling outbound who want to close the loop on reverse logistics without new square footage.
- Commerce platforms and marketplaces that want returns as an embedded, monetizable feature for their sellers.
- Aggregators and brand holding companies running many merchants who need clean per-brand isolation and one roll-up invoice.
If that is you, the partners use case walks through onboarding, sub-account setup, and how the billing roll-up maps to your merchant list.
Frequently asked questions
Can I put my own brand on the returns experience?
Yes. You resell under your brand and your markup while areturnz runs the receiving floor. The surface your merchants use is yours, and partner-CNAME evidence on the roadmap will let you serve evidence from your own domain so the end customer never sees a third party.
How does billing work when I have many merchants?
Billing rolls up to you as the partner in a single invoice, while usage breaks down per brand. Each merchant is an isolated sub-account with scoped API tokens, so you can reconcile your cost per brand against what you charge each of them and keep the margin.
How isolated is one merchant's data from another's?
Fully. Each tenant has its own rules, webhooks, evidence packages, and per-sub-account API tokens. One brand cannot read another's returns, and webhook delivery is isolated so one merchant's outage never affects another. See our writeup on webhook isolation for the technical detail.
How fast can I launch reselling returns?
Weeks, not quarters. There is no warehouse to build. You connect the API, brand the surface, create sub-accounts, and set each merchant's disposition rules. The facility, grading, and evidence pipeline are already live at NJ-01.
What evidence does each return come with?
Every parcel is photographed at receiving and gets an A/B/C/R condition grade, a confidence score, tags, and a full custody chain, delivered by dashboard and signed-JSON API with webhooks. That evidence is what lets your merchants resolve disputes and trust the grades driving their disposition rules.
Related reading: White-Label Returns Platform: The Partner Playbook for Reselling Returns Processing
