Skip to main content
GullySystem
E-commerce · Grocery & Pantry · Cooking Oils

Software Solutions for Cooking Oil Sellers

Cooking oil is sold in tins, bottles, pouches and jars, priced by litre or kilo, and heavy to move. Packs leak and tins dent. Sellers need unit conversion between litre and kilo, careful packing and delivery rules, and a list of oil types that matches how households choose.

At a glance

Sell by litre or by kilo, and deliver oil without a leak.

Oil is the one grocery item that is sold by volume and bought by weight. A fifteen-kilo tin and a fifteen-litre tin are not the same product.

It is also heavy and likes to leak. Delivery planning counts for as much as the price does.

Businesses and operating models

Grocery stores selling oils online

A store lists branded oils in several packs and delivers by area.

Mill and cold-press sellers

A mill sells its own pressed oils, often filled to order and delivered in glass or tins.

Caterers’ suppliers

A supplier sells tins in cartons to restaurants and caterers on account.

How an order moves

The workflow for cooking oils.

  1. 1

    Oil type and pack

    The listing names the oil, the pack type and the pack size in litres, with the kilo equivalent beside it.

  2. 2

    Price per litre

    The price per litre is shown beside the pack price, since customers compare on it.

  3. 3

    Pack and seal check

    Each pack is checked for a tight seal. Bottles go in cushioned cartons and tins in outer boxes.

  4. 4

    Heavy delivery

    Orders above a weight use a vehicle or carrier that accepts heavy loads. The delivery charge follows the weight.

  5. 5

    Leak claim

    A leaking pack is reported with a photograph, and a replacement is sent against the original order.

Where it breaks

The challenges, and what they cost.

Litre against kilo

A trade buyer orders by kilo and the warehouse counts by litre. The mismatch costs stock.

Leaks and dents

Tins dent and pouches split. The claim rate is high enough to need its own process.

Heavy loads

A carton of tins is hard to move and costly to ship, and flat delivery charges make losses.

Fill-to-order stock

A press fills bottles to order, and the listing shows stock that is really a production queue.

Requirements to assess

What is specific to this trade.

These are requirements we would confirm in discovery. They describe what the solution may need to handle. They are not features that already exist.

  • Pack volume and weight held for every oil, with a conversion rule
  • Delivery charges that follow weight
  • A claim process for leaks and dents
Recommended modules

What we would build for cooking oils.

Chosen from the commerce capabilities this business needs, not a list of everything.

Litre and kilo conversion

Density per oil type and a conversion on every order.

Delivery by weight

Charges that follow the load.

Leak and damage claims

Photographs and replacement flow.

Fill-to-order stock

Production queue and promise date for pressed oils.

Users and permissions

Who works in the system, and what each can do.

Warehouse supervisor

Counts stock in litres and checks seals.

Dispatch coordinator

Plans heavy deliveries and carrier choice.

Catalogue editor

Maintains pack data and conversion.

Integrations

What it would connect to.

An integration is confirmed only after its API, access and scope are checked. A connection that updates on a schedule is described as scheduled, not real-time.

  • Shop stock and billing, carrying litre and kilo units
  • Carriers that accept heavy loads, where they allow booking by interface
  • A payment gateway account for single orders
Implementation

How the work runs, and what we need from you.

What you provide

  • Oils and pack sizes, with density where you use it
  • Delivery vehicles and weight limits
  • Claim history from the last season

Units first

Litres, kilos and densities are agreed before any listing is written.

A heavy-parcel test

A few cartons travel by the chosen carrier to see how packs arrive.

Deliverables

What you receive.

  • A unit-conversion rule set
  • A weight-based delivery table
  • Leak claim flow
  • Staff training
Measurement

How progress is judged.

Measures are agreed against your own baseline. We do not promise a result in advance.

  • Leak claims per hundred orders
  • Stock mismatches between litres and kilos
India and international

Selling at home and abroad.

Oil types, pack sizes and labelling rules differ by country. Carriers vary in how they treat liquids, and shipping abroad is confirmed with the carrier first.

The wider requirements for grocery & pantry are on the Grocery & Pantry page.

Suitable software

Grocery & Pantry E-commerce Software

Existing product, extended

GullySystem’s Grocery Management System already runs counter billing, stock, supplier purchases, customer credit, phone and WhatsApp orders, riders and a customer ordering app for grocery shops. Pack variants, an online catalogue by area and trade orders are configured around it. Batch and best-before tracking are not among its listed modules, so they are assessed in discovery.

Oil needs litre and kilo conversion and weight-based delivery, both of which the category solution covers as ordinary catalogue and shipping rules.

Read about the software
Common questions

Questions about cooking oils e-commerce.

Can a buyer order by kilo and the warehouse count in litres?

Yes. The system holds a conversion per oil and shows both units on the order.

Are cold-pressed oils filled to order?

They can be, with a production queue and a promised date instead of ready stock.

Do delivery charges rise with weight?

Yes, by a table you set. The rule is shown to the buyer before payment.

Requirement discussion

Talk through your commerce requirement.

Describe what you sell, where you sell it and what is slowing you down. An engineer will reply within one business day.

  • No obligation
  • A reply within one business day
  • Your details stay private

Only your name, contact details and a short description are required.

Your details stay private. Privacy policyProtected by reCAPTCHA.