On this page
- The short answer
- Map your actual lifecycle
- What makes seed different
- Can a generic ERP work?
- Plan by season and variety
- Start the record in the field
- Connect grower activity
- Field quality in the record
- FOLLOW THE LOT
- Warehouse is traceability
- QC history stays with the lot
- Both traceability directions
- Not a batch-number field
- Testing as a quality gate
- Processing as one lineage
- Reconcile expected yield
- Warehouse and C&F
- Seasonal sales and returns
- Mobile field work
- What stays outside the ERP
- Industry fit vs workaround
- The difficult scenarios
- Standard or custom?
- Red flags
- Evaluation record
- What customer proof?
- Evidence: Limagrain
- Evidence: Pioneer / Corteva
- How exactllyERP fits
- Checklist
- Go deeper
That makes the ERP evaluation different from simply asking whether the software supports manufacturing, inventory or batch management.
The buyer needs to know whether the operating record remains connected from planning and field production through growers, quality, processing, lot transformation, packing, warehousing, distribution and finance.
The useful question is not “Does your ERP support seed manufacturing?”
It is “Can you show us our seed lifecycle without losing the identity, quality status or commercial meaning of the material as it moves?”
The short answer
A seed company should evaluate ERP by following the real operating chain.
That chain may begin with:
- season
- variety
- production location
- field
- grower
- production lot
and continue through:
- field evaluation
- harvest or receipt
- raw-seed warehouse
- processing
- processed-seed warehouse
- testing / QC history
- quality decision
- lot transformation
- treatment
- packing
- packed-seed warehouse
- distribution
- settlement
Not every seed company uses every stage in exactly the same way.
The important test is whether the proposed ERP can represent your lifecycle, preserve identity when the seed changes location or form, enforce the quality decisions that matter, and connect the result to inventory, sales and finance.
A feature checklist alone cannot prove that.
Start by mapping your actual seed lifecycle
Before comparing vendors, draw how your own seed business operates.
Do not begin with the software menu.
Begin with the business.
At minimum, map:
- crop and variety;
- season;
- production plan;
- production location;
- field or plot;
- grower or organiser where applicable;
- field activities and evaluation;
- harvest or receipt;
- lot identity;
- raw-seed warehouse before processing;
- bin allocation by seed type, lot number and season;
- processing;
- processed-seed warehouse before packing;
- quality testing and lot-wise QC history;
- treatment;
- bulking, rebulking, splitting or combining where applicable;
- packing;
- warehouse or C&F location;
- customer/dealer/distributor movement;
- returns;
- grower or supplier settlement;
- finance.
Then ask:
At which points can the identity, quantity, quality status or commercial value of the seed change?
Those are the points your ERP evaluation must test.
What makes seed ERP requirements different?
A seed business can share many processes with other manufacturers and distributors.
It still needs:
- purchasing;
- inventory;
- production;
- quality;
- sales;
- finance;
- credit control;
- reporting.
The difference is often in how those processes connect.
A production record may need to begin before the material enters a factory.
Quality may begin with field observations and continue through laboratory or plant testing.
A lot may be received into raw-seed storage, processed, stored again before packing, split, combined, treated or packed while still needing lineage back to its earlier production history.
Warehouse control is part of that traceability. Seed type, lot number and season may need to remain physically segregated in separate bins, and the QC history of each lot must remain attached to that lot as it moves.
Packed inventory may remain commercially relevant by season, variety, lot and location.
Grower payment may depend on accepted production and adjustments rather than a simple purchase invoice.
So the buyer should not ask whether the ERP has isolated modules.
Ask whether it understands the operating relationships between them.
Can a generic ERP still be right for a seed company?
Yes.
A seed company should not choose industry-specific software merely because it carries a seed label.
Some businesses have relatively simple production models.
Some may already run specialist applications around a broader corporate ERP.
Some generic ERP platforms may support the required operating model through configuration, extensions or connected applications.
The decision should depend on what your critical processes require.
Ask:
Which seed-specific operating concepts must the ERP understand directly?
Which can be configured without creating operational fragility?
Which are better handled by another specialist system?
What will have to be custom developed?
The label matters less than the evidence.
Industry knowledge should make the demonstration harder, not easier.
Plan by season, variety and production requirement
Seed operations are often strongly seasonal.
The ERP evaluation should therefore begin before production starts.
Ask how the proposed system will connect:
- crop;
- variety;
- season;
- target quantity;
- production location;
- planned acreage;
- source or production class where relevant;
- expected yield;
- processing requirement;
- packing requirement;
- demand.
The exact planning model will differ by business.
But the buyer should be able to move from:
What do we expect to need?
to:
What do we need to produce?
and eventually to:
What did the field, plant and packing operation actually deliver?
Do not assume a standard MRP screen proves that connection.
Ask the vendor to show how seasonal production becomes actual saleable seed.
Start the operating record in the field
For many seed-production models, the important operating record exists before plant receipt.
A useful field-production record may need to connect:
- season;
- location;
- field or plot;
- acreage;
- grower;
- organiser where relevant;
- crop/variety;
- production lot;
- field observations;
- expected production;
- actual production.
The terminology differs by organisation.
The principle is more important:
Do not wait until material reaches inventory before creating the history you later need to trace.
Ask the vendor:
Show us how a production field becomes part of the ERP record.
Then follow that same record forward.
Connect grower activity to the production record
Where seed production involves growers or organisers, the relationship is not only a supplier master.
The business may need to understand:
- who produced the crop;
- where;
- for which season and variety;
- against which production arrangement;
- what quantity was produced;
- what was accepted;
- what quality decisions applied;
- what advances or adjustments exist;
- what payment remains due.
Do not evaluate grower payment as an isolated finance workflow.
Ask:
Can the commercial obligation remain connected to the production record that created it?
This is particularly important when accepted quantity, quality or advances influence the eventual settlement.
Make field quality part of the operating record
Seed quality does not necessarily begin in a laboratory.
Depending on the crop and production process, field teams may need to record observations or evaluations that influence whether production may progress.
Those may include, where relevant:
- isolation observations;
- flowering observations;
- off-types;
- crop condition;
- agronomy observations;
- expected yield;
- field acceptance or rejection.
Do not prescribe one universal field-quality process.
Ask instead:
Which field observations matter to our business, and what decision should each one influence?
The important ERP question is:
Can a field evaluation affect the operating status of the real production record, or does it remain an isolated note?
FOLLOW THE LOT
This should be the hardest test in a seed ERP evaluation.
The buyer should take one real production identity and follow it through the business.
Depending on your operation, the chain may look like:
- field lot
- dispatch
- plant receipt
- raw-seed warehouse / bin
- drying or shelling
- conditioning or cleaning
- processed-seed warehouse / bin
- testing and QC history
- treatment
- bulking or rebulking
- packing
- packed-seed warehouse
The exact stages may differ.
The principle does not:
When the seed changes location, condition or form, can the ERP preserve the lineage?
Whether your business calls the identifier a lot, batch, production lot or something else, the evaluation should test the actual relationship.
Treat warehouse storage as part of traceability
Warehouse is not merely a place where seed waits between operations.
In the operating model being evaluated, raw seed can be stored before plant processing, and processed raw seed can again be stored before packing.
That means the ERP should be able to preserve the physical and logical identity of stock while it waits between stages.
Ask the vendor to show how warehouse stock is controlled by:
Where the process requires segregation, each seed type, lot number and season should remain in its correct separate bin rather than being treated as interchangeable bulk stock.
Then ask:
Can the ERP tell us exactly which lot is in which bin, for which season, and what stage of the seed lifecycle it has reached?
The physical bin should not become a break in the traceability chain.
The lot history should continue through storage before processing, storage after processing and storage after packing.
Keep QC history attached to the lot
QC should not exist only as a current status such as “Passed” or “Rejected.”
For every lot, the buyer should be able to understand the quality history that sits behind the current status.
That may include, where relevant:
- field-quality observations;
- Request for Testing;
- test definition;
- test result;
- hold;
- rejection;
- release;
- retest;
- later status changes.
The exact tests differ by crop and business.
The key requirement is:
The QC history of the lot must remain part of the lot history.
If the lot is processed, moved to another bin, treated, packed or transferred, the quality history should not be lost or recreated as a disconnected record.
Test both traceability directions
Do not accept a traceability demonstration that only works one way.
Ask the vendor to prove both.
FIELD → PACKED STOCK
Start with a production field or production lot.
Ask:
Which processed, tested, packed and warehoused material came from this origin?
Then continue to downstream inventory or dispatch where relevant.
PACKED STOCK → FIELD
Start with a packed lot in a warehouse.
Ask:
Which raw-seed lot, warehouse/bin movements, processing history, QC history, production field and grower records sit behind this stock?
Both directions matter.
A customer complaint, quality investigation, return, field issue or internal review may begin at different ends of the chain.
Do not reduce traceability to a batch-number field
A batch or lot number is only useful if the relationships behind it remain intact.
Ask what happens when your real process requires:
- splitting;
- combining;
- bulking;
- rebulking;
- treatment;
- repacking;
- reclassification;
- transfer between locations;
- storage in different bins before and after processing.
The buyer should know:
What was the source?
What did it become?
What quantity moved?
What quality status and QC history applied?
Which warehouse/bin held it at each stage?
What downstream material depends on it?
A number printed on a record is not the same as lineage.
Make testing a quality gate, not an isolated lab record
Seed testing can involve different definitions depending on crop, product, jurisdiction and company practice.
The ERP does not need every company to use the same test.
It needs to support the quality decisions your process requires.
Ask:
- How is a Request for Testing tied to the correct lot?
- Which test definition applies?
- Who records the result?
- Who can approve or release it?
- What happens if the result fails?
- Can the lot remain on hold?
- What does a retest do?
- What history remains after a status change?
- Does the complete QC history remain attached to the lot?
- Can downstream processing, bin movement or packing be controlled by the result where required?
The buyer should not stop at:
“Do you support germination testing?”
Ask:
“Show us a quality result that changes what can happen to this lot.”
That is a much harder test.
Follow processing, treatment and packing as one lineage
Seed can move through several plant activities before it becomes saleable packed inventory.
Depending on the business, these may include:
- drying;
- shelling;
- conditioning;
- cleaning;
- grading;
- treatment;
- bulking;
- rebulking;
- packing.
The ERP evaluation should connect physical transformation with:
- input lot;
- output lot;
- quantity;
- quality status;
- process/work order;
- material consumption;
- treatment or packing requirement;
- finished inventory.
Do not let the demonstration jump from raw receipt to finished stock.
Ask the vendor to show what happened between the two.
Reconcile expected yield with what was actually packed
A production plan is an expectation.
A field estimate is an expectation.
A processing plan is an expectation.
Packed output is an outcome.
The ERP should help the business understand the differences.
Ask how the proposed system can compare, where relevant:
- planned acreage;
- expected field production;
- actual receipt;
- process output;
- loss or rejection;
- usable output;
- packed quantity.
The purpose is not to force one universal seed-yield formula.
It is to make the chain measurable.
Ask:
Where did the difference between expected production and saleable packed output occur?
That is more useful than looking only at the final stock quantity.
Keep lot identity through warehouse and C&F distribution
Traceability should not stop when packing ends.
For a multi-location seed business, ask how packed inventory remains visible across:
- plant warehouse;
- depot;
- C&F location;
- branch;
- distributor-related movement where applicable.
The buyer should be able to understand:
- seed type / variety;
- lot;
- season;
- quantity;
- warehouse/location;
- bin;
- quality status;
- QC history;
- transfer history.
Where raw seed is stored before processing, and processed raw seed is stored again before packing, the system should preserve the same lot identity through each warehouse/bin movement.
Separate physical bins by seed type, lot number and season should remain visible in the ERP rather than being collapsed into an undifferentiated warehouse balance.
If barcode or scanning is part of your operating process, make the vendor demonstrate it with the same lot record rather than as a separate warehouse feature.
Connect seasonal sales, credit and returns
Seed sales can have strong seasonal patterns.
The evaluation should therefore follow commercial execution rather than stop at inventory.
Where relevant to your business, test:
- advance booking
- availability
- customer/dealer/distributor order
- credit control
- lot allocation
- dispatch
- invoice
- collection
Then test the exception:
What happens when the customer exceeds the credit limit?
What happens when the requested lot is not available?
What happens when packed seed is returned?
A return should not destroy the original lot or dispatch context.
The commercial process and the traceability record should remain connected.
Fit mobile field work into the same operating record
Field teams may work far from the main office.
A mobile application is useful only if it strengthens the same operating record.
Ask:
- What can field users capture?
- Which data is available to them?
- What happens when connectivity is weak?
- How is submitted information validated?
- Does somebody re-enter the same data in the office?
- Can photos or observations be tied to the correct field or lot where required?
- Who approves or reviews the information?
The buyer should avoid creating a second field database that must later be reconciled manually with ERP.
The useful question is:
Does field activity become part of the same source of record, or merely another place where data is collected?
Decide what should remain outside the seed ERP
Not every specialist process has to live inside one application.
A seed business may need to coexist with:
- corporate ERP;
- banking systems;
- mobile applications;
- laboratory systems;
- government or certification platforms;
- logistics systems;
- reporting applications;
- other specialist software.
The right architecture depends on the organisation.
Ask:
Which system owns each business truth?
Which information must move?
How often?
What happens when the connection fails?
Who supports the boundary after go-live?
Do not assume that a seed-industry ERP should replace everything around it.
The purpose is to design a coherent operating environment.
Do not confuse industry fit with preserving every existing workaround
A seed company can have genuinely specialised processes.
It can also have historical processes that no longer deserve to survive.
A business may say:
“Our industry is different.”
“We have always done it this way.”
Those are not the same thing.
Some current workflows may exist because:
- old software could not support a better process;
- spreadsheets became permanent workarounds;
- departments built separate records;
- an approval chain was never revisited;
- data was re-entered because systems were disconnected.
Do not custom-build the new ERP merely to preserve every historical workaround.
For each deviation from the proposed standard process, ask:
Is this genuinely required by our seed operation, customer, quality process or regulation — or are we carrying history into the new system?
That protects both generic and industry-specific ERP implementations.
Make the vendor demonstrate the difficult seed scenarios
Do not let the seed ERP demonstration become a tour through masters and transaction screens.
Give every shortlisted vendor the same operating scenarios.
The point is not to demand that every ERP navigate identically.
The point is to make every vendor solve the same difficult business problem.
Record what is standard, configured, extended or custom
After every important seed scenario, ask how the proposed result is delivered.
Classify it as:
The proposed product supports the requirement as part of its normal capability.
The result depends on settings, masters, workflow or other configurable behaviour.
Another application or extension is part of the proposed solution.
Development is required specifically for the requirement.
The claim remains proposed until evidence is provided.
None of these labels is automatically good or bad.
The buyer needs to understand what will have to exist in production to reproduce what was demonstrated.
Seed ERP red flags
The demo begins at plant receipt
Field-production history may be outside the operating record.
“Batch management” is the complete traceability answer
A number exists, but lineage through transformation remains unproven.
Field quality and plant quality are separate worlds
The business may lose the decision chain between production and processing.
Lot splitting or combining requires manual reconstruction
Traceability becomes dependent on spreadsheets or operator memory.
A failed quality result does not influence movement
Quality becomes a reporting record rather than an operating control.
Nobody can explain who can override a quality hold
Control and accountability remain unclear.
Grower payment is disconnected from accepted production
Commercial settlement requires manual reconciliation.
Traceability works backwards but not forwards
The business cannot identify every downstream consequence of an upstream issue.
Warehouse stock is controlled only by quantity, not by seed type, lot, season and bin
Physical segregation and system traceability can drift apart.
QC is stored only as the current lot status
The buyer cannot see the quality history that produced the current decision.
Packed inventory loses season, variety or lot context
Commercial stock becomes detached from production history.
Field users capture data that office users must re-enter
Mobile technology has created another disconnected record.
Every industry difference is described as custom development
The proposed product may lack sufficient native or configurable depth.
Every existing process is treated as a sacred industry requirement
Historical workarounds may be preserved unnecessarily.
External certification or traceability integration is promised without evidence
A named platform is not the same as a proven operating interface.
The customer proof is only a logo
The vendor has not shown a customer whose operating model reduces uncertainty about your own.
A practical Seed ERP evaluation record
For each critical seed workflow, record the evidence.
| Evaluation area | What the buyer should establish |
|---|---|
| Season / variety planning | How production requirement becomes field and plant activity |
| Field production | How location, field, acreage, grower and lot are connected |
| Field quality | Which observations influence progression or acceptance |
| Grower relationship | How production activity and commercial obligation connect |
| Lot identity | How lineage survives movement, storage and transformation |
| Warehouse / bins | How seed type, lot number and season remain segregated before processing, after processing and after packing |
| Testing / quality | How requests, results, holds, release, retest and complete lot-wise QC history work |
| Processing | How input, output, loss/rejection and usable output are recorded |
| Treatment / packing | How final packed identity remains linked to source |
| Traceability | Forward and backward evidence, including field origin |
| Warehouse / C&F | How lots remain visible by seed type, season, lot and bin across storage stages and locations |
| Seasonal sales | How booking, credit, allocation, dispatch and collection connect |
| Returns | How original dispatch and lot context are preserved |
| Settlement | How accepted production and adjustments reconcile |
| Mobile | How field data becomes part of the same operating record |
| Integration | Which external systems remain and how ownership is defined |
| Reporting | Which season, variety, grower, lot, quality and commercial views management can obtain |
| Delivery method | Standard / configuration / extension / custom / not demonstrated |
| Follow-up | What evidence remains unresolved |
Do not turn this into a percentage score.
One unresolved critical process can matter more than many minor feature matches.
What customer proof should a seed ERP vendor provide?
A useful customer reference is not simply another company with “Seeds” in its industry description.
Ask for proof closest to the uncertainty you are trying to remove.
If your concern is field production, ask:
Which customer actually records field, grower and production-lot activity in the system?
If your concern is quality, ask:
Which customer uses field and plant/laboratory quality decisions as part of the operating workflow?
If your concern is lot lineage, ask:
Which customer can trace seed through processing, testing, packing and multiple locations?
If your concern is corporate coexistence, ask:
Which customer operates specialist seed workflows alongside a broader enterprise system?
Customer evidence should validate the difficult workflow.
Not decorate the proposal.
Relevant operating evidence: Limagrain Seeds
Limagrain provides direct evidence across a broad seed operating lifecycle.
Its confirmed Exactlly environment includes:
- Foundation and Hybrid seed production;
- field production;
- growers and organisers;
- field agronomy and evaluation;
- mobile field activity;
- seed testing and quality control;
- plant processing;
- lot management and traceability;
- bulking and rebulking;
- packing;
- multi-location warehouse and C&F inventory;
- seasonal sales;
- customer credit controls;
- finance;
- banking API integration.
One particularly important proof point is that the operating identity begins before plant receipt and continues through later processing, quality, packing and inventory activity.
For the buyer, the required standard is even more explicit: each seed lot should remain traceable to the production field where it originated, its QC history should remain attached to that lot, and warehouse/bin movements should not break the chain.
That is the kind of evidence a seed buyer should ask every vendor to provide against the buyer’s own lifecycle.
Relevant operating evidence: Pioneer / Corteva
Pioneer provides a different kind of proof.
After the wider organisation moved to SAP globally, three specialised seed workflows continued on Exactlly:
- Field Production;
- Grower Payment;
- Quality Control.
The value of this evidence is not that every seed company should run two ERP environments.
It is that specialised seed workflows can have enough operating depth to justify continuing alongside a broader corporate ERP.
This is evidence of coexistence and specialised process depth.
It should not be interpreted as an unverified claim about the technical architecture, interface mechanism, direction or frequency between the systems.
How exactllyERP fits into this evaluation
exactllyERP should be evaluated against the same difficult seed scenarios.
Do not ask Exactlly only:
“Do you have a Seed ERP?”
Bring the actual operating model.
Include:
- crops and varieties;
- seasons;
- production locations;
- field/grower model;
- quality decisions;
- processing stages;
- lot transformations;
- raw-seed storage before processing;
- processed-seed storage before packing;
- bin segregation by seed type, lot and season;
- lot-wise QC history;
- treatment and packing;
- warehouse/C&F structure;
- seasonal sales model;
- grower settlement;
- systems that must remain.
Then ask us to demonstrate:
how the production record begins;
how identity survives each transformation;
how quality affects what can happen next;
how packed stock traces backwards through every warehouse/bin stage to the originating production field, and forwards to downstream stock or dispatch;
how grower and commercial obligations connect;
how the environment will coexist with the other systems you retain.
The relevant Exactlly proof includes real seed operating environments such as Limagrain and Pioneer.
But customer evidence should not replace your own evaluation.
The right question remains:
Can the proposed exactllyERP implementation reproduce our actual seed lifecycle with the controls and evidence our business needs?
Seed ERP Evaluation Checklist
Operating model
Planning
Field production
Field quality
Lot traceability
Warehouse / bin control
Testing / quality control
Processing / packing
Warehouse / distribution
Sales / commercial
Grower settlement
Integration / coexistence
Vendor evidence
The buyer is evaluating the seed ERP as an operating system for the real seed lifecycle rather than as a list of software features.