Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/jjknowledgebase.com/wp.jjknowledgebase.com/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-ulike domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/jjknowledgebase.com/wp.jjknowledgebase.com/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-optimize domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/jjknowledgebase.com/wp.jjknowledgebase.com/wp-includes/functions.php on line 6121
Proposal For Notification When Item Becomes Available To Ship. – knowledgebase JJ
Warning: Attempt to read property "ID" on null in /var/www/vhosts/jjknowledgebase.com/wp.jjknowledgebase.com/wp-includes/link-template.php on line 409

Proposal For Notification When Item Becomes Available To Ship.

Proposal Summary 

This proposal outlines the scope of sending automated email notifications to CSRs and Logistics when an item becomes available to ship in sales orders either by inventory adjustment or by creating item receipts. 

Requirement 

Need to update the existing functionality that sends automatic emails when creating inventory adjustment or item receipt listing all the orders in which the items received were back ordered in such a way that the emails need to be listed only the orders in which the received items became available when received the item. 

Deliverables 

  • The existing functionality to send email notifications to CSR and logistics sends the emails with all the sales orders in which the received items (Either by inventory adjustment or item receipt) were back ordered. Because of this, there can be orders in which the items are available and the orders in which the items still back ordered in the email. 
  • We cannot achieve this using the current script. 
  • So, we need to develop a new script that includes the required functionality for this. 
  • In the new script we will include functionality to get all the orders in which the items were back ordered at the time of receiving the items. And then filter out only the sales orders in which these items became available after receiving the items. 
  • The email notification will be sent to logistics and respective CSRs, the email body will contain the sales orders in which the received item/items are available to ship. 

Assumptions 

  • The email subject, email body, table format will be same as before. 
  • We assume that not all the items in the sales order must be available for including the sales order in email, we may include the sales orders in which the received item became available (other items in order may or may not be back ordered when the email was sent).

1 comment

  1. As per my understanding cache is not for storing big schema (data).

    Need to check alternative logic using files for storing data.

    The cache will create an issue in the key. If the key is the same key is used, in the multiple record creation context, you will get the same data multiple times. Must confirm this scenario before using the cache for storing data.
    Need to check the storage capacity using cache.

    Time should be updated to 32 hours, because we cannot update the existing script instead we need to deploy a new script for the functionality.

Leave a Reply to Swathi Krishna K S Cancel reply

Your email address will not be published. Required fields are marked *