Skip to main content
GullySystem
E-commerce software · Custom software solution

Bottled Water Delivery E-commerce Software

This solution serves bottled water suppliers who deliver jars and cases to homes and offices on fixed days. It holds each customer’s schedule, deposits and empties, plans routes, records delivery on a driver’s phone and bills monthly or on a wallet.

Product status

Custom software solution, built to your requirements

No existing GullySystem product runs jar delivery routes, deposits and empties. The system would be written for you, and nothing counts as available until it has been designed with you and accepted.

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

A jar of water is cheap and the customer is worth a great deal. The system is built around the repeat customer, the route and the empty jar that has to come back.

It does not test or certify the water. It keeps the fill batch and the test report your plant supplies, and shows them where you choose.

  • Dispatch planners
  • Route drivers
  • Customer support
  • Home and office customers
  • Plant managers and owners
Modules

What is in the system.

Customer schedule

Standing delivery days and quantities per customer, with pauses and extra drops.

Route planning

Daily routes built from schedules and areas, with the load for each vehicle.

Driver app

Stops in order, delivery recorded, empties counted and payment noted on a phone.

Deposit and empties ledger

Jars issued, jars returned and deposits held per customer.

Billing and wallet

Monthly invoices or a prepaid balance that each delivery draws down.

Workflows

How the work runs through it.

Daily route

Schedules for the day become routes, drivers load jars and deliver stop by stop.

New customer

A customer signs up, pays a deposit, picks days and receives the first jars.

Month end

Deliveries are totalled per customer, empties reconciled and invoices sent.

Catalogue and product data

What each product record holds.

Products

Jar sizes, cases of small bottles and dispensers, every one carrying a price and a deposit.

Plant details

Source, fill batch and test report reference supplied by your plant.

Areas served

Postcodes or localities covered, with delivery days for each.

Pricing and order rules

How prices and orders are set.

Per-delivery pricing

A price per jar and per case, with a delivery charge by area where you apply one.

Deposits

A refundable deposit per jar, recorded at issue and settled at return.

Corporate accounts

Agreed rates and monthly billing for offices and institutions.

Stock and fulfilment

From stock to the doorstep.

Jar stock by status

Full, empty, with the customer and awaiting cleaning, for every jar the business owns.

Route loads

Quantities per vehicle and per stop, to match the day’s orders.

Empties reconciliation

Daily count of jars out and jars back, per driver.

Payments, returns and refunds

Taking money and giving it back.

Payments

Cash at the door, UPI and card on a link, or a wallet debited per delivery.

Disputes

A disputed jar count is compared with the driver’s record of that stop.

Admin controls and reporting

What the team can see and change.

Roles

Drivers see their route, support sees customers, and owners alone see deposits held.

Reports

Deliveries by route, jars in the field per customer and outstanding payments.

Integrations

What it connects to, and on what terms.

Payment gateway

Links and wallet top-up through a gateway, once the integration and your merchant account are tested.

Messaging

Delivery reminders on a verified messaging account.

Accounting

Invoices and receipts exported for your bookkeeper.

Deployment

How it is set up and run.

Built to order

Designed with you, then kept on our hosting or moved into a cloud account of yours.

Phased

Customer and route records first, then the driver app, then billing and wallet.

Customisation boundaries

What can change, and where the edge is.

What can change

Deposit rules, delivery days, route rules and invoice formats follow your operation.

Where the edge is

Water quality, testing and plant licensing stay with you and the bodies that govern them.

Migration and training

Moving over and getting people ready.

Bringing customers over

Customer lists, deposits and jar counts are loaded from your registers and checked on the first routes.

Training

Drivers learn the app on a short route, and support learns the customer record.

Support scope

What support covers.

Scope

Fixes to the driver app, routes and billing, and help for staff, with the contract naming hours and contacts.

Outside scope

A second plant, new cities and changes to the deposit model are quoted separately.

More in Beverages

Related solutions.

Common questions

Questions about this solution.

Is this a ready-made app?

No. It is custom work, and nothing exists until it has been designed and accepted.

Does it test the water?

No. It stores the batch and test report that your plant supplies. Testing and licensing are yours.

Does it work if the phone loses signal on a route?

Offline capture in the driver app is a requirement to settle in design. It is not assumed, because it affects cost and testing.

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.