Now Available — Processing Fees on the ShalomCloud Shopping Cart

Similar to processing fees on the contribution portal, you may now offer that same capability on the ShalomCloud shopping cart.

Processing Fees Setup for Shalom Cloud Shopping Cart

Overview

This procedure outlines the steps to configure processing fees for credit card and ACH transactions in the Shalom Cloud shopping cart.

Key Steps

1. Access Processing Fees Configuration 0:25

generated-image-at-00:00:25
  • Navigate to the configuration section of the Shalom Cloud shopping cart.
  • Select ‘Processing Fees’ to access the fee settings.

2. Set Transaction Fees 0:44

generated-image-at-00:00:44
  • Specify the percentage for card transactions (e.g., 3%).
  • Specify the percentage for ACH transactions (e.g., 1%).
  • Note: Most congregations set ACH fees to 0% to encourage usage.

3. Configure Fee Options 1:07

generated-image-at-00:01:07
  • Decide if the fee will be mandatory (set to true or false).
  • Customize the verbiage for the fee prompt (e.g., ‘Please consider including…’).

4. Define User Response Options 1:19

generated-image-at-00:01:19
  • Set the phrases for user responses (e.g., ‘Yes, I’d be happy to’ or ‘Sorry, no, cannot cooperate’).

5. Select Financial Category 1:39

generated-image-at-00:01:39
  • Choose the financial category where the fee amount will be posted.

6. Test the Shopping Cart 1:51

generated-image-at-00:01:51
  • Access the shopping cart and select items (e.g., Shabbat Dinner Adult and Child).
  • Proceed to checkout and observe the fee calculations based on the selected payment method.

7. Calculate Fees Based on Selection 2:29

generated-image-at-00:02:29
  • For card transactions, calculate 3% of the total amount.
  • For ACH transactions, calculate 1% of the total amount.

8. Update Fee Settings to Mandatory (if needed) 4:25

generated-image-at-00:04:25
  • Edit the processing fee record to make the fee mandatory.
  • Change the fee prompt to a declarative statement (e.g., ‘Please be aware that we charge a 3% processing fee for card transactions’).

9. Verify Changes in Shopping Cart 5:21

generated-image-at-00:05:21
  • Test the shopping cart again to ensure the mandatory fee is displayed correctly without user options.

10. Confirm Consistency Across Platforms 6:32

generated-image-at-00:06:32
  • Please be aware that the processing fee settings apply to both the shopping cart and to the contribution portals.

Cautionary Notes

  • Ensure that the processing fee percentages are compliant with any applicable regulations.
  • Double-check the verbiage for clarity and user-friendliness.

Tips for Efficiency

  • Regularly review and update the processing fee settings to reflect any changes in policy or user feedback.
  • Train team members on how to navigate the configuration settings to minimize errors.

Link to Video

Not one, not all, but a selection– the shopping cart

Now available with the ShalomCloud shopping cart — grouping of items.

Until now, there were two styles of links or buttons that you could put onto your web site, or into email. You could provide a link to all available items; or you could provide a link to a single item.

We now offer the ability to create group codes, and then to assign items to a group code. For example, you might have several items related to a forthcoming Shabbat dinner. Adult member, child member, Adult non-member, child non-member. Or, perhaps, adult chicken, adult vegetarian option, child chicken, child vegetarian option. You can now create a group, call it Shabbat, and attach that group to all of those variations.

When you create a group, the “Show” screen provides the link that will display all items in the group, and no others.

Group code defined

Group code in action

Now Available — Add/Change/Delete Purchase History

Until this change, the ShalomCloud shopping cart purchase history relied solely on purchases made online. You had no way to change those records. So, if someone accidentally signed up twice, or signed up and later informed you that they could not attend, you had no way to update that data. Your record counts would be off, and the funds collected (or to be collected), would be off.

Another situation: if someone wanted to make a purchase, or register for an event, but would prefer not to use the online shopping cart, you had no way to indicate that. Perhaps they mailed in a check for a Shabbat dinner, for example, and you wanted to add that reservation to the purchase history.

This change allows you to accommodate those situations. You can delete a purchase; and you can manually insert a purchase.

One major caveat, though — any financial ramifications would have to be handled separately, via the normal financial transaction screens.

Here’s a video that demonstrates some basic use cases.