How to Build a Product Returns Process

To build a product returns process, four things have to connect: the original order, the customer conversation, the physical inspection, and the stock movement that follows.

Why returns are handled inconsistently

They arrive unpredictably and touch several teams, none of whom own the process.

Requests arriving by message with no order reference
Inspection results recorded informally
Stock adjusted manually, or not at all
The customer chasing for an update nobody can give

The stages to define

Stage	What happens
Request	Customer submits, referencing the original order
Authorization	The return is accepted or refused, with a reason
Receipt	The item arrives and is logged
Inspection	A checklist confirming condition
Resolution	Stock movement, refund, or replacement

How to build it in Jestor

Create a returns table in Jestor, connected to orders and clients.
Capture requests through a public form, or from a WhatsApp conversation as a card.
Add a checklist for the inspection, completed before the record advances.
Record the resulting stock movement with type, quantity, and date.
Notify the customer automatically at each status change, by email or template.

Why choose Jestor for returns handling?

Because Jestor is relational, the return references the original order rather than repeating its details — so the team sees what was sold, when, and to whom, from the return itself.

SLA tracking per stage shows where returns actually wait, which is usually inspection rather than the parts customers complain about.

Frequently Asked Questions

Can a return reference the original order?

Yes, through a connected field. See jestor.com.

Can the customer be notified automatically?

Yes, on each status change.

Can inspection be evidenced?

Yes, through a checklist on the record.

Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,