From wereapwhatwesow at gmail.com  Wed Apr  6 20:35:01 2016
From: wereapwhatwesow at gmail.com (Steve Young)
Date: Wed, 6 Apr 2016 19:35:01 -0500
Subject: [omaha] Guest checkout procedure
Message-ID: <CAFGSzzi3pWH1h_+Sfmb9=fPOo+-ULNaRO-94xeMdXjVKVvMLsQ@mail.gmail.com>

I am setting up Stripe as the payment processor for my django website.  I
have set it up using the dj-stripe package and it is working fine for
logged in users.  I would like to provide the option for a guest checkout,
like most online stores have.

Is there a 'design pattern' for this?  Like creating a user account that
all guest purchases go thru, or creating a user for every guest purchase?

Thanks.

Steve

From jeffh at dundeemt.com  Wed Apr  6 21:59:15 2016
From: jeffh at dundeemt.com (Jeff Hinrichs - DM&T)
Date: Wed, 6 Apr 2016 20:59:15 -0500
Subject: [omaha] Guest checkout procedure
In-Reply-To: <CAFGSzzi3pWH1h_+Sfmb9=fPOo+-ULNaRO-94xeMdXjVKVvMLsQ@mail.gmail.com>
References: <CAFGSzzi3pWH1h_+Sfmb9=fPOo+-ULNaRO-94xeMdXjVKVvMLsQ@mail.gmail.com>
Message-ID: <CALHZEO8rVu-eXEOVOxva1tK4Bn7nz2T4azxaYvNb=8TJHYXmWQ@mail.gmail.com>

The pattern is often dependent on the shopping cart you are using.

Did you roll your own or are you using a 3rd party cart?
Is it a physical item they will receive or digital?
If digital, is it a one shot and done, or will you let them
re[sume|-download] again in the future with some Order#/Invoice # etc?
Do you want to keep contact data for future marketing/promotions?

Many times, "guest" is synonymous with creating a user account with a
random password, unknown to you or the customer and maybe a a "guest" flag
on the account. Especially if there are scenarios that create a possible
future interaction.  This way you can keep you accounting logic standard
and let them set up an "Account" in the future.  Storage is cheap, creating
multiple logical paths in your code is expensive.

Just my 0.02, others are likely to chime in.  Pick the thing that keeps
thing consistent but gives you the interaction you desire.

On Wed, Apr 6, 2016 at 7:35 PM, Steve Young via Omaha <omaha at python.org>
wrote:

> I am setting up Stripe as the payment processor for my django website.  I
> have set it up using the dj-stripe package and it is working fine for
> logged in users.  I would like to provide the option for a guest checkout,
> like most online stores have.
>
> Is there a 'design pattern' for this?  Like creating a user account that
> all guest purchases go thru, or creating a user for every guest purchase?
>
> Thanks.
>
> Steve
> _______________________________________________
> Omaha Python Users Group mailing list
> Omaha at python.org
> https://mail.python.org/mailman/listinfo/omaha
> http://www.OmahaPython.org
>



-- 
Best,

Jeff Hinrichs
402.218.1473

From keckbug at gmail.com  Wed Apr  6 23:21:42 2016
From: keckbug at gmail.com (Aaron Keck)
Date: Wed, 6 Apr 2016 22:21:42 -0500
Subject: [omaha] Guest checkout procedure
In-Reply-To: <CALHZEO8rVu-eXEOVOxva1tK4Bn7nz2T4azxaYvNb=8TJHYXmWQ@mail.gmail.com>
References: <CAFGSzzi3pWH1h_+Sfmb9=fPOo+-ULNaRO-94xeMdXjVKVvMLsQ@mail.gmail.com>
 <CALHZEO8rVu-eXEOVOxva1tK4Bn7nz2T4azxaYvNb=8TJHYXmWQ@mail.gmail.com>
Message-ID: <CAJFZ-V9qvzz=k6XXT-U4Q5XvXGi6a7LvAo0LUpHUaLFjUhQHuQ@mail.gmail.com>

"Storage is cheap, creating multiple logical paths in your code is
expensive."
Just like grandma always said, right?

Honestly, I'd +1 Jeff's answer here.  You're effectively looking to perform
user actions, even if you may not necessarily care about the specifics of
the user.  Creating users with random names passwords isn't an awful idea.
If you can come up with a decent use case, you could always subclass user
and customize as appropriate, but I'm not really seeing the value yet.

