1 / 6

General requirements

General requirements. All features and functionalities in one page (if possible) Shop consist of three parts: Select/remove products Type payment and contact data Choose means of payment Send invoice Credit card All data is sent via PHP call which:

lillian-underwood
Download Presentation

General requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. General requirements • All features and functionalities in one page (if possible) • Shop consist of three parts: • Select/remove products • Type payment and contact data • Choose means of payment • Send invoice • Credit card • All data is sent via PHP call which: • Returns an email with serial code if paid by credit card • Puts the order in ”PENDING-LIST”-list if normal invoice has been ordered (these will in turn be manually approved, and an email will be forwarded with order confirmation and serial number. • (Pending list must also be developed). • Payment and licence terms must be approved prior to purchasing. • The shop must include a backend that allows for setup of new products with unique and customized ItemID’s to be used in campaigns • Language files must be easily accessible for adaptation to new markets. Preferable in centralised language file. • Mock uphttp://www.bladrekatalog.dk/WEBSHOP/index2.html

  2. ORDER FORM • Products are listed with one button pr. product. Max 5 products avail at the time. • Added products should be removable. • ItemID (aka productID should be insert able manually by administrative people. • ItemIDs should be setup from the backend. UPDATE • Fields with ”*” must be validated with individual requirements. • Error messages should be posted dependent on inserted errors. • Distributor code can be inserted if the order is placed by a distributor on behalf or a customer.

  3. PAYMENT • Payment is available in two ways: • CreditCard • Billing (puts serial code in que, untill manual approval from back-end administration. • PBS (Danish payment gateway): • We are signed up. • Please ref. http://www.pbs-international.dk/frontpage_eng?language=en SEND ORDER • Terms and conditions • Must be approved • ALL TYPED FIELD DATA MUST BE INCLUDED IN PHP CALL TO DATABASE. • Order card details • Customer data • Payment type

  4. ERRORMESSAGES • RED text will mark missing/wrong data in fields with validation.

  5. Flow CONFIRMATION ORDER FORM Serial-number Orderform Order confirmation(Creditcard) Order confirmation (Invoice) ERROR MESSAGE Order confirmation Validation And Storage in DB ”web-list of pending orders” BACKEND Serial-number WEB EMAILS

  6. BACKEND • The backend for the solution should include: • Access to product setup • Module for setting up products and prices – and the ability to create products with unique ItemIDs for e.g. campaigns. • Weblist of pending orders • From the list in which customers ordering without creditcards, we must be able to edit customer data prior to approval. • Emails to be sent from system • EMAIL 1: Order confirmation • Ordered products, Price, Contact data etc. • Communication: Your serial number will arrive shortly • EMAIL 2: Here is your serial number • Sent automatically if paid by creditcard • Sent manually if approved from “weblist of pending orders”Her er dit serialnumber

More Related