Garden centres and independent nurseries in Australia (retail plants, native species, landscaping supplies, workshops) operate retail frontage (200–500 plant species in stock, seasonal turnover Feb–Apr spring rush, seasonal slump Jun–Aug winter quiet), host weekend workshops (propagation classes, garden design, pest control, seasonal planting), manage landscape design clients (design + installation over 2–6 month phases, recurring maintenance contracts), wholesale distribution to landscapers (bulk orders at 20% discount, net-30 terms), and manage supplier relationships (reorder species, negotiate stock levels). Revenue model: 40% retail ($200k/yr for mid-sized nursery), 30% workshops ($150k, 2 workshops/week × 50 attendees × $30 ticket = $156k), 20% landscape design ($100k, 2–3 projects/month at $3–5k each), 10% wholesale ($50k, 3–5 landscaper clients × $800–1.5k orders/month). Current system: generic retail POS (Square, Xero, Shopify) handles cash tills but doesn't track plants as living inventory—no species data, no batch tracking, no seasonal health status, no propagation age (are these cuttings 2 weeks or 8 weeks old? when are they saleable?). Nursery manager (Tom) uses Excel: "Tomato seedlings—50 trays in stock, cost $0.80/tray, selling $4.95 each. Roses—80 plants, red ones = 30, pink ones = 20, unknown variety = 30 (oops). Propagations: fuchsia cuttings started Feb 15—now Jun 13, are they rooted? Unsure." Inventory counts happen every 3 months by hand (walk through nursery, count each batch, 6 hours of labour). Accuracy is 65% (spreadsheet vs reality don't match, some plants sold before Tom updated spreadsheet, some died mid-count). Workshops: bookings via Facebook or email ("Hi, I want to register for Sunday propagation class"), Tom manages a spreadsheet (50 names, some might not show), no email confirmations, 40% no-show rate (people forget). Landscape clients: Tom emails PDF designs, client reviews, requests changes via email, Tom updates design file manually, no version control (which version did client approve?). Wholesale orders: landscapers call or email "I need 30 bags of mulch + 15 wattle trees." Tom checks Excel stock (outdated), says "yes," ships, later finds out wattle trees were already sold to retail (double-booking, lawsuit risk). Supplier ordering: Tom orders "50 ferns" but distributor has 5 varieties of ferns, Tom doesn't specify which, shipment arrives wrong species, wastes $400. Seasonal labour: Feb–Apr spring rush, Tom works 70hr weeks, hires 2 temps (cost $3k), still falls behind (customers can't find staff answers—"are these salvias perennial or annual?" staff doesn't know, spreadsheet is on Tom's laptop not accessible). Plant care reminders: customers bought roses in Mar, don't know to spray for black spot in Jun, roses get diseased, customer buys fungicide elsewhere (lost follow-up sale + customer sees Tom's roses as "diseased" instead of "customer failed to spray"). By year-end: Tom is burned out (manual labour, no data), inventory accuracy is 60–70% (lost sales due to miscounts, overstock of slow-moving plants), workshops are 40% no-show (inefficient labour), landscape projects are delayed (version control nightmare), wholesale has liability risk (double-bookings, wrong species orders), and customer follow-up is zero (no reminders, no data on what they bought when). Total operational bleed: ~$64k/yr manual ops + lost wholesale risk + customer churn from poor follow-up.
A mid-sized independent garden centre in Queensland with 3 acres (1 acre retail frontage, 1 acre propagation shade house, 1 acre outdoor plant nursery stock), 250 plant species in stock (annuals, perennials, natives, shrubs, trees, specimen plants), 2 full-time staff (Tom manager + Sarah retail), 3 part-time weekend staff (Nov–Apr spring rush only), $500k annual revenue (retail $200k, workshops $150k, landscape design $100k, wholesale $50k). Customers: retail walk-ins (families, gardeners, landscapers buying odd jobs), workshop attendees (500/yr, repeat customers), landscape design clients (8–12 active projects at any time, $3–8k each), wholesale clients (3–5 landscaper businesses, $5–15k/yr each). Current system chaos: generic retail POS (Square or Shopify basic) handles cash/card tills but not plant-specific data. Tom uses Excel "Nursery Inventory Master 2026": columns = Species, Colour, Batch ID, Quantity, Cost, Retail Price, Date Received, Health Status, Propagation Age, Seasonal Availability. Rows: "Roses Red—20 plants, cost $2.50 each, sell $12, received Feb 15, good health. Fuchsia cuttings (Feb batch)—40 cuttings, propagation age unknown (Tom wrote down 'started Feb 15' but didn't track rooting progress), unsure if saleable yet. Wattle seedlings—30 pots, cost $0.95, sell $5, mix of 'Golden Wattle' and 'Silver Wattle' (Tom forgot which is which). Tomato seedlings—[PENDING RECOUNT]." Tom hasn't updated Excel since last week (retail sold 15 roses yesterday but Excel still shows 20). Inventory count every 3 months: Tom walks nursery with clipboard, counts plants by hand (6 hours labour), updates Excel. Reality: rose count spreadsheet = 20, actual count = 17 (3 sold since last update, Tom counted wrong). Wattle varieties: spreadsheet says 30, actual count = 28 (2 dead from underwatering, nobody logged it). Tomato seedlings: spreadsheet was "pending," still pending (Sarah sold 12 yesterday, didn't tell Tom). By count day: spreadsheet is 60–70% accurate. Tom orders based on inaccurate data (orders 50 more roses but has 17 unsold, overstock = dead plants by end of season = $100+ loss). Propagation shade house: Tom propagates cuttings Feb–May (peak time). Starts fuchsia cuttings Feb 15. Expects roots in 4–6 weeks (by late Mar/early Apr). Cuttings sit in propagation trays. Tom checks them occasionally (not systematically). By Apr, some are rooted (ready for potting + sale). Some are rotting (fungal issue, lost batch, $200 value). Tom doesn't know which is which without walking in, checking each tray, remembering what he started when. By Jun, original Feb batch is either sold or dead. No data on yield (did 100 cuttings produce 60 usable plants, 70, 40? Tom guesses). Seasonal planning: Feb spring rush arrives. Tom needs to stock 50% more plants (customers want spring planting stock). But what species sell fast? Tom guesses "roses and natives are popular." Guesses wrong in some categories (stocks 30 salvia but only sells 10, stocks 5 wattle but demand is 25—customers walk out frustrated). Workshop booking chaos: workshop "Propagation Basics" scheduled Sun 2pm. Customers email Tom "I want to register" or Facebook message "can I come?" Tom replies "yes," adds name to Excel spreadsheet. 50 people register. Sunday arrives. 30 people show up. 20 no-show (forgot, changed plans, double-booked, nobody reminded them). 30 attendees in a class designed for max 25 (cramped, poor experience). No attendee data (email addresses, plant preferences, follow-up). Workshop ends. Tom has no way to send care tips post-workshop or upsell. Landscape design chaos: client calls "I want a new garden design. Backyard, 100 sqm, mixed perennials and shrubs." Tom meets client, takes photos, sketches design on paper, brings sketch to office, updates CAD/PowerPoint manually (Tom's not a designer, design looks amateur). Emails PDF design to client. Client replies "can you move the wattle tree to the right instead of left?" Tom opens his CAD, changes it, saves as "Design v2", emails to client. Client replies "actually, I liked the original. Go back to v1." Tom is confused (which version did he send?). Opens wrong file, sends v2 again. Customer is frustrated. Month later, design is approved. Tom quotes $8k installation. Client approves. Installation takes 3 months (May–Jul). During phase 1 (May), Tom plants shrubs, takes photos, sends email "Phase 1 complete." During phase 2 (Jun), Tom is busy (spring rush, forgot phase 2 timeline). Client calls "where are you? I expected phase 2 last week." Tom checks notebook "oh, right, phase 2 is Jun 15." Phase 2 starts late. By phase 3 (Jul), project is 2 weeks behind, client is unhappy. No project tracker. By year-end: Tom has 2–3 active landscape projects, no way to forecast phase completion, customers are frustrated, Tom's reputation suffers. Wholesale chaos: landscaper client calls "I need 30 bags of pea gravel mulch + 15 wattle trees for a site job. When can you deliver?" Tom checks stock: spreadsheet shows "Mulch—100 bags in stock" (but 60 are already allocated to another customer order from 2 days ago, Tom forgot to log). Spreadsheet shows "Wattle trees—30 in stock" (but 10 are dead from recent heat wave, nobody logged it). Tom says "yes, no problem, delivery Friday." Tom allocates 30 bags mulch + 15 wattle trees from inventory. Friday, Tom packs order, discovers "oh, I only have 20 healthy wattle trees, 10 are dead, and I already sold 10 bags of mulch to retail customer Tues." Tom calls landscaper "I can only send 20 wattle + 20 bags mulch." Landscaper is angry (job is sized for 15 wattle trees but now delayed + incomplete). Landscaper cancels $2k order, calls another supplier. Tom loses $2k revenue. Supplier ordering chaos: Tom emails nursery distributor "I need 50 wattle trees." Distributor has 8 varieties of wattle (Golden Wattle, Silver Wattle, Hickory Wattle, Prickly Wattle, etc.). Tom didn't specify. Distributor ships "assorted wattle" (mix of all 8 varieties, includes some slow-moving varieties). Tom receives shipment, finds 30 plants he doesn't want (takes shelf space, slow to sell, tie up capital). Wastes $400. Plant care reminders: customer buys roses Mar 1 (Tom rings up sale, no data logged beyond "1× rose $12"). By Jun, roses should be sprayed for black spot (seasonal pest, preventative spray needed). Customer doesn't know. Roses get diseased. Customer blames Tom's roses ("you sold me inferior plants"), buys fungicide elsewhere (lost $25 care product sale), and bad-mouths Tom to friends ("his roses are diseased"). Tom has no way to remind customer or upsell preventative care. By year-end: Tom is burning out (70hr/week during spring, 40hr/week off-season, inconsistent), inventory is 60–70% accurate (lost sales + overstock), workshops are 40% no-show (wasted Tom's time), landscape projects are chaotic (delays, version control nightmare), wholesale has operational risk (double-bookings, wrong orders, customer dissatisfaction), and customer follow-up is zero (no reminders, no data, no loyalty). Total operational bleed: ~$64k/yr manual ops + lost wholesale revenue ($5–10k from double-bookings + wrong orders) + customer churn from poor care follow-up ($5–10k lost repeat sales) + seasonal labour crunch ($6k temps/overtime for peak season disorganisation). Custom platform eliminates all of it.
Why Generic Retail POS Falls Short for Garden Centres
Generic retail POS (Square, Xero, Shopify, Toast) handles cash + card tills and inventory counts (units in/out). Doesn't handle: (1) plant-specific data (species, variety, batch ID, propagation age, health status, seasonal classification—perennial vs annual, dormancy timing, watering needs, pest susceptibility), (2) living inventory lifecycle (plants age, die, propagate, have limited shelf life—a tomato seedling is worthless 12 weeks after germination if unsold), (3) propagation forecasting (when will batch of 100 fuchsia cuttings become saleable? yield forecast?), (4) seasonal inventory planning (which species spike demand Jan–Mar, which are dormant Jun–Aug, when to order stock), (5) workshop bookings + attendance (capacity management, no-show tracking, attendee data for follow-up), (6) plant care reminders (SMS nudges to customers about seasonal spray/prune/feed for plants they bought), (7) landscape design + project tracking (version control on designs, phase milestones, client sign-off), (8) wholesale order management (bulk pricing tiers, inventory allocation across retail + wholesale channels, delivery forecasting), (9) supplier ordering (integrate with distributor APIs, specify varieties, reorder automation). Spreadsheets are manual: inventory counts are monthly/quarterly (data is 2+ weeks stale by the time you use it), propagation tracking is sporadic (Tom checks trays by eye, no systematic logging), seasonal planning is guesswork (Tom stocks based on intuition, not historical demand), workshop RSVPs are scattered (Facebook + email + phone, no centralised database, no reminders = 40% no-show), landscape projects are email + PDF files (no version control, no phase tracking), wholesale orders are phone + email (no allocation logic, double-booking risk, wrong species ordering), supplier orders are via email (no API integration, manual entry errors, wrong varieties shipped). Result: nursery loses ~$64k/yr to manual ops, wholesale revenue is at risk (20–30% of wholesale orders have issues—wrong species, overpromise stock, double-bookings), customer follow-up is zero (no data on who bought what when, no reminders = lost care product sales), and seasonal labour crunch is expensive (temps + overtime during spring rush = $6k wasted). Custom platform replaces every manual step: plant-specific inventory (species, batch, health, age tracked real-time), propagation forecasting (cuttings are logged on day-1, system tracks rooting progress, predicts saleable date 4–6 weeks ahead), seasonal planning (system shows historical demand by species + season, Tom orders 8 weeks ahead based on forecast), workshop bookings with reminder SMS (customers sign up, system sends reminder Sat evening "your propagation class is Sunday 2pm, register here," attendance jumps to 85%), plant care reminders (system logs purchase, sends SMS to customer "roses need black spot spray in Jun, order here," upsells care products), landscape design in web-based tool (client approves design in browser, version is locked, phases are auto-scheduled, client is notified when each phase starts), wholesale orders with allocation (landscaper orders 15 wattle + 30 mulch, system checks real-time inventory, allocates only available stock, prevents double-booking, alerts Tom if shortfall, Tom can offer alternative species or delivery date).
What Custom Replaces: Six Features Garden Centres Need
1. Plant-Specific Inventory with Species, Batch, Health Status & Propagation Age
Tom enters nursery first thing. Currently: walks to rose bench, counts roses by hand (red ones = 12, pink ones = 8), updates Excel manually ("Roses Red—12"). System is 2+ weeks behind (spreadsheet from last count). Custom system: QR codes on each plant batch. Tom scans rose batch tag. System displays: "Roses—Red—Batch #ROS-2026-Feb-15. Received: Feb 15 (4 months ago). Cost: $2.50/plant. Retail: $12. Health: Good. Watering: 2× daily. Next prune: Sep 1. Pest risk: Black spot (spray Jun–Aug). In Stock: 12 units. Sold (this batch): 8 units since recount Feb 15. Total turnover: 40% sold in 4 months. Forecast: 15 remaining plants will sell by Aug, 10 will be slow-moving, 2 will be clearance by Sep. Action: [REDUCE PRICE? YES/NO] [PROPAGATE CUTTINGS? YES/NO]." Tom scans QR, updates stock instantly. By noon, spreadsheet = reality (no 2-week lag). Propagation age: fuchsia cuttings started Feb 15 (batch #FUCH-2026-Feb-15). Each cutting scanned into system on day-1 (100 cuttings logged). System auto-updates as Tom waters + checks progress: Feb 20: "50 cuttings show root emergence." Feb 25: "90 cuttings rooted, 10 rotted (fungal issue, isolated)." Mar 5: "all 90 rooted cuttings are potted, ready for sale." System shows: "Fuchsia cuttings FUCH-2026-Feb-15: germination rate 90%, rooting time 18 days, now saleable. Retail: $4.50/pot. 90 units available. Forecast: 85 will sell by May, 5 will remain (clearance)." Tom knows fuchsia propagation batch is ready without walking in (system logged rooting progress). Seasonal health: roses in Jun need black spot spray (pest peak season). System flags: "Roses peak pest risk Jun–Aug. Recommend: spray every 2 weeks. Preventative customer alerts enabled." System can auto-send SMS to all rose buyers: "Your roses may need black spot spray starting Jun. [BUY SPRAY HERE]." Lost propagation data: old system, Tom had no record. New system: every batch is logged. By year-end, Tom has 50+ propagation batches tracked (fuchsia 90% success, calibrachoa 75% success, lavender 60% success). Tom can forecast spring stock 4 months ahead ("Feb batch will yield 85 saleable plants by May"). Manual system labour: $3k/yr (counting inventory, updating spreadsheet, guessing propagation readiness). Custom system: $0 labour + better forecasting (Tom orders stock based on historical yield, not guesses). Labour saved: $3k/yr.
2. Seasonal Inventory Planning & Demand Forecasting by Species
Spring rush Feb–Apr: customers want summer planting stock. Tom guesses: "roses popular, natives popular, succulents popular." Guesses wrong: stocks 50 salvia (only sells 10, overstock wastes shelf space + $200 capital). Stocks 5 wattle (demand is 20, sold out by mid-Mar, lost sales). System learns: historical data shows wattle peaks Feb–Apr (landscape season, customers planning summer gardens). Roses peak year-round but especially Feb–Apr (Mother's Day, spring gift buying). Salvia peaks Mar–Apr but demand drops May (buyers transition to summer-hardy plants). System forecasts: "Feb 1 stock recommendation: Wattle 40 units (20% margin vs actual peak Feb–Apr = 30 units avg), Roses 60 units (year-round but Feb–Apr = 50 units avg), Salvia 20 units (Mar–Apr spike = 15 units avg, don't overstock May). Tomato seedlings: 100 trays (Feb–Apr surge, peak Mar = 80 trays avg)." Tom orders 8 weeks ahead (by mid-Dec for Feb stock). By Feb: forecast is 90% accurate. Overstock is eliminated (no more 50 salvia gathering dust). Understock is eliminated (no more sold-out wattle, lost sales). Capital efficiency: system freed up $2k in tied-up inventory. Off-season Jun–Aug (winter quiet): customers maintain existing gardens, less buying. System forecasts low demand: "Jun–Aug stock recommendation: Perennials dormant (reduce by 40%), natives for spring prep (increase), winter-flowering natives (increase azaleas, daphne for winter interest)." Tom stocks accordingly. Inventory turnover improves (plants sell faster, less dead plants, more capital available for high-season restocking). Labour: Tom spends 4 hours/quarter on seasonal planning (reviewing forecasts, placing orders). Manual system: Tom spends 20 hours/quarter (guessing + phone calls to distributors + manual tracking). Labour saved: $4k/yr (planning + ordering efficiency).
3. Workshop Bookings with Reminder SMS & Auto-Attendance Tracking
Workshop "Propagation Basics" scheduled Sun 2pm, capacity 25 people. Tom posts on Facebook "register for workshop." Customers reply "me!", Tom adds name to Excel spreadsheet. By Sat, 50 registrations (spreadsheet). Sunday arrives. 2pm: 30 people show up (overcrowded, poor experience). 20 people no-show (20 empty chairs, Tom wasted prep time). No reminder sent. System: customer registers online "Propagation Basics Sun 2pm." System collects: name, email, phone, gardening experience level (beginner/intermediate/advanced). System auto-sends: confirmation email + SMS "you're registered for Propagation Basics, Sunday 2pm, [VENUE]. Reply [CONFIRM]." By Sat 6pm, system sends reminder SMS "Propagation Basics is TOMORROW 2pm. [CANCEL IF NOT ATTENDING]." Of 50 registrations, 45 confirm, 5 cancel (Tom knows 25 are definitely coming, books room accordingly). Sunday 2pm: 25 people attend (capacity matched), no overcrowding. Tom has attendee list (names + emails + phone + experience level). By Wed, Tom sends email: "thanks for Sunday class! We covered [TOPICS]. Here's a [PDF GUIDE] + [SUPPLIER LINKS FOR PROPAGATION SUPPLIES]. [BUY POTS/SOIL/HORMONE POWDER HERE]." Tom upsells propagation supplies to 15 attendees ($300 revenue). Customer experience: attended good class, got follow-up resource, bought stuff, will come back. System tracks: beginner attendees (Tom can reach out "next beginner workshop is Jul 15"), repeat attendees (Tom recognizes loyal customers, offers VIP early-bird pricing), workshop feedback (system sends post-workshop survey "rate the workshop, any topics for future classes?"). By year-end, Tom has run 26 workshops (2/week × 52 weeks). Year 1: 800 attendees (50 registrations × 16 no-show% = 42 per workshop avg). Year 2 with system: 1200 attendees (50 registrations × 5% no-show = 47.5 per workshop, higher satisfaction, repeat bookings higher). Labour: Tom spends 6 hours/workshop on admin (confirm attendees, chase registrations, track attendance). System: 0 hours (auto-reminders, auto-tracking). Labour saved: $3k/yr (312 hrs/yr at $10/hr average overhead).
4. Plant Care Reminders via SMS (Upsell Preventative Care Products)
Customer buys roses Mar 1. Tom rings up sale ("1× roses Red $12"), no data logged except receipt. By Jun, roses should be sprayed for black spot (seasonal pest, occurs Jun–Aug in Australia, preventative spray needed every 2 weeks). Customer doesn't know. Roses get black spot fungus, leaves get spots, customer is disappointed ("Tom sold me weak plants"), blames nursery (reputation damage), buys fungicide elsewhere (lost $25 spray sale), never comes back (lost future $50/yr repeat business = $250 over 5 years). System: customer buys roses Mar 1. System logs: "Customer Jane Doe, Roses Red, Qty 1, Date Mar 1. [CARE REMINDERS: ENABLED]." By Jun 1, system sends SMS: "Hi Jane, your roses may need black spot spray starting now (Jun–Aug peak). Preventative spray every 2 weeks keeps them healthy. [BUY FUNGICIDE HERE]." Jane clicks link, buys spray ($25). By Aug, Jane sends photo of roses (healthy, no spots). Jane is happy, tells friends, comes back next spring (buys $80 new plants). System tracks: "Jane's roses treated, zero disease. Follow-up upsell successful. Customer lifetime value increased $250 (one upsell × $25 spray, plus future loyalty)." Scale 200 spring plant buyers × 50% upsell rate × $25 average = $2.5k revenue gained. Manual system: zero follow-up (Tom doesn't know who bought roses, when, so can't remind). Labour: Tom or staff member spends 8 hours/month chasing care reminders manually (email list, phone calls). Custom system: automated. Labour saved: $2k/yr. Revenue gained: $2.5k/yr. Total impact: $4.5k.
5. Landscape Design Project Tracking with Client Approval & Phase Milestones
Client calls "I want a new garden, 100 sqm backyard, mixed shrubs + perennials, budget $8k." Tom meets, takes photos, brings to office, sketches design on paper. Current system: Tom uses PowerPoint or CAD (amateur, slow, no version control). Tom emails PDF design to client. Client replies "can you move wattle to the right?" Tom opens file, changes it, saves as "Design v2", emails to client. Client replies "actually, I liked v1." Tom opens wrong file (is it v1 or v2?), sends wrong version again. Client is frustrated (3 email back-forths, designer can't track versions). Month later, design is approved. Tom quotes $8k installation over 3 months (May phase-1, Jun phase-2, Jul phase-3). May: Tom plants phase-1 shrubs, takes photos, emails "Phase 1 done." Email goes to spam. Client doesn't see it. Client calls Jun 1 "where's phase 2?" Tom says "it's Jun 15." Client is confused ("I thought phase 2 was June 1, you're 2 weeks behind"). Phase 2 is delayed. By Jul, project is 3 weeks behind, client is frustrated, leaves bad review on Google. System: client signs up, creates "Backyard Garden Redesign" project. Tom uploads photos, system has design tool (web-based, not PowerPoint). Tom sketches design (web canvas, can add text/notes). Client logs in, sees design live, can click to request changes: "move wattle tree 2 meters right." Tom updates design (change is tracked in version history). Client approves. System locks design as "APPROVED v3" (version control automatic). Tom quotes $8k over 3 phases (May, Jun, Jul). System auto-schedules: "Phase 1 (May 1–15): plant shrubs. Phase 2 (Jun 1–15): install perennials. Phase 3 (Jul 1–15): final touches. [SCHEDULE IN CLIENT CALENDAR]." Client calendar shows all phases. May 1: Tom logs in, marks "Phase 1 [IN PROGRESS]." System auto-sends SMS to client: "Phase 1 of your Backyard Garden is starting today! [LIVE PROJECT TRACKER]." Client logs in, can see daily progress photos (Tom uploads). May 15: Tom marks "Phase 1 [COMPLETE]." System auto-sends SMS: "Phase 1 complete! [VIEW BEFORE/AFTER PHOTOS]." Client sees photos, is delighted. Jun 1: Tom marks "Phase 2 [IN PROGRESS]." System detects: phase is on-time. Client automatically notified. By Jul 15: all phases complete on-time, client is happy, gives 5-star review, refers friends (referral = $3k new project). Manual system labour: 16 hours/project (email design back-forths, no version control, manual scheduling). Custom system: 4 hours/project (design uploaded once, version control automatic, phases auto-schedule, photo uploads streamlined). Labour saved: 12 hours × 4 projects/quarter = 48 hours/yr = $2k/yr. Reputation gain: referrals increase 30% (happy clients are 3x more likely to refer), average 2 new projects/quarter from referrals = $6k/yr. Total impact: $8k/yr.
6. Wholesale Order Management with Inventory Allocation & Variety Specificity
Landscaper client calls "I need 30 bags pea gravel mulch + 15 wattle trees for a site job. When can you deliver?" Tom checks Excel: "Mulch—100 bags in stock." Spreadsheet doesn't show allocations (60 bags are already promised to another customer, Tom forgot). Tom says "yes, deliver Friday." Friday, Tom packs order, discovers shortfall: 70 bags are allocated/already shipped, only 30 available. Tom calls landscaper "I can only send 30 mulch, 50 bags short." Landscaper is angry (job needs 30, now fulfilled, but 50 short looks bad—landscaper has to source elsewhere). Wholesaler trust erodes. Also: wattle trees. Tom says "15 wattle," but spreadsheet doesn't specify variety. Distributor earlier shipped "assorted wattle" (Golden, Silver, Hickory, Prickly mix). Tom allocated "15 wattle" but doesn't know if it's Golden (landscaper wants) or Silver (landscaper doesn't want). Landscaper receives Silver wattle (wrong), job is delayed (landscaper has to source Golden elsewhere). System: landscaper orders via online wholesale portal: "30 bags pea gravel mulch (particle size 5–10mm) + 15 wattle trees (Golden Wattle only)." System checks real-time inventory: "Pea gravel 5–10mm: 30 in stock. Golden Wattle: 15 in stock (after retail allocation). [CONFIRM ORDER]." System auto-allocates: reserves 30 bags pea gravel + 15 Golden Wattle from inventory (retail sees reduced available count, can't oversell). System assigns picking ticket to Tom: "Order #WHS-001 for [Landscaper Co]. Pick: 30 bags pea gravel (row C shelf 2), 15 Golden Wattle trees (propagation house batch #WAT-2026-Apr-01). [MARK COMPLETE]." Tom picks, scans each item, system updates inventory. By Fri delivery: system auto-generates invoice (pricing tier 20% off retail, net-30 terms), packing label, tracking number. Landscaper receives correct order, on-time, exact specifications. Landscaper orders $1.5k/month every month (reliable supplier = loyalty). Manual system: wholesale orders are ad-hoc (phone/email, data loss risk, double-booking). Custom system: wholesale orders are streamlined (portal, real-time inventory, allocation logic, zero double-bookings). Labour: Tom spends 4 hours/week on wholesale order admin (phone calls, email clarifications, picking errors, refund disputes). Custom system: 1 hour/week (orders auto-generate, picking is system-guided). Labour saved: 12 hours/week = $5k/yr. Revenue stability: wholesale orders are reliable (no more "sorry, out of stock" or "wrong species sent," reduces cancellations, improves retention). 3 wholesale clients × $1.5k/month × 12 months = $54k/yr revenue. Reduce cancellations from 20% → 5% = additional $8.1k/yr. Total impact: $13k/yr.
Australian Garden Industry Specifics & Quarantine Compliance
Australian nurseries operate under plant quarantine and biosecurity regulations: (1) interstate plant movement restrictions (can't move plants from QLD to NSW without plant health certificate for certain species—native plants, citrus, etc.), (2) pest/disease surveillance (if nursery detects notifiable pest—myrtle rust, Christmas beetle, citrus canker—must report to Department of Agriculture within 24 hours, system can flag pest risk automatically), (3) native plant provenance (native species must be from known provenance—bushfire risk, water use, local adaptation; system tracks supplier provenance), (4) organic/pesticide certification (some customers require organic or reduced-spray production; system can flag products as certified organic), (5) endangered species restrictions (some native orchids, cycads are protected—nursery must verify customer before selling). Industry organisations: Nursery & Garden Industry Australia (NGIA) sets standards, workshops teaching native plant expertise, business practices. Custom system integrates: interstate regulatory database (system checks if plant order crosses QLD-NSW border, auto-flagged for health certificate if needed), pest identification tool (Tom uploads photo, system identifies pest, alerts if notifiable, auto-generates Department of Agriculture report template), provenance tracker (supplier = seed bank, native origin tracked in system), certification tagging (organic vs conventional vs pesticide-free labels tracked per plant), customer verification (endangered species → system requires customer ID + intended use before sale). Compliance burden: reduces manual regulatory tracking, auto-generates reports, prevents accidental non-compliance sales.
Six FAQs
How do we handle dead plants or quality issues in propagation batches?
System logs "Fuchsia batch #FUCH-2026-Feb-15: started 100 cuttings, day-18 rooting check, 90 rooted, 10 rotted (fungal). Loss rate 10%." Tom investigates: "humidity too high in shade house, fungal spores thrived." Tom adjusts humidity (install fan), logs "corrective action: increased air circulation." Next batch (Mar 15): same cuttings type, Tom tracks closely (system sends daily alerts "rooting check day-10, 95 of 100 viable, loss rate 5%"). By end of season, Tom has data: Feb batch 90% yield, Mar batch 95% yield. Tom knows Mar settings are better (lower loss). System forecasts: "Fuchsia propagation: expect 92% average yield per batch (blended Feb + Mar data). Next season: start Mar settings from day-1, eliminate Feb's high-loss setup." Quality control via data.
Can we track plant health issues and prevent disease spread in propagation house?
Yes. System logs propagation house environmental sensors: temperature, humidity, watering schedule. Tom uploads daily notes: "Feb 20, observed early fungal signs on 10 fuchsia cuttings. Isolated immediately." System alerts: "fungal risk detected. Recommend: increase air circulation, reduce humidity by 5%, isolate affected cuttings, check adjacent batches daily." Tom isolates, increases air circulation (fan). System tracks: "fungal issue FUCH batch, day 5 of isolation, 9/10 salvaged, 1 lost. Cost of loss $5. Corrective action: humidity adjustment resolved issue." By next batch, Tom applies lessons (humidity dialled in = zero fungal loss). System prevents disease spread via environmental tracking + alert system.
How do we handle delivery logistics for wholesale orders?
Landscaper orders 30 bags mulch + 15 wattle trees, with delivery Friday. System auto-generates: picking list (Tom picks items, scans to confirm), packing label, delivery manifest, customer invoice (net-30 terms). System integrates with delivery partner (if using local courier): system auto-notifies courier "order ready Fri, deliver to [address], [phone], [delivery window Fri 9am–12pm]." System tracks: "Order #WHS-001, delivery Friday 10:15am, signed by [landscaper name], photo proof uploaded." Customer sees tracking live (delivery portal shows "your order is being picked, estimated delivery Friday 10am"). If shortfall (only 25 bags available, 30 ordered), system auto-alerts Tom before packing: "WARNING: only 25 bags available, 5 short. Offer customer: (A) partial shipment now + 5 bags next week, (B) wait for full stock Friday next week, (C) substitute product." Tom chooses option, calls customer, keeps order intact. Labour: Tom spends 30 min/order (check stock, pick, pack, arrange delivery). System: 5 min (system handles allocation, picking list is generated, Tom just scans to confirm). Labour saved: $2k/yr.
What if a plant species is seasonal and out-of-stock for months?
Azaleas peak Dec–Jan (winter-flowering, popular gift). Feb–Oct azaleas are slow-moving. System forecasts: "Azalea demand by month: peak Dec–Jan (30/month avg), summer slump Feb–May (5/month avg), spring return Jun–Aug (15/month avg), spring peak Sep–Oct (25/month avg)." Tom orders 8 weeks ahead: by Sep 1 (for Nov–Dec stock), Tom orders 60 azaleas (peak months = 30+30). By Feb, stock is nearly sold. Tom doesn't order more (forecasts low demand). By May (off-season), Tom has 3 azaleas in stock (very low). Jun: demand returns (spring planning), Tom orders 120 azaleas (to cover Jun–Oct, 60/month for 2 months). July: azaleas arrive. By Oct: 95 azaleas sold (forecasted 50, actual demand higher—Tom increases forecast for next year). By Nov: Tom has only 25 azaleas left (should have 60 for Dec gift peak). Tom quick-orders 40 more (expedited shipment, higher cost, but covers Dec demand). By Dec: 60 azaleas in stock, sells 55 by Jan 1. System learns: "azalea actual demand Dec–Jan is higher than forecast, increase forecast to 35/month." Next year, Tom orders accordingly, no shortage. Seasonal gaps are minimized via forecasting.
Can we integrate with plant supplier APIs to auto-reorder low-stock species?
Yes. System integrates with nursery distributor APIs (assuming distributor offers API—most big ones do: wholesale.distributor.com.au/api). Tom sets reorder rules: "Golden Wattle: reorder when stock drops below 10 units, order 20 units." System monitors inventory real-time. When stock hits 9 units (sold 1 more since recount), system auto-triggers: "purchase order created, 20 units Golden Wattle, distributor [NAME], estimated delivery 5 business days." Tom approves (1-click) or system auto-submits (if Tom has configured auto-purchase authority). By delivery date, system logs: "shipment received, 20 Golden Wattle, QC check [PASS/FAIL], added to inventory." Tom scans batch QR, system updates. Reorder cycle is automatic. Labour: Tom spends 4 hours/month manually checking stock + emailing supplier reorder. Custom system: 15 min/month (Tom reviews auto-orders, approves). Labour saved: $1.5k/yr.
How do we handle customer disputes (e.g., customer says plant died due to poor quality)?
Customer buys roses Feb 1 (batch #ROS-2026-Feb-15). Plants roses in backyard. By Apr, roses get fungal infection (black spot). Customer blames Tom "you sold me diseased plants." System logs: "Roses batch #ROS-2026-Feb-15: 30 units sold. 28 customers received plants. Customer history: John Doe, purchased Feb 1, batch #ROS-2026-Feb-15, health status at purchase [GOOD]. Follow-up care reminders sent [YES/NO]." System shows: care reminder was sent Jun 1 ("spray for black spot"), customer did/didn't click reminder. If customer never received or ignored reminder: system shows "care reminder sent, customer didn't purchase preventative spray." Tom can show customer "we recommended black spot spray on Jun 1 (email/SMS), but you didn't purchase. Roses need preventative care." If customer received poor-quality roses at purchase: system shows "health status logged Feb 1: [GOOD]. Photo taken at sale: [UPLOAD IF AVAILABLE]." Tom can show photo (roses were healthy at sale), disease developed from lack of customer care (not nursery fault). System arbitrates disputes via data (care history, health status at sale, care recommendations sent). Tom can offer discount ("next spray bottle 50% off") to resolve minor disputes, or escalate refund if health was genuinely poor at sale. Labour: Tom spends 3 hours/month on customer disputes (phone calls, email back-forths, memory fails). Custom system: customer sees full history (care recommendations, purchase health status), disputes resolved faster. Labour saved: $1k/yr.
The Bottom Line
Independent garden centres and nurseries (250–400 species in stock, 3–5 staff, $400–600k annual revenue, split retail + workshops + landscape design + wholesale + propagation) need plant-specific inventory (species, batch, health status, propagation age, seasonal classification tracked real-time), propagation forecasting (which batches are saleable when, yield tracking), seasonal inventory planning (demand by species by month, prevent overstock + understock), workshop bookings with reminder SMS (no-show rate drops 40%→ 5%), plant care reminders (SMS nudges to customers about seasonal spray/feed, upsells care products), landscape project tracking (design version control, phase milestones, client sign-off, photo progress), wholesale order management (inventory allocation, variety specificity, zero double-bookings), supplier order automation (API integration, auto-reorder low-stock, prevent wrong-variety shipping), and compliance tracking (interstate quarantine rules, pest/disease reporting, native provenance, organic certification). Generic retail POS (Square, Xero, Shopify) + Spreadsheets don't integrate these. Manual systems bleed ~$64k/yr to ops labour (inventory counts, plant guessing, workshop admin, landscape project chaos, wholesale order errors, supplier ordering) + lost wholesale revenue (20–30% of wholesale orders have issues = $5–10k lost/yr) + customer churn from poor care follow-up (no reminders, no loyalty = $5–10k lost repeat sales/yr). Custom platform automates all: plant inventory is QR-scanned (real-time, accurate, no 2-week lag), propagation tracking logs rooting progress (system forecasts saleable date, yield tracking prevents overordering), seasonal planning uses historical demand (prevents guessing, improves capital efficiency, saves $4k/yr ordering efficiency), workshop reminders auto-send SMS (no-show rate drops to 5%, higher attendance revenue, repeat bookings increase 30%), plant care reminders auto-send SMS (upsells care products, increases customer lifetime value $4.5k/yr), landscape projects use web design tool (version control automatic, phases auto-schedule, client photos tracked, reduces labour 12 hours/project), wholesale portal streamlines orders (real-time inventory, allocation logic prevents double-bookings, variety specificity tracked, reduces labour 12 hrs/week = $5k/yr + prevents cancellations $8k/yr), and supplier APIs auto-reorder (no manual email, prevent wrong varieties, auto-tracking). Build cost: $50–80k. Year one: $70k investment. Year two: $2k/yr hosting. Break-even: month 20. Year 2+: $18k inventory management + $15k retail POS admin + $12k workshop admin + $8k care reminder labour + $6k landscape project labour + $5k wholesale order labour + $13k wholesale revenue gains + $4.5k care upsell revenue = $81.5k/yr labour + revenue saved. Scale from 1-site 250-plant nursery (3 staff, $400k revenue) to 2 sites (6 staff, $800k revenue, statewide delivery, 500-plant database) without per-site licensing creep. Own your inventory. Own your propagation data. Own your customer relationships. Own your wholesale channel. Custom system. Ship faster. Serve better. Grow quarterly.
Ready to build a custom nursery management platform for your garden centre or wholesale operation? Check Aidxn's custom software packages, or book a call to discuss your current team size (2–5 staff?), inventory complexity (200–400 species?), revenue split (how much retail vs wholesale vs landscape vs workshops?), seasonal turnover (spring rush Feb–Apr?), propagation scale (cuttings/seeds, what varieties, yield tracking?), wholesale clients (3–5 landscapers ordering regularly?), workshop capacity (2–4 events/week?), and growth goals (open 2nd location, 2x revenue, statewide delivery, app for wholesale customers by 2027?).