On Wed, Apr 6, 2016 at 8:59 PM, Jeff Hinrichs - DM&T via Omaha <
omaha at python.org> wrote:

> The pattern is often dependent on the shopping cart you are using.
>
> Did you roll your own or are you using a 3rd party cart?
> Is it a physical item they will receive or digital?
> If digital, is it a one shot and done, or will you let them
> re[sume|-download] again in the future with some Order#/Invoice # etc?
> Do you want to keep contact data for future marketing/promotions?
>
> Many times, "guest" is synonymous with creating a user account with a
> random password, unknown to you or the customer and maybe a a "guest" flag
> on the account. Especially if there are scenarios that create a possible
> future interaction.  This way you can keep you accounting logic standard
> and let them set up an "Account" in the future.  Storage is cheap, creating
> multiple logical paths in your code is expensive.
>
> Just my 0.02, others are likely to chime in.  Pick the thing that keeps
> thing consistent but gives you the interaction you desire.
>
> On Wed, Apr 6, 2016 at 7:35 PM, Steve Young via Omaha <omaha at python.org>
> wrote:
>
> > I am setting up Stripe as the payment processor for my django website.  I
> > have set it up using the dj-stripe package and it is working fine for
> > logged in users.  I would like to provide the option for a guest
> checkout,
> > like most online stores have.
> >
> > Is there a 'design pattern' for this?  Like creating a user account that
> > all guest purchases go thru, or creating a user for every guest purchase?
> >
> > Thanks.
> >
> > Steve
> > _______________________________________________
> > Omaha Python Users Group mailing list
> > Omaha at python.org
> > https://mail.python.org/mailman/listinfo/omaha
> > http://www.OmahaPython.org
> >
>
>
>
> --
> Best,
>
> Jeff Hinrichs
> 402.218.1473
> _______________________________________________
> Omaha Python Users Group mailing list
> Omaha at python.org
> https://mail.python.org/mailman/listinfo/omaha
> http://www.OmahaPython.org
>

From wereapwhatwesow at gmail.com  Mon Apr 18 21:20:00 2016
From: wereapwhatwesow at gmail.com (Steve Young)
Date: Mon, 18 Apr 2016 20:20:00 -0500
Subject: [omaha] April Meeting - This Wednesday, the 20th, at 6:30
Message-ID: <CAFGSzzghD33WWNYVVrXs95x2XQ35wa8iv+bb4ioOD3Qcng4VAg@mail.gmail.com>

Hello everyone,

We have a room at DoSpace, but I have been unable to confirm a speaker.  I
thought Jeff H. might be able to do his Sonos SoCo demo, but I have not
heard from him yet.

Let me know if you are planning to attend, and if you have something to
present or discuss please chime in.

I did a short script to rename some images that I would like to share and
see what can be done to clean it up.

Steve

From keithnickum at gmail.com  Tue Apr 19 11:50:11 2016
From: keithnickum at gmail.com (Keith Nickum)
Date: Tue, 19 Apr 2016 10:50:11 -0500
Subject: [omaha] April Meeting - This Wednesday, the 20th, at 6:30
In-Reply-To: <CAFGSzzghD33WWNYVVrXs95x2XQ35wa8iv+bb4ioOD3Qcng4VAg@mail.gmail.com>
References: <CAFGSzzghD33WWNYVVrXs95x2XQ35wa8iv+bb4ioOD3Qcng4VAg@mail.gmail.com>
Message-ID: <CAHwr1pq_un99NcKAWXGQfo+A5b90P5ZBjsqWRynQ6-MCWadnjA@mail.gmail.com>

As I already told Steve, I won't be able to attend this month's meeting,
but I've committed to going over web scraping during the next meeting.

On Mon, Apr 18, 2016 at 8:20 PM, Steve Young via Omaha <omaha at python.org>
wrote:

> Hello everyone,
>
> We have a room at DoSpace, but I have been unable to confirm a speaker.  I
> thought Jeff H. might be able to do his Sonos SoCo demo, but I have not
> heard from him yet.
>
> Let me know if you are planning to attend, and if you have something to
> present or discuss please chime in.
>
> I did a short script to rename some images that I would like to share and
> see what can be done to clean it up.
>
> Steve
> _______________________________________________
> Omaha Python Users Group mailing list
> Omaha at python.org
> https://mail.python.org/mailman/listinfo/omaha
> http://www.OmahaPython.org
>