Laddawn.com : Holds

Holds emanating from request types that will be on the web in Phase 1 (12,022)	Holds emanating from request types that will NOT be on the web in Phase 1 (8,227) - or so we thought...

… The differences between request types (transaction types/customer intentions) and reasons to put something on hold (pause in completing a request type) are a little squishy. For instance, "expedite," a request type, could also be a reason to put another request type - a quote conversion on hold. (In Avante, I suppose it needs to be a req type if the req to expedite occurs separately, after the quote is converted – and the reqs to expedite may not always be put on hold?)

The back orders request type escaped (045) our attention when we determined which req types would be handled on the web in Phase 1. Not sure if this could be a web transaction. Left it on Avante side for now.

Next steps:

• Clear up questions about request types like back orders and expedite – are they really hold types for transactions to be done on web?

• Determine list of all hold types relevant to new web transactions.  Quick and dirty first pass based on "route to" (32 total)
  TOTAL HOLDS (THIS INCLUDES PRINT ACK, BACKORDERS, AND EXPEDITES) - 13,868

  
  
  

• Identify hold types that could be reengineered out of being a "hold" (a la price discrepancies).
• Spec out remaining hold types that could be addressed via a special CE drawer (or whatever) in Cart, Checkout, Saved Items, etc. while leveraging existing workflow/routing behind the scenes. Make them more intentions-based, so they are more intuitive, and do not necessarily require CE to know where or to whom to route something.