Handling membership fees in OFN


At present, the OFN platform doesn’t have a clear way of handling membership fees. A lot of CSAs and hubs are ‘members only’ and OFN can of course be set up for members only - but if there is a fee required - how are people handling this?

The only thing I can think of is to add ‘membership’ as a product. But the enterprise manager still has to look at each order to make sure they paid the membership before giving them access to the shop. Plus - if the product sticks in the shop, some members forget and buy it twice and have to be re-funded. In addition - most membership-driven programs, esp cooperatives, want to collect some information from people beyond what is completed at checkout, and give them a member number…

Anyone have work-a-rounds? How important is this - should we be putting a wishlist item together?

@Kirsten @nick @lauriewayne1 @CLFC @MyriamBoure @lin_d_hop


Cooperative on the Norwegian platform use 2 shopfronts and tagging

  • 1 public shopfront with the membership(s) as products
  • 1 private shopfront with the coop’s products

This of course involves manually watching the membership shopfront and adding to the customer list of the private shopfront. I think it works quite well.

This could of course be much more automated and solved with a membership feature, but that’s another wishlist :wink:


This seems simple enough using tags: just tag “members” users, and put a condition to display only some products (or even the whole shop), or apply other fees , depending on the tag being there or not.

You can then either sell the membership as a product online to non members, or manage it offline and add the tag manually.


yes - if the only difference between a member and non-member is the membership fee, or just a few products/variants, then tagging what you don’t want to show and do want to show for members works. Thanks @berteh. You are correct. But tagging lots of things in a shop with hundreds of products is kind of a pain. Second - yes, its possible to tag a whole OC. BUT again - this is awkward until we make some further improvements in OFN - because when you go to set up an OC, its very difficult (if there are lot of products in incoming) to figure out which ones go into which (member vs non-member OC) - because at this screen , you only see product name and size - not price (which is often the difference between member vs non-member). So it can be done - but is finicky. So - yes - your suggestions are how to handle it - but sometimes it just doesn’t feel that easy for users - i was hoping to learn about an option I haven’t figured out. Cheers.


you are indeed right @tschumilas. My additional problem with the “tagging” approach is that is does not account for the anniversary of the user subscription, when I need to ask for renewal.

Since we operate all year long, new users can join at any time, for a whole calendar year… and membership´s gotta be renewed after a year. But most other CSAs operate on a season base, so I didn’t want to elaborate.