Skip to main content
GullySystem

Regular customers and bulk accounts for sweet shops

Some customers visit weekly and some order once a season. Offices, temples and regular families come back to the same shop for the same sweets. Each one is kept in the books with past orders, loyalty and any balance owed, so the counter knows who is calling.

A customer card and the account behind it

Every regular customer has a card. It holds who they are, what they buy, how they pay and what they owe. An office or a temple has an account built the same way. A contact person and a billing name sit on it.

Contact and billing name

A customer is entered with a name and a contact number. For an office or temple, the person who orders and the billing name are added. The counter finds them by either. No second card is made for a repeat visit.

Past orders and favourite sweets

Each sale or order is stored under the customer. Opening the card shows past orders, the sweets bought and the boxes packed. A family that wants last year’s festival order hears it read back at once. Memory is not needed.

Balance owed and payment history

A bulk account can buy now and pay later. Billed, paid and still owed are shown on the card. Chasing a temple that pays after the festival is left until it ends. Nothing is hidden.

Loyalty and visit record

Regular customers are marked so the counter recognises them. The record counts visits and spend. What a loyal customer earns is the shop’s decision. Record-keeping is the system’s part, not the reward rules. A familiar face is greeted by name.

A temple’s season and a family’s weekly box

A temple orders a large quantity before its festival and pays when the festival ends. A family buys a small box each week. Both are served well if the counter can see who is calling. Recognition saves a long conversation.

The family that orders every season

A regular family phones for the usual festival box. Staff open the card and read last year’s order back. Differences alone are changed. The advance is taken and the order entered. No form is filled twice.

The office buying gifts

An office buys boxes for its staff each season and pays on account. The bill goes to the named person under the office name. One account carries the whole season’s balance. Nothing is split across loose slips.

The temple that pays after the festival

One temple orders sweets for its festival and settles the account later. The balance stays open on the account after delivery. To the owner it is money still to come. When to remind is the manager’s call.

A regular at the counter

A weekly shopper who buys a fixed mix is greeted by name. Staff find the card and bring up the last purchase. The new sale joins the record. The reorder is quick. Pickup details are already on the card.

Customer cards: who reads which part

A customer’s card is read at the counter, in the kitchen and in the owner’s office. Each place needs a different slice. The counter wants the person, the manager the balance and the kitchen the last order.

For counter staff greeting regulars

Counter staff find a customer by name or contact and see the last order and any balance owed. They take a new order with its advance on the spot. Remembering is the card’s job. Staff need not guess a name.

For the owner chasing balances

The owner reads accounts with a balance owed, oldest first. Offices and temples that pay late are visible. A call to them is backed by figures. Credit is a choice, not a habit. Which accounts earn credit becomes clear.

For the head cook planning seasonal orders

The head cook reads the past orders of bulk accounts to judge what is coming. Laddus ordered in bulk last year by a temple may be wanted again. The plan has a basis. Last year’s figures sit beside this year’s book.

For branch managers serving regulars

A branch manager sees customers who buy at that outlet and the balance of each. A regular who shops at two outlets is one customer with one card. Both managers read the same history. Nobody is asked for details twice.

Credit, loyalty and account rules to settle

Credit and loyalty are promises the shop makes. Before the first account is opened, the owner decides who gets credit and who earns a reward. Then a naming rule helps staff find accounts.

Which customers may buy on credit

Decide who may buy now and pay later. Offices and temples may need it. A walk-in customer does not. Name a limit and a person who can raise it. Without a rule every customer asks.

What a loyal customer earns

Loyalty needs a reward the shop can afford. Decide whether it is a discount, a free box or a festival gift. Decide how the counter records it. The software holds the record and the shop sets the prize.

How an office or temple account is named

Temples may be known by several names. Decide the one name the account carries. Decide who its contact person is. Staff then find the same record whichever name a caller uses. Duplicates split a history in two.

Which old customers come over

Your notebook lists regular customers and open balances. Decide which names are worth carrying across. Decide which balances are still real. Unclear old entries are better closed than imported. Each carried name needs a contact. Cleaning the list first saves work later.

How customer cards reach orders, bills and reports

The customer card is joined to every sale and every order. A bill at the counter adds to the visit record. An advance order adds to the balance. Owner reports read from the same card. Nothing about a customer now lives only in a notebook. Staff change, but the record stays.

  • Counter weighing and billing attaches each sale to a card
  • Festival and wedding advance orders keep the family’s balance
  • Gift boxes and assortments remember the box a family chose
  • Kitchen production plan reads past seasonal orders
  • Accounting export carries credit sales to your accountant

Limits of customer and loyalty records

The card records who bought what and what is owed. It does not collect a payment or decide who deserves credit. Messages to customers go out through channels you set up, such as WhatsApp or SMS. Consent for those messages is the shop’s responsibility. A shop whose customers all pay at the counter can run without accounts.

FAQ

Frequently asked questions

Can we record a balance owed by an office?

Yes, a bulk account keeps what has been billed, what has been paid and the balance owed. Part payments are entered against the bills they settle. Open balances sit on one list. That list is the owner’s to read.

What does a loyalty record actually store?

It stores visits, purchases and spend for each customer. The shop decides what a regular earns. Counter staff apply that rule. The system keeps the history, not the policy. Rewards can change without touching the history.

Can a family’s last festival order be repeated?

Each past order is shown in full on the card. Staff read it back and write a new order beside it. Quantities and dates change as needed. The advance and pickup details are taken fresh. Nothing old is copied blindly.

How do we bring in our regular customers?

Share the names, open balances and past orders from your notebook or sheets. Your team and ours key and review them together before billing begins. Unclear entries are queried rather than guessed. Regulars arrive on day one.

Can customers get messages about their orders?

WhatsApp and SMS are among the channels that can be connected to the system. An order confirmation or a pickup reminder can go out that way. What you send is your decision. Whether a customer has agreed to hear from you is your responsibility too.

Where it fits

How this feature fits the system.

Sweet Shop Management Software: the parts that work with this feature, the trades that use it and the ways to put it in place.

Counter weighing and billing

Weight, rate, packing and tax meet on one bill, printed at the counter in a festival queue.

Point of Sale Billing

Festival and wedding advance orders

Bulk orders keep their date, advance and balance, and the kitchen sees what is due each day.

Order Management

Kitchen production plan

Trays to cook are set from sales history, the order book and festival dates.

Production Planning
Talk to us

Tell us what you need.

Tell us what your team does today, where work gets stuck and what you want to change.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements