View all features
View all suite

Growing & production

Trade, export & supply

Retail & e-commerce

Beyond horticulture

View all industries
Library Contact sales
EN IT
library · tech brief

One system rarely fits every nursery.

A wholesale grower propagates plants and never touches a till. A garden centre rings up walk-in customers and grows nothing. They run different businesses, yet most software sells them the identical slab and lets them sort out which half to ignore.

the mismatch

A retailer and a grower barely overlap.

They sit at opposite ends of the same supply chain, with different workflows and different daily realities. A system that treats them as the same business serves neither of them well.

the one-size-fits-all trap

The cost of buying the whole slab.

The traditional way to sell business software is to build one enormous system, put everything in it, and sell that same everything to everyone. It is tidy for the vendor and miserable for the buyer. You pay for the whole thing whether you use a tenth of it or all of it, and every screen, menu and field that belongs to someone else's kind of business is still there in yours, cluttering the interface and complicating the training.

For a nursery this is especially painful, because the distance between business types is so wide. A propagation grower lives in production schedules and mother plants; a retail-only shop lives at the till; an online seller lives in dispatch. Sell all three the same monolith and at least two of them are wading through features they will never touch to reach the handful they need.

A better-shaped system is a single modular one that shows you only the parts matching the business you actually run.

Complexity you did not ask for and cannot escape.

paying for parts you never touch

Complexity you did not ask for and cannot escape.

A monolithic system makes its whole surface area your problem. Every feature built for every other kind of customer sits in your menus too, and the real cost of that, over and above the licence, is the drag of complexity on everyone who uses it. Staff hunt for the three screens they need among thirty they don't. Training takes longer, and the system feels heavier than the job it is doing.

Worst of all, it is rigid in exactly the place you need give. The features you will never use cannot be removed, and the ones you depend on cannot be brought to the fore, because the slab was poured for everybody at once. You end up shaping your nursery around the software.

Only the modules that match your business.

shaped to where you sit

Only the modules that match your business.

The horticulture supply chain holds very different businesses. Look closely and it resolves into at least six broad business types: grower, wholesaler/distributor, garden centre, ecommerce seller, retail-only shop, and the omnichannel businesses that span several at once. A business-type-aware system should surface the modules that fit where a nursery sits, and keep the rest out of the way.

A retailer never grows plants, so the propagation and production screens should simply not appear. A wholesale grower may have no physical till, so the point-of-sale side need never show up. The system stays focused on what you actually do, because it was shaped to fit your kind of business from the start.

the right way round

The system should fit the nursery, not the nursery the system.

Software is supposed to take the shape of the work. When it does, the screens you see are the screens you need.

Modular does not mean a pile of disconnected apps you have to bolt together yourself. A true modular system stays one system with one set of records — catalogue, stock, customers and money all joined up. What it shows you is governed by how your business is set up, and most of what turns a module on or off should be a matter of settings rather than concrete.

And because the whole thing was written for horticulture rather than adapted to it, the parts you do see speak your language. Plant passports, propagation, growing protocols and batch traceability are first-class features for the businesses that need them, and absent for the ones that don't.

What the grower sees, and what the retailer sees.

the same system, two faces

What the grower sees, and what the retailer sees.

Picture the two extremes side by side. The grower opens a well-fitted system to production cycles, mother plants and propagation, quotes and wholesale orders — the machinery of turning a cutting into a saleable plant. There is no till in sight, because there is no shop.

The garden centre opens the same system to a different face entirely: the catalogue, stock, pricing and the till, with returns handled over the counter. The production modules a grower lives in are simply not part of their world, so they never see them. One system, two businesses, each shown only the half that is theirs.

A shape that changes as you do.

you are not locked in

A shape that changes as you do.

A business type is a description of how the system is shaped for you today, not a box you are sealed into. Nurseries change: a wholesale grower opens a garden centre, a retailer starts selling online, a single site becomes an omnichannel operation spanning all of it. When that happens, the modules you see can change with it.

Because the capabilities are modular and governed by settings, growth does not mean migrating to a different product or starting again. A system built this way can widen to include the new side of the business while keeping everything you already had. You add the parts you grow into, exactly when you need them, and not a screen sooner.

atlas core

How Atlas Core handles modular, business-type-shaped software

Atlas Core puts the principles above to work for horticulture:

  • Six preconfigured business types (grower, wholesaler/distributor, garden centre, ecommerce seller, retail-only shop and omnichannel) decide which modules appear, so a retailer never sees propagation screens and a wholesale grower never sees a till.
  • Governed by settings, not code: capabilities switch on and off by configuration for your operation, rather than being fixed in concrete or bolted on as separate apps.
  • One joined-up system: catalogue, stock, customers and money stay in a single set of records, so modularity never fragments into disconnected tools you stitch together yourself.
  • Horticulture-native, first-class: plant passports, propagation, growing protocols and batch traceability appear for the businesses that need them and are absent for those that don't.
  • Grows without a migration: when a grower opens a garden centre or a retailer starts selling online, the same system widens to add the new modules while keeping every record you already had.

Read further

See the system shaped to your kind of nursery.

Grower, garden centre, wholesaler, online seller or all of them at once — talk to us about how Atlas Core would fit the way your nursery actually works, and grow with it.

Talk to us