0
Boxes to prepare for October 22
All caught up.
Low stock, new orders and approvals will show here.
Staff
Operations · Gathered
Good morning, Staff.
Primary work
0
Atmospheres that can’t fill their orders
0
Open escalations
Needs attention
Quick actions
Pending approvals (0)
Flower catalogue
Manage the flowers that appear across Gathered.
| Flower | Type | Colours | Role | Origin | Grower | Availability | Price / stem | Status | Change |
|---|
Availability
Palette capacity
How many boxes each atmosphere can fill with this week’s stems, against what customers ordered.
| Atmosphere | Can fill | Ordered | Status | What limits it |
|---|
Each atmosphere is counted on its own; colour coverage below adds up every order together. Box recipe used: about 50 stems, 10 per main colour, 5 per accent, 10 foliage, and at least 15 focal stems. Recipe to confirm with operations
Colour coverage
This week’s intake
What came in from the growers, graded by colour at Sesquilé.
| Flower | Colour | Type | Grower | Stems | Remove |
|---|
Manifest columns: flower, colour, type (focal, filler or foliage), grower, stems. Colours must use the site’s 28 names.
Sample data for the prototype. Quantities and orders are illustrative.
Pricing
The three tiers testers choose from in shipment 4, and what each one includes.
How testers will see it in shipment 4
Pending with the client The three tiers, shipping and billing timing are open decisions (pilot plan, section 10). The pilot plan values the four free boxes at about $300.
Atmospheres
What customers can choose on the site: colours, season and the example box. An atmosphere pauses itself when the stems can’t fill its orders.
Example stems are placeholders until operations defines real combinations per atmosphere.
Pilot
Launch gates
Scorecard
| KPI | Target | Current | Based on | Status | Owner | Next action |
|---|
Delivery by lane
| Lane | Boxes | Average transit | Within 72 hours | Slowest |
|---|
Sample pilot data: shipment 1 shipped October 8 and is complete; shipment 2 ships October 22. Segments are reported separately, as the pilot plan asks.
Customers
Pilot details (segment, how they joined, screening, photos) are visible to: . Change it in Team and roles.
Pilot waitlist
| Name | Segment | Lane | Applied |
|---|
Two missed prompts can trigger replacement from the waitlist (pilot plan, section 6).
Fictional names and sample data. When the pilot ends, pilot customers stay here; only the Pilot cohort tag remains.
Responses
What testers send back by iMessage and through the QR in the box, joined to each box.
| Tester | Box | Moment | Channel | Answer | In their words | Photo |
|---|
Escalations
Team and roles
Who runs each part of the pilot, and what each role can see and change.
Pilot section
Owners (pilot plan, section 7)
Permissions
To confirm Who can grant exceptions and approve atmospheres is still an open decision.
Activity
Every change made in the console: who, what and when.
| When | Who | What changed |
|---|
Orders
Every box with its full record: palette, packaging, lane, transit and what was sent.
| Box | Tester | Atmosphere | Packaging | Lane | Status | Transit | Record |
|---|
Pilot boxes only, sample data. Packaging A and B alternate in shipment 2, as the pilot plan asks.
Preparation bench
Pick lists come from this week’s intake and the box recipe. When a colour runs out, the bench says how many stems need a substitute.