Skip to main content
The pot size validation API uses “Growth Equivalent” logic to map raw container labels (like “400mm AS” or “20L Planter Bag”) to standardized maturity stages.

The problem

Legacy systems rely on exact string matching. This affects the supply chain because:
  • Units differ: Litres (Volume) vs. Millimeters (Diameter).
  • Formats differ: “Pot”, “Bag”, “Tubestock”, “Planter Bag”.
  • Abbreviations are common: “AS” (Air Slot), “RP” (Root Pruning), “XG” (Ex-Ground).

The solution: Growth equivalents

When you send a list of strings to /v1/verify/pot-sizes, the API maps them to a stage of maturity (0-5). This allows you to determine if two items are swappable.

The maturity hierarchy

Additional metadata

The API returns metadata for logistics and risk management.

1. Logistics information

The API flags freight constraints.
Scenario: A “Standard Tube” is flagged as is_stackable: true. A “200mm Pot” is is_stackable: false. Value: Applications can calculate that shipping 1,000 tubes is less expensive than shipping 1,000 pots.

2. Quality and risk profiles

The API provides information on handling and perishability.
Scenario: You validate a “Bare Root” tree. Response: The API returns transplant_shock_risk: "High" and seasonal_restriction: "Winter Only". Value: You can display a warning in your UI: “Warning: This item is perishable and only available in Winter.”

Example request

Example response