the solution is to NEVER have a bitcoinD on the web server. multiple security issues for this.
all you need is a database of public keys.
simply generate keys from an offline computer and put just the public keys into a database onine for the website to then display to customers. and you simply keep updating the database as the addresses get used.
you then use the offline computer to manage the bitcoins far far far away from the website. this is called "cold store".
then all you need is a API for price evaluation.
... simples
lastly
ADVERTISE, ADVERTISE, ADVERTISE.
no one will spend bitcoins if you dont advertise your business accepts them. EG everyone knows overstock and dell accepts bitcoin, thus they are doing $millions in bitcoin transactions
I think the big problem regarding sales is my company's small market is simply not using BTC yet.
I recently learned of these tools that I'll research and hopefully implement instead of Coinbase (which I'll be dropping completely) and seem to be a bit better developed than a homebrew solution:
https://github.com/coinkite/coinkite-real-time-invoice
https://github.com/gary-rowe/MultiBitMerchant
Are there any glaring security issues with these technologies?