Hi - This is a e-commerce question but a differnt than others. I'm working to put together a specification that my dev team can use to build the e-commerce solution that has clear requirements to maximize that I get what I want.. and provide the best estimates possible.

 

The solution is to provide a business and customer facing interface to a pre-existing website that uses PHP, Apache & MySQl. The businesses will register to create "deals" and the customers will register and logon to buy "deals".. kind of like groupon. Expect maybe 10 deals / day max entered by businesses and 100 max / day by customers..

 

Would appreciate any and all input on what key parts are missing, what questions need to be answered and what pitfalls you see! My web platform technical background is limited - I know enough to be dangerous...

 

REQUIREMENTS:

 

1.) A separate interface for businesses rather than the customer login, e.g. maz.com/business.

The page should provide an UI/boxes to gather the following information, which would then be translated to database record(s). This is in in addition to what already exists.

 

Business Account info:

--Business name.

--Date registered

--Business Federal Tax ID.

--Business state tax id.

--Business address.

--Business phone number.

--Business Login Id.

--Credit Card information.

--[RO] Account Active/validated by us: True/false.

 

Deal info:

-Deal name.

-Deal origional price:

-Deal discount price.

-Deal date validity:

-Deal Limit#:

-[RO]Deals remaining:#

-MAZ fee/cut:

-[R0]Deal approved by us: True/False.

 

2.) Purchase of SSL certificate from Verisign etc.. for secure logon.

 

3.) A integration with e-commerce solution. ..

-OpenCart has good reviews and is fast which I'm leaning towards. Magento is another option though it has performance drawbacks and steep learning curve. Ultimately I will allow the platform is the one the dev team has the most experience with and is most comfortable with. If no experience (eek! don't know yet...) deffinetly not Magento!

 

4.) && then???

 

For customer data, haven't designed the datbase records but it's just a version of the above.

 

Thanks!

why don't you discuss it with your 'dev team'? Isn't that what you have them for?