Skip to main content
GullySystem
E-commerce software · Configured implementation

Fresh Juice E-commerce & Delivery Software

This solution configures an online store for fresh and cold-pressed juice: order cut-offs tied to production, press dates on every bottle, delivery slots, chilled packing records and multi-day programmes with pauses. It is built on a platform selected in discovery, extended where that platform cannot hold the rules.

Product status

Configured implementation on a commerce platform chosen in discovery

A commerce platform is selected with you in discovery and set up for chilled goods, with extensions for same-day cut-offs and press dates. The platform sets how far those rules can go, and nothing here is an existing product.

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

Juice that is pressed overnight has to be sold within days. The store therefore works backwards from the delivery slot to the cut-off, and from the cut-off to the press.

It does not run the cold chain. It plans the orders and records the packing and handover that the cold chain depends on.

  • Kitchen supervisors
  • Delivery riders
  • Subscribers
  • Corporate buyers
  • Owners
Modules

What is in the system.

Storefront

Juices, shots and programmes with the next available slot shown on each.

Cut-off and press plan

Orders before the cut-off become the next press list, with quantities by recipe.

Delivery slots

Windows by area, with a limit and a cut-off for each.

Programmes

Multi-day plans with pauses, swaps and a stop date.

Chilled dispatch record

Packing method, rider and handover time logged against each order.

Workflows

How the work runs through it.

Order to press

A buyer orders by the cut-off, and the kitchen’s list for the morning shows recipes and counts.

Programme run

A subscriber pauses two days, the plan shifts and the kitchen list changes with it.

Delivery complaint

A buyer reports a bottle that arrived warm, and the dispatch record shows packing and handover times.

Catalogue and product data

What each product record holds.

Recipes and sizes

Each juice is a recipe with sizes, ingredients and storage advice, written by you.

Press date and consume-by

A press date printed on each bottle, and a recommended consume-by period shown on the page.

Seasonal menu

Juices that exist for part of the year, switched on and off by date.

Pricing and order rules

How prices and orders are set.

Slot pricing

A delivery charge by area and slot, with a minimum basket.

Programme prices

A price for a plan, with a refund rule for paused days.

Corporate orders

Standing quantities for offices, billed monthly after approval.

Stock and fulfilment

From stock to the doorstep.

Production-led stock

Availability follows the press list, so a juice not pressed is not offered.

Slot capacity

Each slot closes when it is full, so riders are not overloaded.

Chilled handover

A record of the pack used and the time the order was handed to the rider.

Payments, returns and refunds

Taking money and giving it back.

Payments

Payment by card or UPI at checkout, with a wallet or monthly billing for programmes.

Complaints

A late or warm delivery is logged with its times, and you decide on credit or a fresh bottle.

Admin controls and reporting

What the team can see and change.

Press list

Quantities by recipe for each morning.

Reports

Orders by slot, programmes by status and complaints by area.

Integrations

What it connects to, and on what terms.

Courier or riders

Dispatch to your own riders, or to a courier that offers chilled service after its terms are checked.

Messaging

Slot and delivery messages through a verified business messaging account.

Accounting

Sales and refunds as a file for your bookkeeper.

Deployment

How it is set up and run.

Platform-based

Built on the platform selected with you, and held in your own cloud or merchant account where the platform permits.

Phased

Single orders first, then programmes, then corporate accounts.

Customisation boundaries

What can change, and where the edge is.

What can change

Cut-off times, slot lengths, recipe lists and programme rules are set to your kitchen.

Where the edge is

Temperature monitoring in the vehicle is not part of the store. A sensor system would be scoped separately.

Migration and training

Moving over and getting people ready.

Bringing recipes over

Recipes, sizes and prices arrive from a sheet, and the kitchen checks each against its working copy.

Training

Short sessions for the kitchen and for riders, using real order lists.

Support scope

What support covers.

Scope

After launch we repair faults and adjust cut-offs and slots, within support terms that name the contacts.

Outside scope

Vehicle sensors, new cities and a rebuilt storefront are priced as separate work.

More in Beverages

Related solutions.

Common questions

Questions about this solution.

Is there a juice-specific product?

No. This is a configured build, put together for the seller during discovery.

Does it keep the juice cold?

No. It records how each order was packed and handed over. The cold chain itself is run by you and your riders.

Can customers pause a programme?

Yes, up to the limits you set. A pause moves the plan and changes the next press list.

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.