In no particular order - let's run through and then prioritize.
- When searching for ashads, how often are you using the customer part# to search instead of dimensions? What about Job Reference?
- There’s a single label comment per master order going forward – will this be ok going forward since you won’t be using the label comment for customer part# or po info?
- We won’t be converting pallet info (pallet type/pkgs per pallet/pallet height/pallet weight) because these fields are no longer a part of the configuration … this data will have to be stored as a customer preference or built up again on orders. On the new site, do we need to move pkg comments forward to the new order when an ashad quote goes through checkout in case this is item-specific and not set up as a customer preference? Today, this info naturally moves forward with the configuration.
- There are 2 fields on the quote line screen: ‘price per lb’ and ‘lb per uom’ – are these used?
- Special Instruction Up-charges –
- Are they limited to the Inside, Liftgate, Tailgate, Residential (possibly 1 or two more carrier assessed charges) … and Export Pallets?
- My understanding is that Liftgate, Tailgate, Export Pallets are only for LTL while Residential is for both.
- For BW orders what logic is employed in allowing/disallowing these Instructions or the related charges?
- Are we comfortable charging a single flat rate for all of these services (no variation per carrier or per warehouse)
- Call / do not call - RE price discrepancies
- No overrun - run recent decisions by T & M - Re: Preference Structure
- Full gauge findings & recommendations - Full gauge preference
- No cradlepack findings & recommendations
- Ship & backorder preference
- Upcharges - WORK IN PROGRESS
- Process for capturing customer part numbers and descriptions for stock and MOD, in the moment, and preferences for printing on labels and pack slips via web screens– is this within scope for first release? (Will we “break” anything if we do not address it in the web interface?) - WORK IN PROGRESS
From IT
- c/e requests – is it important to continue the one to one relationship between a c/e request and an order or quote? If we combined multiple quotes/orders on a single request, how would they put individual trx on hold? If individual requests, what is start/stop time of each request?
A (10-30): We probably do not need to continue the one to one relationship. RE on hold - Right question, wrong time. We need to do further analysis. May be some opportunities to leverage web functionality (sharing, saved carts, etc.) Person who put on hold should not necessarily be person to resolve. Orders on hold could perhaps be resolved by customer online. e.g price discrepency - CE shares cart, customer can log on and check out. Need to preserve visibility, traceability.- If a quote is put on request hold, what kind of change(s) would they make to the quote when they recall the onhold request? Zip Code, Quantity, etc?
A (10-30): We didn't end up discussing this because we didn't resolve how c/e requests will be created for multiple transactions. If a c/e request won't get them back to a trx that is onhold, then they will have to use Godzilla search. I would like to leave this one open for now.
- If a quote is put on request hold, what kind of change(s) would they make to the quote when they recall the onhold request? Zip Code, Quantity, etc?
Resolved (resolution - for now)
Worst case label scenario (2 PO, 2 part numbers etc.), using new Bartender software - will it all fit? If not, what then...
A: It will all fit
We need to confirm: When a saved MOD is returned to the widget, will we also return a) YMAC results and b) Godzilla results?
A: We will return YMAC, not GodZilla. This has been noted on Saved Items page.
Order Source – What do they enter on sales orders that aren’t being created from an email or fax (ie, phone call/other). Do they enter catalog#? Are the still running daily order report by order source?
We want to know source phone, fax, email, web; but we don't want CE to have to enter it every time. We will control the setting of an order's source behind the scenes (based on c/e request source).
Duplicate P/O Popup … is checkout too late? Do we need to ask for the P/O# to check for dupes on c/e request, cart, somewhere else?
A: No, it is relatively infrequent; for MODs Godzilla results will show recent order on same PO. We DO want a duplicate PO check for web orders too (today it is CE only).
Must Ship Today Flag – need to look up my notes on this. Did we decide to give c/e a checkbox during bundling?
A: Customers and CE will have a flag, but we will only offer during a specific window. In stock situation - must ship today. "Must ship on or before." Up to 11 am it says today's date. 11-3 on or before tomorrow's date (+ must ship today choice in alternatives). after 3 tomorrow's date - no must ship today choice in alternatives. Owen to have Steve mock up, add notes later. DONE.
Alert Messages – could be moved to c/e request screen with exception of alerts for a shipto (we won’t know shipto yet). Have you identified how many alert messages are by shipto?
A: Our goal is to eliminate all alerts. Let's discuss only if we still need some alerts.
When/how often are order discounts overridden (to give a web discount)?
A: CE needs ability to add 1% discount (and only 1%) - via checkbox. I have relayed this design addition to Steve.
Credit Checking – what do they do (if anything) when they see that an order has gone on credit hold?
A: CE always continues with the order. CE better off not seeing it.
Brandit ‘Customer Information’ from header Options Menu – is this used anymore?
A: 'no' - don't need to worry about this any longer