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

Spice E-commerce & Lot Traceability Software

This solution keeps spices as lots with origin, grind and packing dates, holds blend recipes with yield loss, and links every pack to its lot. Spice sellers who grind, blend and pack their own stock are the intended users.

Product status

Custom software solution, built to your requirements

No product GullySystem runs today holds spice lots with grind dates, blend recipes or shelf-life batches. It would be written from scratch, with the scope fixed in a proposal before work starts.

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

Spices lose strength with time, so the grind date carries the same weight as the packing date. The system records both, and ties each pack back to the lot or the blend it came from.

It covers lots, recipes, packing and the storefront. It does not test purity, grade quality or state what a regulator requires.

  • Blend and grind staff
  • Packing team
  • Procurement buyers
  • Online order desk
  • Owners
Modules

What is in the system.

Lot register

Whole and ground lots with origin, supplier, receipt date and weight.

Blend recipes

Ingredient lots and percentages by weight, with the yield loss from grinding and roasting recorded per run.

Pack and date record

Pack size, packing date and best-before date for each filled batch.

Small-pack storefront

Packs from sample sizes to large bags, with whole and ground options and a per-100-gram price.

Trade orders

Hotels, caterers and shops order by kilo, on quotation and on account.

Workflows

How the work runs through it.

Lot to blend

Whole spice arrives as a lot, is cleaned, ground and blended by a recipe, and the run records weights in and out.

Batch to pack

The blend is filled into packs. Each pack batch carries its grind date, pack date and best-before date.

Order to trace

A customer’s order links to the batch. A query can find every order that used a given lot.

Catalogue and product data

What each product record holds.

Whole or ground

The same spice is offered in both forms, each with its own shelf-life rule.

Blends and recipes

A blend lists its ingredients, so the listing can show them and the system can use them.

Pack variants

Sample, retail and trade packs of one spice are options of a single listing.

Pricing and order rules

How prices and orders are set.

Per-weight pricing

A price per 100 grams drives pack prices, with a premium for small packs where you set one.

Blend costing

Cost is built from ingredient lots and yield loss, so a blend’s margin is visible.

Trade quotations

Large orders are quoted by kilo and delivered to a site.

Stock and fulfilment

From stock to the doorstep.

Lot stock

Whole and ground stock by lot, with the oldest used first.

Date control

Packs near best-before are flagged. The listing never offers a batch past its date.

Recall search

One lot number finds the batches and the orders affected.

Payments, returns and refunds

Taking money and giving it back.

Payments

Online payment for small orders, and advance with balance for trade.

Returns

Opened packs are handled as quality claims. The batch is recorded against each claim.

Refunds

Money returns by the route of payment after the batch behind a claim has been checked.

Admin controls and reporting

What the team can see and change.

Roles

Production, packing, procurement and the order desk see their own work.

Approvals

Recipe changes and trade discounts need an owner’s approval.

Integrations

What it connects to, and on what terms.

Shop product

Counter billing and stock can sit in GullySystem’s Grocery Management System, with the lot layer around it.

Label printing

Lot and date labels are generated, and printer integration is scoped once a printer is chosen.

Freight and gateway

Connected after their access and terms have been confirmed.

Deployment

How it is set up and run.

Design and hosting

Shaped with you in discovery, then operated by us or handed to a cloud tenancy you administer.

Order of work

The lot register comes first, then blends, then the storefront.

Customisation boundaries

What can change, and where the edge is.

What can change

Shelf-life rules, recipe structure, pack sizes and label content follow your range.

Where the edge is

Purity testing, quality grading and what a label must state are decided by laboratories and your adviser. The system records them.

Migration and training

Moving over and getting people ready.

Loading lots

Current stock is entered by lot and compared with your records before the first order.

Training

Grinding and packing staff learn the lot and batch screens on live runs.

Support scope

What support covers.

Included

Corrections to lots, recipes and batches, and help for your team, are covered by a written agreement.

Excluded

New markets, new product lines and label redesigns are quoted separately.

More in Grocery & Pantry

Related solutions.

Common questions

Questions about this solution.

Does this exist as a product now?

No. Development would start from nothing, and no part can be used before you accept it.

Can it help with a recall?

It can find the batches and orders that used a lot. It does not decide whether a recall is needed.

Does it say what a label must show?

No. What a label must carry is set by your adviser and the rules of each market.

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.