Laddawn.com : Thursday web jam

Meetings at 1:30 pm

Part 1 is a roundtable update, with updates on IT, CE, UI and Marketing. Part 2 is set aside to address questions noted during Part 1.

Notes from Web Meeting of 2/13/14

Ladd, Dawn, Owen, Cathy, Jim

Decided to postpone the following functionality for initial release (in favor of the very best go live date):

Avante work to alter Sales Order Entry and Display to offer Master User functionality. CE/CR will use existing tools to retrieve Sales Orders for review or change.
Displaying red marker flags in the widget for required fields. Required fields will be communicated using words.
Special Logic MOD CPU's that can not be made in the local CPU warehouse. Recognition of this issue will be achieved in the way it is achieved today.
Using the Banner Search for MOD Item or Customer Part Number look ups. Logs will be included in the next release.
Development of new forms for Acknowledgements and Quotes. We will make small needed changes to existing forms and enhance our forms formats and capabilities later.
Shipping Notifications. Logic will be included in the next release.
Pricing Discrepancies logic. Discrepancies will be handled just as they are today for initial release and new logic will be included in the next release.
Random Repeat Plate Sorting. We will implement as initially developed and will include most recent design in the next release.
Residential and Limited Access preferences. We will implement as initially designed and will include the most recent design in the next release.

Notes for Part 2 portions

2-7-2014

Shipment confirmation email - we looked at the design. Everyone thought the overall design was good, but details like whether/how to include tracking links, shipped via, partial v. complete, dropship PO, etc. were tabled for Owen Richardson and Steve Borowick (Unlicensed) to work on offline.
Is there an end in sight for 000 comments? Yes. For the stubborn few comments that remain that we need to accommodate, we're going to develop a free form comment box for Checkout and the User Preferences area, that only Tina and Meme can use. Customers will be able to see these comments, once entered, for reassurance. We'll need to train customers who are used to entering free form comments online to take advantage of all the new options they'll have in user preferences. Susan will work with Tina, Meme, Owen and Mark on some other comments that should probably be handled some other way, but this effort can be spread out over time leading up to launch. The remaining focus will really be on ensuring checkout and user preferences (and other screens if appropriate) address the programmable comments.
Judy asked if we still need an "on hold quote warning" - a warning that shows up when CE calls up a quote to work on that someone else has put on hold. This comes into play mostly on pricing issues. We decided that although the warning is helpful for CE, it was not absolutely essential; we'll take a "wait (until after launch) and see approach."
This led to a broader philosophical discussion about the nature of design changes we are willing to consider from here on out, as whether it makes sense to continue to have these meetings.
- Ladd indicated that except for a few odds and ends, the design work is essentially done. We'll never launch if we strive for perfection. We've got a really good design and we need to make it work, rather than try to address gaps between how we do things today in Avante and the new site, which could delay the launch. When we launch, mistakes will be made (for example, if we forgo current features like the 'on hold quote warning'), problems will arise - but none that we can't easily recover from (such as issuing the customer a credit); we'll note them, address them, move on, and continually improve.
- We could even forgo some of the design work we've already done, such as Godzilla - if that gets us significantly closer to launch and does not cause too many headaches for CE.
- Given all of this, we probably do not need to have this whole group keep meeting every week. Rather, we will meet only on an as needed basis, should serious problems or challenges arise. The IT group has developed a good sense of what will or won't fly; it now has carte blanche to use its judgment to decide which issues require a group discussion, and for those that don't, to come up with solutions to problems on their own, without having to seek everyone's buy in.

1-30-2014

