IT_Architect
12-11-2006, 04:04 PM
I'm new to ECommerce:
I need to setup a shared cart that can be accessed by multiple clients. It would probably be good if they could login and download transactions into QuickBooks. From what I read here, OSCommerce fits that bill. Some customers simply login, and print it out.
Authorize.net has gateway capabilities to interface with QuickBooks.
I don't understand the difference between how these two operate. I would think that the OSCommerce solution would book it as an order in QuickBooks because the order could be declined. I would think that Authorize.net would book it as a sale, since you have their money.
As far as site integratioin, some people would have no integration at all. Their site would simply pass the products selected to the secure shared shopping cart site where they type in their cc information. Sales tax would need to be applied, depending on the state. Some may want to have products with inventory levels shown on their own site. There may be cases where the inventory in Quickbooks needs to be reflected on the site. I know there is service named QBGateway, but that is not a product I can buy. I could code it if no solution is available since I've coded for the Quickbooks API before.
That creates a spec like this. A shopping cart that can be:
1. Can be shared among customers.
2. Could optionally supply downloads for QuickBooks.
3. Could optionally work with Authroize.net.
4. Could optionally work with PayPal.
5. Platform independent if possible.
Another question, I need a good source to check the server for security vulnerabilities. What are some that you use?
Thanks!
I need to setup a shared cart that can be accessed by multiple clients. It would probably be good if they could login and download transactions into QuickBooks. From what I read here, OSCommerce fits that bill. Some customers simply login, and print it out.
Authorize.net has gateway capabilities to interface with QuickBooks.
I don't understand the difference between how these two operate. I would think that the OSCommerce solution would book it as an order in QuickBooks because the order could be declined. I would think that Authorize.net would book it as a sale, since you have their money.
As far as site integratioin, some people would have no integration at all. Their site would simply pass the products selected to the secure shared shopping cart site where they type in their cc information. Sales tax would need to be applied, depending on the state. Some may want to have products with inventory levels shown on their own site. There may be cases where the inventory in Quickbooks needs to be reflected on the site. I know there is service named QBGateway, but that is not a product I can buy. I could code it if no solution is available since I've coded for the Quickbooks API before.
That creates a spec like this. A shopping cart that can be:
1. Can be shared among customers.
2. Could optionally supply downloads for QuickBooks.
3. Could optionally work with Authroize.net.
4. Could optionally work with PayPal.
5. Platform independent if possible.
Another question, I need a good source to check the server for security vulnerabilities. What are some that you use?
Thanks!
