Laddawn.com : Functional Specs - Checkout

Created by Judy Ascensao, last modified on Jan 28, 2014
  1. Multiple Order# Assignment:
    1. Each MOD item will create a new order
    2. Possibly combine stock bundles as long as for same warehouse and have same shipping instructions (ship via method, comments)
    3. A master order# (and file) will be created to link orders from the cart.  We have discussed an alpha suffix (preferable), and .x suffix (could be an issue with order# length if goes past .9 and the extra dot most likely problem for Clippership).  Have also discussed locking SYSTBL NUM*OMN and adding the number of orders we are going to create to the counter before saving).  Master order# must be written to SOHDR.USR?
    4. Show master order# on all customer-facing documents (acknowledgements, sharing email, packslip, BOL, Invoice)
    5. How will the master order# be handled in credit card process - what will show on ccard receipt to customer and on settlement report?
    6. How would credit checking be done?  On grand total of all orders under master order#?  If doesn't pass, all orders go on credit hold?
    7. Must Ship Today Flag - if we decided to merge ship and backorder from primary warehouse into a single order, we must remove the 'must ship today' flag and order comment when going through invoice update and changing date to b/o date.
  2. Fix 'new drop ship' logic on the web to set Ship Via to "BW" for all newly created drop ships (regardless of the ship via on the order being created)  IN 'CREATE SALES ORDER' SPECS FOR WAYNE
  3. From Wiki Shipping/Handling page: We should charge for Inside Delivery, Tailgate Delivery, and Liftgate Delivery.   We had some preliminary conversations about how  this will function and each might show as a check box on the Freight Estimator that translates into a comment for the order and an adder to the freight charge. 10/24 web jam mtg: The comments defined as having 'flat rate' shipping upcharges (everything except export pallets): these upcharges will be added to every order/every shipment of each order.  Need to upcharge columns in the table/comments file: 1 for small pkg (ups/fedex) and the other for LTL shipments. Some of the small pkg upcharges may be 0.00.  Export Pallet upcharges will be calc'd for every bundle based on weight.  MOD bundles should include overrun weight (if allowed).
  4. Make sure 'configurator-generated' comments are still being generated into CFBLD.  The comments moved to checkout (ie export pallets) would have to be written back to CFBLD???  Must check to see if the comment already exists on CFBLD/CFBLD.USR (because of ashads from old config). If already there, don't add again.
  5. Would 'ashad' comments have to be re-entered during checkout?
  6. Where will c/e enter: allow overrun, remove gauge, and customer-supplied plates? 1/16/14 - we will no longer be offering customer-supplied plates
  7. Does checkout process check that the quoted zip code matches the shipto customer's zip?
  8. How will they add w/o comments during checkout (ie, RUN W/ORDER XXXXXX or LABEL END OF BOX)
  9. How will c/e see ashad details (so they know color and other item specifics before re-quoting)? GODZILLA
  10. Enter Quote/Convert Quote in single step is rare DOESN'T MATTER ANYMORE - CONVERT QUOTE HAS BEEN PROGRAMMED
  11. Ashad search - they now use 'customer part#' search more than bag size search - per c/e, this isn't true
  12. Make sure operator code on sales order is the c/e rep when creating orders on behalf of the customer - ON SPEC TO WAYNE
  13. 1% web discount - if c/e is converting the quote on behalf of the customer, no web discount.  If customer, add web discount to order. (assuming automaticing convert quotes). IN 'CREATE SALES ORDER' SPECS FOR WAYNE
  14. Per web jam, pull sales order comments forward when creating an order from an ashad quote ... this would be part of automating convert quote on the web
  15. Quotes requiring print plate pdf upload:Allow Overruns question - preference set by customer (internal users only can set this).  Allow c/e to also set the no overrun flag on an individual quote

    1. We met today on print plate uploads for Random Repeat, and the result was the following:

      1. A quote requiring a new print plate must be alone in a cart.  Add checks to ensure that other items are not placed in the same cart.
      2. Allow anyone to upload the pdf (customer or c/e).  Assign plate# as usual and save the pdf in the plates file
      3. Allow c/e and customer to go through checkout screens, but stop them before ‘order creation’.  Must save all checkout info for the cart for future use once the plate is approved.  Show TBD instead of lead time date.
      4. If c/e, nothing else is required at this point.  They will route the c/e request to Marketing-Plates for Chris to approve.  If customer, send email to the c/e queue and tell customer that c/e will take it from here and they will receive an acknowledgement soon.  Include on the c/e queue email:  Cart Name, Quote#, Plate#, all checkout info.  A c/e request will be created when pulled from the queue and routed to Marketing-Plates for approval.
      5. Once plate is approved, c/e will finish checkout and create the order.  They should be forced to go through each checkout step again to verify data.  We will re-calculate lead time in case the plate approval didn’t occur the same day.
  16. 1/22/14 - Packaging Upcharges (pallet type, #cs per pallet, pallet wgt, pallet, hgt) - are we still charging for these now that they are in Checkout?  If so, same calculations or new calculations?  Currently SOPS9097.3 has this logic commented out and is in AVBP version.  If we aren't going to change this, should AVBP be copied to DBP and put on task?  Do we really need an AVBP version?:
    1. Export Pallet Upcharge - #pallets x per pallet rate ... use same calc for #pallets as we do today (SOPS9097.2).  Export Pallets will be a onetime charge on the 1st shipment for the 1st warehouse on the order.  ie, split shipments between 2 warehouses will be on the same order because they have the same ship date.  In this case, we will calculate the #pallets based on the entire order, then charge it on only one warehouse's invoice.  Apply total upcharge to Cart Total.  Make sure that it will work the way we expect in Avante.  Make sure it will flow correctly if a credit card order.
    2. Residential Upcharge: For LTL - this is a flat rate per shipment.  For Small Pkg, it's #packages x per pkg rate *** how will we calc #pkgs?
    3. Flat Rate Upcharges - these are one per shipment, which equates to the #bundles that we show.  So if stock riding with MOD, that's one bundle/one shipment.  If Ship and Backorder, that's 2 bundles/2 shipments.  Split Shipment - 2 bundles/2 shipments.  Add the upcharge for each bundle that has that shipping instruction selected.
    4. 16 Hours to program??
  17. 10/24 web jam:  Credit Checking will be done on each individual order created (not on whole checkout$).  Try to create stock orders first, then MOD orders (so that the stock orders get out if under credit limit).  11/14 WEB JAM - NOW THEY WANT TO PUT WHOLE MASTER ORDER ON HOLD (EVERY ORDER)
  18. Creating Order - write cart name to SOHDR/QUHDR - will be used as 'order name' on order history. IN 'CREATE SALES ORDER' SPECS FOR WAYNE
  19. Make sure the screen is checking that the 'future date' of a bundle isn't more than 'x' days in future (from a SYSCON).
  20. 10/31 - remove web popup (if it exists on new site) when a must ship today order goes on credit hold.  Neither c/e nor customer should see any message.  It s/b handled by accounting.
  21. 11/5 - Per Ladd, small order charges are going away. 
  22. The 'order source' field in SOHDR must be set based on c/e request source (if ce) or set to 'web' (not ce). IN 'CREATE SALES ORDER' SPECS FOR WAYNE
  23. Must Ship Today - automate as follows: IN 'CREATE SALES ORDER' SPECS FOR WAYNE & JANICE'S BUNDLING SPECS
    1. If the order is being created before 11:00am, Set the must ship today flag=1 *** CHANGED TO '2' FOR AUTOMATED SETTING
    2. If the order is being created between 11:00am and xx:xxpm (based on whs), allow c/e and customer to flag as a must ship today via 'in a hurry ... we can ship today' option
    3. If the order is being created after xx:xxpm (based on whs), don't give a must ship today option.  Assign tomorrow's date to the bundle.  Show on bundle "Ship on or before tomorrow's date"
    4. Remove the 'must ship today' comment from the pickslip.  Change box hdg to: 'Ship On' or 'Ship on or Before' or 'Arrive On'
    5. Must Ship Today Report - resort by flag (1=user selected; 2=automated (before 11am)) or by shipment status (move shipped orders to bottom)???
    6.  Pickslips s/b okay - the 'MUST SHIP TODAY' comment is auto-added to the picking slip if SOHDR.USR<10> # 0
       
  24. Ship Via/FOB Code - if PPD, don't allow carrier to be changed (both stock and MOD items).  This s/b set to "BW"  - given to Wayne
  25. On a 'ship and backorder' bundle, put a 'BACKORDER' comment onto the backordered order.  The rest of the order shipping today would have no comment on it.  On a 'shipping everything in +3 days' (our default bundle when we sense a backorder situation), put a 'SHIP COMPLETE' comment on the order.