Skip to content

Customer Implementation Requirements Guide

OrderFlow Ltd.

Document Version: 4.2.4

Document Built: 2024-02-16

This document and its content is copyright of OrderFlow Ltd. All rights reserved.
You may not, except with our express written permission, distribute, publish or commercially exploit the content.
Any reproduction of part or all of the contents in any form is prohibited.

Returns

Returns

How returns are handled depends on your returns authorisation process. OrderFlow can be configured so that a return cannot be processed until the original order number is entered.

Recommendation

During the requirements gathering phase we recommend a dedicated session (using a TeamViewer demonstration) to explain the system options available for returns, and to match these against your business requirements.

  • Do you wish to process returns without an original order number?
  • Are your returns initiated by a third party system?
  • Do you wish Customer Service and/or a third party system be notified of a return?
  • Do you wish OrderFlow to capture and store any details on a completed returns form?
  • What additional information should the user recording the return be able to capture?

  • What are the different returns outcomes that each item might be routed to, for example:

    • Return to stock
    • Destroy
    • Hold for inspection
    • Return to manufacturer
    • Charity

  • Do some returned items need to be sorted by manufacturer when they are stored?