W Toku

573860 Zen Cart or PHP - Max Budget Twelve Hundred Dollars

I was browsing on ScriptLance and came across your company. I wondered if you had any interest. If so, see below.

Regards,

Michael McGahee

A) You must have Skype - we interview by Skype - do not bid if you cannot be interviewed by Skype.

B) ****WE WILL ABSOLUTELY KNOW IF YOU DID NOT READ THE SPECS**** - Do not bid until you read the specs - this is an automatic disqualification.

C) We completely own the program - this is a total buy out with no further future payments or obligations. It is okay to use modules from other programs, we expect most programmers will. You may have most of these functions in place.

D) If you have any doubt about doing this project, do not bid. It is a waste or your time and ours. Sorry, we don't mean to be harsh but please follow this guide line.

PROJECT

This must be open source code such as PHP or some existing cart as a basis, so that if the original creator is not available in the future, we have the ability to continue to change or upgrade when necessary.

Almost all of the functionality written below, most likely is present in existing software and modules. They are covered here to make sure none the areas we presently use are omitted.

This is for in house use and we are not selling the cart to other companies. We will own the code for our use although we understand that some modules come in from other vendors and may be part of the cart.

Below is a link with a list of the present screens in use and their set up. This cart does not need to have the same look. It just needs the functionality as noted below. If there is another, different or an existing solution, that will be okay.

Each screenshot listed below will have a letter or number in front of it and sometimes a color border to point out the area of the screen.

The corresponding JPGs are at this link. [url removed, login to view]

In your bid state what code, (such as PHP) or what cart (such as Zen Cart) that you are using as a base to start from.

Green – The main menu is on the left with different utilities by category.

1) Red – configuration – covers a number of configuration utilities

2) Blue – configuration>users

3) Config>users> You can see here that we add, edit and delete users

4) User setup screen – This is the same for both “new” and “edit” buttons - can filter access and ability to edit the cart and email notification

5) Red – Config>Return Policy – we are able to create a “return policy” that is printed at the bottom on all receipts and packing slips. The return policy is connected to an item or product SKU. There is also a default return policy that shows up if no return policy is assigned to the order.

6) Config>checkout>sales tax – need to be able to set sales tax and chose from one of the following Country, State, County, City

7) Red – Config>Shipping – need to be able to manage shipping costs and input the “ship from” point – can create a shipping rule such as flat shipping at $6.95 or a rule like rush shipping that can be assigned to the SKUs. There needs to be a filter to restrict areas not to ship to because there are high risk postal codes that need to be blocked.

8) Red – Config>Screen Branding – This may be part of setting up the check out page for the item. I'm showing you how they do it here. You can see we: i) create, edit, make default or delete a theme, ii) create pages under the theme such as checkout page & view cart. We use “single page checkout” mostly. I guess if people have multiple items they would want a page for “view cart” but I we've never used it as ours is forced continuity and up sells one page at a time.

a. Jpg exist as 8a – We can edit the theme page with html under various fields – see “Attachment A” for code and fields with out present page

b. Jpg exist as 8b - Conversion and Tracking tab on the top of the Screen Branding Page (second step on JPG 8) – we were able to track using third party such as Google Analytics

9) Red – Config>Export Orders – mapping export order information.

10) Red – Config>Call Center (Ignite) – this will be changing but this is how it is presently handled – there is a call center area to config and these are the present screens. Contact: To be Announced

a. Go to: To be announced

b. This will essentially consist of creating three folders on the server where orders reside – folder “a” will contain the basic record without the actual CC number – folder “b” will be the area the CC will pass through from Callfire – code has to be written to merge the data in folder “a” and folder “b” which will then reside in folder “c”. A chron will run ever “n” hours that pulls the records in as a csv or xml file to the cart where they get processed.

c. I will need some code to down load the wav files from “to be announced” into their own folder and convert them to an MP3 file. I have the converter.

d. I have a company that will transcribe the MP3 files and then the customer info is placed into folder “a” as noted above.

11) Red – Config>Auto Order Cancelation Notification – stet up for email to customer when auto-order is canceled.

12) Red – Config>Auto Order Update Billing Notification – setup for email to customer when auto-order needs to be updated.

