At Habu we understand that every workspace is different. Some workspaces want a fully self-service style eCommerce marketplace, where anyone can sign-up to become a member or access other products. Others take a fully curated approach, where becoming a member or having access to workspace products requires a personal meeting. The majority, however, take a mixed approach.
Habu, in any of these cases, supports you in making sure your point of sales matching your business model, whether through integrated products in your website, or the Habu User Area.
There are three categories when it comes to setting access to products and plans:
- Add to Cart
- Add to Account
If you do not have a payment gateway integrated, you will only have View and Add to Account.
You can set what the user journey is based on the user's status.
- Users (non-members who have verified Habu accounts in the User Area)
- Public (non-members who do not have a Habu account)
With this in place, it means you can create, for example, a day pass that members can add to their account for payment in their monthly payment cycle, that non-members will pay for upfront, and member of the public can only enquire about via email.
There are a few assumptions behind the logic in the checkboxes for permission.
- 'Add to Account' is a privilege based on trust (for payment gateway integrated accounts), which is why it's of the highest order
- Admins are hardwired to have 'add to account' as a non-editable default setting
- There's a hierarchy of users. Members are first order, Users (anyone with an account) are second order, and Public (no account, no known details) are third order. This means what ever permissions you assign to a second or third order user, are automatically assigned to first order. In plain English, if you assign Public 'Add to Cart' permissions, this will be automatically assigned to All Users (inc. Members). If you assign 'Add to Account' to All Users that automatically includes Members.
- Team members from an Organization only have 'Add to Account' functionality.
Ok, with that in place let's get into the nuts bolts of this.
I'll run through permissions using the same product with this configuration:
This is effectively a view only product or plan. Users can see the item, but they can't buy it directly. They can effectively only send an email enquiry.
To make things simpler for the end-user, Habu pre-populates the email enquiry with the product or plan details.
Once that email is received by your or your team, you can add the product to their account and email them the invoice. Or follow up with them according to your sales flow if it differs:
Add to Cart
This is setting allows the user to select and pay for the product upfront using a credit or debit card.
This will then take the user through to the checkout where they can sign in or create an account.
They can then use the card they previously added if they had an existing account or pay with a new card. Upon completion they'll be taken to the "order successful" screen along with any product instructions you've set and their receipt emailed to them. You'll receive an in-app and/or/nor an email notification depending on your settings too.
Add to Account
This setting allows the user to add this to their account for payment at a later date. Typically this will be as part of the monthly billing cycle where all charges are collected together in an invoice on the 1st month if you are using any degree of billing automation. You also can also manually issue an invoice at any point of your choosing too.
The user flow when the 'Add to Account' button is used, is a streamlined version of the 'Add to Cart' checkout flow as no payment is required at this point and are taken to the Success screen:
What happens when there are multiple items in the users cart that have different permission settings? For example if I offer a day pass with 'Add to Account' permissions and an event as 'Add to Cart'?
If there are multiple items in a users cart with different permissions because the user had added a product but not completed the order, Habu makes it clear to the user that they need to click the highlighted link to finish things:
If the item outstanding has the 'Add to Account' permission, the user will see this screen and needs to click the 'Add to Account' option in the Order Summary:
If the item outstanding has an 'Add to Cart' permission, the user will be taken to the check out:
How does this work for team members in Organizations? I don't see an option to set whether they can 'Add to Cart' or 'Add to Account'?
Great question! Team members in Organizations only have the ability to 'Add to Account' and that account belongs to the Organization. This because all charges are sent to that Organization for a central biller payer to pay. This is indicated on the team member's profile page under charges:
If you have any other questions, hit our online support and one of the Habu team will be happy to help you out (and add that question here for future reference!)