Interesting - like the idea of having a number of ‘open’ order cycles for modification. I also love that they have a button to see what is in that week’s delivery. CSAs that offer ‘a la carte’ items, in addition to the farmer-chosen items need this here.
But it looks like in this model customers are billed weekly. We tend to call this a ‘food box scheme’ versus a ‘CSA’. Here the difference is that in (what we call) a CSA, the customer makes an upfront commitment to 22 - 26 weeks of pickups/delveries. Most CSAs require at least 50% of the payment up front, with the remaining payment midway in the season (or some payment schedule). I’ve just been setting up demos for 3 different CSA models here - just to see how ‘close’ OFN can get and what the gaps are. Word is still out from some of them - but at this point the key features we are missing are: ability to make and track partial payments, ability to tailor ‘delivery locations’ (split shares between locations, different product mix, different days) without setting up separate ‘distribution’ enterprises (which is what we have to do now in OFN to get the flexibility), ability to manage different customer lists per delivery location. Not sure if our ‘subscription 2’ is heading towards CSA-support, or ‘simply’ better subscription (standing order) support.