Every time marketing adds a new product category (e.g. tamper-evident zip tops), it needs to give certain info to IT to properly incorporate it into the widget menus and rules. Although there are some data elements and rules that Marketing can enter into Avante themselves, there are some aspects of adding a new product that only IT can handle. Before anything is published to a catalog, IT will need a certain amount of lead time to ensure the new category is properly coded into the widget. IT and marketing need to jointly develop a repeatable process that includes a checklist of steps. Owen Richardson to ensure IT has all the info it needs for any new product category added since black conductive.
Moving items from one cart to another, or some variation on that, that would enable CE to do a batch of quotes one day, save to a single cart, and convert some subset of those quotes on another day, without losing the quotes not being converted. (Still assuming we don't want CE to save to saved items list.) Moving items to another cart was deemed confusing and unfamiliar. "Save as" is out because it could lead to placing the same live quote in more than one cart. "Order only the checked items" was discussed, but deemed uncommon and confusing also. Another solution discussed was to prompt to save item or put in another cart when deleting items out of the cart. Each approach had pros and cons, and we decided any of them might undermine what Ladd envisioned, so we decided that IT would continue to discuss internally and we'd discuss as a group next week when Ladd is back.
In part 1, Owen discussed his work on drafting partial shipment notifications. Cathy and others had questions about the look and feel of such notifications - Owen Richardson and User c0361 to get together to discuss and determine next steps.

1-23-14

Random repeat price change, for now for both old and new sites: If width > 28”, add a 12% upcharge (put 12% in table so can be easily changed). This is based on the total order value (except for shipping$ and miscellaneous$ (discount)). At some later date, we would also like to increase the minimum order qty for jobs < xxxx lbs.
For ziptops (marketplace), if we find an exact stock match, don’t show a marketplace MOD result.
1. Zip top broad searches can produce results that are technically "broad" but actually pretty narrow - e.g. item 3550/3550-A, import v. domestic. Are we OK with there being no MOD YMAC result? Yes we are, because the MOD will always cost more, take longer because MOD is marketplace.
2. What if there’s one exact stock match, that’s an import, and the YMAC MOD result is more expensive (and of course will take longer) – what about the customer who really wants a US-made product and is willing to pay more? We want to suppress the MODs there as well; customers can CALL CE if they really care.
Where will CE land after placing an order? (Noted on Checkout > 5. Summary - COMPLETE.)
1. Regardless of who is placing an order - CE or the customer - after clicking place order you will get an order confirmation pop-up; the pop up's background will remain as the order summary page.
  1. If CE is placing the order (any dollar amount), or the customer is placing an order under $100, closing out of the pop-up will return you to the Shop page.
  2. If the customer is placing an over $100, the pop-up will return you to the Giving page. Once done with the Giving page, we will return the user to the Shop page.
Action item:Steve Borowick (Unlicensed) needs to design autocomplete for addressing - applies to both types of sharing addressing order confirmations. See X - Auto Complete.
The order history tracking pop-up window will group shipments by bundle, as opposed to line, as is now depicted on the specifications page; it will still included unshipped - "expected" - bundles. The overall design is still valid, but the groupings need to be different. (Noted on Order History - COMPLETE.)
The share interface on the staging site, either as designed or as coded, is not showing off this key functionality as we had hoped; it's also spilling below the fold and not scrollable. We revisited why and whether the share interface needs to be in a modal v. inline, and if putting it back to inline would help. Having it as a modal mainly had to do with forcing the user to make a deliberate choice to complete the action or abandon it; if we keep it inline, we have to determine all sorts of rules for preserving state, etc. if the user clicks out of the sharing area before completing the action, and we don't know their intention. Decided to make a go of it in the modal. Action item:Steve Borowick (Unlicensed) to make a series of tweaks to the modal design.
A live quote cannot be in more than one cart or order. What happens when you have a live quote that is only in a cart, and the user or CE attempts put it in another cart, with the same zip code. Discussion was inconclusive; there was confusion over the exact scenario(s) under discussion, as well as some discussion of a solution being a pop-up question similar to what you get when you return a saved item to the widget and make a change (confirm the user's intention). Action item:User c0361; Judy Ascensao; Jim Maloy; User df0f1 to define the issue so everyone has a clearer understanding and propose solution.
We've agreed before that CE will have their own carts, i.e. if CE creates a cart on behalf of a contact (Bob's cart authored by Meme), it's separate from the contact's own active cart (Bob's cart). This will prevent conflicts. But while CE is actively working in a new cart, should we automatically name and save these carts? At first the answer seemed to be yes, but then complications arose. Will they appear in the contact's saved carts list while being worked on, or only after CE has completed its work? What should the name be? What's useful for the contact v. what's useful for CE? We agreed this question wasn't so simple after all. Action item: the group that's working on CE workflows will add it to the list.
When there is a price discrepancy, just the sub-order(s) that have price discrepancies will go on hold, not the entire master order. So if a stock sub-order goes on hold, don’t put the MOD sub-orders on hold, and vice-versa. If the customer deliberately bundled a stock item with a MOD, the whole sub-order will go on hold.
When an order is cancelled due to customer inaction, we will send a confirmation. Action item:Owen Richardson to draft.
Upcharges:
1. Heat treated pallets: This was close to being resolved via email; needs to be documented. We discussed that purchasing will be emailed when pallet > 48”. Also, if the order’s lead time is < 10 days, change the lead time to 10 days (we need time to get these pallets in). Q: Is this phase II??? JM-I think we agreed that since the process of recongnizing the actions around Export Pallet changes was one that is in place today and generally works, we were willing to let this be a Phase II action item. Action item: Susan Parker (Unlicensed) to review, follow up on loose ends if any, and document here: Upcharges.
2. Residential deliveries - action item: UPS/Fedex charge around $3 per package for LTLTL (small package count) residential shipments. Because we cannot reliably predict number of packages in such shipments at this time, User c0361 to follow up with Leo to see if he can come up with a per lb rate to be used for LTLTL (small package count) shipments.
Shipping notifications - who gets them and when do they go out? The contact who placed the order gets the notification; if they cc'd others on the order confirmation, they can forward shipping notification if they choose. Notifications will go out as close as possible to when the shipment actually leaves the building - during the Invoice Update process in the evening. Owen Richardson to draft notification language.

1-16-14

We are no longer interested in accommodating customer-supplied plates.
CE 1% web discount will be a checkbox on the order summary page.
User df0f1 handed off entry of YMAC rules to User 8c183 and User 82550.
QA uncovered some design flaws (and bugs) in the way the shop widget level 3 print plate menu is working. Steve Borowick (Unlicensed) showed some design tweaks. There is more that we could do to improve the UI, but that will be postponed to release 2. Steve is capturing the tweaks here.
There are 3 main objectives for Godzilla results:
1. Support CE's need to ensure they're finding the right item for customers, who often assume CE knows key details that they may omit from their requests or get wrong.
2. Minimize duplicate transactions. Customers may submit requests for the same transaction more than once, which may be fielded by different CE and sales staff.
3. Provide shortcuts that expedite work. For example, begin with a "needle in the haystack" search, and quickly find the right item in order history, get it reordered without having to re-do all the instructions.
What happens to an item in a cart that was not saved to the saved items list, and the cart expired or was deleted? It lives on in Avante, on the Island of Misfit Toys, and will show up in Godzilla results - it's location will be "Expired item." Clicking the link for these items will bring you back through the widget.
If I do a search and get a fresh, unnumbered made on demand result, and then I put it in a cart or save it, system numbers it MOD1234. Then I return to the widget later, and run the exact same search, the results will return MOD1234 as an exact match. This item will NOT show up in the Godzilla result as an item in a cart or saved items list, because it is already the exact match that Godzilla is comparing other items to. However, if it was ordered, it WILL show up as a past order. True? JM - I believe this to be true,
Within Godzilla, "Active Cart" really means a cart that is active and has not been named yet and put in the Saved Carts list. If a cart happens to be both named, and active, it will just show up in the list once as a named/saved cart. True? JM - I believe this will show up as the Active cart. All contacts in a bill to (or CE logged in on their behalf) will be able to see all of each others' Godzilla matches, including all active/un-named carts. The "show only my items" checkbox will default to unchecked for both CE and contacts logged in as themselves. If a contact wants to prevent some or all colleagues from seeing their stuff, they will be able to indicate that in user preferences; but the initial default setting for all users will be for all godzilla results (and filtered lists - saved carts, saved items, order history) to be viewable and accessible by all contacts within a bill to.
CE's standard practice when quoting MOD for customers will be to put items in carts, save the cart, and share the cart with the customer they are logged in as. Q: What if quoting multiple items to the same zip code? Will they create separate carts or put all in one cart? There was some discussion of this, but I do not recall resolution, or is it still TBD? If so, we will resolve in upcoming meetings. JM - I don't think there was resolution but think ti might be done either way based on circumstances - namely, are the quotes random or relevant to one another?
What will display in order history, when the user clicks the summary link? We decided the user will see an exact replica of the checkout order summary, albeit with a master order number (and sub-order numbers?)
1. Q: What happens when the customer requests change to order? (Sales order changes; this will continue to be done in Avante for release 1.) A: We decided that the order summary the user sees when they click 'summary' in order history will be appended to show addition, deletion of lines, etc. resulting from CE sales order changes. Q: This is awfully vague. "Etc." is always a bad sign. Do we need to get further into the details here, either now or down the road of what an appended order summary would look like? JM - I am thinking is may make sense for the techincal design team to figure out what we can do and see if it adds up for all of us.
2. Q: What happens if there is a Laddawn fulfillment issue - we do something different bundling-/warehouse-/shipping-wise than what we said we'd do at time of order placement. A: The order history tracking screen will reflect "actual" fulfillment.
3. In the course of discussing this topic, we decided we needed to fine tune how lines/bundles/orders are presented in order history, order tracking popup. Also, some fine tuning of what CE sees in the tracking column - for shipping portals that CE can login to, but not customers, provide a link, which automatically passes our credentials and brings CE to the shipper's online tracking. Include PRO #. Q: Also, RE 9-b above, do there need to be any visual indicators that what we did was different from what we said we'd do, or do the "actuals" just speak for themselves?Susan Parker (Unlicensed) to coordinate. JM - I am thinking we might want to give them the actuals without a lot of fanfare ... as I fear it could become or feel like one of those "We suck, we couldn't do what we originally promised" things.
Discrepancies and emails: We will use something more user-friendly than "pack-out" or "put-up" - let's call it count per case or count per roll. If the price discrepancy is really huge, the transaction will be put on hold and CE will call customer. Likewise if there is more than one type of discrepancy. I.e., we're not going to have the preference-driven hold-release logic kick in.

1-9-2-14

Addressing in Shared Items/Shared carts. The screen is a large pop-up to begin with; an additional pop-up will not work well. A drop down menu has drawbacks too. We decided addressing will be via typing in input box, predictive auto-complete. As the user types, we will recognize both name (dawn) and email address pre-fix (dseiple@...) from the store of contacts associated with the user's sales organization. Susan Parker (Unlicensed) will capture on Sharing change page.
Adding an item from search results to Cart: Ladd felt that the 3-radio-button pop-up about conflicting carts was a bit verbose and overwhelming. (But not the 2-radio-button pop-up?) He might like to see a message upon log-in reminding users that they have an active, unsaved cart with X items in it, so they know that before they start a new search. (But we still need to direct the user some how if, despite this message, they attempt to add an item w/X zip code to a cart with Y zip code, right? If so, do we need to make changes to the verbiage/design of those boxes?)Owen Richardson, Steve Borowick (Unlicensed) to resolve.
We decided some tweaks were needed for the order summary page. Steve Borowick (Unlicensed) to capture these on the Order Summary page.
1. Change verbiage to: "Order name"; "Copy order summary to:"
2. Give pop-up warning for entering a non-contact email address, to help avoid untintentionally sending a copy of the order with Laddawn pricing to a distributor's end user.
3. "Copy order summary to..." will pre-fill based on a) contact 1 (Jen) placing contact 2's (Bob's) saved item in a cart, or checking out contact 2's (Bob's) saved cart; and b) pre-set notification preferences (Jen always wants to copy Jim on her orders.)
4. The method for adding recipients to the input field will be the same as for addressing in Shared Items/Carts (item 1 above).
Godzilla (Steve Borowick (Unlicensed), please make design revisions and capture the following specs on the Godzilla page:
1. To get a Godzilla result you need to enter all required dimensions including gauge; but gauge matches in Godzilla will still include items with different gauges.
2. If CE is working on behalf of a contact, they will automatically see all of the Godzilla matches for the bill to that the contact belongs to; this includes multiple active carts if the bill to has multiple contacts with active carts open. The scope of results a customer contact will see will be driven by preferences (I think this requires fleshing out some more - I am not clear on what the preference would be... "Always show Betty's stuff in my Godzilla search results "???? Are we talking about all contacts or just master users? What am I missing? Does a list filter at the top of the Godzilla list make more sense, similar to the filters we have for saved items/saved carts/order history?).
  1. UPDATE (1/14): We decided that the Godzilla results will be based on matches from the entire bill to organization for the contact, whether the contact is the one logged in, or CE is logged in on their behalf. The Godzilla results need a checkbox that will enable the user to filter the list down to just their matches - something like "Show only my matching items...." (exact verbiage TBD). If the bill to has matches, but the contact does not, the screen clears and a "no match" message appears (verbiage, design TBD).
3. We revised the hierarchy as follows:
  1. There are just two levels - 1) location: active and saved carts; all other locations, intersorted, not separated as they are now; and 2) date (reverse chron).
