AUTOMATING CUSTOMER RETURNS
BUYING INVENTORY & RETURN MATERIAL AUTHORIZATION (RMA)

RMA support inside SendSafe can be used to enable automated returns of orders and / or purchasing of items from customers for resale. RMA Orders are negative dollar values which are tallied against positive dollar value product orders. The result is an accurate cash balance is maintained in the database.

This RMA function does not currently automatically issue credit card credits. This functionality can be added.

RMA Return items and items for purchase are mutually exclusive and cannot be placed in the same shopping cart.

See also: RMA Orders Admin page for more information on using the RMA admin page.

Sections:
Steps to process an rma order
RMA order structure
RMA line item structure
RMA special db items
RMA lineitem disposition flags
RMA Event Date Stamping
RMA System Configuration
Stages of an RMA
Automation of RMA Process
RMA shipper / packaging material job
I-CRM RMA nag job
RMA items checkin job
Disposition handling job
Adjusted Trade Offer Price Calculation
Zero Cost Limiting of Adjusted Trade Offer Price Calculation
Automatic ATO acceptance
RMA reinventory job
Inventory Tracking

*RMA Request chart can be clicked on to open an enlarged view

*RMA Fulfillment chart can be clicked on to open an enlarged view

STEPS TO PROCESS AN RMA ORDER

The three steps outlined below is the general process that is followed for handling an RMA order.

There are four key RMA Admin pages which will be used for processing RMA Orders. These pages are:

RMA Order
RMA Order Report
RMA Receiving
RMA Inspection

*All these admin pages can be found in the main Navigation links on any admin page. To open your admin pages type the appropriate URL into your web browser i.e. https://www.yourdomain.com/SendSafeAdm/v2.RMAOrder.asp

RMA Step 1 Send a shipping container to the customer (optional). The RMA Order Report page can be used to print shipping container labels and advance an RMA order to the next step (this is called activating the next step).

If you print labels for an order an automated e-mail will be sent to the customer informing them that packing material has been sent to them: i.e. "Your shipping container has shipped"

If you are sending a shipping container to the customer, open the RMA Order Report Admin page and enter an appropriate date range AND set the Process Step to 10. From the report results, select the orders you wish to send shipping containers by placing a checkmark to the left of them and then press the [ Print Label / Activate ] button. Once the button is pressed you will be presented with a printable list of shipping labels for the shippers. You should never process more than a few dozen orders at a time because the pages of barcoded shipping labels can grow very large. Batched label printing solutions can be implemented. Typically the shipping label is printed by the customer and not e-commerce business and therefore, this limitation in printing shipping labels is seldom a factor.
https://www.yourdomain.com/SendSafeAdm/vao.RMAOrderReport.asp

The size of the RMA report is limited to 100 entries. This means you can print up to 100 labels per report. If you have more than 100 RMA order to process, you will need to do them in groups of 100 labels. To do this follow these steps:

1. Select a date range
2. Select "Process Step" = 10 from the dropdown box
3. Press the [ Create Report ] button
4. Select all the orders (checkbox)
5. Press the [ Print Label / Activate ] button
6. Print the labels
7. Go back to step#3 and press the [ Create Report ] button - The report will list the next 100 orders for printing.

• Printing address labels from some browser will print a header and footer on the page. This printing is not under the control of the RMA System. To disable printing headers and footers either: (a) change the printing preferences in the browser OR (b) make the registry changes listed below for Mircosoft I.E.
  
  Setting these two registry keys to empty values will disable header and footer printing in IE:
  • HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\PageSetup\header
  • HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\PageSetup\footer

RMA Step 2 Check in the RMA returns as they are received. The RMA Receiving page is used when the returned items are received at your shipping dock. This page activates the next RMA step and will cause an e-mail be sent to the customer “We received your returned item.”

This page also sets the RequiredShipDate in each lineitem of the order. This setting of the RequiredShipDate established the date and time that the RMA return hit your recieving dock. This date is critical because it controls the order in which RMA Orders are processed for final disposition and it effects how items appear in RMA related reports such as the accounting report.

When receiving an RMA order at your shipping/receiving dock, you must start the item check-in process with the RMA Receiving Admin page.
https://www.yourdomain.com/SendSafeAdm/vao.RMAReceiving.asp

To receive items follow these steps:

