Hold Until Complete - Revision history

Russ horton: /* Phase 2 possibilities */

2017-01-20T00:37:58Z

Phase 2 possibilities

← Older revision		Revision as of 00:37, 20 January 2017
Line 31:		Line 31:
	*No specific option to de-allocate is included although an item or order can be forced onto back order which does deallocate		*No specific option to de-allocate is included although an item or order can be forced onto back order which does deallocate

	=Phase 2 ~~possibilities~~=		=Phase 2 - CMS 9.0.6=
	*Automate allocations so newly received stock can be committed to current HUC orders (those already saved but not yet fulfilled/released)		*Automate allocations so newly received stock can be committed to current HUC orders (those already saved but not yet fulfilled/released)

			=Future Possibilities=
	*Making the use of HUC conditional based on a global user-specified threshold of Expected Delivery dates for back ordered items (so items coming in soon may be worth holding an order for while others beyond the threshold may not be worth holding an order for.)		*Making the use of HUC conditional based on a global user-specified threshold of Expected Delivery dates for back ordered items (so items coming in soon may be worth holding an order for while others beyond the threshold may not be worth holding an order for.)
	*Treating future ships in a similar way with allocations and fulfillments onto -1 (future shipping vs future fulfillment), perhaps a "Hold Until Date"		*Treating future ships in a similar way with allocations and fulfillments onto -1 (future shipping vs future fulfillment), perhaps a "Hold Until Date"

Russ horton: /* Hold Until Complete (CMS 9.0.5) */

2013-12-10T01:29:49Z

Hold Until Complete (CMS 9.0.5)

← Older revision		Revision as of 01:29, 10 December 2013
Line 12:		Line 12:
	**If the option for 'Partial Orders can Ship' is selected in Fulfillment Manager, but not all items are available, CMS will allocate them to the waiting HUC orders while leaving the remaining items on back order. In this case the invoice remains on hold until all items have been fulfilled and no payment is created until the final fulfillment.		**If the option for 'Partial Orders can Ship' is selected in Fulfillment Manager, but not all items are available, CMS will allocate them to the waiting HUC orders while leaving the remaining items on back order. In this case the invoice remains on hold until all items have been fulfilled and no payment is created until the final fulfillment.
	**When fulfilling the remaining items on an HUC order CMS will set the fulfill date of the invoice to today, allocate remaining stock needed, and create a new payment if needed (the same as any other back order fulfillment) and will remove the HUC hold flag		**When fulfilling the remaining items on an HUC order CMS will set the fulfill date of the invoice to today, allocate remaining stock needed, and create a new payment if needed (the same as any other back order fulfillment) and will remove the HUC hold flag
	*HUC PAYMENTS - CMS defaults to, and we recommend, setting an electronic payment (eCheck or credit card) for $0.00 when placing the order. CMS will create an appropriate payment using that payment information for the total order amount when the order is fulfilled.		*HUC PAYMENTS - CMS defaults to, and we recommend, setting an electronic payment (eCheck or credit card) for $0.00 when placing the order. CMS will create an appropriate payment using that payment information for the total order amount when the order is fulfilled. That said, you can take deposits/payments on HUC orders. The HUC hold type is ignored for payment processing so if you desire to apply a down-payment to an HUC order (e.g. layaway), it will be processed today without have to set Bill Delayed or marking the order as shipped. We have noted though that some companies have found reporting issues with accepting payments against unshipped orders or those on hold so you may wish to test this before starting to accept such payments.

	Orders set as HUC can be reviewed in the Fulfillment Manager under the tab for Invoices on Hold where hold can be individually reviewed and edited as needed.		Orders set as HUC can be reviewed in the Fulfillment Manager under the tab for Invoices on Hold where hold can be individually reviewed and edited as needed.

Russ horton: /* Hold Until Complete (CMS 9.0.5) */

2013-12-10T01:06:51Z

Hold Until Complete (CMS 9.0.5)

