The basket, wishlist and salespreparation objects are all ItemCache collections. These are responsible for collecting sales information and eventually moved into an invoice.
The invoice is responsible for charging the customer and provides the ability to track payments. So you can have multiple payments, payments that can be associated with one or more invoices - etc. It is the accounting aspect.
An order is responsible for fulfillment concerns (shipping and inventory). For example, if you have people that work in a warehouse that package up shipments, you may not want them to be notified of a sale if it has not been paid as receiving payment is not their concern - payments are an accounting issue. Once an invoice has been paid, the warehouse staff receives one or more orders based on what was sold to the customer. The order will not have tax or discount items ... Each order can then be broken up into one or more shipments.
You can think of the SalesPreparation as a sort of temporary container that allows one to save customer information and things like ship rate quotes during the checkout workflow. All of this information eventually gets added to the invoice / order. It also has some logic to invalidate itself if something changes in the basket ... like an item being added / removed which could affect shipping charges and tax calculations.
Some clarification: what is Basket / Order / Invoice?
I am confused.
Whant is a Basket, an Order and an Invoice?
I know that a Basket is the object that contains items selected from buyer before of him confirm.
When the Basket is confirmed by the buyer, the basket creates a Invoice. The Invoice can be visible in Backoffice.
Then, what is Order? Is it a alias of Basket?
Thanks
Hi Flavio,
The basket, wishlist and salespreparation objects are all ItemCache collections. These are responsible for collecting sales information and eventually moved into an invoice.
The invoice is responsible for charging the customer and provides the ability to track payments. So you can have multiple payments, payments that can be associated with one or more invoices - etc. It is the accounting aspect.
An order is responsible for fulfillment concerns (shipping and inventory). For example, if you have people that work in a warehouse that package up shipments, you may not want them to be notified of a sale if it has not been paid as receiving payment is not their concern - payments are an accounting issue. Once an invoice has been paid, the warehouse staff receives one or more orders based on what was sold to the customer. The order will not have tax or discount items ... Each order can then be broken up into one or more shipments.
Make sense?
Ok, I understand now Invoice and Order, and I think to know wishlist.
Can you say more details about of SalesPreparation object? Why exists it?
You can think of the SalesPreparation as a sort of temporary container that allows one to save customer information and things like ship rate quotes during the checkout workflow. All of this information eventually gets added to the invoice / order. It also has some logic to invalidate itself if something changes in the basket ... like an item being added / removed which could affect shipping charges and tax calculations.
Ok,
thanks very much, Rusty!
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.