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

Snacks & Confectionery E-commerce Software

A store for packed snacks and confectionery, with pack and flavour variants, batch and best-before stock, festive cut-offs, hampers and stockist ordering. It is assembled from the platform selected in discovery, with extensions where that platform cannot hold a batch rule.

Product status

Configured implementation on a commerce platform chosen in discovery

No GullySystem product runs this storefront. It is assembled from a commerce platform selected in discovery, and that platform sets how far batch rules and festive limits can go.

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 store should know what is in each batch and how many parcels can leave each day. It records the date on the stock, not only the count.

It covers the storefront, stock rules, hampers, dispatch records and a stockist portal. It does not write labels, certify ingredients or set what an allergen statement must say.

  • Merchandisers
  • Packing staff
  • Support team
  • Stockists and gifting buyers
  • Owners
Modules

What is in the system.

Storefront

A branded store with search, filters by flavour and pack, and festive collections.

Batch stock

Counts by batch with best-before dates, and picking by nearest date.

Hampers and combos

Boxes defined as sets of items, with choices inside the box.

Order limits and cut-offs

Last order dates and daily limits that close an item or a date when full.

Stockist portal

Carton-based ordering for shops and canteens at agreed rates.

Claims

A breakage and damage flow with photographs and a decision recorded on the order.

Workflows

How the work runs through it.

Festive order

A buyer picks a hamper and a date, the basket compares that date with the festive limit, and the packing desk then receives a pick list by batch.

Stockist reorder

A shop opens its last order, changes cartons and sends it, and the account is billed on the agreed terms.

Breakage claim

A photograph is uploaded against the order, a decision is recorded and a credit or replacement follows.

Catalogue and product data

What each product record holds.

Packs and flavours

Sizes, flavours and multipacks are options of one product, each with its own code and weight.

Ingredients and allergens

Text supplied by you sits beside each pack and prints on the packing slip where you choose.

Photographs and descriptions

Several images per pack, and care notes such as storage advice, shown with the listing.

Pricing and order rules

How prices and orders are set.

Prices by pack

A price per pack size, with multipack and festive prices set by rule.

Stockist rates

A separate price list and minimum carton quantity for trade buyers, hidden from consumers.

Order limits

A daily cap on parcels and a last order date for each festive item.

Stock and fulfilment

From stock to the doorstep.

Batch counts

Stock by batch and date, with low-stock and near-date lists for the packing desk.

Scheduled sync

Where a connected shop or marketplace refreshes at set intervals, the store says so and keeps a small reserve for the gap.

Pack records

Weight, box size and photograph logged at dispatch, kept with the order.

Payments, returns and refunds

Taking money and giving it back.

Payments

Card and UPI checkout through the seller’s own gateway account.

Breakage and returns

A claim adjusts the order, and a damaged pack never goes back on the shelf.

Refunds

A refund returns to the card or UPI account that paid, and support notes the reason.

Admin controls and reporting

What the team can see and change.

Roles

Each role opens only the screens its work calls for.

Approvals

A discount, refund or trade credit above your limit is held until a named person releases it.

Reports

Sales by product and batch, near-date stock, festive order volumes and claims by reason.

Integrations

What it connects to, and on what terms.

Courier services

Parcel booking and tracking with carriers that cover your pin codes, after their access has been tested.

Marketplaces

Listings and orders for chosen channels, after each channel’s access and rules are verified.

Accounting

Sales and credit notes leave as a file for your bookkeeper. Any live connection to the books is scoped as its own item.

Deployment

How it is set up and run.

Platform build

Built on the platform chosen at discovery, held in your own account where possible.

Phased

One range first, then the festive collection, then trade ordering.

Customisation boundaries

What can change, and where the edge is.

What can change

Pack options, cut-off rules, hamper layouts and page design are set to how you sell.

Where the edge is

Anything the platform will not allow, such as a batch rule it cannot hold, is raised at the start and priced as extension work.

Migration and training

Moving over and getting people ready.

Bringing products over

Pack lists, prices and stock arrive from sheets or an older store, then are reconciled to a physical count.

Training

Short sessions for the merchandiser, the packing desk and support, using your own products.

Support scope

What support covers.

Scope

After launch we correct faults and make small changes. The support terms list who to call and when.

Outside scope

Extra marketplaces, further countries and a full redesign are priced as their own piece of work.

Subcategory coverage

Where each snacks & confectionery subcategory is covered.

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

  • Chips & Savouries

    Covered on this page

    Flavour variants and box-size shipping rules are configuration of the category store, with no separate stock logic needed.

  • Biscuits

    Covered on this page

    Retailer ordering, schemes and credit are what the category solution and the existing wholesale ordering product already cover.

  • Chocolates

    Its own solution page

    Weather-driven dispatch rules and a gift personalisation flow are a different system from the category store.

  • Sweets

    Its own solution page

    Orders against a daily production plan, with slots and advances, are a different workflow from packed goods and fit an existing bakery product.

  • Nuts & Dried Fruit

    Covered on this page

    Price per kilo and bulk-to-pack conversion are rules and records within the category store.

  • Snack Bars

    Covered on this page

    Nutrition fields, variety packs and subscriptions are configuration of the category store.

Common questions

Questions about this solution.

Does a ready-made product run this store?

No. Each store is built per seller. Discovery comes first, and the platform is chosen then.

Is there anything to look at before a proposal?

Neither exists yet. No price list, trial or demonstration is published, and a written proposal sets scope and cost.

Can the store share stock with our shop?

That depends on what the shop’s billing software exposes. We inspect it before promising anything, and an interval-based update is described as such.

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.