How to design a shopping cart

This article is not about the process design, UI design of the electric Dealer's shopping cart, which is the user's shopping process. We should be concerned about what happens after the user puts things in the cart.

First survey, you feel, on the PC, app, WAP, on the same user, shopping cart should be consistent? That is, the same user, on the PC into the shopping cart merchandise, in the app shopping cart, in the WAP shopping cart, can see, these scenes of the shopping cart is interoperable?

If your answer is yes, then you and Shibe are the same kind of person, if your answer is no, Shibe to ask humbly, why would say so.

Shibe because of coincidence, found an electric dealer's app and website inconsistency, so, curious to the mainstream electric dealer's shopping cart all over again. The result was a surprise to the students who answered yes.

The result is that, in addition to Amazon is completely in line with the Shibe of the expected, Xun app is not interoperable, the rest of the electric business under the various scenarios of the shopping cart, all are fragmented, completely fragmented.

Shibe want to ask is why?? The independent of the shopping cart data in different scenarios means that the object of the shopping cart is not in storage or, in different scenarios, in different libraries. In addition to avoiding conflicts that result from concurrent client-side operations, Shibe cannot think of any better reason to support such a design.

But is there a lot of conflict, or users will be in different scenarios, the relay to complete a shopping flow of the situation more? Shibe pick things slowly, sometimes it takes a lot of time to get together, and it's usually possible to move from the office to the app and back home to finish the final order. Sometimes, just switching between two computers (this scenario should be common), most of the current design of the electrical quotient, can not guarantee the continuity of the shopping cart data.

Shibe Ideally, all the clients were just showing the form, and all the data sources came from the same service group, but a bug in store 1th had broken the idea. The order time on the app is a day ahead of the site. In the face of this unintentional discovery of the order through, Shibe don't understand, app data from where?

Now from the performance of the shopping cart, it is also so, we are all interested in it? Can you give me a reason? If the reason is, the shopping cart data exists the client local more convenient development and maintenance, Shibe will be silent.