9
Evolution of eCommerce @ Stanford May 5, 2003

Evolution of eCommerce @ Stanford May 5, 2003

Embed Size (px)

Citation preview

Page 1: Evolution of eCommerce @ Stanford   May 5, 2003

Evolution of eCommerce @ Stanford

May 5, 2003

Page 2: Evolution of eCommerce @ Stanford   May 5, 2003

We began in 1999 with a vendor providing order entry and payment processing – our vision was to provide a ‘payment gateway’ to the University’s financial systems

The vendor did not provide a means to interface with the General Ledger nor a way to report on activity for all accounts

We had to manually gather data from each account, compile reports, and send them to the Controller’s office for reconciliation

Page 3: Evolution of eCommerce @ Stanford   May 5, 2003

We found other departments repeating the same process

Page 4: Evolution of eCommerce @ Stanford   May 5, 2003

In December, 2000, our vendor gave us a 60 day notice of termination

We selected a vendor that offered ‘plug-and-play’ integration and successfully moved our clients (12 accounts) to the new service

Unfortunately, this vendor did not provide a means to gather data from all accounts

By the beginning of 2002, our number of client accounts had grown to 20+. The manual process for reconciliation and reporting was becoming difficult to support

Page 5: Evolution of eCommerce @ Stanford   May 5, 2003

We had run out of funding for the project and still did not have a General Ledger interface or an enterprise reporting environment

At the same time, the office of Student Financial Services was looking for a replacement for their 15-year old cashiering system

Through the vendor review process, we found a system that could provide cashiering service and also provide a ‘payment gateway’ to other departments – including eCommerce

Page 6: Evolution of eCommerce @ Stanford   May 5, 2003

We partnered with Student Financial Services and used our existing eCommerce hardware infrastructure to lower implementation cost

Page 7: Evolution of eCommerce @ Stanford   May 5, 2003

Pros Unified procedures Single db of all transactions for

reconciliation and reporting Interface to ERPs Secure ach and credit card transactions Ability for students to pay bills and

deposit to campus card via web Ability to charge convenience fee No custom coding Direct link between products and GL

Page 8: Evolution of eCommerce @ Stanford   May 5, 2003

Cons Less control Diebold interface needs work Ecommerce function may need

enhancement Vendor adds percentage to credit card

fee

Page 9: Evolution of eCommerce @ Stanford   May 5, 2003

eCommerce @ Stanford Activity: 1999 - 2002

0

10

20

30

40

50

1999 2000 2001 2002

Client Accounts

$0

$2,000,000

$4,000,000

$6,000,000

$8,000,000

1999 2000 2001 2002

Dollars Processed

0.00

5,000.00

10,000.00

15,000.00

20,000.00

25,000.00

30,000.00

1999 2000 2001 2002

Transactions