Hey Lev, Initially the shopping is strictly handled as 'cart', once you move into the checkout process the 'order' bits come into play. The 'cart' is (on beginning) not tied to or based on any user, but is session based. You can try this yourself with a browser which isn't logged in. You can add stuff to your shoppingcart,but as soon as you hit checkout, it asks for a login. A cart id is created and stored as a cookie (see screenshot 1) as soon as you add something to the shoppingcart. This shoppingCardId cookie is the GUID referenced in the tables. In [sf_ec_cart_order] its the [id] field and all the subsequent cart tables reference it by the [cart_order_id]. (see screenshot 2) In the 3rd screenshot you can see a SQL diagram how they connect to each other. (relationship/referential integrity are strictly to highlight the fields) As far as I know, the shoppingCardId cookie is strictly a random GUID. Jochem.
Thank you for your extensive explanation. It was really helpful. I hope Lev got the answer for his question. As a token of appreciation we updated your telerik points.
Your best bet is to store the information you need as a session variable or in a cookie to persist between post backs. In your external page reference the Sitefinity classes and that will expose the API. For that see this article on eCommerce.
Glad to hear. Let me know if you have any additional questions!