Laddawn.com : Functional Specs - Shipping and Packaging

Created by Jim Maloy, last modified on Nov 05, 2013

Functional Specs for Shipping and Packaging Functionality

Logic Shipping Paid By and Ship Via fields:

  • NOTE: the defaults for each stock bundles will be derived according to the total value of all stock items into the entire cart.
  • Stock Bundles for carts that total to less than $500 and MOD/Marketplace Bundles that have been priced as Customer Pays Freight .
    • Shipping Paid By will default to Prepay and Add and the Ship Via will default to Best Way.  If the customer has a Ship Via Preference (and since they will be paying freight) the Ship Via Preference will become the default Ship Via for each stock bundle.
    • Because the customer is paying freight he/she will be able pick any freight carrier he/she prefers and will also be able to change the Shipping Paid By field Collect (see additional prompting below).
    • When a user enters change mode for the Ship Via field, he/she will have a Check  Box to indicate that this is his/her Ship Via preference.   If this box is checked,  the Ship Via default in the ship to customer master file will be updated when the orders are created.
  • Stock Bundles for carts that total to $500 or more and MOD/Marketplace Bundles that have been priced as Laddawn Pays Freight.
    • Shipping Paid by will default to Prepaid and Ship Via will default to Best Way. 
    • Since Laddawn is paying freight the customer will not be able to use his/her Ship Via Preference or select another ship via code.   However, the user may override the Shipping Paid By field to a customer paid option and then may select from other Ship Via options. 
  • Third Party Bill and Collect Logic
    • For UPS and FedEx Ground Collect shipments the Account Number is required.
    • For UPS Third Party shipments the Account Number and Address is required.
    • For FedEx Ground Third Party Shipments the Account Number is required.
    • For all LTL Third Party shipments the Address is required.
  • CPU Processing
    • The user will establish the cart as being a CPU cart when the cart is created and being loaded.    Therefore, in the Checkout process, all bundles for the cart will be CPU bundles that will display on the Web as "No Charge" and "I Will Pick Up".  We will have supporting codes in the VIA and FOB System Tables.  If the user is unable to physically pick up using his/her own truck he/she will have the option to "Send a Truck".  When this option is selected from the Ship Via drop down the user will be prompted to "Enter Truckers Name".    The truckers name will be saved in the SOHDR.USR file and shown on the pick slip in place of the carrier description.

Logic for Special Instruction (Comment) fields

  • Base Logic
    • On the Special Instructions Page there will be four different categories of acceptable and available instructions:  Delivery, Carrier, Pallet, and CE.  The back-end will convey the category and sequence of each choice being passed so that it may be offered appropriately in the UI
    • Some Special instructions will have additional prompts needed to communicate the full message.    When additional information is needed the window will expand to prompt for it.
    • Some Special Instructions can be converted into Preferences for the Ship To customer.   The window will expand and offer a Check-box entitled "Make This a preference for this customer" when this option exists.  The preference in questions will be added to the appropriate customer master file when the order(s) are created.
    • When the default bundles are initially created all Customer Preferences on file will be automatically imbedded in the applicable bundles.  
  • Up-Charges
    • All of the "Carrier" ship instructions will carrier up-charges.   These up-charges will be predominantly flat rate charges that will be captured and stored in the COMMENTS.USR file and passed to the UI.    While in the UI, upon returning from the Special Charges window all relevant charges will be aggregated from the Special Instructions area and displayed in the Order Total area.  NOTE: we do need to devise an algorithm to determine how many pallets to use for a given bundle.  This will be needed to assess the Export Pallet up-charge.
    • Up-charges will be added when export pallets are used.  In this case we will charge a dollar rate per pallet used.   The calculation for the estimated number of pallets used will be discussed further (see current configurator rules).
  • Pallet Options
    • Pallet related Special Instructions will not be offered if the bundle is not is not conducive to pallet/LTL shipment.   This will likely be based on total weight of the bundle.  Logic to be determined.
      • Number of Packages Per Pallet will be available for MOD bundles only.
    • 40X48 skids will not be offered is the product is too large to ride on a 40/48 pallet. Logic to be determined.
  • CE Options
    • Need to review these individually with Susan

