Returnberry sits between the places return requests arrive and the system that processes them. It connects to both sides — by native connector where one exists, by API and webhooks where it doesn’t, and by file when a file is all your system takes.
Status comes back — by webhook, API sync or status file — matched on the references Returnberry sent, then posted on the original ticket.
Point any mailbox at your workspace address. Nothing to install.
Read a shared inbox directly. Every message is ingested exactly once, however often it’s read.
Read a returns queue, and reply on its tickets only when you allow it — each write is its own switch.
Structured forms and attached spreadsheets are read without AI.
Any modern helpdesk or shared inbox — connected by API or forwarding address.
Create the return — the RMA — directly in your OMS, mapped field by field.
Your system’s own API, with your authentication and your field mapping.
CSV or XLSX in your system’s exact import layout, by download or SFTP. The path that makes “any order system” true.
Any order management system with an API, or one that accepts an import file.
Your system tells Returnberry the moment a return is approved, shipped or received.
Returnberry asks on a schedule, for systems that don’t push.
Imported through preview, confirm and commit — and reverted if the file turns out to be wrong.
The same operations the app uses, available to your own systems — so an in-house tool is never the thing that keeps you keying by hand.
Submit a return request from your own systems
Orders, verdicts and their audit history
Subscribe to created, sent and completed
If it has an API or accepts a file, it already works. Tell us what you run and we’ll show you the mapping.