LOGIKA product prototype

ALFA FRUKT

Software for wholesale fruit and vegetables

A LOGIKA product project for wholesale fruit and vegetables. It shows the connected process from the order to the document, the sale and the report — with the units of measure, prices and particularities of the trade.

Type
Custom software, internal system
Screens
Desktop and phone
Related service
Software development
Stage
Interface prototype; the server side — in a real project

Prototype illustrations with sample data.

Connected scenario

  1. Orderin the customer’s units of measure
  2. Stock checkby class, origin and minimum
  3. Pickingactual quantity, partial fulfilment
  4. Documentbased on what was delivered, with the price for the date
  5. Sale and reportturnover by period, customer and product
The task in the industry

What the system is for

In a fruit and vegetable warehouse, orders come early in the morning by phone, email and messages. Goods are sold in kilograms, pieces and crates, prices change by date and differ for restaurants, shops and hotels, and the actual quantity often differs from the ordered one.

ALFA FRUKT is our product concept for such a system: one connected process instead of spreadsheets, notes and retyping — from the order to the turnover report.

Task and scope

To show how one system connects stock, orders, business partners, documents, quotes and market prices with the particularities of trading fresh produce.

  • Stock by product, class, origin and unit of measure
  • Orders, picking and sales with partial fulfilment
  • Business partners, individual prices and history
  • Documents, rule-based quotes, reports and AI analysis

From the weighing slip to stock and sales.

Demonstrated in the prototype with sample data: the weighed goods for order No. 1207 are recorded once and used everywhere after that.

Handwritten weighing slip

Example Bistro
Tomatoes I — 2 crates
gr. 22.8 / t. 2.4
n. 20.4 kg

1. Business partner and product

Business partner
Example Bistro · HoReCa
Order
No. 1207 · for 29.10
Product
Tomatoes, class I · Bulgaria
Ordered
20 kg

2. Gross, tare, net

Gross22.8 kg Tare · 2 crates × 1.2 kg2.4 kg Net20.4 kg
  • Entered by hand from the slip
  • Electronic scale — a possible future connection

3. Quantity, price, value

Quantity
20,4
Unit of measure
kg
Price
€2.40/kg HoReCa, from 29.10
Value
48,96 €

0.4 kg over the ordered amount — the document follows the weighed quantity.

4. Confirmation

The record is confirmed. Entered once and used everywhere after that.

  • Stock165.6 kg
  • Document No. 1207104,16 €
  • Sales for the day1 862,40 €
  • Report · tomatoes214.4 kg
  • Stock

    Tomatoes, class I · BG

    186.0 kg165.6 kg

  • Document No. 1207

    “Tomatoes” line €48.96

    total excl. VAT104,16 €

  • Sales for the day

    9 documents

    with No. 12071 862,40 €

  • Report · Example Bistro

    tomatoes, 01–29.10

    194.0 kg214.4 kg

Main areas

Seven parts of one work process.

  • Stock

    By product, class, origin and unit of measure — kg, pieces, crates; a minimum for each item.

  • Orders, picking, sales

    From the order to the weighed delivery and the sale, with partial fulfilment.

  • Business partners

    Price group, individual prices, history of orders and payments.

  • Turnover and reports

    By period, customer and product; from the figure to the specific documents.

  • Documents and invoicing

    A delivery note and a draft invoice based on the quantity delivered.

  • Quotes and sending

    Personalised quotes by group; automatic sending by rules, with a review when there is a deviation.

  • AI analysis of market prices

    Comparable prices from approved sources — with date, origin, class and unit of measure.

Overview

One screen connects orders, stock, sales and business partners.

Choose a figure to see the detail behind it. The numbers are examples, but connected: order No. 1207 is in the partial orders, in the sales and in the customer’s report.

Partially fulfillable orders

No. 1207 · Example BistroCucumbers, class I · Greece3 of 4 crates · 1 crate for 30.10 No. 1201 · Example RestaurantCourgettes12 of 20 kg · 8 kg for 30.10

What is missing stays in the order and is tracked until the next delivery.

Stock below the minimum

Cucumbers, class IGreece3 crates · min. 10 CourgettesBulgaria12 kg · min. 40 BananasEcuador2 crates · min. 8

The cucumber shortage is the reason this week’s quote needs a review.

Sales on 29.10 · 9 documents