4. Mention was made of the column heads being sortable. We concluded this would be counterproductive. Some of the columns (ie differences and tags) don't really lend themselves to meaningful sorting, and sorting is further complicated by having two nested hierarchies.
Workflow, spinning off requests, junk drawer, BS box, etc. We identified some (Susan Parker (Unlicensed) has scheduled meeting with Judy, Jim, Cathy and John to work on these questions to carry the conversation forward next Thurs.) UPDATE (1/14): The meeting was held; progress made but many questions still unresolved, further analysis needed. Judy, John, Jim, Cathy to meet again this week; Susan to schedule another meeting 1/21.
1. CE requests for transactions that can be completed on the web will be initiated via new, generic request type. Even if the fax or phone call involves multiple “transactions,” CE only has to open one generic request to get going with them on the web. (Pretty much as documented in embedded PPT here.)
2. Behind the scenes, multiple requests by transaction type will automatically be spun off when CE closes out of the call/fax or whatever that involved 1 or more web transactions. This is the easiest to program for Release 1, yet still gives CE a more efficient process for handling transactions.
  - Do we need to spin off requests for lookups (price inquiry, stock check) too? If so, how? Would we do this only when the lookup had to go onhold (eg, price inquiry leads to request for price override).
3. Best practice for CE when quoting MOD: put in a cart, save the cart, share the cart with the contact. If on the phone, ask permission to save the item.
4. How long do saved carts live? If a cart containing a MOD expires, does the MOD live on? Does it continue to be findable by CE and customers? What means of searching will be available? Where would they turn up, in Godzilla? Saved items/pricing history?
5. What is the scope of carts (and saved items and order history?) that Godzilla displays when CE is logged in on behalf of a contact? Just that contact’s or the entire bill to’s? I think the answer was the latter.
6. On what screens will the workflow drawer containing the BS boxes appear? What is its meaning if it appears on the search results page? Will its contents (workflow routing choices) be dynamic, depending on what screen you’re on? How will the BS boxes be associated with specific transactions, such that they get tied in with the separate request that gets spun off? Are we going to be able to get the recipients of the routing request directly to the screen where the hold was initiated? (I.e., how will Mark get to the Cart that was put on hold?)

1-2-2014

Judy raised a concern that furniture bags need a "you should know" message from the current site to carry over to the new site as a tool tip. After the meeting this generated some discussion about tightening up tooltips in general. Owen Richardson and Steve Borowick (Unlicensed) to document any changes that are made here.
User 82550 asked about changing random repeat print jobs from 'made' to 'bought' orders. The current process requires placing order, finding vendor who will take job, then cancelling order and recreating as NS-bought. We ultimately concluded that CE will convert these quotes, but place them on hold and route them to David (Wholey?) who will release the order as either made or bought, thus generating only one order and order acknowledgment and eliminating need to cancel, etc. This can be put in place today.
Export pallets larger than 40 x 48 - given low volume of orders, it does not make sense at this time to fully automate selection of size, pricing and lead time. Compromise is for any order with an item with dimensions over 48 inches on an export pallet to kick off a workflow to Diana. We will tilt aggregated average pricing to what Dallas is paying. Owen Richardson to follow up with Diana.
Susan Parker (Unlicensed) to ensure that a comment automatically goes on work orders for export pallet jobs to NOT use untreated wooden slats. Susan Parker (Unlicensed) to touch base again with Corey and Rich about what to use in place of wooden slats if anything (extra shrink? cardboard?), and whether any other customers have requested no slats for non-export jobs.
Susan Parker (Unlicensed) and Susan Parker (Unlicensed) to follow up with sales on a handful of customers with 'layer with corrugated' comment. See slats and corrugated for background.

