prp
commented
12 years ago We could derive a class EbayMarketplace from Marketplace that can store Ebay-specific information, including the costs for listing an item. If all marketplaces that we want to support have a somewhat common fee structure, we could also include relevant fields in the parent class. Looking at the fees for Ebay, however, things get complicated quite quickly.
Perhaps we should think of fee reporting as a desirable feature for the future but we shouldn't put it on the critical path just yet? Once we have the basic trading workflows implemented and working, we could get back to it...?
pdushkin
Hi Guys,
I feel that we need to do some early thinking about how pricing is going to work in our system.
For now, we can reflect what eBay does, since we only have this marketplace wired up. For example, if I go to eBay because I want to sell my iPad, it will tell me that N pictures will cost X, where N + 1 pictures will cost 2X. If I want a basic profile it is free, but if I want a fancier profile, it will cost me. And so on. Our sellers should be seeing this information in their own listing creation process.
When we add new marketplaces to our system, the middleware will need to calculate listing costs as a combined sum.
Again, reporting the costs to the seller in each step of the creation process. A final, "total costs" summary should be presented to the seller before the item is sent to the marketplace or marketplaces.
Should the user update an active listing, the system, again, needs to reflect any adjustments to listing costs and notify the user of these changes in-process.
I am working on updating the business rules and am reflecting the above in this document. However, I wanted to start the dialog so we are thinking about how to report pricing to the sellers.