Skip to Content
Settings

Settings

Settings control how returnfast behaves for your store. Review settings before launch and whenever your return policy, warehouse routing, support process, or team access changes.

Store settings

Store settings identify your merchant account inside returnfast. Review the store name, support contact, timezone, and buyer-facing return information.

Accurate store information helps buyers recognize the return flow and helps support teams understand which store a request belongs to.

Return policy settings

Return policy settings control how buyers submit requests and how your team reviews them.

Review:

  • Return window.
  • Eligible return reasons.
  • Required buyer notes.
  • Photo requirements.
  • Review rules.
  • Any instructions buyers see during the return flow.

Keep these settings aligned with the return policy published on your store. If your public policy changes, update returnfast before buyers start using the new policy.

Return destination

The return destination is where approved items should be shipped. It is used when prepaid return labels are created.

Confirm:

  • Recipient or warehouse name.
  • Street address.
  • City, state or region, postal code, and country.
  • Team contact information when required by the carrier.
  • Any receiving instructions your warehouse needs.

If the destination is wrong, labels may send buyers to the wrong place or fail during creation.

Team access

Give dashboard access only to team members who need it. Review access when team roles change.

Recommended access practices:

  • Give review access to support agents who handle buyer requests.
  • Give label and wallet visibility to operations or finance users who need it.
  • Remove access promptly when a team member no longer needs returnfast.
  • Use shared internal procedures instead of shared user accounts.

Before changing settings

Before changing return policy or destination settings, review active returns. Decide how your team will handle requests submitted under the previous settings.

For significant changes, notify support and warehouse teams before buyers are affected. Keep an internal note of the date the change was made so your team can explain decisions consistently.

FrequencyWhat to review
WeeklyNew requests, failed labels, wallet balance.
MonthlyReturn reasons, support notes, warehouse destination.
QuarterlyTeam access, policy alignment, operational exceptions.
Before peak seasonWallet funding, support coverage, destination accuracy.
Last updated on