Would love to be able to track sales within an account that will then look at total items or value within a set period of time and then apply an appropriate discount.
The idea of this feature is to offer it to customers with a perm line.
There is a base discount on a MOQ.
With additional sales, we can offer a further % rebate calculated quarterly for example.
Thanks for the suggestion, Dan.
I think this might be a duplicate of One frees - cumulative retros/loyalty discount/scheme (e.g. get one free for every 10 purchased) but can you please confirm that you agree? If so, please let me know and don’t forget to vote on that other thread.
Cheers.
thanks @luke I think its similar, but not the same.
For this application, we want to be able to track the customers account over a defined period - say 3 months and then apply a cumulative discount over the period. This may result in a cash rebate at the end of Month 4.
E.G.
Based on MONTHLY orders (month = 4 weeks)
List Price Keg = £100
4 kegs (1 keg PW) = 5% (min contract amount - built into price book/deal)
6-7 kegs (1.5 kegs PW) = 6% discount -
8-11 kegs (2 kegs PW) = 7% discount
12+ kegs (3 kegs PW) = 9% discount
We would invoice monthly. If at month 3 the customer tips into the next bracket, we would apply the higher bracket of discount to the whole period and then rebate the cash amount back to the customer.
It is a complex way of working, and will only apply to our high volume customers where they can leverage discount brackets during busier periods.
Happy to discuss
Sorry for the slow response.
Yes, that makes sense and you’re right; this is a separate request to the other. Sorry for the confusion there.
Can I ask, why is a month a 4-week period? This would result in about 13 “months” each year, and they couldn’t be named as Jan, Feb, etc as most of “month” 12 wouldn’t even be in the calendar month of December. I realise, of course, that months vary in length which is not ideal and maybe why, but I feel that thinking of 4-week periods as months would cause customers confusion. Maybe they’re just called “Periods”, and there are about 13 of them each year? But even then, they would all be on different dates next year, so I think the actual week periods would get a bit confusing. I realise I’m thinking out loud here (or via my keyboard). Maybe this is common and I’m overthinking it, but it’s not something that I’ve personally come across before.
Would you want one invoice per month only? So orders would be delivered un-invoiced throughout the month? Currently, it’s not possible to deliver multiple orders on a single invoice (without workarounds) so this would also be quite a complex change to ensure it all tied in nicely.
And don’t forget to vote for your own request 
Sorry Luke, i used 4 weeks as a reference point only as I was trying to get out my idea in a way that made sense (to me), but think it clouded the matter.
Ultimately, MONTHS is easier as a PERIOD rather than WEEKS as it means that we can use QUARTERS for rebate purposes.
Happy to invoice as we go - that will mean we use an ‘account statement’ mechanism for the monthly orders rather than an ‘invoice’.
I mean this idea is in its infancy, so happy to flesh it out.
Ah ok, sorry I derailed this somewhat! That makes sense.
I think this would make a great feature, so if anyone else would like this too, please do give this a vote.
In the meantime, you could run this quite easily manually by looking over reports from Breww. For example, you could use a Products sold (order lines) raw data explorer report with a BrewwQL filter along the lines of:
invoice.order_status = "Invoiced" and invoice.issue_date >= "1st Jan 2024" and invoice.issue_date <= "31st Mar 2024"
You could also tag all customers that are part of this rebate scheme and filter to just show those customers.
This “share code” should get you started:
--- BEGIN BREWW RDE SHARE CODE ---
eyJiYXNlX2RhdGFfY29kZSI6ICJwcm9kdWN0c19zb2xkIiwgImZpZWxkc190b192aWV3IjogInByb2R1Y3QuY29kZSwgcHJvZHVjdF9uYW1lLCBxdWFudGl0eSwgdmFsdWUsIHZhdCwgdG90YWxfYW1vdW50IiwgImJyZXd3cWxfZmlsdGVyIjogImludm9pY2Uub3JkZXJfc3RhdHVzID0gXCJJbnZvaWNlZFwiIGFuZCBpbnZvaWNlLmlzc3VlX2RhdGUgPj0gXCIxc3QgSmFuIDIwMjRcIiBhbmQgaW52b2ljZS5pc3N1ZV9kYXRlIDw9IFwiMzFzdCBNYXIgMjAyNFwiIGFuZCBwcm9kdWN0Lm9ubHlfY29udGFpbmVyX3R5cGUudHlwZSA9IFwiS2VnXCIifQ==
--- END BREWW RDE SHARE CODE ---
I hope this helps 
Thanks - I will review this over the weekend - its not super urgent but looks like it would solve the issue on the face of it.