1. Open the RMA Receiving Admin page
2. Enter the RMA Order Number or Serializer Number into the webpage.
3. Press the [ RECEIVING STEP ACTIVATION ] button.
4. The customer's name and address will be displayed (you should double check that the correct RMA# or Serializer# was entered by comparing the name and address displayed with that on the packages return address label.
5. Repeat steps #2 and #3 for all RMA packages being recieved.

Once this order step is activated on the RMA Receiving admin page, the page will remain open for the next order to be entered. This is useful if you are using a hand scanner to read in each package's RMA# by scanning the barcode on the label.

RMA Step 3 Inspect the returned items for completeness and defects. The RMA Inspection page is used for this step in the RMA Process. Open the RMA Inspection page and enter or scan either the RMA Order number or Serialzer number into the form then press the [ Inspection Step Activation ] button. Pressing the button will advance the RMA Order to the Inspection step, open the RMA Order Admin page, and load the order into the page. The RMA order is flagged with the customerId of the employee who is doing the inspection (i.e. the customerId logged into the admin page). This information is saved in the InspectedBy column.

On the multi-line-item admin page you can enter final disposition of the returned items. The drops downs for each line item are used to:

1. Enter defects or problems found by entering notes, manual price adjustments, OR Price Adjustment flags
2. Set the RMA disposition flags for each line item on a page (i.e. RMA-ACCEPTED, RMA-REJECTED, RMA-REAPIR, etc.)
3. Press the SAVE button and set adustments on other pages.
4. Once all adjustments have been made on an order then the page should be released for automated processing by the system.
5. Press the Process Order button to release the order for processing. You can not make any more changes on an order once it has been released for processing. Warning! If you use any other admin page (such as Admin OrderLineItem Or Admin Orders) to modify some part of the order while processing is occuring, you could overwrite the results of processing.

You can manually unlock a record, but this can result in unpredictable processing of that order. To unlock an order, load it into the normal Order admin page (not the RMA order page). In the normal order admin page, set the processStep 15 and delete any date in the AcklFulFillmentCompleted field. Save the order once these changes have been made. The order is now unlocked and the process step has been set back to the RMA inspection step. You can set the step all the way back to 10 (which result in the order being completely reworked and the customer receiving additional duplicate e-mails).

Important! You may lose disposition flag settings, if you unlock an order and attempted to save it when any of the Disposition flags are set to values automatically assigned by the RMA system (i.e. values not available in the dropdown – for additional information: see Disposition flags automatically set by the system).

The drop down boxes for price-adjustment codes can be selected for each line item in an RMA order. You can also print a traveler AND go to the OrderLineItem admin page where you can manually adjust the price of each returned item in addition to any price adjustments automatically entered by selecting adjustment codes.

Important! If you change a price in the LineItem page you must reload the order in the RMA order page so that the RMA order page can re-adjust the order totals (if so desired). Some companies chose to leave the price discrepancy in place to flag the order as price adjusted.

If an item is flagged as needing repair, the system will automatically issue an Adjusted Trade Offer (ATO) e-mail to the customer (as part of automated procssing). The ATO will not be issued until all items in an RMA order have had RMA disposition flags entered.

When inspecting an RMA order for defects and completeness, you should start with the RMA Inspection Admin page.
https://www.yourdomain.com/SendSafeAdm/vao.RMAInspection.asp

Notes:

• RMA Disposition Flags appearing inside [ braces ] in the dropdown list are values set by the system, not the user. The user cannot set disposition flags within [braces] on the RMA Order page and should not manually do so using the Admin LineItem page.
• Flags and other information entered into the form is not saved until the [ Save Information ] button has been pressed
• By default, the "Display All Fields" option is set to hide. If you need access to all the fields in the RMA Order you can set this dropdown box to "show all" which will reveal all the fields.
• Printing travelers from some browser will print a header and footer on the page. This printing is not under the control of the RMA System. To disable printing headers and footers either: (a) change the printing preferences in the browser OR (b) make the registry changes listed below for Mircosoft I.E.
  
  Setting these two registry keys to empty values will disable header and footer printing in IE:
  • HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\PageSetup\header
  • HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\PageSetup\footer