← Older revision		Revision as of 01:06, 10 December 2013
Line 9:		Line 9:
	HUC orders are released/fulfilled using the Fulfillment Manager's Back Order processing. This allows you to have a single list of back order invoices, potentially a mix of HUC and non-HUC back orders, and can fulfill FIFO. No added filter is necessary, just click the radio button for All Orders Shown and then the button for Process Orders.		HUC orders are released/fulfilled using the Fulfillment Manager's Back Order processing. This allows you to have a single list of back order invoices, potentially a mix of HUC and non-HUC back orders, and can fulfill FIFO. No added filter is necessary, just click the radio button for All Orders Shown and then the button for Process Orders.
	*Those orders with no HUC flag will fulfill based on settings on the options shown (partial orders can fulfill, partial items can fulfill) and fulfill onto a -2 (or later) invoice as is standard behavior now		*Those orders with no HUC flag will fulfill based on settings on the options shown (partial orders can fulfill, partial items can fulfill) and fulfill onto a -2 (or later) invoice as is standard behavior now
	*Those ''with'' a HUC flag (and no other hold flags) and all items available will fulfill onto the -1 invoice		*Those ''with'' the HUC flag (and no other hold flags) and all items available will fulfill onto the -1 invoice
	**If the option for 'Partial Orders can Ship' is selected, but not all items are available, CMS will allocate them to the waiting HUC orders while leaving the remaining items on back order (the invoice remains on hold until all items have been fulfilled, no payment is created until the final fulfillment)		**If the option for 'Partial Orders can Ship' is selected in Fulfillment Manager, but not all items are available, CMS will allocate them to the waiting HUC orders while leaving the remaining items on back order. In this case the invoice remains on hold until all items have been fulfilled and no payment is created until the final fulfillment.
	**When fulfilling the remaining items on an HUC order CMS will set the fulfill date of the invoice to today, allocate remaining stock needed, and create a new payment if needed (the same as any other back order fulfillment) and will remove the HUC hold flag		**When fulfilling the remaining items on an HUC order CMS will set the fulfill date of the invoice to today, allocate remaining stock needed, and create a new payment if needed (the same as any other back order fulfillment) and will remove the HUC hold flag
	*HUC PAYMENTS - CMS defaults to, and we recommend, setting an electronic payment (eCheck or credit card) for $0.00 when placing the order. CMS will create an appropriate payment using that payment information for the total order amount when the order is fulfilled.		*HUC PAYMENTS - CMS defaults to, and we recommend, setting an electronic payment (eCheck or credit card) for $0.00 when placing the order. CMS will create an appropriate payment using that payment information for the total order amount when the order is fulfilled.

Russ horton: /* Phase 2 possibilities */

2013-12-10T01:01:43Z

Phase 2 possibilities

← Older revision		Revision as of 01:01, 10 December 2013
Line 32:		Line 32:

	=Phase 2 possibilities=		=Phase 2 possibilities=
	*~~Way to handle~~ allocations so newly received stock can be committed to current HUC orders (those already saved but not yet fulfilled/released)		*Automate allocations so newly received stock can be committed to current HUC orders (those already saved but not yet fulfilled/released)
	*Making the use of HUC conditional based on a global user-specified threshold of Expected Delivery dates for back ordered items (so items coming in soon may be worth holding an order for while others beyond the threshold may not be worth holding an order for.)		*Making the use of HUC conditional based on a global user-specified threshold of Expected Delivery dates for back ordered items (so items coming in soon may be worth holding an order for while others beyond the threshold may not be worth holding an order for.)
	*Treating future ships in a similar way with allocations and fulfillments onto -1 (future shipping vs future fulfillment)		*Treating future ships in a similar way with allocations and fulfillments onto -1 (future shipping vs future fulfillment), perhaps a "Hold Until Date"

Russ horton: /* Related Exceptions and Comments */

2013-12-10T01:00:49Z

Related Exceptions and Comments