13) Red – Config>Order Receipt Notification – setup for email to customer for receipt.

14) Red – Config>Order Refund Notification – setup for email to customer for refund.

15) Red – Config>Order Ship Notification - setup for email to customer for shipment.

16) Red – Item Management>Item – this just leads to the item menus – the next one is the actual menu on the item

17) Item Management>Item>Item (tab at top) – this is the item input screen for a new Item – SKU

18) Item Management>Item>Discount/Pricing Tiers – this may be incorporated as part of the item screen – I'm just bringing it up so it does not get lost

19) Item Management>Item>Auto Order – this is the input screen top and bottom – didn't fit on one page for screen shot purposes – this shows you the auto order inputs – the “delay”, “add”, “before” and “after” buttons at the bottom are very important. If you have a different approach I'm open. You can see by the example how a button will open up fields to be filled in. Also note downgrade field which allows (by the SKUs noted) us to take a person from 3 bottles quarterly to monthly. I don't know the tagging of other SKUs is necessary as long as the order allows us to change from the original order to a different SKU if the customer wants to change. Also note that a sample schedule shows on screen in case it is not what we mean to have happen and allows for quality control.

20) Item Management>Item>Auto Order – this shows more of the functions when buttons are used and what has to be put into the fields. Again, you may cover this a different way but it is the present structure. The following is an example of the “delay before” and “delay after” buttons. The 30 day “delay before” is in use because the first shipment is a 30 day supply with a different SKU, so this SKU is triggered on the day the first vitamin bottle is sent, then this 3 bottle order ships 30 days after the initial with this one being a quarterly shipment – the delay after is also used as an example when doing a free offer (example sku 101) then delay next shipment in 30 days with a different SKU (example sku 102) which is then shipped – sometimes we insert an item in the middle of the chain which will need a delay before or after, depending on the item.

21) Item Management>Item>Shipping – This is set up as screen:

a) on this we don't need the Case Relations, Custom or Inventory Control & Distribution screens

b) Shipping methods & Shipping Costs are needed and Destination Markups & Restrictions are not

c) Don't need Delivery Day, Ship Day or Package Requirements

22) Item Management>Upsell After – these are items set up in the upsell after. The next screen will be the actual input screen

23) Item Management>Upsell After>New or Edit – These are the set ups – we may do them differently as long as we get the screens seen on the Excel Spreadsheet – the code is on “Attachment B” – these allow us to set up new up sell after screen without having to have someone write code each time and that is the goal of this set up. As an example you have: a) use an existing cart with the standard up sell pages used by most carts, then b) set up this chain by creating a module (and replicate it 8-10 times so that one of the ten can be assigned to an sku), with 10 possible up sell separate pages that allow html for the look and feel and the ability to skip any number, e.g. use 1, 2, 3, 4 and skip 5-9 with 10 being the final check out page. Or make any page the final check out by clicking an option box on that page. Allow for an “if statement” that is basically [if submits (captured) fields containing name, address, phone, item sku, CC and if idle for > than 30 minutes then submit the order for processing] – you may read this and think of a simpler version

24) Green – Order Management>Red – Accounts Receivable (and pending orders – if together would have to have a color to distinguish which is which) – this is where the checks or rejected credit cards sit until we manually click them and they get rejected or go through the shipping department if the CC clears. There is a button that does not show here to submit the CC and a comments field. A single order from the web, if they are rejected will need to go to Accounts Receivable so we can re-submit manually in X days or there may be a check that is held in Accounts Receivable for X days to clear. The orders that come in batched from the phone go through as a batch and that is when some CCs are rejected and they to go to Accounts Receivable.

25) Green – Order Management>Red – Auto Order Search – this is the screen to do searches – this is separate from the regular search screen (below) for non-continuity orders. – JPG 25A shows the screen results when search is done – you can see we can edit or cancel auto orders on the page which brings up a cancel number which is then copied and pasted into the order comments field – it should just be on the record without going through the copy past procedure however.

a) shows the results of the search – wild cards (*) can be used to allow more parameters in the search

b) This shows the input for the order with notes opened to reveal any action taken on the order – this is also where the cancel and refund buttons reside at the bottom of the screen

