Recurring splits

[ccmadmin]

We have a vendor that has moved a majority of items to bulk ordering. Our members used to use the "recurring" order feature for this vendor and would like to know if this is possible with splits - it would make life a bit easier for them and (possibly) us.

I have seen mention of this feature in 2013 and you mentioned it was on the to-do list. Any chance it's been completed? Or perhaps could we up-vote it so it creeps up in priority on the the backlog?

Thanks!!

[support]

It is not yet done, but I will bump it up in priority since you asked. Hopefully it can get done in the next few weeks.

[ccmadmin]

Excellent!! Thanks.

[ccmadmin]

Can you provide a status update on this?

[support]

In progress. Should be available within a week or so, if not sooner.

[ccmadmin]

Outstanding. Thank you!!

[support]

Recurring splits feature is now available for use. Please report any issues you find with it. Note that after archiving, it will not update the information in the split (price, size, description) from the database by default. (it does do this by default for recurring Orders)

For splits, since so many of them are for produce items which change so often, it leaves everything as it was, because often the item code will be gone entirely in the next database which would result in deletion of the entire recurring split, defeating the purpose. Rather, what admin users should do is go and look at the Splits page immediately after archiving (or after the next database update), and compare the recurring split items to what is currently available in the database.

For those clubs who are sure they want the "refresh from database" feature for recurring splits, there is a new Source setting to enable it:

Refresh recurring split items from product database after archiving

[support]

From an e-mail exchange about produce vendors with unstable item codes (e.g. OGC, Veritable Vegetable, Discovery, Pro Organics, Co-op Partners):

will it not work with (Produce vendor X)? or will I just have to manage the data?

They will work with (Produce vendor X), the data just won’t be refreshed after archiving (or when the database updates). Basically when the database updates, you will want to go through any splits that were there from the prior cycle, and make sure they are 1) still available, and 2) price about the same.

You could just wait to do this at invoicing, which is what most produce clubs do anyway. Since prices and availability can change all the time, it’s not that different than the normal situation. But having splits stick around for several cycles just increases the likelihood they will get stale and need to be edited or removed, especially with produce.