Skip to main content
GullySystem
E-commerce software · Existing product, extended

Grocery & Pantry E-commerce Software

This solution lets a grocery or pantry seller list staples in several packs, price them per unit, take delivery slots by area and keep shop and online stock together. It builds on an existing grocery product for the counter, and adds the catalogue and order flows each seller needs.

Product status

Existing GullySystem product, with the online storefront configured around it

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.

There is no published price, free trial or live demo for this solution. Scope and cost are settled in a written proposal after discovery.

Purpose and users

The shop already runs from one stock record. This solution lets that same record feed an online catalogue, so a counter sale and a web order draw from one number.

It covers the catalogue, orders by area, repeat baskets and trade orders. It does not source stock, set prices for you or give nutrition advice.

  • Store owners
  • Counter staff
  • Online order desk
  • Pickers and riders
  • Trade customers
Modules

What is in the system.

Online catalogue

Staples shown with pack sizes, unit prices and delivery areas, taking numbers from the shop’s own record.

Counter and stock

Billing, stock, supplier purchases and credit from the existing grocery product.

Order and delivery

Web, phone and WhatsApp orders on one list, picked, billed and sent with a rider.

Repeat baskets

A customer’s past order reloaded and edited in a few taps.

Trade ordering

Account customers order in larger quantities at agreed rates.

Workflows

How the work runs through it.

Order to doorstep

A customer orders, the shop picks and bills, and a rider delivers and records payment.

Repeat basket

A reminder offers last month’s list, and the order joins the same queue.

Trade order

A caterer or shop orders by the sack or carton against credit.

Catalogue and product data

What each product record holds.

Packs and units

One item lists several pack sizes with a price per kilo or litre beside each.

Attributes

Variety, form, brand and allergen details held as fields where they apply.

Local names

Names customers use are mapped to each item so search finds it.

Pricing and order rules

How prices and orders are set.

Rates and price changes

Prices are updated at the item level and flow to every pack, with the rate saved on each order.

Trade and credit

Account customers are shown only their agreed rates and settle against a ledger.

Delivery charges

Charges follow area, order value or weight, as you set them.

Stock and fulfilment

From stock to the doorstep.

Shared stock

The web catalogue and the counter read one stock record, refreshed on a timetable you set.

Picking and weighing

Variable-weight items are weighed at picking and billed at the actual weight.

Substitution

Out-of-stock items follow the customer’s own substitution choice.

Payments, returns and refunds

Taking money and giving it back.

Payments

Online payment, cash or UPI at the door, and credit on account for trade.

Returns

Damaged or wrong items are claimed with a photograph and credited.

Refunds

A refund returns by the original route once the claim is accepted.

Admin controls and reporting

What the team can see and change.

Roles

Owners, counter staff, pickers and riders each use their own screens.

Approvals

Price overrides and large trade orders wait for an owner.

Reports

Sales by item and pack size, delivery performance, stock and low-stock lists.

Integrations

What it connects to, and on what terms.

Grocery Management System

Counter, stock and delivery run on the existing product, which the web catalogue reads.

WhatsApp

Orders and updates run through a verified business number.

Payments and carriers

Each is linked only after the access it offers has been confirmed.

Deployment

How it is set up and run.

Hosting

The product is cloud-hosted. The web catalogue is placed with it or in an account you hold.

Start small

A handful of categories open first, so stock and delivery areas are tested.

Customisation boundaries

What can change, and where the edge is.

What can change

Pack lists, delivery areas, substitution rules and the storefront’s styling are set to your shop.

Where the edge is

Batch and best-before tracking, lot records and bulk-to-pack conversion are assessed in discovery and may need added work.

Migration and training

Moving over and getting people ready.

Loading the shop

Item lists, units and prices are loaded from your billing software or a sheet, then checked.

Training

Counter staff, pickers and riders learn their own screens before launch.

Support scope

What support covers.

Included

Corrections, small changes and staff questions follow a written agreement.

Not included

New outlets, new channels and bigger changes are scoped on their own.

Subcategory coverage

Where each grocery & pantry subcategory is covered.

Each subcategory is either covered by this solution or has a page of its own where its software requirements differ.

  • Grains

    Its own solution page

    Bulk-to-pack conversion, lot stock in kilograms and weighed billing change how stock behaves. No other grocery subcategory needs that data model.

  • Pulses

    Covered on this page

    Pulses sell in packs like grains, without bulk repacking. Name matching and repeat baskets are data and flows the category solution already covers.

  • Cooking Oils

    Covered on this page

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

  • Spices

    Its own solution page

    Lot, grind-date and blend-recipe records make a data model that no other grocery subcategory needs.

  • Sauces & Condiments

    Covered on this page

    Variants, fragile packing and date rules are ordinary catalogue and picking rules, covered by the category solution without a separate system.

  • Baking Ingredients

    Covered on this page

    Retail packs, kits and bakery repeat lists are data and flows the category solution handles. A separate system is not needed.

Common questions

Questions about this solution.

Is the whole thing one product?

In part. The shop-side product exists. The online catalogue and the flows around it are configured for each seller.

Does it hold best-before dates?

Not among the product’s listed modules. If you need them, that is assessed and added in discovery.

Can it list us on quick-commerce apps?

No. The customer store is your own. Listing elsewhere would be negotiated with those apps directly.

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.