Lots by lab code and cut week
A lot is a lab code and the week it was cut, and a line is not a lot. Every count, transfer and loss hangs off the lot the bench actually wrote on the label.
Contract propagation labs
Tissue culture software for contract propagation labs
Lots, cut weeks, tub and plant counts, losses and deliveries on one record, so the report your plant-health authority or your customer asks for is prepared from what the bench already wrote down.
Free plan to start. No card needed.
The record a lab is asked for
A contract lab runs on volume, on weeks rather than dates, and on paperwork that leaves the building. These are the things that have to be right the first time they are written.
Tubs and plants, kept apart
A tub is what a controller inspects; a plant is what a customer receives. Both counts are recorded, plants-per-tub is held per stage, and a derived figure says it is derived.
Losses before and after control
Scouting disposals, controller grades and dispositions logged where they happen, so the tub balance reconciles and a missing sheet shows up as a number rather than a surprise.
Media recipes and SOPs
Keep the recipe a jar was poured from and the SOP a step followed attached to the culture, with the version that was current at the time.
QR labels for jars, trays and batches
Print labels before the bench fills up and scan one to open its record on a phone at the hood.
Deliveries with a history
Mark what left as cut plantlets, in agar or acclimatised, to which customer and when, so the lot record travels with the delivery when someone asks where it came from.
Written for the way a contract lab actually runs
Planning is a week, not a date. Stock is a count as of a week, a cut is planned for a future week, and the same lot is inspected at several stages with a different number of plants in each tub. xPlant Pro records at that resolution — the lab's own codes, its own stage names, its own grade vocabulary — rather than asking the bench to translate into somebody else's.
Many labs answer to a plant-health authority, and some ship across a border or hold listed genera whose provenance has to be documented. xPlant Pro is record-keeping software: it keeps the lot history, the counts and the lineage that those documents are prepared from, and a person reviews what leaves. It does not inspect, permit or verify, and your authority's own system remains the source of truth for what it requires.
Questions labs ask
We plan by week and label by lab code. Does the record follow that?
Yes. A lot is identified by lab code and cut week, stages carry the names your bench uses, and counts are kept in tubs and in plants with plants-per-tub held per stage rather than as one figure per lot.
Can it prepare the paperwork our plant-health authority asks for?
It keeps the lot history, counts, losses and lineage those documents are prepared from, and it can render them in the shape you are asked for, for you to review before anything leaves. Your authority's own system stays the source of truth; xPlant Pro does not inspect, permit or verify.
Our mother stock arrives already initiated from another lab. Is that a problem?
No. A pipeline can start at multiplication, and a lot can record an arrival origin instead of an initiation, including the token your supplier used for it.
Is there a free plan?
Yes. Start on the free plan and move to a paid plan when the lab needs more seats or records. Current plans and what each includes are on the plans page.
Keep the lot record the way the bench writes it
Lab codes, cut weeks, tubs and plants, on one record with every change attributed to a person. Start with the free plan and bring in the sheets you use today.
Free plan to start. No card needed.