Possible Use Case

[Lloyd Christmas]

Morning!!

I have a client who has a pro-shop, golf course, bar, and restaurant.  I am curious if Slatwall has the capabilities already within to handle all of these.  The client would like a member to be able to buy something at the pro-shop, then go hit a round, and have drinks.  They would like the member to pay with just their member ID number or something like that.  So we would need to store their information somewhere so that anyone could ring up their "order" and charge via their saved CC.

Thanks in advance!

[Chris Kent]

Hi Lloyd,

Yes, you can set up payment methods to allow saving the details for future use. This will request a token from the payment processor/gateway on their first purchase to be stored against their Slatwall account. This token or saved payment details can be used on future purchases allowing the customer to make complete payments without reentering their CC details. Take a look at the payment method admin details. I believe the standard Slatwall templates include the required code to allow the customer to optionally save payment details for future use. 

Sounds like you will have some different product types:

• Merchandise for shop purchases
• Probably best to use Events - for golf club rounds and restaurant bookings. Events will allow you to set limits e.g. maximum number of diners in the room or by table or for rounds maximum that can start a round per hour or some other setting.

You will probably require some custom coding to get a better check for availability for restaurant bookings as tables will become available again as one group leaves.

An other Slatwall feature that you may wish to use is to set up "On Account" payments. These would allow pre-determined credit limit to be set for accounts, customers can place and complete orders up to this credit limit and then pay for many purchases with a single account payment. This account payment could use the saved payment details and then be applied to one or more orders to complete the order.

Chris.

[Lloyd Christmas]

Thanks Chris! Exactly what I was hoping for.  Totally doable then.  I like the "On Account" option too so they only see one charge on their card at the end of the day

[Chris Kent]

Lloyd,

You can set the "On Account" limit by account, so some accounts could have a higher spend limit.

Usually this "On Account" would be used for B2B and have a time period associated, e.g, Set a time period of 30 days and a spend limit of $1,000 per period. This would allow the customer to quickly place as many orders as they wish in that time frame that have a total spend of less than their limit, then make a single payment on receipt of a consolidated invoice.

"On Account" payment methods can be used in parallel to traditional CC payments so you can for example process B2C and B2B, by only setting your business/trade customer to have the "On Account" as an eligible payment method. Other customers pay at order completion time.

Chris.

[brad.gu...@ten24web.com]

Lloyd - 

Agree on the need to have those saved payment methods against the account. 

The "Member Id" could just be stored as an attribute on the account - not sure who is creating the member ID, but that would create a place to store it and of course, you could automatically trigger order confirmations to be sent out even for those in-person purchases. Getting a receipt for the pro shop while on the course would be pretty slick. 

A few other things to consider would be to leverage the point-of-sale UI in Slatwall instead of building a custom front end, especially for the pro shop experience portion. We could work with you to get that set up and make hardware recommendations. 

On the restaurant reservation side, are they looking to actually track reservations or something more simple for the payments?

Brad

[Chris Kent]

Brad,

I usually put IDs to external applications/systems in the remoteID, makes it easier to include them in admin displays/search/reports rather than custom attributes.

Chris. 

[brad.gu...@ten24web.com]

Definitely, if they're connected to an existing system, using the remote ID for anything coming from an external source is always recommended.

[Lloyd Christmas]

Thanks for the additional info.  Brad, if they bite on the full proposal, I will reach out about POS  for sure.

The restaurant part they are still up in the air about what they want to do but are excited about the thought of getting rid of three fractured systems for one.