RMA Step 4 Accept or Reject Adjusted trade offers (ATO). This optional Step is for orders which received “Adjusted Trade Offers”. If a customer receives an ATO they will be sent an e-mail with a link to a webpage which displays the ATO. The custonmer can either accept or reject the offer by pressing a button on this webpage. The RMA system can be optionally configured to automatically accept an ATO if the customer does not rejected it in a specified number of hours (see: RMA AUTOTRADEADJ). You can check on the status of an ATO by opening the RMA Order page and looking at the RMA Disposition Flags. The flags can be any listed value:

• If the flags are set to either: RMA-PENDING-REPAIR-REJECTED or RMA-FINALIZED-REPAIR-REJECTED then the ATO have been rejected.
• If the flags are set to either: RMA-PENDING-REPAIR-ACCEPTED or RMA-FINALIZED-REPAIR-ACCEPTED then the ATO have been rejected.

ATOs can only be accepted or rejected in their entirety. The is no provision in the system to accept only part of an ATO.

When an ATO is sent the AckRMACheckIssued DB column is date stamped. This date stamp is used by automatic ATO acceptance logic, to later automatically accept the ATO if the custom does not respond in the required time.

RMA ORDER STRUCTURE

RMA order records differ from sales orders in some ways and are the same in other ways.

RMA number is the transactionid of the order.

RMA orders have an ApprovalCode entry same a sales order.

RMA orders which are pending completion have a status {REQUEST ACCEPTED} and will include a semicolon delimited flag of: ";RMA" (see: order status)

RMA orders which are complete have a status {COMPLETE} code the same a sales order but will include a semicolon delimited flag of: ";RMA" (see: order status)

RMA orders have a negative dollar amount unlike sales order. This negative amount can be directly tallied against sales orders so that net true sales dollars can be reported.

RMA LINE ITEM STRUCTURE

For a normal RMA, the item is added to the basket is a special case DB Items that has been set up as an RMA return item. This item is identified by the SKU = Application("RMAGenricReturnItemSKU") and can NOT contain the substring Application("RMAItemTag") in it. This item must have the ProductType set to (or prefaced by) Application("RMAItemTag").

RMA orderlineitem records differ from sales orderlieitem in some ways and are the same in other ways. RMA OrderLineItems are added to the cart from either orders OR a special type of Item which is used only to issue credits to customers (for example purchasing items from a customer for resale).

RMA ItemParameter field contains a coding which indicates the details of the returned item:
[RMAITEMTAG]-[ORIGINALSKU]-[ORIGINALTRANSACTIONID]