12-12-2013

John announced that part numbers CAN be added to locations that are tagged on the fly in the Saved Items dialog box. In addition, when the user gets to checkout, and is presented with location that matches their zip, they will also see any 'unassigned' locations (locations w/out zips, from the location-tag-on-the-fly in Saved Items). Steve Borowick (Unlicensed) to capture this.
"Call on backorders" - handle in manner similar to price discrepancies? (No more calls. Just: release order, no special contact/email and hold order for 2 hours, then release/email and hold order for 24 hours, then cancel.) The preference for the latter two choices is a preference that should be set by CE only at the bill to level, and be overridable at the contact level. Note - this applies only to orders being placed by CE on behalf of customer. If customer is placing their own order and chooses a backorder bundle, this order-hold logic does not kick in. "Backorder" does not include made items shipping complete within 72 hours. this is really just outside/imports where the b/o exceeds 72 hours. The verbiage of the email will be along the lines of 'check out what we've done, and call us (w/in 2 or 24 hrs) if you have concern' (v. the straightforward approve/cancel w/price discrepancies). Owen Richardson to work on verbiage for back order and price discrepancy emails?
Hold data - for release 1, we resolved to pretty much replicate the current on hold routing list within a drawer that wold be available to CE globally (the drawer tab would replace the live chat tab, which they do not use). We will do some minimal data analysis though to determine if there are any other hold-types that can be re-engineered (a la price discrepancies). User 57165 to focus in on holds routed to customers. (Owen Richardson, Steve Borowick (Unlicensed), Susan Parker (Unlicensed) - to sort out the specifics UI-wise. There are a few odds and ends that need to be handled at a line level, like flagging price discrepancy, no overrun, etc. but these should be minimal.)
Question arose as to whether NS orders will be included in the web order history tab (w/things that cannot be done on web, like reorder, disabled). NS and samples high on phase 2 list. Don't want users to have incomplete order histories. Susan Parker (Unlicensed) will capture on appropriate post-launch feature lists.

