Skip to main content

Websites for grocery and provision stores

A grocery basket is decided on price per kilo, but pack price is what gets displayed. That gap is why a 900g pack at Rs 240 outsells a 1kg pack at Rs 250 while being dearer. Publishing the unit price closes it.

What usually goes wrong online in this trade

01

Nobody divides in the aisle

Shrinking a pack while holding the price works because the shopper compares pack prices, not unit prices. Online, where the arithmetic could be done for them, almost no local grocer does it.

02

Fresh weight never matches the order

A kilo of tomatoes arrives between 950g and 1,050g because vegetables do not come in exact units. Unstated, that becomes a complaint every week.

03

Unwanted substitutions lose the customer, not the sale

Sending a different brand because the ordered one was out is the commonest grocery grievance, and it is entirely avoidable with a stated policy.

04

Cold-chain items get left at doors

Dairy and frozen goods spoil in an hour of Tamil Nadu heat. If the site never flags which items need someone home, the loss lands on the shop.

How we build it

What the theme does about it

Not a feature list — each of these exists because of a specific problem above.

  • Unit price — per kilo, per litre or per piece — printed beside every pack price, and on every size variant

  • Multi-size variants that show their own unit price, so 25kg at Rs 58/kg against 5kg at Rs 62/kg is visible without arithmetic

  • An explicit weight tolerance on fresh produce, stated as a term rather than discovered as a dispute

  • A substitution policy that defaults to omit-and-refund, never send-and-hope

  • Cold-chain items badged and flagged as requiring in-person receipt

  • Best-before dates described as read from the stock being packed, not from a catalogue

  • A dense four-column layout, because a provisions list is scanned rather than browsed

The theme for this

Complete working storefronts. Open one and use it — the filters, the cart and the product pages are all real.

Functional counter

Price per kilo on every line.

STP-PON-25
Generated placeholder, not product photography.
Grocery & provisionsComplete

A provisions store that prints the price per kilo beside every pack price, so a basket can actually be compared — and states what happens when fresh stock falls short.

Direction
Functional counter · unit-priced · variance-honest
Typefaces
Archivo · Nunito Sans
Routes
5 pages
Rendering
Static export

Questions owners ask us

My prices change every week. Is that a problem?

No, but it is a data question rather than a design one. The catalogue is edited as content, so a weekly price run is a short job. If you already price from a billing system, connecting it is a separate piece of work we would quote.

Do I have to show the unit price?

You do not have to, but it is the whole proposition. Packed commodity labelling already requires a net quantity declaration, so the number exists — this simply does the division for the customer and wins the comparison.

Can customers order on WhatsApp instead?

Yes. For a provisions order that is often faster, and the enquiry arrives with the item list already assembled.

Can it handle loose grain sold by weight?

That is the default case here. Loose rice, pulses and oils are priced per kilo or litre and packed to order, which is how a provisions counter actually works.

Tell us about your shop

What you sell and roughly how many products. We come back with which theme fits, a timeline and a price — before you commit to anything.

Or message +91 73389 72295 on WhatsApp. Either reaches the same person.

We only use this to reply. No newsletter, no sharing.