When products come from different places, the store should explain the availability and way of shipping. Ordering these rules before implementation reduces surprises in the basket and during order execution.
Describe actual product flow
The company from Warsaw can sell the goods from its own warehouse, stationary point and suppliers. For the customer it is one store, but the facilities may need several processes. Before integration is created, decide who confirms availability and prepares each part of the order.
It is not always worth showing the entire warehouse structure in public. However, it is necessary to show the consequences that are important for the recipient: different times, separate shipments or restrictions on personal reception.
Agree Mixed Basket Rule
Check what happens when the customer selects products from several sources. Is the order waiting for completion, or is it shared? How are the costs and available delivery methods presented? These rules should be known before designing the summary.
- Show information affecting the time and cost before confirmation.
- Keep a clear breakdown of the products if the consignments are separate.
- Set the behavior at the inaccessibility of one position.
- Report to service the data to identify the source of the commodity.
Plan status update
If part of the order has been sent and the remaining items are waiting, one general status can be misleading. The interface and messages should correspond to the agreed method of execution. Do not send confirmation of completion of the entire order solely because one warehouse has closed its stage.
Make a Test on a Difficult Example
Test several products with different availability, change the quantity and temporarily no connection to the data source. Determine which message the customer will see and what task the service will receive. directory import guideThe store does not need to reveal the entire backroom technique, but should clearly state what affects the expectations of the buyer.
