Returns + reverse logistics.

Why now

Returns are 15-30% of e-commerce. Reverse logistics is the leakiest workflow.

What the signal looks like

Repos with WMS / TMS adapters, return-policy engines, and refurbishment / liquidation integrations.

Public examples

We name publicprojects + categories only, never founders we track inside the paid product. The buyer’s edge stays inside the product.

• Optoro shape
• ReturnGO / Loop Returns
• Open-source returns-logistics libraries

What this displaces

A returns pile in the warehouse + manual refurbishment.

How to validate it in an afternoon

Before committing build time or a thesis memo to returns + reverse logistics, run three cheap checks against public engineering activity. Each takes minutes and none require access to private data.

1. Count active builders. Search GitHub for repositories matching this category, then check how many accepted commits in the last 14 days. More than a handful of active teams means the category has energy, not just mentions.
2. Look for the hot, multiple deals per month pattern in funding. If funded companies keep appearing here, multiple funded companies are landing in this category per quarter right now. Cross-check the supply chain leaderboard to see whether any of the accelerators sit adjacent to this niche.
3. Test the one-quarter build cost assumption honestly: expect a quarter of sustained build time, usually two or three people, before first external users. If your calendar cannot absorb that, the opportunity is real but not yours yet.

The weekly signal feed tracks 10 Supply Chain sub-niches including this one, so the cohort side of this check can run continuously instead of manually.

Common questions about this niche

Buyer?

DTC + mid-market e-commerce + retail.

Pricing?

Per return processed.

Defensibility?

Workflow + integrations.