Legacy platform

Implementation

Edit online

This section describes the configurations and initial setup required to implement the return orders solution.

A store associate must have the resource permission for Return Order to view the Return Order portlet on the Home page. For more information about administering user group permissions, see Administering user group permissions.

Return order configuration

  • The following rules apply to return orders:
    • YCD_SHOW_RESHIP_ON_RETURN_ENTRY: If this rule is turned on, any products that were reshipped to a customer are displayed.
    • Exchange Type: This rule is read for the exchange type for a product in a return order. The exchange type is REGULAR by default, but can be changed to ADVANCED or PREPAID.
  • The WSCContant.YCDCHANNEL_COMMON_CODE_STORE has the entry type set as Store. To allow carry order lines while capturing an order, the Allow Cash And Carry Lines should be selected. For more information about configuring entry types, see Defining order entry types.

Blind return configuration

  • The following rules apply to blind return orders:
    • A store associate can only create a blind return if the Allow blind return of product is on. The rule is on by default.
    • The Number of days to be considered for determining the lowest price on returns without a receipt rule is set to configure the period of time in days for the application to find the lowest product price. For more information, see Configure pricing enterprise rules.

Return policy configuration

The following rules apply to return policy configuration:
  • The YCD_OVERRIDE_RETURN_POLICY_NOTE_TYPE is used for the Return policy override note type. The default value of the rule is YCD_OVERRIDE_RETURN_POLICY.
  • The WSC_RETURN_OVERRIDE common code is used to set the different override reasons for return

Return Policy Validation

You can configure rules for your return policy. The return policy will be validated based on the rules that are configured. The following validations are considered:
  • BLIND_LINE: Checks if the product is a blind return.
  • IS_RETURNABLE: Checks if the product is returnable.
  • RESTOCKING_FEE: Checks for a restocking fee, and if applicable, applies the fee to the product.
  • RETURN_REASON_VALIDATION: Checks the return reason for the product.
  • RETURN_UNIT_PRICE_LIMIT: Checks if the product exceeds the allowed limit for a product to be returned.
  • RETURN_WINDOW: Defines the window of time in which a product is returnable.

For information about configuring return reasons, see Manage return reasons.

For more information about configuring return rules, see Configuring return rules.

Payment configuration

The store associate must have the Payment Method status modification permission.

If the Authorize Payment Methods In Real Time for Draft Orders rule is enabled, payments from the customer in an exchange order are authorized in real-time.

The following rules apply to payment configuration:
  • Encrypt Credit Card Name and Expiration date
  • Use Enterprise Code For Payment
  • Use a Single Field To Enter The Name On te Credit Card In The User Interface
  • Charge Ship to Home Order Lines At Store
  • Postpone Payment Processing Until Pickup
  • Enable Payment Card Type Configuration
The following rules relate to refund payment types:
  • Default for return
  • Valid For Return
  • Refund To Same Payment Method
  • Refund To New Payment Method
  • Refund to New Payment Method Type
  • Charge Up To Available
  • Processing Not Required
  • Charge Instead of Authorize

For more information about configuring payment types, see Configuring payment types.

For more information about setting up payment encryption, see Setting up payment encryption.

Payment is governed by the configured financial rules. For more information, see Configuring financial rules.

You must configure the store payment rules appropriately. For more information, see Payment Rules.

Override price configuration

  • You must define the price override reasons appropriately. For more information, see Managing price override reasons.
  • The store associate should be granted resource permission for the Override Price action.

Services

The following services are provided out-of-the-box:
  • The YCD_ProductDetails_Email service uses the StoreProductDetailsEmail_17_1_multiApi.xsl.sample and StoreProductDetailsEmail_GenerateData_17_1_multiApi.xsl.sample templates.
    Configure the YCD_ProductDetails_Email service for your email-server in the Applications Manager using the following steps:
    • Navigate to the email service using the following path in the Applications Manager: Applications > Application Platform > Process Modeling
    • Open the Order Fulfillment process type.
    • Select Service Definitions > Store > YCD_ProductDetails_Email
    In the E-mail component, set the E-mail Server field to point to your mail server. The Subject and From fields have certain default values as part of the service, which can be customized as required.
  • The StoreReturnReceipt_95 service is used to print the return receipts. If you want to customize the output generated using this service, you must configure it in the Applications Manager. The service uses the StoreReturnReceipt_95_multiApi.xsl.sample and StoreReturnReceipt_GenerateData_95_multiApi.xsl.sample templates to print return receipts.
  • The YCD_StoreReturnEmail service is used to email the return order receipt to the customer. You must configure this service for your email-server appropriately in the Applications Manager. The YCD_StoreReturnEmail service uses StoreReturnEmail_95_multiApi.xsl.sample and StoreReturnEmail_GenerateData_95_multiApi.xsl.sample templates. In the service definition, set the E-mail Server field to point to your mail server. The Subject and From fields have certain default values as part of the service, which can also be customized as required.

The input or multi API XSLs are used to call multiple APIs that retrieve the information to be printed or mailed, while the output XSLs are used to format the API output as HTML content. The print and email templates are present in the <INSTALL_DIR>/template/prints/ycd/xsl/ and <INSTALL_DIR>/template/email/ycd/ directories respectively. The templates are provided as sample implementation and suffixed with .sample. You can continue to use the sample templates or rename them to remove .sample from the file names and customize as required.

You must enable the Email Product details resource permission for the store associates to share the product details with the customer.

For more information about creating and modifying service definitions, see Defining service definitions.

Other configurations

  • You can configure disposition codes for a store associate to select to complete the return or exchange order flow. For more information, see Manage disposition codes.

  • When you configure the Web Store channel in Sterling Business Center, the CodeValue attribute must be set to Store. The Store value is used to evaluate return policies set for the sales and return orders.

  • For more information about administering user group permissions, see Administering user group permissions.
  • While adding products to a return order, the Add Products screen shows cached inventory availability, but does not display future product availability. In both the View Cart and Returns List screens, real-time and future inventory availability is displayed.

  • For information about configuring order modification types, see Defining modification rules.

  • To configure system payment processing rules, see System payment processing rules.
  • For more information about APIs, see the IBM® Sterling Order Management System: Javadoc™.