Sales

manage your orders, credit notes, payments and more in the sales section the customers section is where all the data on your customers is held the customers section is also closely tied with the sales section using both of these sections will allow you to leverage breww's powerful crm capabilities orders breww allows you to easily manage your orders and payments we'll help you see which invoices are over due payment and quickly input new orders using our accountancy integrations we can also sync them to your accounting platform typically, an order in breww will progress through the statuses as follows graph lr draft > |build order, add products, etc| confirmed confirmed > |prepare delivery/collection| invoiced status explanation draft draft orders are completely editable it's a useful holding state for an order that hasn't been finished for some reason, perhaps you are waiting to hear back from the customer about one final item or you want to flag to your delivery drivers that this isn't ready to be delivered yet confirmed confirm an order when you are happy that, provided nothing changes, it is all good to deliver this way your delivery team know it's ready to go confirmed orders can be moved back into draft at any moment (with the exception of orders created by an external sales platform integration), so if a customer phones up to change their order it's not a problem orders cannot be delivered until they have been confirmed invoiced invoiced orders are the point the order becomes an invoice breww will move confirmed orders that have been dispatched to this stage automatically, but you can do it manually if you wish this is the point the invoice will appear in your accountancy software if you have connected one invoiced orders cannot be edited cancelled cancelled orders cannot be delivered or invoiced however, this flowchart shows the possible options graph td draft > |build order, add products, etc| confirmed confirmed > |need to make a change?| draft confirmed > |prepare delivery/collection| invoiced confirmed > cancelled draft > cancelled invoiced > abort{need to cancel?\<br>has the delivery been dispatched?} abort > |dispatched| cn{raise a credit note instead} abort > |not dispatched| cancelled price books when you create products to sell within breww (see the products section) you enter the basic price price books are how you manage more complex pricing you can create multiple price books (e g retail and wholesale ) and then assign customers to the correct price book this way you can ensure that customers are always charged the correct price, and that pricing itself never becomes a pain please see the creating price books and managing product pricing article for more information about price books customer groups the customer groups tool allows you to add individual customers to a group this is used when dealing with pub chains and will allow you to deliver the beer to the relevant pub but send the invoice to the head office of the pub chain customer tags you can define your own "tags" in breww which can then be assigned to customers or contacts tags are really flexible as you can make them work in so many ways and use them to filter lists and reports using brewwql there are some built in tags (such as receives invoice emails ) that change the way the system treats the customers/contacts that have the tag (in this case the tag causes the email addresses associated to be included by default when you send an invoice to a customer via email) customer lists customer lists are used to build lists of customers that fall into a defined set of parameters using brewwql customer lists are especially useful in our crm, for example, you could create a list of customers with the tag of monday call if you know you always call them on a monday customer lists also dynamically update, meaning that every time you open a list, the customers on that list have been searched for again using the defined brewwql syntax this means for example that if you have a list of customers whose last order value was over £100 but haven’t ordered anything within the last 30 days, only customers fitting these parameters would be included in the list the brewwql for this example would be average order value > 100 and last order date < "30 days ago" to learn more about brewwql, please see our full guide to using brewwql it's also possible to add individual customers manually to customer lists, to ensure they're always on the list regardless of the brewwql filters that you set up ullage ullage is used to manage lost or spoilt beer after you've sold it and make sure you don't pay unnecessary beer duty if a customer contacts you to let you know some beer was lost and cannot be sold, you can reclaim the duty paid on that beer by using our ullage tool this tool can be found at containers > actions & tools > ullage