c) This shows the refund screen and all the fields as well as buttons such as skip notification to customer, halt future order (or not) and allows for correct amount of refund as well as the issue refund button at bottom of screen

26) Green – Order Management>Red – Shipping – the buttons on this show all the actions to take with any or all orders when picked.

27) Order Management>Red – Shipping>shipping record – the buttons on this show all the actions to take with any or all orders when picked – also note there are multiple tracking number fields below not shown and we use them sometimes on a re-ship and there is a comments field as well not shown.

28) Order Management>Shipping>shipping record>Edit Customer>Billing Tab – this is the button at the top of the record and defaults opening in the billing tab – tabs are seen at the top of the screen

29) Order Management>Shipping>shipping record>Edit Customer>Shipping Tab

30) Order Management>Shipping>shipping record>Edit Customer>Other Tab – There are three windows here, the original and two drop down windows in this tab – When changing the screen branding themes it also changes the packing slip and this may be different with us if the packing slip is generated from the SKU – the “current location” field allows us to “reject” an order if the person calls in and cancels before ship or does a refund or moves the order from shipping to “Accounts Receivable” or to move the order back to shipping after correcting an error in the CC that then takes it from “accounts receivable” back to “Shipping” – NOTE the tax tab at the top which allows us to put a tax rate if for some reason it is different. We presently have a nutritional item which is non-state tax in Florida and because we ship to other states there is also not sales tax. Also if cancel a customer need to be able to re-enstate

31) Order Management>Backend Order Entry>Entry screen is shown – it's pretty straight forward – NOTE: this has it's own login so people can input an order without access to the whole cart and without having to go through the screen pop of a web order. *An important point here is that if you are a vendor bidding on this project you must put “HORSE” in the subject of the bid to show you are actually reading the specs.*

a) Entry screen is shown with dropdown window which does an auto-fill when typing in the order SKU – this could just open another window and choose the SKU as well.

32) Order Management>Export Orders> This was originally configured under the Configuration>Back Office>Export Orders screen and now has the different export mapping that were set up under configuration – If credit cards are involved then a PGP has to be acquired and used. There are three PGP software companies that I know of – you may know more about this

33) This is like #25 above but any order and not just auto orders – the order screen is somewhat different as it only has one order in it and not all the recurring orders connected as in the auto-order screen – much of the same functionality is there though.

34) Green – Reports> This is the basic reports menu – as I noted the primary report needs to show for example:

a) out of 100 orders for January how many returns – raw and %

b) out of 100 orders for January how many were auto-order – raw and %

c) out of 100 order for January how many are still on auto-order month by month – raw and %

d) then all of the normal stats like gross income – number of orders – number of refunds

35) Green – Reports> This is the basic reports menu – as I noted the primary report needs to show:

Areas not mentioned above that are important and need to be in the cart

36) First there is the up sell after screens that have to be in this cart for a different product than shown on the screens in the Excel document – the title of the spreadsheet is “Cart Screen [url removed, login to view]”.

37) Must have to have terms and condition box on check out page

38) Require “ship to” “phone” field on check out

39) In the orders >accounts payable – need to have a notify email and prompt if the accounts payable is not handled in X days.

40) Ability to block customers that try to order, either by name, address or phone and/or I.P. address.

The next few points are in (or should be in) the screens but making a note not to miss the following points:

41) We need to be able to export orders for shipping and preferably with a [url removed, login to view] interface.

42) We need to be able to export order with certain fields.

43) Need to be able to export in CSV or Excel.

44) Allow to run test orders

45) On orders and auto orders need a ship notice email and order email

Umiejętności: ASP, PHP, XML

Zobacz więcej: zen cart upgrade to 1.5, zen cart upgrade from 1.3.9 to 1.5, zen cart upgrade from 1.3.8 to 1.5, zen cart upgrade 1.3 to 1.5, zen cart how to upgrade, xml utilities, xml use case, xml inventory management, x cart programmers, write three wants, write ten step to structure a report, write a letter how you search for someone, write a cover letter example, window schedule sample, window schedule example, which of the following is not part of configuration management, where to get programmers, where to get leads for free, where to buy sales leads, where companies look for programmers

O pracodawcy:
( 0 ocen ) Clearwater, United States

Numer ID Projektu: #2319834