For #1 - what if it wasnt even physical shipping per se? What if it was just express delivery of a custom script or a sub-feature that cost a little extra? While user logins would be cool, i wouldnt see that being a barrier to a supplemental option that just adds a bit to the total $ amount due. Personally, i like the current setup of not having a user signup to go thru. How easy would you think this supplemental option with additional $ amounts would be to customize?
I don't exactly see why you want to add on an additional cost if there's nothing physical to ship. Files can already be downloaded instantly after the payment is confirmed so you can't get much more express than that. But if you're using the manual email method then I can see why it might be slightly useful. The reason I want to wait until I create a user account system before adding support for physical items is so that returning customers don't have to write out their shipping address every time they buy something, among several other reasons. When I do it, I want to do it properly. There's a lot more to selling physical items than you might initially realize, that's why most other shopping cart applications are so complicated.
I wouldn't get rid of the fast anonymous checkout option even if I did create a user login system. My plan is that when people go to checkout they can have the option of creating a new account, logging in with an existing account, or proceeding with an anonymous checkout. The other good thing about a user login system is that I can allow users to fill their carts with multiple items before checking out instead of buying one item at a time. Then they can view all their files and their complete order history by logging into their account. I basically want to implement all these ideas at the same time because they all fit together perfectly, which is why I don't want to release little plugins that half-do the job.
Just curious but what do you think the shopping cart interface that is the easiest to setup/maintain outside of bitshop is? Ive looked at opencart, oscommerce, etc and they seemed so taxing on setup/administration compared to bitshop? Did you like any of them as far as ease-of-setup/admin goes?
Well like I said selling physical items is a lot more complicated than selling digital items. But I am pretty good at making things easy to use and I think you'd have trouble finding anything else as simple and elegant as BitShop. But unfortunately if you want to sell physical items then BitShop probably isn't the best way to do it right now, but maybe in the future when I implement those ideas I just mentioned it will be the best way.
Problem #1 - partial payments - i tried to setup the shop to allow for "4 digit accuracy". My expectation was that a payment accurate to the 4th digit would qualify as PAID IN FULL. So for example, an amount due of 0.123499807 would allow for a payment of .1234 and be considered PAID at that point. But i had varying results on a test item which cost .001859 at the time of testing.
I assume you're referring to the payment variance setting? The default value is 0.000001 which means that the amount received can be 0.000001 less than expected. It doesn't just ignore everything after the nth digit as you expected.
- a link to update the wallet balances for each order and displays balance as a column field. That way I could visually make sure the payment amt matches amt due.
If you go to MANAGE ORDERS and then click on one of the rows you will see all the details of that order. You will also see a link which says "get balance". If the order has been paid it will notify you and update the status of the transaction. If you have an unconfirmed order you can use that feature to check the balance of the address attached to the order before you delete it.
- Going to my example of the 4 digit accuracy payments - the red/green flagging wasnt giving the appropriate flags based on what was in the wallets. Again, im wondering if the balance in the payment wallet + current confirmation amounnts is something that auto-updates?
Well partially received payments are still technically incomplete and so they remain red. I guess I could make the rows for partially paid orders orange so you can tell the difference. It's actually not so simple because BitShop doesn't record the exact balance of each address, it only knows if the required amount has been paid or not. But I can see why that might pose an issue with accounting because you wont know exactly how much you made until you export your private keys into a wallet which can tell you the balance of each address. It shouldn't be too hard to remedy this issue, I'll try to improve the situation in the next version.
While the EXPORT KEYS is cool - my point was having a pre-generated list that is fed in and then doled out until you run out of wallets at which point u import more wallets. The current way requires u to export, decrypt and then sweep all the balances to ur final personal wallet.
Oh I see what you mean now, I thought you were talking about using the same set of addresses repeatedly. What you mention is possible but wouldn't be a very good solution because your shop would stop working if it ran out of addresses. You'd have to manually make sure it was always supplied with fresh addresses. But I can see why some people may like that option because the private keys don't need to be stored on the server or trusted with a 3rd party like coinbase, so I'll consider adding it into the next version of BitShop.
Am i correct that the addys are generated on the fly at time of checkout? So whatever i export on order mgmt page will equal the # of orders.
Yes, there is one private key and one address for every order (addresses are created from private keys so all you really need to worry about is the private keys). Think of the private key as the key to unlock the coins held in the corresponding address. A wallet is essentially just a collection of private keys.