Sabina Fischer: Thanks for the reply, and for reviewing my request. The other pending request would not address my issue. If you think of the different steps in the life of a Japan Rabbit Order, they include "Order Completed, Product Not Received" then "Order Complete, Product Received", which creates a "Package" to be dealt with. If a a User places three orders (A, B, C) for one item each, it is possible that the product for Order A is received (and Packaged) before the products for Orders B and/or C are received.

In my case, I buy a lot of pre-orders, so I currently have four Orders (call them #1, #2, #3, and #4) with all products received, which are listed ahead of a fifth Order (#5) that is anticipated "end of May". I had Order #4 and Order #2 shipped immediately when each product arrived at Japan Rabbit; however, I'm letting the products from Order #1 and Order #3 await Order #5's completion, before consolidating them all into a single Package.

Tracking Packages "In Transit" is a valuable feature; however, it doesn't address Orders that have been unfulfilled or partially fulfilled. My broader suggestion would be to adjust your workflow such that:

User adds first Product; new Cart is created (This is the current workflow)

User adds and removes Products from Cart until happy

(If Cart becomes empty, Cart is destroyed in the system)

User checks out Cart; Cart is locked in the system; Order is created

Orders (like Carts) also have Products within them

Orders are shown on the Orders screen with a progress bar (or other indicator) reflecting how many Products have been received by Japan Rabbit

As Products arrive, User can click into the Order and see which are marked Received and which are not (along with the notes you currently have; e.g., "End of May")

Products can be assigned to Packages

(Note that this also opens up the possibility to consolidate some items into one Package and other items into another Package, which would be very helpful for sending gift boxes to friends in different countries.)

Packages would then have the same workflow as currently exists.

Please let me know if I can provide any additional details. If your development team would like, I can create a finite state diagram or pseudo code to better communicate the technical change I'm suggesting.

Andrew Kozak: Thanks for the detailed explanation! I see now that the "in transit" does appear to explicitly mention items literally sent from the store. That's actually very difficult for us to achieve so a "pending" section seems to make sense which would line up more with your request here.

It's interesting you mention consolidating before items arrive as that is something we are also considering but we're not sure if or when that will happen yet.

Our current thoughts are to use the packages view rather than orders for this "pending" view so people can see all their items in one place.I These are rough mockups but would be interested in your thoughts and if this addresses the issue (one is more an exact "timeline" while the other batches items into wider arrival groups)

Sabina Fischer:

I like your statement about "people can see all their items in one place". I prefer explicit dates in the estimated arrival, but this is a personal preference. More importantly, seeing "all [my] items in one place" makes the individual Item the primary object of interest.

The screenshots you attached appear to show "Pending" as an additional status on the "Packages" screen. In your internal data model, does each Item in an Order become a Package as soon as it the Order is placed? In other words, if Order #123 contains Item X, Item Y, and Item Z, once the Order status is changed to "Completed", would I see three Packages appear: Package X, Package Y, and Package Z?

It seems to me that the concept of a Package object implies a connection to a tangible box, and thus a Package doesn't exist until an Order is packed for shipping (or multiple Items are "consolidated" for shipping). With this in mind, "Pending" is a status appropriate for Orders (not Packages), and more specifically "Pending" is a status appropriate for Items within an Order.

In summation, the Pending view in your screenshots would be very helpful. I suggest that Pending be a status for Orders (not Packages) but you understand your data model better than I do, so that is merely a suggestion.

Thank you for the attention you've paid to my feedback. Please let me know if I can contribute anything further to make this a reality.

Andrew Kozak: Orders don't become packages per se but they don't stay as orders either. The items themselves would only be grouped based on release date and order on this view, they wouldn't actually enter a package until they arrive with us. So if item XYZ all are in the same order with the same release date, they would show as one group in this view as we expect them to arrive together (that is not always true of course, but they can just become real packages as they arrive).

If we want to allow people to possibly pre-consolidate in the future it makes sense to have this view in packages rather than orders, but perhaps it will end up in orders. We haven't finalized things yet but it's good to hear it should fulfill your needs.

I'm unsure when all this may go live but thank you taking the time to provide your thoughts on this. If anything else comes up I will come here to ask!