Data Panda brings your WinTree data together with the data from the rest of your nursery. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
WinTree is built by TSD IT B.V., a Dutch software house founded in 1981 and based in Lelystad. The product is the de-facto registration system for tree-nursery production and trade in the Netherlands, with a long presence in the UK and Ireland strengthened by the 2022 acquisition of Passfield Data Systems. Six packages cover the segments the trade splits into: avenue and forest trees, hedge planters, perennial growers, container specialists, and pure traders. Around it sit the WinTree App for the field, the Cash & Carry module for the yard counter, and TreeCommerce for B2B trade between nurseries.
Pulling WinTree into a warehouse matters because tree nurseries carry a stock that takes years to grow and a season that compresses revenue into a few months. Plant-stock turnover per article-grade-size, batch-level margin against the cost of growing it, the share of revenue from municipal tenders versus landscaper repeat orders versus the auction, and the order book against what is sellable from the field this week, all live across WinTree, the accounting ledger and the webshop. In the warehouse, those sit on one grain so the buyer for next spring is making the call against last spring's data, not against a memory of how the season felt.
Stock, sales, purchasing and trade-communication data on one grain across every segment.
Let WinTree events drive the accounting, webshop and CRM stack.
Turn years of WinTree history into planting and pricing suggestions.
Internal tools on WinTree data for buyers, sellers and the field team.
A list of concrete reports, automations and AI features we have built on WinTree data. Pick the one that matches your situation.
Which plants moved this season, and which are about to lose us money?
Turnover per article-grade-size against the carrying cost of the remaining stock, with the rate of sale plotted against the same week in prior seasons. The buyer sees which articles to plant heavier next year, and which to mark down before another winter of cost is added on top.
How does our season break down across customer types?
Revenue and margin split across municipal tenders, landscapers, garden centres, dealer trade and the auction, week by week and per article group. Sales stops treating the season as one number and sees which channel really paid for the year.
Where is the order book promising more than the field can deliver?
Confirmed orders per article-grade-size against the available-to-sell stock from the WinTree field count, with the gap surfaced before the lift week. The yard team gets a list of substitutions to negotiate while the customer is still planning, instead of a phone call from a planter standing in front of an empty truck.
Plant-stock value, batch margin and channel mix tied to the accounting ledger. The year-end stock count stops being a separate exercise from what WinTree already shows, and slow-moving articles get a real cost behind them, not just a count.
Order book, tender hit rate and customer-segment margin in one view. The sales team works the season on data that already separates the municipal tender from the dealer repeat, instead of treating both as nursery revenue.
Order book against available-to-sell from the field, slow-moving stock with carrying cost and TreeCommerce trade activity on one dashboard. Lift planning runs against the same numbers the office quotes on.
Sales invoices, credit notes and supplier bills from WinTree post into Exact Online with the correct customer, VAT code and ledger account resolved per article group. Dutch boomkwekerijen keep WinTree for the nursery and Exact Online for the books, without a weekly export round.
Smaller nurseries and pure traders on SnelStart get WinTree invoices and supplier bills posted into the right administration with VAT and grootboek already resolved. The bookkeeper stops rekeying the seasonal invoice spike from a WinTree export.
Article-grade-size availability from WinTree is pushed to Shopify so the webshop sells what is liftable today, with order confirmations flowing back into the WinTree order book. Nurseries running a B2C or B2B webshop next to the trade business stop double-selling stock that walked out the gate yesterday.
Landscapers, dealers and municipal contacts in WinTree, plus the trade requests that come in via TreeCommerce, flow into HubSpot as companies, contacts and deals with order history attached. Sales works the spring season against a real pipeline instead of against the inbox.
You keep the reporting tool you already have. We connect it to the warehouse where your WinTree data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Yes. The pull is on the underlying WinTree data, so avenue-tree, hedge-planter, perennial, container and trader packages all land in the warehouse on the same article-grade-size grain. TreeCommerce activity (B2B trade requests, responses and resulting orders) flows in alongside, so handel-via-handel shows up as its own channel rather than being lost in the order book.
Yes. Stock movements and counts are kept on the article-grade-size grain WinTree itself uses, so the warehouse number reconciles to the WinTree screen rather than being a roll-up that lost the size or quality on the way out. That matters for nurseries because two centimetres of trunk diameter is a different price and a different customer.
We review your WinTree setup and the systems around it. Together we pick the first thing worth building.