--- title: "Havenue 1.4: suppliers, orders, payments and invoices | Havenue" description: "Your supplier raised a price this morning. Havenue already knows which recipes it touches. Supplier records that govern ordering, purchase orders suggested from your booked events, receiving on a phone, event payments, and supplier invoices checked eight ways with a person who approves." canonical: https://havenue.co/updates/havenue-1-4/ markdown: https://havenue.co/updates/havenue-1-4.md language: en last_updated: 2026-07-27 --- # Your supplier raised a price this morning. Havenue already knows which recipes it touches. Most catering software stops at the menu. This release closes the two loops that sit underneath every margin figure a caterer actually cares about: what a supplier charges, and what actually arrived. ## Four things that did not exist last month Each one is live in production today. Each one has its own page with the real screens on it. - **A supplier record that governs ordering** : Preferred channel, order cut-off, lead time, delivery days and minimum order value. Not notes on a card: the ordering engine obeys them. - **Orders suggested from the future** : Your booked events, minus your stock, plus anything below par, minus what is already on order, grouped by supplier. Every line says why it is there. - **Receiving built for the back door** : Short, over, damaged, rejected, wrong item, substituted. On a phone, at the door, confirmed once. Only this raises stock. - **Money in, joined to the event** : Quotes and invoices raised from the event, deposits and balances with due dates relative to the event date, and a link your client pays on a phone. - **Supplier invoices, checked eight ways** : Photograph it, and about thirty seconds later its lines are structured data. Then eight checks run, and a person approves. - **A buyer who can draft but not send** : A chef de partie assembles next week's order. The head chef presses send. A drafting buyer who reaches the end is told, not left hunting for a missing button. ## Two loops, and everything hangs off them One carries money and runs forwards. One carries goods and runs backwards into stock. Until this release Havenue held the right-hand end of both and guessed at the left. ## One case of salmon, all the way to the dish This is not an illustration. It is the arithmetic Havenue runs, and every step shows its working so you can check it rather than trust it. ## Monday morning, on one screen Your head chef opens it to answer three questions: what is arriving today, what has to be ordered by today to arrive in time, and what is late. Deliveries, place-by dates and tasks sit on the same month rail your events already use, with filters and saved views scoped to orders. A day with nothing on it still opens, because tapping a quiet day and getting silence feels broken on exactly the days you opened the calendar to add something. ## What it refuses to do This section will tell you more about the product than any feature list. Each line is a place where guessing would have been easier, and wrong. ## The dietary engine is why Havenue exists. 1.4 is what surrounds it. When somebody asks what a coeliac guest was served in March, the answer should not be a folder of PDFs. Havenue checks every dish against every guest using verified ingredient data, finds suitable replacement dishes from your own recipes, and produces the guest menus, the BEO and the allergen matrix for chef approval. Supplier prices and invoice scanning are additions to that. They are not a replacement for it. ## The client portal Your clients already pay through a secure link. We are extending that link into the place they review the event, approve the menu and settle the balance, without an account to create and without a password to forget. This is the shape of it, not a screenshot, and we are not putting a date on it. ## See both loops running on your own suppliers Book a walkthrough and bring a supplier price list and a recent invoice. Or start free and put the invoice on your desk through it yourself.