12-5-2013

Atlanta logic - discussed some questions Judy had about timing of Atlanta going live (prior to launch of new website).
We will open the widget early next week to a small number of team members - not for full blown QA but to relieve IT of some of the burden of identifying issues, and to get some early insights into how it's working. TBD who will be asked to test it. John P. et al. need to set appropriate expectations RE what is and isn't working and provide clear direction on whether and how he wants feedback relayed.
Saved carts - what happens to the copy of the share messages, when the saved cart disappears from the list (either by being checked out, automatically expiring, or user deliberately deleting)? This spawned concern by Dawn that users will not have an intuitive place to go to retrieve expired quotes that they did not save as a saved item. We noted that Godzilla results should include all expired quotes, not just those from saved items list, but a result set is not quite the same as having a place to go. We talked about not removing expired carts from the list, and having a bifurcated list of carts that operates loosely like Outlook; the carts that are < 30 days are in the first list, followed by a collapsed list of expired carts.This approach was not completely satisfying (for the original question and the concern about retrieving quotes); we tabled this for next week. No changes incorporated into to Saved Carts specs yet.
Saved items, location tagging and duplicate customers. Two types of duplicate customers - 1) non-dupe dupes - customers with several bill to's (e.g. Xpedx), where the name is always the same, even though the address, customer number, etc. is different and 2) actual duplicates - essentially the same customer with multiple records in our system, with only slight variations. For the first group, we don't want to force them to have the city in their name, like Xpedx - Rochester and Xpedx - Cleveland, because that is problematic for many distributors. Instead, in the locations list, we will concatenate customer name, and city in parentheses - Xpedx (Rochester). For the second group, we are going to do a cleanup at some point in the near future; there is a report that Judy can run so CE can clean these up over during the holiday slow time. Judy also pointed out the current website has logic that prevents customers from creating new dupes, which does not exist today in Avante. We need CE to be able to create new ship to's on the web so this logic prevents them from creating dupes too.
We also talked about part numbers in saved items dialog box. They cannot be added for locations that aren’t yet in our system. So when the user has added a new location to the location tag list on the fly, and then they click “add new” below in the part number section, we want them to have a pop-up message saying: “There is no address associated with this company. You can assign an item number at checkout.”
We discussed 'on holds' - how CE puts transactions on hold today in Avante, with an eye towards agreeing on the scope of what we aim to do, and discussing a general approach. The classification scheme was not as robust as Dawn recalled. Nevertheless, as far as scope is concerned, for phase 1, we are not interested in recreating the backend routing/workflow system that works fairly well today for internal 'on holds.' More analysis and conversations with CE are required, to decide what remains in Avante or happens on the web, whether the list of on-hold types can be pared down, whether certain types of 'on holds' can easily be re-engineered (like price discrepancies); and whether the mechanisms for CE to put web transactions on hold live in one screen or a few. But we agreed on some general principles and approaches – for instance, we don't want CE having to go back to an Avante request in the middle of a web transaction to put it on hold - we're them to have a menu, or checkbox, or whatever, that behind the scenes seamlessly links back to Avante and spawns the appropriate emails/workflows in the way they do today.

Saved Items spec will be updated with items 4 and 5.