A bundle is only as fresh as its shortest component
A hamper holding flowers, patisserie and a ceramic vase has three different clocks inside it. Florocia tracks each component separately and sets the bundle window to the shortest one.
Gifting and hamper studios
A hamper has several clocks inside it. Track all of them.
Multi-item bundles mix perishable and non-perishable components, each with its own window and reorder behaviour. Florocia tracks them at component level and sets the bundle window to whatever runs out first.
Built for
Gifting studios, hamper makers and multi-component gift catalogues
Stock model
Component-level, shared across every bundle that draws on it
Scale
Single site or multiple sites with per-site rules and a central view
ComponentState
Blush hand-tied, mediumFresh
Dark chocolate box, 12 pcFresh
Seasonal fruit selectionWatch
Ceramic vase, matte sandStocked
Linen wrap and ribbonStocked
Bundle window set to 4 days by the fruit selection. Suggested: offer this build for same-day and next-day only.
What makes gifting harder
Four problems a single-item florist never meets.
Bundling multiplies everything - the stock relationships, the lead times and the ways a promise can break.
Catalogue depth that breaks a spreadsheet
Dozens of bundle formats sharing a common pool of components. One stock change needs to ripple through every bundle that draws on it, which it does.
Seasonal volume that triples overnight
Festival gifting is not a lift, it is a different business for three weeks. Capacity, component buying and delivery windows all need planning against that shape.
Delivery logistics across a wider map
Corporate bulk drops, residential gifting and courier-shipped hampers have different lead times and different failure modes. Each gets its own window logic.
Component-level stock
Change one component, and every bundle that uses it already knows.
Components are tracked once and referenced by every bundle that draws on them. When the fruit selection drops to four days, every hamper containing it inherits that window, and the ones offered on a seven-day lead time stop being offered.
- Bundle availability derived from the shortest component window
- Perishable and hard-goods components in the same build, tracked on their own logic
- Reorder points on packaging, vases and ribbon alongside freshness windows
- Substitution rules per component, so a build survives a supplier shortfall
Multiple sites, one picture
Studios running more than one production site get a centralised dashboard with per-site freshness, per-site capacity and per-site delivery rules. Stock is not pooled across sites unless you want it to be, because a batch in one cold room is not available in another.
- Per-site rules for windows, cut-offs and capacity
- Central view of write-off and recovery across every site
- Transfers recorded as movements, keeping each batch history intact
Seasonal load
Festival weeks need planning, not heroics.
Component buying, worked backwards
Demand forecast for the peak translates into component quantities and the lead time each supplier needs, so the order goes out early enough to matter.
Capacity planned as a shape
Three weeks of tripled volume is a staffing plan, not a busy Tuesday. Build capacity is set per shift across the whole window.
Delivery mix set per channel
Corporate bulk, residential gifting and courier-shipped hampers get separate lead times and separate cut-offs during peak.
Bench docket No. 0468Prepared for your workroom / freshness, demand, delivery
Bring your three busiest bundles.
We will break them into components, set the windows, and show you which build is quietly limited by one short-dated item.
What gets set up
Bundles modelledthree, to start
Components mappedwith own windows
Sites configuredone or many
Peak plandrafted together
Every clock accounted for