Everything in §0.6 can be switched on later. That is not a footnote — it is the intended way to adopt BlossomERP, and it deserves three pictures.
The trader who found her departments. A provisions trader starts with three staff, one shop, everything off: she sells from invoices raised directly (Simple depth), pays suppliers from simple purchase invoices, and her Profit & Loss is one honest page. Two years later there are two shops and a small office team, and the question changes from "did we make money?" to "which side made the money?" She turns on Track branches and Track departments one quiet weekend. From Monday, documents ask for their branch and department; her reports gain filters; the two shops become comparable for the first time. Nothing about the first two years needed redoing — the history simply predates the split, and everything after it carries the address.
The maker who taught the system to plan. A furniture maker starts with base inventory: stock in, stock out, an adjustment when the count disagrees. The pain arrives as growth: the third stock-out of the same timber in a quarter. He turns on Planning. The worklist starts telling him what will run out, using his own lead times — information first, no behaviour change, while he learns to trust it. A season later he turns on Advanced, and the worklist begins drafting his purchase orders for approval instead of merely advising. The counting discipline arrives last: ABC classes mean the expensive hardwoods are counted monthly and the screws quarterly, which is the first stock count regime his team has ever actually kept.
The farm that met its expiry dates. A fish farm's feed store holds bags with use-by dates, and the cost of feeding expired feed is not a rounding error — it is a pond of dead fish. When the store outgrows memory, the farm turns on lots and FEFO for its feed products. Every delivery becomes a lot with its dates; issues are proposed in expiry order so the oldest safe bag leaves first; and an expired lot simply cannot be issued for use — the application refuses, by name, rather than trusting whoever is on shift to notice. The farm's other products — nets, fuel, fingerlings — stay untracked and uncomplicated, because the switch is per product, not per company pride.
The pattern is the same in all three: a switch is turned on when a real question cannot be answered without it, and the application grows exactly as far as the business has — and no further.