Delivery note No. 1207Example Bistro104,16 € Delivery note No. 1208Example Hotel286,70 € 7 more documents1 471,54 € Total excl. VAT1 862,40 €

Example Bistro · HoReCa

Deliveries 01–29.10including No. 120712 Turnover 01–29.10excl. VAT1 251,06 € Most purchased productTomatoes, class I · Bulgaria214.4 kg

The customer’s prices follow the “HoReCa” group and the delivery date.

Interactive demo · sample data

AI analysis of market prices

It compares only what is comparable and says what comes next.

Prices come from approved sources. The analysis compares the same product, class, origin and unit of measure for nearby dates and shows what each figure is based on.

Tomatoes, class I · Bulgaria€/kg · excl. VAT

SourceDateOrigin · classPrice
Wholesale market (example)28.10Bulgaria · I1,85
Supplier B (example)27.10Bulgaria · I1,95
Our purchase price28.10Bulgaria · I1,70
Our selling price, HoReCafrom 29.10Bulgaria · I2,40

Excluded from the comparison

“Tomatoes, class II” — a different class · “Tomatoes, Turkey” — a different origin · a price in €/crate — a different unit of measure, without the crate weight.

Summary for a commercial decision

The selling price for HoReCa is €0.45–0.55/kg above the wholesale market prices and €0.70/kg above the purchase price.

  • The price for 29.10 can stay at €2.40/kg.
  • If the wholesale market price falls below €1.70/kg, the system suggests reviewing the price for the group.
  • The decision stays with the trader; the analysis shows the source and date of every figure.
Turnover and reports

The sale doesn’t end with the document.

Every document goes into the turnover. The report by period, customer and product shows what is bought and how much — and leads back to the specific deliveries.

Report · Example Bistro01–29.10.2026

Deliveries12 Turnover excl. VAT1 251,06 € Last delivery29.10 · 104,16 €

By product

Tomatoes, class I · BG214.4 kgCucumbers, class I · GR19 cratesLemons · ES640 pcs

Key decisions and why they were made.

01

The order stays in the customer’s units of measure

The customer orders 20 kg of tomatoes, 4 crates of cucumbers and 60 lemons. The system doesn’t convert everything into kilograms: it checks the stock in each unit and immediately shows what is short.

02

The price depends on the customer and the date

Price groups (HoReCa, shops) have prices with a validity date. An order for tomorrow takes tomorrow’s price, not today’s.

03

The document follows what was delivered

The tomatoes weigh 20.4 kg, and there are 3 crates of cucumbers instead of 4. The document is based on the actual quantity, and what is missing stays for the next delivery — traceable in the order.

04

Automatic sending — with rules and control

The quote can go out on a schedule, but only if the price changes are within set limits. This week cucumbers went up by 12% because of a shortage, so the quote waits for a review.

Technologies

Technologies

Built with Python and PostgreSQL on the server and HTML, CSS and JavaScript in the browser: the business logic and data, the overview, the figures, the documents and the quotes.

  • Pythonbusiness logic on the server: orders, business partners, price groups, documents
  • PostgreSQLdatabase: products, classes, origin, units of measure, prices by date
  • JavaScriptlogic and calculations in the screens
  • HTMLstructure and accessibility of the screens
  • CSSlayout on desktop and phone
Solution architecture

Components and connections

  1. InterfaceOverview, orders, picking on a phone, document, quote, report, AI analysis done
  2. Systembusiness logic on the server (Python): orders, business partners, price groups, documents done
  3. DatabasePostgreSQL: products, classes, origin, units of measure, prices by date done
  4. Market pricesapproved sources; AI only for matching and summarising future server side
  5. Sendingquotes by email by rules; a review when there is a deviation future server side
What it shows

The result

The prototype shows the value of the system as a whole: one order goes through the stock, picking and the document and reaches the customer’s turnover, while market prices help with the commercial decision. The next step for a real warehouse is an analysis of its data and documents.

What we clarify in a real project

  • How orders come in today and who enters them.
  • Which units of measure and classes are used and how they are converted.
  • Where market prices come from and which sources are reliable.
  • Which accounting system is used and which documents are issued.

Do you work with orders, units of measure and prices that change every day?

Cookie settings

The website uses no cookies, visitor analytics or advertising. Your browser keeps only one necessary setting:

If we add an optional service, we will ask you here before loading it.

Details in the policy