RM

Statuses & Timeline Events

Understand and configure return statuses and timeline events.

3 min read
Last updated 31 December 2024

Statuses track where returns are in the workflow. Timeline events record everything that happens. This guide covers both.

Default Return Statuses

StatusDescriptionNext Statuses
PendingAwaiting approvalApproved, Rejected
ApprovedReady for shippingLabel Sent
Label SentCustomer has labelIn Transit
In TransitPackage en routeReceived
ReceivedPackage arrivedInspected
InspectedAssessment completeResolved, Rejected
ResolvedReturn complete(Final)
RejectedReturn denied(Final)
CancelledCustomer cancelled(Final)

Status Configuration

Customising Statuses

  1. Go to Settings → Returns → Statuses
  2. Edit existing or add custom statuses
  3. Configure transitions and triggers

Status Properties

PropertyDescription
NameDisplay name
Internal CodeSystem identifier
ColourVisual indicator
DescriptionExplanation for team
Customer VisibleShown to customers?
TriggersAutomated actions

Timeline Events

What Gets Recorded

Every action creates a timeline entry:

  • Status changes
  • Notes added
  • Emails sent
  • Documents uploaded
  • System events

Viewing Timeline

  1. Open any RMA
  2. Scroll to Timeline section
  3. View chronological history
📷
RMA Timeline
(Screenshot placeholder)
Complete timeline of return events

Event Types

TypeIconDescription
StatusCircleStatus change
NoteChatStaff or customer note
EmailMailEmail sent
SystemGearAutomated action
DocumentFileFile uploaded

Custom Statuses

When to Add Custom Statuses

Add statuses when:

  • Your workflow has unique stages
  • You need finer tracking
  • Reporting requires specific states

Example Custom Statuses

  • Quality Hold - Items awaiting QA review
  • With Manufacturer - Sent to vendor
  • Awaiting Parts - Repair on hold
  • Customer Response - Waiting for customer

Creating Custom Status

  1. Go to Settings → Returns → Statuses
  2. Click Add Status
  3. Configure:
    • Name and code
    • Position in workflow
    • Allowed transitions
    • Automated triggers

Status Transitions

Configuring Transitions

Control which status changes are allowed:

Received → Inspected ✓
Received → Resolved ✗ (must inspect first)

Transition Rules

Set rules for transitions:

  • Who can make the transition
  • Required fields before transition
  • Automated actions on transition

Timeline Best Practices

  • Add notes for all significant actions
  • Use clear, descriptive language
  • Mark notes as customer-visible when appropriate
  • Include relevant details (names, amounts, reasons)
  • Review timeline before contacting customers
Was this helpful?
Contact Support