Laddawn.com : Old checkout work

Screenshot from Target

Preliminary design

Designer's best guess, does not reflect up-to-the minute discussions

1a - Determine ship-to address

Currently this is its own screen/step. In the new checkout process, we propose combining selection/confirmation of ship-to address with a new option to combine item shipments (see 1-b below) on one screen/step.

Ship-to selection box (exact location within layout TBD) will display a ship-to address on the basis of the zip code that carries over from the active cart. The system will predict and serve a shipping address based on prior ship-to address(es) associated with that distributor/user login and zip code. Users will be given opportunity to override the address presented (or enter a new address when there is no match).

Scenario 1: When only one prior address matches the ship-to-zip

• Preamble will be "Based on zip-code match, shipping direct to (your customer, your billing address, your warehouse).
• Clicking Select when “confirm this address” is selected refreshes box, with radio buttons and select buttons removed and more subdued “Edit” link added. (See scenario 1-A below.)
• Clicking Select when “Add an address for this zip…” is selected refreshes with scenario 2-A (see below).
• Clicking “Change zip code” link will return user to cart, with zip code box highlighted. “i” will explain that pricing and availability may change with a new zip, and that the user needs to refresh cart to update pricing and availability for that zip.

Scenario 1A:

Scenario 2: When more than one prior address matches the ship-to zip

• Clicking Select when a recipient is chosen from drop down list refreshes to Scenario 1-A (see above). 
• Clicking Select when “Add an address…” is selected will refresh with Scenario 2-A (below).
• Clicking “Change zip code” link will return user to cart, with zip code box highlighted. “i” will explain that pricing and availability may change with a new zip, and that the user needs to refresh cart to update pricing and availability for that zip.

Scenario 2A:

• • City, state, zip not editable.
  • Clicking Save after entering rest of new address  a) refreshes with Scenario 1-A view and b) stores address in distributor’s address file (as either customer address or alternate location). 
  • If user accidentally clicks Save before completing all required fields, error msg is generated. Likewise, if user fails to check either drop ship or alternate location checkbox.
  • “Back” link returns user to prior box (Scenario 1 or 2 depending on user's address data to begin with)

Scenario 3: When the zip doesn't match any prior address

• City, state, zip not editable.
• Clicking Save after entering rest of new address  a) refreshes with Scenario 1-A view and b) stores address in distributor’s address file (as either customer address or alternate location). 
• If user accidentally clicks Save before completing all required fields, error msg is generated. Likewise, if user fails to check either drop ship or alternate location checkbox.
• Clicking “Change zip code” link will return user to cart, with zip code box highlighted. “i” will explain that pricing and availability may change with a new zip, and that the user needs to refresh cart to update pricing and availability for that zip.

Scenario 4: Customers with established customer pickup preference

Zip for cart must match primary Laddawn warehouse. (Zip for product searches would be pre-set in user preferences.

If there are bundles or items in an order that cannot be picked up at the primary warehouse (????) need some mechanism for splitting off to separate order ?

1b Confirm or change bundling

( No equivalent in current Laddawn site. )

At the search results and cart stages, availability date and warehouse are based on inventory (for stock) or lead time (for MOD), on an item-by-item basis. See item-by-item defaults. However, at the checkout stage, the system will determine warehouse and availability defaults on a combined basis, for optimal bundling of shipments.   

Explanatory statement preceding shipment bundles

"We’ve grouped your order into the following shipment(s) in an effort to minimize costs and maximize convenience. Please review all ship dates and points of origin. To see additional options, click on an item’s ship date." Alternative variation if there is only one item in order: "Please review ship date and point of origin. To see additional options, click ship date."

Key: PW = primary warehouse; AW = alternate warehouse; MW = manufacturing warehouse.  Numbers refer to turnaround times; PW-24 means if today is 7/22/12, item is in stock at primary warehouse and date of availability will display as 7.23.12.

Bundling defaults

• • Combine all stock that is available within 72 hours from each warehouse into 1 shipment per warehouse giving it the latest availability date.
  • For example, there are 3 stock items in an order; on an individual basis two are each PW-24, the third is PW-72. Default is to bundle all three items into a single PW-72 shipment.
  • Create a single shipment for any stock item (purchased) that has a lead time greater than 72 hours.
    Create a single shipment for each MOD item using warehouse and availability date derived from configurator - exception, if multiple MODs happen to be shipping same date, same warehouse, default is to bundle those items. TBD: How to indicate warehouse for Marketplace items.

Each bundle will be headlined with ship date and warehouse of origin.

Line Level Overrides

Note that when a user elects to override a default, the default swaps place with the override (and other override options, if there were any, persist).  For example, if a user changes an item in an AW-24 bundle to PW-72, after that item moves into a PW-72 shipment, when the user clicks the date, they will see AW-24 now as an override option, along with

• Ship partial PW-24 and BO rest PW-72 (if partial qty available at PW)
• Ship with next MOD item (if MOD item(s) also part of order)

OLD CONTENT

The same layout is used when the user chooses to ship their items together, but only one shipping batch is shown (and ship method/paid by/instructions(delivery & packaging? see (2) below).

• jbm 4/14/12 - I apologize if we've already jumped over this hurdle but ...
• I worry that a customer may just want to get his stock to ride for free but doesn't necessarily want to hold up multiple MOD items to ship together.  Did we decide that this was okay to take the leap of faith that we could make this assumption?
  

From 4/4:  As in search results and cart, Laddawn item # and "MOD" are editable; customer can replace with customer #. If customer # is in system and displays, it is not editable. Same character limits, etc. as search results and cart. (Not shown in crude mockups above.)

• jbm 4/14/12 - I know we've touched on this a little but for Stock items, the database supports a single "customer item number" per Ship To location which is currently loaded into our database and not editable - we should ask ourselves whether it is important to allow them to add, change, delete as part of their Web process before we finalize whether or not to incorporate this logic into the Web (for stock items).  

(2) Other shipping & packaging options and comments

Delivery & packaging here????

Certain special "delivery & packaging" options are currently embedded in custom configurator pricing. For example, a certain type of skid, pallet dimensions (height, weight, pallet itself), or type of delivery location (business v. residence). Attached PPT contains reference screens. Others appear at current "Shipping>" step for checkout (now stock only; see images to right)

On 3/21 we decided that with the new combined search and cart processes for MOD and stock, it makes more sense for the user to be presented with the opportunity to select shipping/packaging options at the Active cart - COMPLETE stage (see Quick Add/Total Summary section), and that Laddawn would continue to charge for some options and not for others. (decision reversed on 4/3)

2. Labels SAME LOGIC/CONTENT (except carts now contain custom/mod items)

Per 4/4: Job reference added to checkout - is this the appropriate point in the proces