← Older revision		Revision as of 01:00, 10 December 2013
Line 26:		Line 26:

	=Related Exceptions and Comments=		=Related Exceptions and Comments=
	*Orders that are a mix of future ship and back order items ~~will not~~ be ~~candidates for~~ HUC		*Orders that are a mix of future ship and back order items cannot be set as HUC
	*After fulfillment, there is no record retained to indicate that the order was previously HUC		*After fulfillment, there is no record retained to indicate that the order was previously HUC
	*Reporting changes are being evaluated for inclusion in CMS version 10. Please contact your NHS Support rep to obtain the latest Crystal invoice template if you'll be using HUC		*Reporting changes are being evaluated for inclusion in CMS version 10. Please contact your NHS Support rep to obtain the latest Crystal invoice template if you'll be using HUC

Russ horton: /* Hold Until Complete (CMS 9.0.5) */

2013-12-10T00:59:44Z

Hold Until Complete (CMS 9.0.5)

← Older revision		Revision as of 00:59, 10 December 2013
Line 4:		Line 4:
	In CMS 9.0 we added a Back Order All function to make it easy to force an entire order onto back order, so it can fulfill complete, but it does fall short of allocating stock to an order for the items available now. This prevents the user from being able to fulfill/allocate in a [http://en.wikipedia.org/wiki/FIFO FIFO] (first in first out) manner, in other words, allocating to the customers in sequential order of when they purchased.		In CMS 9.0 we added a Back Order All function to make it easy to force an entire order onto back order, so it can fulfill complete, but it does fall short of allocating stock to an order for the items available now. This prevents the user from being able to fulfill/allocate in a [http://en.wikipedia.org/wiki/FIFO FIFO] (first in first out) manner, in other words, allocating to the customers in sequential order of when they purchased.

	=Hold Until Complete (CMS 9.0.5)=		=Hold Until Complete ([http://updates.newhavensoftware.com/whatsnew905.htm CMS 9.0.5])=
	The Hold Until Complete (HUC) feature works in conjunction both with CMS's existing Hold mechanism and Fulfillment Manager. If an order has any items on back order, CMS can place the order on hold using a new HUC hold type when the order is saved. Whether or not the order is placed on HUC will be based on a new Order Entry option indicating if you want orders with back orders placed on HUC automatically. You can override the default and manually set or remove the HUC flag before or after the order is saved (done from the View Invoice screen for the invoice in question).		The Hold Until Complete (HUC) feature works in conjunction both with CMS's existing Hold mechanism and Fulfillment Manager. If an order has any items on back order, CMS can place the order on hold using a new HUC hold type when the order is saved. Whether or not the order is placed on HUC will be based on a new Order Entry option indicating if you want orders with back orders placed on HUC automatically. You can override the default and manually set or remove the HUC flag before or after the order is saved (done from the View Invoice screen for the invoice in question).

Russ horton at 00:57, 10 December 2013

2013-12-10T00:57:00Z

← Older revision		Revision as of 00:57, 10 December 2013
Line 1:		Line 1:
	~~Specification discussion for a CMS customization being considered.~~

	=Overview=		=Overview=
	When orders are placed on back order, in many situations it will make sense to hold the order until all of the items are available so it can ship complete. The current CMS behavior is designed to support a "ship asap" model which is better for cash flow and inventory movement but causes problems when trying to reduce the number of shipments for an order, be it for shipping expense or desire to deliver complete to the customer.		When orders are placed on back order, in many situations it will make sense to hold the order until all of the items are available so it can ship complete. The current/default CMS behavior is designed to support a "ship asap" model which is better for cash flow and inventory movement but causes problems when trying to reduce the number of shipments for an order, be it for shipping expense or desire to deliver complete to the customer.

	In CMS 9.0 we added a Back Order All function to make it easy to force an entire order onto back order, so it can fulfill complete, but it does fall short of allocating stock to an order for the items available now. This prevents the user from being able to fulfill/allocate in a [http://en.wikipedia.org/wiki/FIFO FIFO] manner (allocating to the customers who requested the items first).

	~~=Phase 1=~~		In CMS 9.0 we added a Back Order All function to make it easy to force an entire order onto back order, so it can fulfill complete, but it does fall short of allocating stock to an order for the items available now. This prevents the user from being able to fulfill/allocate in a [http://en.wikipedia.org/wiki/FIFO FIFO] (first in first out) manner, in other words, allocating to the customers in sequential order of when they purchased.
	~~The Hold Until Complete (HUC) feature will work in conjunction both with~~ CMS~~'s existing Hold mechanism and Fulfillment Manager~~. If an order ~~has any items on~~ back order, ~~CMS~~ can ~~place~~ the ~~order on hold using~~ a ~~new HUC hold type when the order is saved~~. ~~Whether or not~~ the order ~~is placed on HUC will be based on a new Order Entry option indicating if you want orders with back orders placed on HUC automatically~~.

	~~User~~ can override the default ~~behavior~~ and manually set or remove the HUC flag after the order is saved (done from the View Invoice screen for the invoice in question).		=Hold Until Complete (CMS 9.0.5)=
			The Hold Until Complete (HUC) feature works in conjunction both with CMS's existing Hold mechanism and Fulfillment Manager. If an order has any items on back order, CMS can place the order on hold using a new HUC hold type when the order is saved. Whether or not the order is placed on HUC will be based on a new Order Entry option indicating if you want orders with back orders placed on HUC automatically. You can override the default and manually set or remove the HUC flag before or after the order is saved (done from the View Invoice screen for the invoice in question).

	HUC orders are released using the Fulfillment Manager's Back Order processing. This allows ~~the user~~ to have a single list of back order invoices, potentially a mix of HUC and non-HUC back orders, and can fulfill FIFO. No added filter is necessary, just click the radio button for All Orders Shown and then the button for Process Orders.		HUC orders are released/fulfilled using the Fulfillment Manager's Back Order processing. This allows you to have a single list of back order invoices, potentially a mix of HUC and non-HUC back orders, and can fulfill FIFO. No added filter is necessary, just click the radio button for All Orders Shown and then the button for Process Orders.
	*Those orders with no HUC flag will fulfill based on settings on the options shown (partial orders can fulfill, partial items can fulfill) and fulfill onto a -2 (or later) invoice as is standard behavior now		*Those orders with no HUC flag will fulfill based on settings on the options shown (partial orders can fulfill, partial items can fulfill) and fulfill onto a -2 (or later) invoice as is standard behavior now
	*Those ''with'' a HUC flag (and no other hold flags) and all items available will fulfill onto the -1 invoice		*Those ''with'' a HUC flag (and no other hold flags) and all items available will fulfill onto the -1 invoice
	**~~This~~ fulfillment will set the fulfill date of the invoice to today, allocate remaining stock needed, and create a new payment if needed (the same as any other back order fulfillment) and will remove the HUC hold flag		**If the option for 'Partial Orders can Ship' is selected, but not all items are available, CMS will allocate them to the waiting HUC orders while leaving the remaining items on back order (the invoice remains on hold until all items have been fulfilled, no payment is created until the final fulfillment)
			**When fulfilling the remaining items on an HUC order CMS will set the fulfill date of the invoice to today, allocate remaining stock needed, and create a new payment if needed (the same as any other back order fulfillment) and will remove the HUC hold flag
			*HUC PAYMENTS - CMS defaults to, and we recommend, setting an electronic payment (eCheck or credit card) for $0.00 when placing the order. CMS will create an appropriate payment using that payment information for the total order amount when the order is fulfilled.

	Orders set as HUC can be reviewed in the Fulfillment Manager under the tab for Invoices on Hold where hold can be individually reviewed and edited as needed.		Orders set as HUC can be reviewed in the Fulfillment Manager under the tab for Invoices on Hold where hold can be individually reviewed and edited as needed.

Russ horton: /* Related Exceptions and Comments */

2013-12-10T00:36:44Z

Related Exceptions and Comments

← Older revision		Revision as of 00:36, 10 December 2013
Line 30:		Line 30:
	*Orders that are a mix of future ship and back order items will not be candidates for HUC		*Orders that are a mix of future ship and back order items will not be candidates for HUC
	*After fulfillment, there is no record retained to indicate that the order was previously HUC		*After fulfillment, there is no record retained to indicate that the order was previously HUC
	*~~No reporting~~ changes are ~~considered~~ for ~~phase 1 but will~~ be ~~evaluated on a case by case basis as requested~~		*Reporting changes are being evaluated for inclusion in CMS version 10. Please contact your NHS Support rep to obtain the latest Crystal invoice template if you'll be using HUC
	*No specific option to ~~deallocate~~ is included although an item or order can be forced onto back order ~~with currently available controls~~ which does deallocate		*No specific option to de-allocate is included although an item or order can be forced onto back order which does deallocate

	=Phase 2 possibilities=		=Phase 2 possibilities=

Russ horton at 17:15, 3 May 2013

2013-05-03T17:15:30Z

← Older revision		Revision as of 17:15, 3 May 2013
Line 6:		Line 6:
	In CMS 9.0 we added a Back Order All function to make it easy to force an entire order onto back order, so it can fulfill complete, but it does fall short of allocating stock to an order for the items available now. This prevents the user from being able to fulfill/allocate in a [http://en.wikipedia.org/wiki/FIFO FIFO] manner (allocating to the customers who requested the items first).		In CMS 9.0 we added a Back Order All function to make it easy to force an entire order onto back order, so it can fulfill complete, but it does fall short of allocating stock to an order for the items available now. This prevents the user from being able to fulfill/allocate in a [http://en.wikipedia.org/wiki/FIFO FIFO] manner (allocating to the customers who requested the items first).

	=~~Proposal for~~ Phase 1=		=Phase 1=
	The ~~proposed~~ Hold Until Complete (HUC) feature ~~would~~ work in conjunction both with CMS's existing Hold mechanism and Fulfillment Manager. If an order has any items on back order, CMS can place the order on hold using a new HUC hold type when the order is saved. Whether or not the order is placed on HUC will be based on a new Order Entry option indicating if you want orders with back orders placed on HUC automatically.		The Hold Until Complete (HUC) feature will work in conjunction both with CMS's existing Hold mechanism and Fulfillment Manager. If an order has any items on back order, CMS can place the order on hold using a new HUC hold type when the order is saved. Whether or not the order is placed on HUC will be based on a new Order Entry option indicating if you want orders with back orders placed on HUC automatically.

	User can override the default behavior and manually set or remove the HUC flag after the order is saved.		User can override the default behavior and manually set or remove the HUC flag after the order is saved (done from the View Invoice screen for the invoice in question).

	HUC orders are released using the Fulfillment Manager's Back Order processing. This allows the user to have a single list of back order invoices, potentially a mix of HUC and non-HUC back orders, and can fulfill FIFO. No added filter is necessary, just click the radio button for All Orders Shown and then the button for Process Orders.		HUC orders are released using the Fulfillment Manager's Back Order processing. This allows the user to have a single list of back order invoices, potentially a mix of HUC and non-HUC back orders, and can fulfill FIFO. No added filter is necessary, just click the radio button for All Orders Shown and then the button for Process Orders.

Russ horton at 19:18, 15 February 2013

2013-02-15T19:18:03Z

← Older revision		Revision as of 19:18, 15 February 2013
Line 19:		Line 19:

	Additional enhancements include:		Additional enhancements include:
	*Orders set as HUC cannot be ~~returned/~~cancelled and the user will be warned if a ~~return~~ is attempted (HUC flag must be removed first by someone with employee permissions to remove that flag)		*Orders set as HUC cannot be cancelled and the user will be warned if a cancel is attempted (no affect on return of shipped) - The HUC flag must be removed first by someone with employee permissions to remove that flag.
	*Employee permission will be added to indicate who can alter the HUC of an order		*Employee permission will be added to indicate who can alter the HUC of an order
	*Option in Order Entry, (location tbd, perhaps in the Holds UI) to refresh allocation on the order (so if some new stock has become available, allocations can be updated)		*Option in Order Entry, (location tbd, perhaps in the Holds UI) to refresh allocation on the order (so if some new stock has become available, allocations can be updated)