> For the complete documentation index, see [llms.txt](https://docs.live-eo.com/tradeaware/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.live-eo.com/tradeaware/additional-resources/glossary.md). # Glossary This glossary provides simple definitions of key terms related to TradeAware. It's a quick reference to help you understand the terms we use, making it easier for you to navigate and use our platform. #### Analysis A determination of the risks present on a plot of land using geospatial analysis including TradeAware's Precision Analysis which distinguishes deforestation from agricultural management. #### Business connection It is the result of accepting a business invitation. When a buyer and a supplier establish a business connection the supplier's plots are shared automatically with the buyer. It is important to note that the data sharing flows downstream, from suppliers to buyers, and not the other way around. #### Business invitation A request from a buyer to a supplier asking to share the geolocation data of their plots for the EUDR compliance process. It is similar to the concept of inviting other users in a social network to connect and share data. In TradeAware context, business invitations are a way to establish business connections. #### Commercial network It allows companies to connect with each other for ongoing data sharing to simplify the process of ongoing due diligence and to prevent re-entry of plot information for each new buyer request. It allows suppliers to request and anonymously share data from their sub-suppliers so they don’t have to worry about sharing commercially sensitive data. #### Commodity Commodities means those referenced in the EUDR namely: Cattle, Cocoa, Coffee, Oil Palm, Rubber, Soya, and Timber. #### Plot As defined in the EUDR "land within a single real-estate property, as recognised by the law of the country of production, which enjoys sufficiently homogeneous conditions to allow an evaluation of the aggregate level of risk of deforestation and forest degradation associated with relevant commodities produced on that land." **Transaction** An entity in TradeAware that can be used to create due diligence statements by linking to product information in items such as purchase orders (PO). **Product**: an item in a buyer's product list in TradeAware, with a name, an EUDR HS code and an optional reference. The commodity comes from the HS code. **Plot mapping**: the set of plots a supplier links to a buyer's product, saying which plots that product comes from. Each supplier of a product has their own mapping. **Mapping valid until:** an optional date a supplier sets on a plot mapping. It's for information and doesn't block the mapping once it has passed. **Product status:** Not shared, Shared, Ready or Expired, showing how far the plot data for a product has come. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.live-eo.com/tradeaware/additional-resources/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.