ivendnext.comPartners

Apps › Stock

Restaurant back office

Recipes take your dishes' ingredients off stock with one press a day; allergens on the till and receipt; food cost by recipe against actual; sales by item, till user and day part.

Freeby iVendNextiVendNext POSiVendNext DeskWhere it works: Every countryIndustries: Hospitality

What it does

Ring dishes as today; their ingredients come off the kitchen's stock by your own recipes.

What it does

  • A dish is an item with your recipe (Bill of Materials). Issue ingredients books one stock issue per store and day of what the tills sold, never twice; offline sales are caught once posted.
  • A store short of an ingredient books nothing that day and names each short part; the next press after a delivery books it.
  • Work out food cost by recipe, waste and stock count, as a share of sales. Sales by item, till user and day part.
  • Check allergens records each dish missing an allergen of its recipe, or a variant missing its template's. The till shows Allergens on the line and the receipt.

How to set it up

  • Make the app's user: Is Desk User, only the role IVENDNEXT RBO Integration, an API key. Give that role read on POS Invoice, POS Profile, Item, BOM, Bin, Stock Ledger Entry, Stock Reconciliation and Warehouse, and read, write, create and submit on Stock Entry.
  • Choose the user on the feed IVENDNEXT RBO Back office feed; in the App library open Details and press Connect again.
  • Make IVENDNEXT RBO Settings for each company: Issue sales booked from (now), the kitchen store, the day parts. Give dishes their recipes and allergens.
  • Switch on the three services (read, consent) in Retail Extension Subscription and the three buttons in Retail Desk Action. In POS Studio, Fields, on each theme: show ivendnext_rbo_allergens on the line and the receipt.

Good to know

  • Each press sends the record's name, the user and the language to restaurant-back-office.ivendnext.app (CitiXsys). It reads sales, recipes and stock, writes stock issues and its records, keeps nothing.
  • Ingredients book to their own expense account (set cost of goods sold on their Item Defaults). The app's user can book any issue: give its role to no one else.
  • Ingredients come off at the press, not the sale. No answer in time: press again later, nothing is booked twice. After a reinstall, set Issue sales booked from again. Kitchen tickets do not print allergens.
Adds
4 new lists · 1 new field on Item · 1 new field on Stock Entry · 2 reports · 1 event feed · 3 till extensions · 3 Desk buttons
Used by
Stock Manager, Accounts Manager, Item Manager, System Manager, Cashier
Licence
Apache-2.0

Version and changes

Version 1.0.0 · 23 Oct 2026

1.0.0 (23 Oct 2026): First listed version, hosted by CitiXsys.

Need it your way?

An iVendNext partner can tailor this app to how your stores work: your own fields, rules and screens, delivered to your site alone. Ask your partner, or ask us through Help to introduce one in your region.

For builders: this app's code is open in the Partner Kit (Apache 2.0) · The code · How to make it your own

Related apps