Skip to main content
GullySystem
Other industries

Batch and Serial Tracking for Organic farms

Trace goods using batch identifiers or individual serial numbers.

Manufacturing

Does this function belong in your operation?

Use when physical goods require lot history, expiry control or individual identification.

Traceable goods are received, produced or moved.

Compost windrows, seed lots and harvest lots each carry a number that links to the field and the date. A crate of tomatoes can be followed back to its bed. Recalls start from the lot.

Bring the records the workflow depends on.

  • Item tracking rules
  • Batch or serial identifiers
  • Movement and expiry records

Outputs to check

  • Lot or unit movement history
  • Trace-forward and trace-back report
  • Held or expiring stock list

Follow the batch and serial tracking workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Set tracking rules

    Identify which items require lot, serial or expiry details.

  2. 2. Capture identity

    Record the required reference at receipt or production.

  3. 3. Carry it through movement

    Preserve identifiers during transfer, issue and supply.

  4. 4. Control held stock

    Apply the authorised inspection or restriction decision.

  5. 5. Trace an issue

    Find source and destination records for the affected lot or unit.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Storekeeper

Records the batch at goods receipt and issues the oldest one first.

Quality checker

Holds a batch, releases it, or marks it rejected, and the stock obeys.

Service desk

Types a serial number and sees the sale date, the warranty and every visit made since.

Owner

Asks one question after a complaint: who else received it.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Unknown batch at receipt

Hold the affected quantity until identification is resolved.

Duplicate serial number

Investigate the physical units and source entries before accepting another movement.

Batch put on hold

Prevent the agreed issues or sales and record the authority that later releases it.

Can this work independently?

Traceability requires identifiers on the physical goods and their recorded movements. It can run from controlled imports, but goods receipt, production, stock and sales must preserve the same references. A trace report cannot recover identifiers that were never captured at a handoff.

Systems and records it connects with

  • Goods receipt: Counted, accepted and rejected supplier-delivery quantities.
  • Stock: Item-location quantities and authorised stock movements.
  • Quality control: Inspection results and authorised hold or release decisions.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.

Configure, test and introduce the workflow.

  • You tell us which items carry shelf life or serials. We write back how each will be numbered.
  • The storekeeper shows how goods arrive. You get a goods receipt screen to try, with a field for the supplier’s lot. Send current stock. A trial import comes back with gaps listed for the team to fill, using whatever batch details exist.
  • Counter and service staff practise. They issue by batch and look up a serial, and you get a trained group and a corrected import.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Tracked items cannot move without required identifiers.
  • Serial references do not duplicate active units.
  • A lot can be traced to its recorded recipients.
Organic farms

How the business operates.

Organic growers answer to an inspector as well as a buyer. The farm must show how long a field has been out of conventional use, which inputs went on, and that organic and non-organic produce never mixed. Both want the same records.

Field history and conversion status

Hold each parcel with its conversion start date, status, buffer zones and every crop, input and cover crop it has carried. The full history prints on one sheet.

Approved input register

Keep a list of permitted seed, fertilisers, soil improvers and pest controls, each with its supplier statement attached. An unlisted product cannot be recorded against a field until someone on the farm has reviewed it and filed the supplier’s statement beside it.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Parcel register and conversion status. Hold each parcel with its area, conversion start date, status and buffer zones. Past crops, inputs and cover crops print as one history sheet.
  • Approved input list. Maintain a dated list of permitted seed, fertilisers and plant protection products with supplier statements. A product not on the list cannot be applied in the record until it is reviewed.
  • Seed source statements. File the organic status or approved exception for each seed lot, with the supplier, the variety and the quantity sown on each parcel.
  • Compost and manure batches. Record source materials, windrow number, turning dates and temperature readings. Each application on a parcel names the batch.

Operational bottlenecks to check

Field history is spread over seasons of paper

Conversion dates, previous crops and past applications are in folders from different years. The inspector asks for three years on one field. Someone spends a day finding them.

Nobody checks an input against the approved list

A foliar feed arrives from a new supplier, and the label says little. Whether it is permitted is settled by memory or a phone call, after it has been sprayed on the crop. Too late.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Parcel set-up

    Each parcel is entered with its conversion start date, buffer strips, neighbouring land use and the crops it has carried. Status shows on every screen that touches it.

  2. 2. Planning and seed

    Rotations, cover crops and green manure are planned per parcel. Seed is ordered with the supplier’s organic status statement attached to the line.

  3. 3. Inputs and compost

    Any fertiliser, soil improver or pest control is checked against the approved list before it is recorded. Compost is made in numbered windrows with turning and heat readings.

  4. 4. Growing and field work

    Sowing, weeding, mulching and netting are logged against the parcel. Observations on pests and disease are filed with photographs.

  5. 5. Harvest and packing

    A harvest creates a lot code with parcel, crop and date. Grading, packing and weights are recorded against that lot, after a cleaning record is signed.

  6. 6. Sale and audit

    Orders for boxes, stalls and trade customers are packed from named lots. At audit time the history, statements and trails are printed from one place.

Industry reports to connect with

  • Parcel history for any chosen number of years, with crops, inputs and cover crops
  • Inputs applied by product, parcel and date, with approval reference
  • Compost batches with source, turning and heat readings, and where each was spread
  • Lot trail from parcel to pack to customer, forwards and backwards

Questions before implementation.

When should organic farms consider batch and serial tracking?

Use when physical goods require lot history, expiry control or individual identification. Traceable goods are received, produced or moved.

What should we bring to the requirements discussion?

Bring anonymised examples of Item tracking rules; Batch or serial identifiers; Movement and expiry records. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Trace goods using batch identifiers or individual serial numbers. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Traceability does not replace product testing, recall decisions or regulatory obligations.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Tracked items cannot move without required identifiers. Use this check when reviewing the first working version.

Talk to us

Discuss batch and serial tracking for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements