The list is not the harvest
One note says “12 bunches of zinnias” and another “30 cosmos stems, cutting pending”. To prepare a weekly list, a supervised register could preserve units and separate prepared from expected flowers. Do not convert bunches into stems or a forecast into a reservation: the grower checks each line and confirms what can be offered.
Pistil Production says it updates its variety and price lists weekly during the growing season and that stems per bunch can vary by variety. That is one grower’s practice, not an equivalence for your farm.
A completely fictional working example
For the week of 9–15 November, invented notes say: “Pink zinnia: 12 bunches already prepared, 10 stems per bunch, checked on Monday; white cosmos: 30 stems expected for cutting on Wednesday, check pending; orange dahlia: quantity not counted, price pending.” There are no orders or reservations in this example.
Expected record: zinnia, 12 bunches, 10 stems per bunch, prepared and checked Monday; cosmos, 30 stems expected for Wednesday, confirmation pending; dahlia, quantity and price pending. The offer week is not a cutting date. Do not add or translate units without a checked rule for each line.
An offer register with statuses, not a promise
Adaris could assess a custom register bringing together growing notes, quantities and dates with their sources and statuses. An AI function could suggest a list and flag missing details; the grower would check each line before deciding whether to share it. Connecting other systems would depend on compatibility, permissions and the agreed scope.
In the fictional example the zinnia is recorded as 12 prepared bunches of 10 stems; the cosmos is 30 stems expected for Wednesday and awaiting confirmation; the dahlia has no quantity or price. These are illustrative notes, not real stock or a measured AI output. There are no reservations, automatic conversions or guaranteed deliveries.
Return to the notes before sharing
Check variety, colour, quantity, unit and date against the source. If the answer turns 30 expected cosmos stems into 30 available bunches, correct it and keep the line pending until checked. Also check whether a quantity is already committed: the fictional input contains no reservations, so you cannot deduct them or guarantee delivery.
Philadelphia Floral Guild posts availability week by week; Cut Flower Exchange describes a weekly list with prices and quantities of stock. These are examples of specific businesses’ communication, not proof that your list is current. Add an update date and confirmation conditions suited to your own process.
A small test before using real data
To assess a prototype, prepare three invented notes: the example above, one with bunches but no stem count, and one with a later update changing the quantity. Compare each list with its source and count changed units, omitted statuses and invented details; measure preparation and review time separately against your usual method. These are proposed measures, not observed results or a guarantee of savings.
Use fictional data in the trial; do not share producers’ or customers’ commercial or personal data without permission and suitable access, use and retention conditions.
From notes to a supervised process
If updates and reservations need gathering, Adaris can assess custom development with change history, permissions and human review before preparing a list. The proposal does not assume connected stock systems or automatic sending.
Agree which source prevails if notes conflict, who confirms each line and how errors, data, retention and maintenance are handled. Compatibility with particular programs is not assumed. Commercial contact is in Spanish.
Related services
Sources
Want to organise your cut flower availability?
Adaris brings AI-integration expertise to flower growers, structuring weekly stem lists, reservations and changes with a history for production staff to confirm availability and composition. Tell us in Spanish how you prepare your lists. We can assess development for your workflow.

