Stock and intake records
Batch received dates, varieties, grades, quantities, supplier identity and the freshness profile applied to each line.
Florocia reads stock and order data to do its job, so it is worth being plain about what it reads, what it works out from that, and where the line sits between a suggestion and an action.
Ownership
Your inventory, order and customer data stays yours, exportable at any time
Approval model
Pricing, bundles and promotions require an explicit release before going live
Access
Role-based, with an audit trail on every commercial change
Bundling and promotion suggestions always require your approval before going live. Florocia will tell you that twenty-two bunches of lilies have two days left and propose a bouquet at a price. It will not publish it, discount it or send it to a customer until you release it.
Florocia does not buy external data about your customers or scrape your competitors. It works on what your business already generates.
Batch received dates, varieties, grades, quantities, supplier identity and the freshness profile applied to each line.
What was ordered, what stock it drew on, the delivery window it was placed in, and whether that window was met.
Contact details, delivery addresses, stated preferences and recurring occasion dates, entered by you or your team.
Window capacities, cut-off times, margin floors, protected varieties and the vase-life profiles you tune.
If a suggestion cannot be traced back to a batch and a rule, it is not worth acting on. All three outputs can be.
Freshness position
Calculated from the received date of a batch against the vase-life profile for that variety, adjusted by the handling and storage conditions you record at intake. It is arithmetic on your own data, not an opinion drawn from elsewhere.
Demand forecast
Built from your order history weighted toward recent months, the occasion calendar for your region, and seasonal shape. Early on, the calendar carries more weight. After a full cycle, your own history carries most of it.
Bundle suggestions
Composed from stock currently in the watch zone, the formats you already sell, and the margin floor you set. Every suggestion can be traced back to the batch and the rule that produced it.
Lock-in through data is a bad way to keep a customer. Export is a standing feature, not a support request.
These are the controls in place. Where something is in progress rather than complete, we will say so on a call rather than imply otherwise here.
All traffic between your browser and the platform runs over TLS. Stored data, including backups, is encrypted at rest.
Bench staff, delivery staff and owners see different views. Commercial data such as margins and supplier pricing is not open to every account on shift.
Price approvals, bundle releases, stock adjustments and capacity overrides are recorded with the account that made them and when.
Inventory, orders and customer records can be exported in a standard format at any time, including after cancellation.
The platform asks for what the freshness and scheduling logic needs. It does not require payment card data from your customers to function.
Regular automated backups with a documented restore path, tested rather than assumed.
Where the data sits, who can reach it, what the audit trail records and what happens on the day you decide to leave. All fair, all answerable.
What gets set up