Choosing an inventory system

Restaurant Stock Software: Units, Packs and Conversion Tests

Test restaurant inventory units with cartons, bottles, kilograms and recipe quantities so purchasing and counting describe the same physical stock.

By Restrova Team · Published · Updated

4 min read · How we prepare our guides

Illustration of restaurant pantry containers, fresh produce, a scale and a blank counting clipboard
Editorial illustration, generated with AI · Not a product screenshot or customer photograph
Your practical checkMake purchasing, counting and usage refer to the same quantity
  1. Choose a base unit
  2. Record the pack conversion
  3. Test a changed receipt and count

A stock number is not meaningful until the team knows which unit it represents.

Illustrative decision process, not a product screenshot or customer result.

Unit confusion can make restaurant stock records wrong before any ingredient is used. A supplier may deliver cartons, a stock keeper may count bottles and a kitchen may record litres. The inventory system needs an agreed way to connect those quantities, or the team needs a clear manual conversion procedure.

This guide focuses on units and packs when selecting stock software. It does not assume that every platform supports automatic conversions, multiple purchasing units or recipe deductions.

Choose a stable counting unit

For each item, agree the unit in which the restaurant wants to understand stock. Rice might be counted in kilograms, bottled drinks in individual bottles and cooking oil in litres. The appropriate choice depends on how the item is received, stored and used.

Write the unit beside the item name in the working catalogue. Avoid a bare quantity such as “12” when it could mean twelve cartons, bottles or litres. Consistent item identity and unit definition are prerequisites for a useful report.

Record the conversion explicitly

Consider an illustrative oil delivery: one carton contains six bottles, and each bottle contains two litres. One carton therefore represents twelve litres. Receiving three complete cartons represents thirty-six litres, assuming the pack specification is correct and all bottles are accepted.

Quantity descriptionConversionBase quantity
One bottle2 litres per bottle2 litres
One carton6 bottles × 2 litres12 litres
Three cartons3 × 12 litres36 litres
Two bottles2 × 2 litres4 litres

These are worked examples, not a supplier’s actual packaging specification. Verify the pack used by your restaurant and keep changes under control.

Test partial and changed packs

Ask the supplier to demonstrate a receipt that includes two full cartons and two individual bottles. Under the example above, the accepted quantity is twenty-eight litres. Determine whether the proposed system records the purchasing unit, the base quantity and the conversion used.

Then introduce a changed pack size. A new supplier may deliver five bottles per carton rather than six. Ask how the new conversion applies without silently rewriting the meaning of historical receipts. If the software cannot model that distinction, document an operating method that preserves clear records.

Keep weight and volume separate

Do not treat kilograms and litres as interchangeable simply because both describe an ingredient. Any conversion between them requires an appropriate product-specific basis, not a universal one-to-one assumption. In many cases the simplest reliable approach is to choose one consistent unit for the relevant record.

Similarly, distinguish purchased quantity from usable yield. Trimming or preparation may change the usable amount, but that is a separate process from opening a carton. Do not hide yield loss inside a pack conversion without explaining it.

Inspect rounding and small quantities

Test a quantity smaller than one base unit if your workflow needs it. For example, a recipe requirement may use grams while the stock record is in kilograms. Ask how the system displays, stores and rounds the quantity.

Use a small independently calculated example and compare the resulting stock movement. Repeated rounding can make a difference over many transactions, so the owner should understand the actual behaviour before relying on a precise-looking balance.

Correct mistakes without losing the explanation

Enter a deliberately incorrect pack quantity in an authorised demo and ask how it is corrected. Record who can change the entry and what history remains. The team should be able to explain whether a change affected one receipt, future configuration or both.

A receiving mistake should not be repaired by an unrelated closing adjustment with no explanation. Keep the correction close to the source issue where the agreed system permits it, and retain the reason for reconciliation.

Verify Restrova with your real pack examples

Restrova’s inventory service and related video introduce stock management. They do not independently confirm all conversion, pack-version or recipe-unit requirements in this guide.

Bring the carton-and-bottle example to a demo. Use the receiving guide, permissions checklist and stock-count help to assess the complete process.

Unit questions

Should every ingredient use the same unit?

No. Use a consistent, appropriate unit for each item and make any required conversion explicit.

Can I assume a carton always contains the same quantity?

No. Verify the supplier’s pack and manage changes so new receipts do not corrupt the interpretation of older records.

Does automatic conversion remove the need for checks?

No. The configured conversion still needs to be correct, and the physically accepted quantity still needs verification.

This inventory introduction shows the starting product context for a stock discussion. Verify the particular unit, receiving, permission, counting or transfer requirements in this guide in a live demonstration.

Restrova Inventory Demo | Restaurant Inventory & Stock Management System

Restrova’s inventory demonstration introduces stock items and inventory-level monitoring for day-to-day restaurant supplies.

Watch this demonstration on YouTube · Published

Written overview, not a transcript. Use a live demonstration to verify the specific requirements in this guide.

Review customer implementations · Discuss your requirements

Keep reading