SYS9012 - Comment Master Maintenance:

  • Add the following fields to the screen
    • Web Category - set up a SYSTBL called WCC.LAD and add the four categories described below.  These will be used to drive the look and feel of the Web Screen itself.
    • Category Sequence - sequence (within category) that this comment will be displayed in the UI.
    • User Access Type - set up a SYSTBL called UAT.LAD and add two types -  CE or All.  This will be used on the Web to determine whether a CE User only or all web users will have access to this comment in the Checkout process.
    • Up-charge Type - set up a SYSTBL called UCT.LAD and add two types - Flat, Per Pallet, or None.  This will drive the logic in the UI that indicates that an up-charge applies.
    • Up-charge Amount - this will be the amount that is shown and included in the Order Total portion of the UI.

If there will ever be a need to charge a different flat rate/per pallet rate by warehouse, this may not be the best approach.  Currently, all upcharges (flat rate and per) are stored by warehouse in a configurator table.  The problem with the config table approach is that any new comment upcharge would have to be added to this table by IT, whereas your approach could be handled by CE.  Has a different rate by whs been discussed? Judy

Technical Specs for Shipping and Packaging Functionality

Customer Master - CUSTMST Definition

  • <6> Default Ship Via (possibly Ship Via Preference)

The following fields must be established in Avante database (COMMENTS.USR) to support the web functionality:

  • Web Category (Delivery, Carrier, Pallets, CE Options)
  • Category Sequence
  • Access Type (CE Only or All)
  • Upcharge Type (Flat, Per Pallet, None)
  • Upcharge Amount (Flat, Per Pallet, 0)

The following fields must be established in the database (SHOPPINGCART.USR) to represent all information needed in the Bundling and Packaging Area:

  • Bundle ID
  • Shipping Paid By
  • Ship Via
  • Items (MV / A1)
  • "delete?" Descriptions (MV / A1)
  • Quantities (MV / A1)
  • Comments Codes (MV / A2)
  • Comment Input 1 (SMV / A2)
  • Comment Input 2 (SMV / A2)

The following Comments information must be passed to the Website to allow the UI to produce the Special Instructions window that facilitates choices by bundle:

  • Comments Codes (MV / A1)
  • "delete?" Comment Description (MV / A1)
  • Comment Text (MV / A1)
  • Comment Input 1 (MV / A1)
  • Comment Input 2 (MV / A1)
  • Comment Category (MV / A1)
  • Comment Access Type (MV / A1)
  • Comment Upcharge Type (MV / A1)
  • Comment Upcharge Amount (MV / A1)

The following System Tables will be set up to be used on Comment Master Maintenance

  • WCC.LAD - Web Category Codes (this will be used to allow the Web Ui to be generated dynamically).
  • UAT.LAD - User Access Types (internal users will have different permissions than customers).
  • UCT.LAD - Up Charge Type (currently we only have a flat rate up-charge but this may evolve).

Questions

  • Is the customers' Ship Via Preference their default Ship Via on CUSTMST or is it a new field call SHIP ONLY VIA as referenced in the design.
  • Need clarification on what is required for 3PB and COL shipments.  Seems like 3PB is not on the site at this time.    Systems seems to require and account number on Avante when it is a collect but not when it is 3PB.  Also system seems to require address when UPS Collect - get more info from Leo.
  • Are we only allowing Preferences to be set for the Ship to Customer during the checkout process.  The is no provision for allowing the user to set a global preference for the bill to customer.
  • Need to devise logic for number of export pallets, number of cartons per pallet, pallet weight, and pallet height and incorporate it into the new web.
  • Figure out logic for small eliminating 40X48 choice and other pallet related choices.
  • Lots of questions on individual CE Options.
  • (Judy) How does the 'preference checkbox' work for ship via?  Default to ship via when P&A and don't show checkbox because it's already a preference?  Or show checkbox and allow to uncheck (Meaning what ... they want to remove preference or just don't use on this order)??