Presentation that covers the state of the project, what it does, who uses it and where it's going. Talk from the Plone Conference 2009 in Budapest, Hungary.

1. GetPaid: Ecommerce in Plone
Christopher Johnson
ifPeople Cofounder
www.ifpeople.net | cjj at ifpeople.net
Plone Conference | October 29, 2009
Budapest, Hungary

2. My Background
 ifPeople cofounder
 Social enterprise
 Partnership-based
 Strategy-centered
 Plone consulting since v 2.0 (2004)
 Plone Foundation member
 Cat-herder/organizer of Getpaid

3. Questions I (hope to) answer for you today
 What is GetPaid? Is it for me? Is it ready?
 What has happened in the last year?
 Who is using it?
 How do I understand the product/structure?
 Can I make customized ecommerce?
 How do I get GetPaid?
 What's happening now? How do I get involved?

4. What is GetPaid?
 Zope3 and Plone-based framework for
developing unique and highly customized
ecommerce sites
 Basic features available out of the box for
processing payments on Plone site
 More features possible with
developer/integrator working on site

5. What is GetPaid?
 25k+ lines of code (+125%)
 Releases now numbered by recipe
 Plone 3.x focus (<= 0.6.2 also works on 2.5)
 14 payment processors (+133%)
 Active community (50+ contributors)
 Mailing list: 185+ people (+40%)
 http://groups.google.com/group/getpaid-dev/
 11 Languages (+20%)
 Chinese, English, Finnish, French, German, Italian,
Japanese, Dutch, Spanish, Portuguese, Brazilian
Portuguese
More info: http://www.ohloh.net/p/GetPaid

6. Who is Using GetPaid?

7. Who is Using GetPaid?

8. Who is Using GetPaid?

9. Who is Using GetPaid?

10. For More on Who Uses GetPaid
 Sites Using GetPaid:
 snurl.com/pgpstores

11. Who is GetPaid for?
 Site owners with simple shopping cart needs,
including donation forms
 Integrators who want to have own store product
 Integrators/developers creating custom
ecommerce applications

12. Zope 3
 Basis of GetPaid architecture
 We have no Archetypes!
 Component architecture
 Nicely organized, independent packages
 Adapters + Interfaces + Views
 Marker interfaces
 Used in GetPaid
 Inspiration from Plone4Artist

13. GetPaid Components

14. Features
 Content Integration via Marker Interface
 Buyable
 Donation
 Shippable

15. Features
 Shopping cart
 Checkout wizard
 Payment processor
 Order management
Full feature list:
www.plonegetpaid.com/features

16. GetPaid Add-on Ecosystem

17. Add-ons for Specific Use Cases
 One-page Checkout
 Making a Store
 Managing Inventory and warehouse
 Discounts and Coupons
 Recording orders in Salesforce.com CRM

19. Payment Processors
 Authorize.net (US)  Ogone (Europe)
 ClickandBuy (26  Pagseguro (Brazil)
countries, EU/US)  Payflo Pro
 Google Checkout  Paymentech (US)
(US/UK)
 PayPal
 Luottokunta (Finland)
 PxPay (Aust/NZ/S.
 NetCash (S. Africa) Africa/US/UK/Asia)
 Network Merchants  VCS (S. Africa)
Inc (US)
 Verkkomaksut
(Finland)

20. GetPaid Admin Area

21. OOTB

22. Add button to rich text area

 Add image
 Add link to image for:
 /@@getpaid-cart-add?add_item=True
Image: edkohler

23. One-Page Checkout
 Addon:
getpaid.formgen
 Extend with
PFG+Salesforce
 Tip: edit GetPaid
adapter last

24. Store, Inventory, Warehouse

25. Inventory Management
 Track inventory stock
and quantity available
 Add warehouse
location info
 Shows on order
 Warehouse location
used in shipping
calculation (UPS)

26. How to Make a Store
 GetPaidStore
 http://snurl.com/getpaidstore
 Includes product archetype, workflow, views
 Used for orderliterature.com
Thanks to TOT!

 Use GetPaid plug-ins:
 getpaid.warehouse
 New approach in the works: getpaid.atstore (Mikko)

27. Beyond Add-ons: GetPaid
Flexibility
Image: yogi

28. Customization, easy to hard
 Settings
 Templates
 Content types
 Custom Payment
 Custom Shipping
 Event handling

29. GetPaid Info On Your Template

30. GetPaid Info On Your Template
 See howto at:
http://snurl.com/getpaid-attributes-doc

31. Make Your Own Buyable Content
 Example particular archetypes:
 Products
 Donations

32. Make Your Own Buyable Content
 How to do it in GetPaid:
 Create custom content type
 Make it buyable
 Admin interface (Through The Web)
 Programmatically (see
http://snurl.com/getpaid-ct-doc )
 Thanks to Michael Dunstan!

33. Pay-to-submit Content
 Examples:
 Job posting
 Applications
 Directory listings
 Ads

34. Pay-to-submit Content
 Subscriber to
workflow
state change
 Howto at:
“how-to-tie-
actions-to-
payments”
(plone.org)
www.investorscircle.net

35. Why Use GetPaid?
 Useful out-of-the-box
 Basis for custom e-commerce processes
 Established project
 Several releases
 Dozens of public stores
 Uses Plone
 Store + best of CMS

36. How to Get GetPaid
 Product page: plone.org/products/getpaid
 getpaid.recipe.release
 http://snurl.com/gp-recipe
 Developer buildout (mr.developer)
 http://code.google.com/p/getpaid/wiki/
DevGettingStarted

37. Adding Additional Products
 Edit buildout.cfg file and add the name of the
add on egg
 Ex: getpaid.authorizenet, getpaid.warehouse

38. What's Next?
 Payment processor interface refactoring:
 Brandon Rhodes leading analysis and
implementation
 Additional features:
 Tax, shipping, downloadables/premium content
 Improvements to distribution method
 Involving new community members in project!

39. How to Get Involved
 Tomorrow: Open Space!
 Saturday: Sprint!
 See David from OpenNetwork
 Find us at #getpaid on irc and mailing list:
http://groups.google.com/group/getpaid-dev/
code.google.com/p/getpaid (project site)

40. Thanks!
 Kapil, Perrito, Lucie, Brandon and all
contributors to GetPaid
 Thanks to Whit for the name!
 Sponsors of GetPaid: ifPeople,
One/Northwest, Contextual Corp, Trees for Life,
Totsie.com, Train of Thought
 Find me: cjj (at) ifpeople.net
cjj on irc