[RMAITEMTAG]	A keyword/flag which can be used to differentiate types of RMA returns. (see also: Application("RMAItemTag")
[ORIGINALSKU]	This is the SKU of the product being returned.
[ORIGINALTRANSACTIONID]	(Optional) This is the order# (transactionid) of the order from which this product being returned. This field may not be used (for example) if items are being purchased by the store from a customer for resale.

Examples:
ItemParameter = "I-RMA-SKU6152-928784"
ItemParameter = "I-RMA-SKU6562"

RMA AltItemDescription field contains keywords which indicate the disposition of the item (see RMA LineItem Disposition).

RMA SPECIAL DB ITEMS

Special purpose items can be entered into the database as RMA items. An RMA item is used to allow the customer to select a product to be returned whether they have previously placed an order for the product or not. RMA Items are useful for businesses which buy equipment from customers and / or allow a customer to return an item without identifying the original order it came from.

RMA Items are identified in two ways: (1) The ProductType of an RMA item must EQUAL the reserved keyword: "I-RMA" defined by Application("RMAItemTag") (2) The SKU must be set to the same keyword + the SKU of the original DB Item or type of item being returned. (see also: Application("RMAItemTag")

Example of SKU:

RMA LINEITEM DISPOSITION FLAGS

RMA AltItemDescription field contains keywords which indicate the disposition of the item. This field can contain any of the keywords (flags) listed below. The keywords listed in RED are manually set by the store (employees). The keywords listed in BLACK are automatically set by the system.

These flags are set using the RMA Order page. The flags displayed on the RMA page after an order has been released for processing and completed processing (i.e. ProcessStep > 16) can be used to determine which flag was originally selected before the order was released for processing. For example: if you see the flag RMA-FINALIZED-ACCEPTED this means that RMA ACCEPTED was the disposition flag that was set when this order was released for processing.

RMA-ACCEPTED	This flag is set by the store manually after inspection of the product. The return has been accepted and a full credit will be issued.
RMA-FINALIZED-ACCEPTED	This flag is set by the system and indicates the disposition of this item has been processed by the system.
RMA-REPAIR	This flag is set by the store manually after inspection of the product. The return can be accepted for less money; an "adjusted trade offer" is issued.
RMA-PENDING-REPAIR	This flag is set by the system and indicates the disposition of this item has been processed by the system and that an "adjusted trade offer" has been issued.
RMA-PENDING-REPAIR-ACCEPTED	This flag is set by the store manually if an adjusted trade off has been accepted, by the customer when responding to an ATO via an offer-webpage generated by the system or (optionally) automatically if the acceptance period has expired.
RMA-FINALIZED-REPAIR-ACCEPTED	This flag is set by the system and indicates the disposition of this item has been processed by the system and that an "ATO" has been accepted.
RMA-PENDING-REPAIR-REJECTED	This flag is set by the store manually if an adjusted trade off has been rejected. This flag can be set either using the RMA Order Admin page OR by the customer when responding to an ATO via an offer-webpage generated by the system.
RMA-FINALIZED-REPAIR-REJECTED	This flag is set by the system and indicates the disposition of this item has been processed by the system and that an "adjusted trade offer" has been rejected.
RMA-REJECTED	This flag is set by the store manually after inspection of the product. The return is rejected. The rejected flag is all or nothing for an order. If any item in an order is flagged as rejected then the entire order is rejected. Rejected orders should be voided after the order has completed processing and is set to ProcessStep code = 18.
RMA-FINALIZED-REJECTED	This flag is set by the system and indicates the disposition of this item has been processed by the system.

RMA EVENT DATE STAMPING

Certain events are date stamped in the database:

CONFIGURATION

SendSafe global.inc.asa file:

SendSafe storefront.config file:

STAGES / PROCESS STEPS

There are several stages in the RMA Process. Each stage is defined by "ProcessStep" in the OrderPostProc record.

MANUAL STAGES FOR HANDLING OF RETURNED ITEMS

When an item is received for return a number of steps should be followed. Some of these steps will result in automated actions being taken by the system.

OPTIONAL STAGE #11: If a return container (and /or physical shipping instructions) has been sent to a customer the ProcessStep for the order is advanced to #11 (see stages above for more info).

STAGE #13: Once a returned item has been received by the shipping/recieving department (but not yet inspected), the ProcessStep for the order is advanced to #13 (see stages above for more info). This step advancement would typically be done by a STEP ACTIVATION page.

STAGE #15: When ready to inspect RMA items for defects and completeness, the processStep is advanced to #15 (see stages above for more info). This step advancement would typically be done by a STEP ACTIVATION page. The disposition of the item must have been previously entered into the OrderLineItem record. An optional comment can also be added/appended to the comment field for the item. For "adjusted trade offers" - the flag on the lineitem is changed manually by the store to RMA-PENDING-REPAIR-ACCEPTED or RMA-PENDING-REPAIR-REJECTED depending upon the decision of the customer. These changes are made in the RMA Order Admin page.

STAGE #16: The order is released for processing by pressing the Process Order button on the RMA admin page.

AUTOMATION

1. RMA Request Confirmation E-Mail with instructions and RMA# is sent by the system once a return request is received by the system. (see step code #10).

2. RMA Return Packaging material has been sent to the customer confirmation E-Mail is automatically sent by the system when it finds a step code of #11 for an order.

3. I-CRM Nag E-Mail is sent by the system to the customer when the return has not been received for N number of days.

4. RMA returned Items have been received Confirmation E-Mail is sent by the system once the returned items are checked in by the shipping/recieving department (but not yet inspected).

5. Return Disposition handling is performed on items once the disposition is flagged after the items have been inspected.

6. RMA Items Reinventory is performed on items once all items are finalized disposition flagged and an order is in step#18 (completed).

RMA SHIPPER / PACKAGING MATERIAL JOB

RMA Return Packaging material has been sent to the customer. A confirmation E-Mail is automatically sent by the system when it finds a step code of #11 for an order. The system checks for RMA orders (i.e. orders with a step code of #11. The rate of checking is determined by the scheduling of the RMA Packaging Material job. When the system finds orders with a status code of #11, it automatically sends out confirmation e-mail and then bumps the step code #12 (an idle state).

This job sends e-mail notices to customers that RMA Return (container) Packaging material has been sent to them.

This function is run by a JobQueue job which looks like the example below:

Notes:

• All e-mails will be ASCII text only.
• This job should not be run more than once every few hours (recommend that you run this job every 4 hour).

I-CRM RMA NAG JOB

I-CRM Nag E-Mail is sent by the system to the customer when the return has not been received for N number of days. The system checks for RMA orders pending returns (i.e. orders with a step code of #10 or #12 depending upon whether you are using the optional Shipping Material Step#11). The rate of checking is determined by the scheduling of the RMA NAG job. When the system finds "old dated" orders with a status code of #10 or #12, it automatically sends out confirmation e-mail and sets the NagIssued date. The SQL Select logic used to pick orders for this NAG E-Mail is configurable; as a result, this means that several Nag jobs can be run concurrently, which each looking for different conditions to send a NAG e-mail.

For example: A NAG job could be looking for Step #10 and NO NagIssued date and a difference of greater than 10 days and less than 15 days between NOW and the OrderDate.

For example: A NAG job could be looking for Step#12 and A NagIssued date with a difference of great than 20 days and less than 22 between NOW and the NagIssued date.

This job sends e-mail notices to customers that their return has not been recieved yet.

This function is run by a JobQueue job which looks like the example below:

Notes:

• All select statements MUST include a TOP clause. The TOP clause should be set to approximately 50 to 100. This sets the max number of orders to process each pass (max value = 500)
• All e-mails will be ASCII text only.
• This job should not be run more than once every few hours (recommend that you run this job every 4 hour).

RMA ITEMS CHECKIN JOB

Items Received Confirmation E-Mail is sent by the system once the returned items are checked in as received (but not yet inspected). The system checks for RMA orders (i.e. orders with a step code of #13. The rate of checking is determined by the scheduling of the RMA Checkin job. When the system finds orders with a status code of #13, it automatically sends out confirmation e-mail and then bumps the step code #14.

This job sends e-mail notices to customers that the returned products has been received (but not checked yet.

This function is run by a JobQueue job which looks like the example below:

Notes:

• All e-mails will be ASCII text only.
• This job should not be run more than once every few hours (recommend that you run this job every 4 hour).

DISPOSITION HANDLING JOB

Return Disposition handling is performed on items once the disposition is flagged. The system checks for RMA orders (i.e. orders with a step code of #16. The rate of checking is determined by the scheduling of the RMA Disposition job. Once all items in an order have been flagged and disposition processed, the system will automatically bump the order to Step#18 (complete). See disposition handling job for more details.

Disposition handling includes:

• Sending out consolidated status e-mails
• Sending out consolidated ATO e-mails
• Automatically accepting an ATO if this function is enabled.
• Automatically calculating an ATO price for lineitems (if Price Adjustment Flags are used).
• Automatically finalizing an RMA order.

This job will continue to check all orders with a step#16 and items disposition set to null or any other value other than a flag which contains the phrase "RMA-FINALIZED" ...

Once an order is found to contain step#16 and all items are flagged with a disposition of "RMA-FINALIZED" then this job will bump the order to step#18 (completed) after processing has be completed.

This job will sort orders for processing based on the RequiredShipDate. The sort is descending so the first order to be handled by this function will the order most recently recieved at your shipping dock and then orders working backward in time. This sorting is done to prioritize processing older orders which have not been recieved by your shipping department. Make sure you set param3 (max order processed at a time) to a value that is equal to or larger than the number of orders which are handled by your company in any 24 hour period divided by the number of minutes between each run of this job. Setting this value too low can result in RMA orders being ignored by the system for final disposition for a period of days. A good starting point for this value is 50.

This function is run by a JobQueue job which looks like the example below:

Here is a list of disposition codes and actions taken by the system:

Notes:

• All e-mails will be ASCII text only.
• This job should not be run more than once every few hours (recommend that you run this job every 4 hour).

ADJUSTED TRADE OFFER PRICE CALCULATION

An ATO is automatically generated by the system. The adjustment of the order can be done in any combination of the two ways listed below. Any adjustments to the order must be completed before the ProcessStep is set to #16 (order released for processing).

1. The price of line items can be changed manually using OrderLineItem admin page to change the value (shipping and sales tax can be changed in the order record.
2. Special Price Adjustment Flags can be set for each line item.

Special Price adjustment flags are entered into OrderFlag column of each effected OrderLineItem. The flags are SKU# PostFixes which identify "Adjustment Items." Each postfix flag is enclosed in "{}". There is a maximum of four flags allowed per lineitem. "Adjustment Items" control values which will be used to adjust the offer. For example:

1. If a lineitem with a SKU = "VX100" has a ordersflag = "{BXD}."
2. This would instruct the system to look for an item in the database with a sku of: VX100-BXD.
3. If the item is found, the lineitem has it's price decreased by the PriceEA of the VX100-BXD item.

If adjustment flags are present, they must be contiguous and they must be delimited from other order flags by a comma. Allowable flags are defined using the Application("RMAReturnDefectFlags") and by adding Adjustment items to the DB. Example of flags in an orderlineitem:

If a lineitem has a ordersflag = "{BXD}{TTX}{VVX}." These flags mixed with other flags would look like this:
NOPT,PLSTINSZERO,{BXD}{TTX}{VVX},MULTIADDR

The "Adjustment Item" is defined by its special composite SKU#. The ProductType for Adjustment Items can be anything you want; though we recommend that you set the productType to something like: Application("RMAItemTag")+PRICE ADJ i.e. I-RMAPRICEADJ. This will make it easier to block these items from product browsing (which is typically required).

Zero Cost Limiting of orders will prevent any RMA order from going above $0.00 (i.e. the customer would owes the business money). RMA Orders are negative dollar values which are tallied against positive dollar value product orders. The result is an accurate cash balance is maintained in the database. If sufficient problems / damage are found on a RMA, the refund price can be adjusted all the way to zero. For orders with more than one item, an individual line item can go above zero, however the entire order amount will be limited to $0.00. Zero cost limiting is in effect both during automatic and manual ATO calculations.

Specific "Adjustment Items" can be configured to limit their effect on the price of a returned item. If an "Adjustment Item" contains a SpecialPrice in its record then this SpecialPrice will set a limit as to how low the dollar value of the refund can be reduced by this special "Adjustment Item." For example if an "Adjustment Item" has a SpecialPrice = -1.00 then the value of the returned item (i.e. its refund) will be capped at a minium of one dollar. The use of SpecialPrice insures that a customer will recieve this miniumum about for the product when adjusted by the "Adjustment Item."

Examples:

• Setting the SpecialPrice = 0.00 will result in a refund value capped at $0.00 for this lineitem.
• Setting the SpecialPrice = 1.00 can result in a negative refund where the customer could owe $1.00 on this specific lineitem. This combined with zero-cost-limiting is useful to charge customers a $1.00 fee on special problems which can be deducted against other items being returned while limiting the total refund at $0.00
• Setting the SpecialPrice = -1.00 will result in a refund value capped at $1.00 for this lineitem.

*Please note that RMA orders contain negative dollar amounts for each lineitem and the total amount of an order. Because of this intrisict negative value, price adjustements are positive values. Adding the positive price adjustment to a negative order balance will reduce the negative balance (i.e. reduce the amount of the refund).

The default import value for SpecialPrice is $0.00

A special import tool is provided to import item records which are to be used as "Adjustment Items" - click here for information on this import tool.

Example of Adjustment Item SKU = [PARENTSKU]-[POSTFIX]

Notes:

1. The PriceEa of adjustment items can be either +/- a dollar amount. If the value is positive, the adjustment will add value. If the value is negative, the adjustment will subtract value.
2. Sales Tax is not recalculated.
3. Shipping costs are not recalculated.
4. The AckRMACheckIssued DB columns is touched (datestamped) when an ATO is issued.

RMA REINVENTORY JOB

RMA Items Reinventory is performed on items once all items are finalized disposition flagged and an order is in step#18 (completed). The system checks for RMA orders (i.e. orders with a step code of #18). The rate of checking is determined by the scheduling of the RMA Reinventory job. This job will adjust quantities of items in inventory for all the items in an RMA orders which have been flagged as salable.

This optional job moves items back into inventory (see also inventory tracking)

This function is run by a JobQueue job which looks like the example below:

Notes:

• This job should not be run more than once every few hours (recommend that you run this job every 8 hour).