An ecommerce returns app for operations teams. Create returns, inspect items, approve or reject the request, and close it with an external refund reference.

Return desk follows a return from Draft through submission, inspection, approval, and closure. Each item has a requested quantity and value, inspection condition, disposition, and approved refund quantity. The app enforces a 30-day interval between purchase and receipt before submission. Closing an approved return requires a reference to a refund recorded elsewhere; no payment is executed. The built pilot uses ToolJet Database and fictional records. Choose Deploy to ToolJet to start on Cloud, or download the application package for self-hosting. Follow the included README to import the app and load its fictional sample data.
Built for Retail and ecommerce operations teams recording return inspections and manual refund decisions.
An ecommerce returns app for operations teams. Create returns, inspect items, approve or reject the request, and close it with an external refund reference.
Review open requested value, inspection and decision counts, oldest cases, and return reasons.
Record order reference, customer, purchase and received dates, and return reason. Add or edit returned items in Draft before submitting.
Record condition, disposition, approved refund units, and a note for each item. Advance only after the inspection is complete.
Approve or reject inspected work, then close an approved return with a refund reference and note. The app stores the outcome without executing a refund.
Review the oldest submitted or inspected returns, requested return value, and reasons items came back.
Create a unique return reference linked to an order and customer, then add SKU, item name, quantity, and unit value in Draft.
Record condition, disposition, approved quantity, and inspection notes. Approved quantities cannot exceed returned quantities, and every item must be inspected before the case advances.
Approve a positive refund value or reject the return with a note. Close approved work with an external refund reference; reopen rejected or cancelled work to Draft when review must restart.
The pilot uses 1 table with fictional records. No external database is needed to explore the source app.
| Table | Sample data | What it stores |
|---|---|---|
| Returns | 5 sample returns | Order and customer references, dates, reason, item-level inspection, refund decision, and history. Includes five sample items. |
The pilot uses a fixed 30-day intake rule and USD item values. It does not verify purchases against an order system, issue labels, arrange shipping, update stock, execute refunds, or send notifications. Approval requires a positive approved item value. Reopening to Draft clears the current inspection fields while retaining decision history. This English desktop pilot reads up to 1,000 rows per table; larger datasets need pagination. Access policies, package export, and clean installation remain unverified.
This design is a starting point. Describe the look you want, add your logo and brand colors, or ask for new features in a prompt. Use the starter prompt to build your own version in the ToolJet AI builder, or use a suggested prompt to modify an app you already have. Review and test the result.
Suggested prompts describe changes you can request. Additional features and translations still need to be built and tested.
Choose ToolJet Cloud, or download the application package to import into your self-hosted instance. Unzip the download, import its application JSON, then follow its README to load the fictional sample data.
Explore the sample records in ToolJet Database, then add your records and configure the workflow for your team.
Describe your preferred design, branding, and new features in the AI builder. Test your workflow, then share your app with the people who need it.