PlantWay.← Index
— Partners

The living-goods data layer for TMS platforms.

A research and integration partnership for TMS, WMS and freight platforms whose customers move freshness-sensitive and living cargo — edible flowers, herbs, protected crops, nursery stock, hospitality botanicals.

— Background
Who is behind PlantWay

Built from horticulture, not from logistics theory.

The freshness envelopes, schema and field records on this site come from one operator — combining RHS horticultural study, organic vegetable growing and direct horticultural logistics work. Small surface, deep specificity.

  • RHS Level 2

    Royal Horticultural Society — principles of plant growth, propagation and protected cropping. Ongoing study.

  • Organic vegetable growing

    Working knowledge of soil, succession and protected-crop systems for edible production.

  • Horticultural logistics

    Operational background in moving freshness-sensitive and living cargo — greenhouses, nurseries, hospitality routes.

  • Field-record archive

    Live observational dataset from North West movements — the empirical base behind the freshness envelopes.

No inherited dataset, no scraped industry report. Every figure on this site is observational and held open for partner review.

—Field records logged · live
— Premise

Standard freight systems treat living cargo as freight.

A pallet of basil is modelled identically to a pallet of bolts. Edible-sector customers — fine-dining suppliers, hospitality wholesalers, protected-crop growers — work around this in spreadsheets. PlantWay closes the gap as a small, neutral data layer that any TMS can consume.

— What PlantWay brings

Four integration layers.

  • 01

    Freshness API

    Species × ambient conditions × loading × dispatch window → observed hospitality-viable hours. Used inside route planning to flag corridor cut-offs before dispatch.

  • 02

    Living Goods Operational Schema

    A small, open spec for living-cargo metadata — species, freshness window, airflow tolerance, dwell threshold, single-tier requirement. Any TMS can adopt it.

  • 03

    Co-published operational research

    Joint reports on freshness-sensitive freight using anonymised partner data. Differentiates the partner in the edible / hospitality vertical without engineering cost.

  • 04

    Field-record reference set

    Live operational archive from North West movements — used as a reference dataset for partner R&D and as proof in customer conversations.

— Operational schema · v0.1 (working draft)

Shape, not feature.

Held open. Documented from live work, not derived in a vacuum. Partners are welcome to extend it.

living_goods_consignment:
  species: "Edible viola"
  baseline_hospitality_hours: 4
  modifiers:
    ambient_temp_c: 22          # >18°C reduces window
    loading: "single_tier"      # vs stacked (-35%)
    dispatch: "am"              # vs pm (-20%)
    handover: "shaded"          # vs exposed (-15%)
  derived_window_hours: 2.7
  flags:
    - corridor_cut_off_risk
    - airflow_critical
— Sample record

See the format before you ask.

One anonymised dispatch record — consignment, freshness envelope, timeline, notes. The shape of every entry in the PlantWay field archive.

Download sample dispatch (PDF · 1 page)
— How it works

Research first. Integration if it earns it.

  • 01

    Conversation

    Short call. Identify which of your customer segments move living or freshness-sensitive cargo.

  • 02

    Joint operational report

    4–6 week piece. Anonymised partner data + PlantWay field records + horticultural research. Co-branded, publishable.

  • 03

    API trial

    Freshness endpoint live for one partner team. Tested against real consignments. No commitment.

  • 04

    Integration

    If the trial holds, a paid integration — per-seat or per-consignment, depending on platform shape.

— Partner enquiries

For TMS, WMS and freight platforms.

One short email. We'll come back with a proposed scope for a joint report inside a week.

partners@plantway.co.uk