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

Garden Supplies E-commerce & Stock Software

This solution sets up an online garden-supplies store on a commerce platform chosen in discovery. It holds batch and date records, sowing and planting seasons, pack weights and breakable goods, and it reads stock from the seller’s billing system. It suits nurseries, garden centres and garden-goods brands.

Product status

Configured implementation on a commerce platform chosen in discovery

No existing GullySystem product covers a garden-supply storefront with live stock, seasons and weight-based freight. The online store is assembled on a commerce platform picked in discovery and shaped to the seller’s range.

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

The aim is a store that knows what is in season, what is in date and what can be shipped on which day. Staff then answer questions from the record, not from memory.

It does not give horticultural advice, test soil or inspect plants. It shows the guidance the seller writes and the details the maker states.

  • Catalogue editors
  • Nursery and stock staff
  • Dispatch staff
  • Customer care
  • Owners
Modules

What is in the system.

Storefront

A consumer store for plants, seeds, planters, soil, tools and irrigation, with season-aware listings.

Batch and date records

Lots, pack dates and stated validity for seed, soil and fertiliser, and batches for plants.

Season and region rules

Sowing and planting windows by region, shown on listings and used to hold orders.

Weight and volume freight

Freight quotes from pack weight, carton size and zone.

Claims and returns

Photographs, dated evidence and settlement for breakage and arrival issues.

Stock link

Counts read from the seller’s billing system on a stated refresh.

Workflows

How the work runs through it.

Seasonal order

A buyer chooses a variety, sees that it suits the season and region and orders with an expected dispatch day.

Heavy goods order

Soil, planters and tools ship by weight or volume, with freight shown before payment.

Claim

Damage on arrival is reported with photographs and linked to the packing record.

Catalogue and product data

What each product record holds.

Variants

Size, pot, pack or weight as options of one listing.

Season and region

Windows for sowing or planting held as data.

Guidance

Care and usage notes written by the seller and shown on listings.

Pricing and order rules

How prices and orders are set.

Pack-based prices

A price for each pack, weight or pot size.

Trade accounts

Garden contractors and garden shops see trade lists.

Subscriptions

Recurring orders for refills or seasonal boxes where the gateway supports them.

Stock and fulfilment

From stock to the doorstep.

Batches and dates

Oldest-in-date first, with batch on the order.

Dispatch rules

Orders held for days that suit live goods or long routes.

Parcel type

Light parcels, bulky cartons and heavy bags each have their own rules.

Payments, returns and refunds

Taking money and giving it back.

Payments

Card and UPI, and invoicing for trade buyers.

Claims

Photographs, dates and the packing record decide a claim.

Returns

Live goods and opened products follow the terms shown at checkout.

Admin controls and reporting

What the team can see and change.

Roles

Editors, stock staff, dispatch and care see different screens.

Reports

Stock by batch and date, orders held, freight against value and claims by cause.

Approvals

Refunds and trade-rate changes wait for an owner.

Integrations

What it connects to, and on what terms.

Commerce platform

Storefront, checkout and customer accounts on the platform chosen in discovery.

Billing system

Stock counts read from your billing system by export, or over a link that has passed testing.

Carriers and gateway

Brought in after each provider’s interface and terms are reviewed.

Deployment

How it is set up and run.

Platform based

The store is hosted on the platform picked with you, with batch rules beside it.

Season by season

The range opens in the order of the planting calendar.

Customisation boundaries

What can change, and where the edge is.

What can change

Season windows, freight rules and claim terms follow your nursery or shop.

Where the edge is

Plant health advice, soil testing and rules on moving plants stay with people and advisers.

Migration and training

Moving over and getting people ready.

Moving the range

Lists of varieties, packs and stock arrive from sheets or your billing system, then get matched to a physical count.

Training

Staff practise batch entry, dispatch holds and claim handling on live stock.

Support scope

What support covers.

Scope

Faults and small changes during the season are covered by the support terms.

Beyond scope

New sites, regions and large changes are estimated apart.

Subcategory coverage

Where each garden supplies subcategory is covered.

Each subcategory is either covered by this solution or has a page of its own where its software requirements differ.

  • Plants

    Its own solution page

    Living stock, dispatch days and arrival claims need their own data and flows, unlike the packaged goods covered by the category solution.

  • Seeds

    Covered on this page

    Lot dates, sowing windows and subscriptions are configuration of the category solution and its stock.

  • Planters

    Covered on this page

    Dimensions, colour lots and volume-based freight are configurations of the category storefront.

  • Soil & Fertilisers

    Covered on this page

    Pack weights, batch dates and refill schedules are covered by the category solution as configuration.

  • Gardening Tools

    Covered on this page

    Linked spares, serial records and trade lists are configuration of the category solution and need no separate flow.

  • Irrigation

    Its own solution page

    A layout designer, compatibility rules and a stored system record change what the software must do and need their own page.

Common questions

Questions about this solution.

Can this be bought as a finished product?

No. It is a configured implementation on a platform chosen in discovery. Nothing here is pre-built for garden sellers.

Does it name the platform?

No. The platform is chosen with you after discovery, based on your range and rules.

How much does it cost?

Nothing is listed yet. Pricing is not published, and no trial or demonstration exists. A written proposal states the scope and the cost.

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.