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

Software Solutions for Pulse and Dal Sellers

Pulses come whole, split, with skin or without, polished or not, and each form cooks differently. Buyers know them by local names. Sellers need names and forms that match how customers search, and a repeat basket that restores a household’s monthly dal list in one step.

At a glance

List whole, split and polished dals so buyers pick the right one.

One pulse can appear as five different products. Toor dal, for instance, may be polished or oiled, split or whole, and sold under three local names.

A household buys the same set each month. Making that second order quick is where the value lies.

Businesses and operating models

Grocery stores selling dals online

A store lists dals in several packs and delivers within a local area.

Packers of branded pulses

A packer sells sealed packs directly and through marketplaces.

Monthly kit sellers

A seller offers a ration-style list that a household repeats each month.

How an order moves

The workflow for pulses.

  1. 1

    Form and name listed

    Each pulse is listed with its form, polish and the local names customers use in search.

  2. 2

    Pack size chosen

    Packs of half a kilo to several kilos are offered, each with a price per kilo.

  3. 3

    Basket from last month

    A returning customer loads the previous list, edits quantities and orders.

  4. 4

    Pick, check, seal

    The picker checks the pack against the listing before sealing, because look-alike dals are easy to confuse.

  5. 5

    Delivery and reorder

    Delivery follows the area’s route. A reminder before the usual order date offers the repeat basket.

Where it breaks

The challenges, and what they cost.

Names differ by region

One pulse has several names, and search misses the one a customer types.

Look-alike packs

Two dals in similar bags are mixed at picking, and the customer opens the wrong one.

Prices shift with supply

Prices change several times in a season, and some listings go stale.

Monthly lists are retyped

Customers re-enter the same items each month and abandon a long basket.

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.

  • Local names and forms held as searchable data
  • A repeat basket that survives price changes
  • A pick check that separates look-alike packs
Recommended modules

What we would build for pulses.

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

Synonym search

Local names mapped to each listing.

Form and polish fields

Whole, split, skin and polish as filters.

Repeat basket

One-step reorder with edits.

Pick verification

A scan or tick against the listing before sealing.

Users and permissions

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

Catalogue editor

Maintains names, forms and pack sizes.

Picker

Verifies each pack against its listing.

Customer care

Edits repeat baskets on a customer’s behalf.

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, such as the grocery product GullySystem already runs
  • A payment gateway for single and repeat orders
  • WhatsApp for reorder reminders, from a verified business number
Implementation

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

What you provide

  • Your pulse list, with local names and forms
  • Pack sizes and how they are labelled
  • The regions you deliver to

Names before pages

Local names are collected from your counter staff and your enquiry history, since search depends on them.

Test the repeat basket

A few regular customers try the monthly list before it is announced.

Deliverables

What you receive.

  • A pulse catalogue with name synonyms
  • The repeat-basket flow
  • A pick-check step
  • Staff training
Measurement

How progress is judged.

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

  • How many orders come from the repeat basket
  • Complaints about a wrong dal
India and international

Selling at home and abroad.

Pulse names and preferred forms differ between regions and countries. Overseas buyers often search by a different name, so synonyms are held per market.

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.

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

Read about the software
Common questions

Questions about pulses e-commerce.

Can customers search by the name they use at home?

Yes, where the name is in the synonym list. The list grows from your enquiries and your staff’s knowledge.

Is the monthly basket automatic?

It is offered by reminder and placed when the customer confirms. A standing auto-order is possible where payment allows it.

Does it list nutrition claims?

Only what you or the brand supply. The system does not generate claims.

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.