Seed Seller Pages: Keep Customer Garden Observations Apart From Growing Instructions

A seed packet says sow in spring and thin to a given spacing. A customer writes that theirs flowered a month early in a sheltered courtyard. Both are useful, but they are not the same kind of information. If a product page blends them, a reader may take one gardener's experience as the seller's instruction. This article proposes a way to keep them apart. It is an example workflow, not an observed result.

Two content types

Growing instructions: what the seller states for the product, such as sowing depth, spacing and general timing. These come from the seller's own packet or grower information and are reviewed by the person responsible.

Customer observations: what a person reports from their own garden, such as soil, position, sowing date and what they saw.

Each type gets its own heading on the product page, its own owner and its own update rule.

The observation record

When collecting an observation, ask for:

Product name and the lot code printed on the packet, if the customer has it.
Month and year of sowing.
Rough conditions in plain words, such as sheltered, shaded, raised bed or container.
What happened and when, in the customer's words.
Whether the customer allows publication under a first name or anonymously.

Do not ask for a street address or other private details. Do not publish exact locations; a general description of the conditions is enough.

Publishing rules

Label every observation as a customer observation and show the sowing month and conditions beside it.
Never merge an observation into the growing instructions text.
Do not present observations as advice. Use neutral phrasing: one customer reported, rather than you should.
Keep the growing instructions section unchanged unless the responsible person reviews and edits it.

Decision branches

Observation matches the instructions: publish it as an observation if it adds useful context; do not touch the instructions.
Observation differs from the instructions: publish it with its conditions, and flag it for the responsible person to consider whether the instructions need a review.
Several observations point the same way: raise a review of the instructions, but only the responsible person changes them.
Observation claims a health, safety or edibility fact: do not publish. Pass it to the responsible person, who decides what to do.
Observation lacks conditions or a sowing date: ask the customer for them, or leave it unpublished.

Stop conditions

Stop if the product or lot cannot be identified. Stop if the observation contains personal data beyond a first name. Stop if a customer asks to remove their observation; remove it promptly.

Example

Proposed example: a customer reports that a sunflower variety sown in late April reached a given height by midsummer in a raised bed against a south wall. The seller publishes it under customer observations with the April sowing month and the raised bed, south wall conditions. The growing instructions are unchanged. Later, another customer reports a very different result in a shaded plot. Both are shown with their conditions. The responsible person sees the contrast, decides the instructions are still accurate, and records that decision.

Why separation helps

Readers can compare their garden with the stated conditions. The seller avoids silently turning anecdotes into instructions, and customers see their own contribution treated as an observation rather than a guarantee.

Practical acceptance test

Prepare four sample observations: one matching instructions, one conflicting, one missing a sowing date and one claiming a safety fact. Ask a team member to process them with this article.

Pass if:

The first is published as an observation with conditions.
The second is published and flagged for review, with the instructions untouched.
The third is held for more information.
The fourth is not published and goes to the responsible person.
No private data appears on the page.

If any observation ends up inside the instructions section, fix the page structure and run the test again.

Conclusion

Customer experience enriches a product page when readers can tell whose voice they are hearing. Two labelled sections, a short record and a clear review path keep both honest.