20,000 meals.3,500 bags.Five hours.

Why we're building this

The daily flow, with rates

What has to happen every day, whatever the design. Figures come from the Basis of Design; the ones marked indicative are our arithmetic, and your throughput model should replace them.

1. 04:00–08:30

   Pick-up

   About 30 refrigerated cargo vans collect about 670 meals each from local kitchens, on reusable trays of 5–9 meals stacked 15 to a dolly.

   ~670meals a van, about 7 dollies
2. 08:30–09:30

   Arrive and receive

   20,000 meals on about 3,000 trays through four dock doors or fewer. Every meal is bulk-scanned against the expected inventory.

   222–333meals a minute if unloaded over 60–90 minutes
3. From 08:30

   Buffer

   Absorbs the gap between the arrival peak and the line. Held in refrigeration with every meal still identified.

   7,000–12,000meals waiting after the first hour, indicative
4. To mid-morning

   Induct and identify

   Each meal comes off its tray, level, and is positively identified. The hanging RFID tag comes off before the bag. The five-hour average is 67 a minute, but bags still have to be finished and loaded by 13:30, so induction realistically runs faster and finishes early.

   130–220meals a minute to finish by 10:00–11:00, indicative
5. During induction

   Sort to pods

   Each meal goes to the pod holding its customer's bag. At container width, a 3,500-bag site needs about 10–15 pods.

   13–22meals a minute into each pod at ten pods, indicative
6. Until the last meal lands

   Pack

   Every bag stays open until its last meal arrives, and is complete only when each expected meal is verified in it and nothing else is.

   3,500bags open at once, about 300 per pod
7. As bags complete

   Finish

   Ice packs where requested (about two a bag), a tamper-evident liner seal, and a printed RFID bag tag read back to confirm it's on the right bag.

   11.7+bags a minute, the five-hour average
8. By 13:30

   Sequence and load

   Bags put in van, route and stop order on carts that roll onto the vans and lock in place. Every van gone by 13:30.

   19–23bags a minute through four doors over the last 2.5–3 hours, indicative
9. Evening and overnight

   Returns

   Vans bring back bags and ice packs. Bags are inspected; ice packs are inspected, sanitized and refrozen on carts of 100.

   6,000ice packs a day, at most

Throughout: no meal outside refrigeration for more than 10 consecutive minutes at any transfer.

What we're sourcing

Mark what your company can do, or what you'd like to hear more about. Your picks collect at the bottom of the page and go to in one email. Pick anything: one specialty, several, or the whole system.

Requirements are written in RFP language (MUST, SHOULD, MAY) because they're drafted for the formal RFP. For now, read them as what a proposal will need to address; nobody is asking you to comply yet.

1. 1

   WP-01

   Receiving and de-tray

   Take 20,000 packages off about 30 vans and present them singulated to sortation, inside 90 minutes of arrival.

   We can do thisInterested

   Invitation scope areas in this package

   • Receiving & Induction System for Inbound Meals

     Design intake of approximately 20,000 chilled meals per day from refrigerated vans, including scan/verification, inventory visibility, flow-rate control, buffering and controlled release to sortation. The fewer dock doors needed, the better. Meals will arrive on mobile, lightweight, durable, reusable, stackable trays. Meals will be in various tray/bowl packaging sizes and shapes, limited to 10" x 10" x 3" h, and weighing 2 lb or less.

     We can do thisInterested

   • Automated Tray Stacking/Storage

     Develop the post-sort handling system for empty trays, including nesting/stacking, removal from the sorting room, compact storage and potential inventory visibility.

     We can do thisInterested

   What a proposal will need to address 10 requirements

   Governed by BOD-05, BOD-08, BOD-11, BOD-21, BOD-23, BOD-40 to BOD-42, BOD-50.

   Input: loaded dollies rolled from a refrigerated van (BOD-42).

   Output: singulated, upright packages presented to WP-03, plus empty trays to ambient staging.

   Requirements

   REQ-WP1-001MUST

   Accept loaded dollies direct from the van (BOD-42).

   REQ-WP1-002MUST

   De-stack trays and singulate their 5–9 packages, whatever their arrangement on the tray (REQ-PKG-010).

   REQ-WP1-003MUST

   Handle every package geometry in BOD-40 mixed on the same tray, within BOD-23.

   REQ-WP1-004MUST

   Read every package into an inbound manifest reconciliation against the van's expected inventory (REQ-COC-002).

   REQ-WP1-005MUST

   Route empty trays to unrefrigerated staging, counted and attributed to the originating kitchen.

   REQ-WP1-006MUST

   Hold packages within the exposure limit (BOD-21) across the entire receiving operation, including dock dwell.

   REQ-WP1-007MUST

   Operate through four dock doors or fewer, shared with outbound loading (BOD-38, REQ-FAC-005).

   REQ-WP1-008SHOULD

   Detect and reject damaged, leaking or mis-oriented packages before they enter sortation.

   REQ-WP1-009SHOULD

   Support manual induction as a fallback at reduced rate when automation is down.

   REQ-WP1-010MUST

   Nest or stack empty trays, remove them from the sorting area, store them compactly and keep a count of trays by kitchen (REQ-PKG-011).

   What we want to see in your response

   • Sustained and peak de-tray rate, in packages per minute, with the availability assumption.
   • How you handle a tray whose packages have shifted in transit.
   • Whether dollies enter a pod or stay in the warehouse, and the thermal consequence either way.
   • Empty tray buffer size and how trays leave the building.
2. 2

   WP-02

   Chilled surge buffer

   Absorb the gap between a 90-minute arrival wave and a five-hour processing line.

   We can do thisInterested

   What a proposal will need to address 6 requirements

   Governed by BOD-05, BOD-08, BOD-11, BOD-12, BOD-20, BOD-35.

   The inbound wave arrives in about an hour (BOD-05, BOD-11); sortation and packing run to the end of the production window (BOD-12). Something must hold the difference, in refrigeration, without losing package identity.

   Input: singulated packages from WP-01, faster than the line can take them.

   Output: packages metered into WP-03 at line rate.

   Requirements

   REQ-WP2-001MUST

   Buffer capacity sufficient to decouple the arrival peak from sortation rate. State the capacity your design requires and show the queueing calculation.

   REQ-WP2-002MUST

   Buffered packages stay within BOD-20 for the full dwell.

   REQ-WP2-003MUST

   Package identity is preserved through the buffer. A package entering and a package leaving must be the same known unit.

   REQ-WP2-004MUST

   Meter into sortation at a controllable rate.

   REQ-WP2-005SHOULD

   Sequence out of the buffer in an order that helps downstream — for example, releasing packages that complete nearly-finished bags first. State whether your design can do this.

   REQ-WP2-006SHOULD

   Degrade gracefully: if sortation stops, the buffer should absorb inbound for a stated period before receiving must stop.

   What we want to see in your response

   • Buffer technology and why (shuttle, carousel, accumulation conveyor, tote-based AS/RS, something else).
   • Enclosures and floor area consumed by the buffer, and the pod count at which it is first needed.
   • Maximum dwell time and its effect on food quality.
   • Whether buffering requires re-reading identity on exit, and the cost of that read.

   Alternative worth arguing for

   If you believe a buffer is the wrong answer — that receiving should simply run at 220+ packages per minute, or that pick-up routes should be staggered instead — make that case. Youtopia controls the pick-up schedule and can change it. Holding loaded vans, plugged in and locked, as the buffer is another option, and it is the one Youtopia's candidate concept shows. Section 16 asks the question directly.

3. 3

   WP-03

   Identification and sortation

   Read every package individually, resolve it to a household and a packing room, and divert it there.

   We can do thisInterested

   Invitation scope areas in this package

   • Automated Package Identification & Sortation

     Automate picking, identification and routing of variable meal packages from receiving to the correct refrigerated packing room, with rate control, buffering, exception management, and package-sequence logic. All functions other than conveyance happen inside of 40' refrigerated containers accessed by windows cut into one of the doors. No wall, ceiling, or floor penetrations.

     We can do thisInterested

   • Material Movement / Conveyor Systems Between Modules

     Transport system for meal packages, bags and/or ice packs between receiving, buffers, sorting and packing rooms, with solutions appropriate to refrigerated container-based spaces and the defined material-flow strategy.

     We can do thisInterested

   What a proposal will need to address 14 requirements

   Governed by BOD-07, BOD-08, BOD-31, BOD-33, BOD-40, BOD-50, BOD-51.

   Input: singulated packages from WP-01/WP-02.

   Output: packages delivered to the correct packing room, identity confirmed.

   Requirements

   REQ-WP3-001MUST

   Read the hanging UHF RFID tag on every package, individually attributable to that package (REQ-COC-005).

   REQ-WP3-002MUST

   Resolve the package to its bag and packing room by lookup against the Youtopia platform. No data is written to the tag (BOD-51), which is encoded once at the kitchen.

   REQ-WP3-003MUST

   Divert to the correct packing room across the full room count your design requires.

   REQ-WP3-004MUST

   Sustain the rate established under REQ-OPS-010.

   REQ-WP3-005MUST

   Handle a no-read deterministically: divert to a known exception lane, raise the event, and never pass an unidentified package downstream.

   REQ-WP3-006MUST

   Report a measured read rate and mis-read rate, distinguishing the two. A mis-read — reading tag B when package A is present — is materially worse than a no-read and must be reported separately.

   REQ-WP3-007SHOULD

   Provide a secondary identification path (vision, barcode on the printed label) as cross-check or fallback.

   The footprint and modularity problem

   A sorter with a divert per packing room, running mixed unstable geometries with adequate gapping, is plausibly 60–100 ft of machine. A container is 36 ft long (BOD-34). The sorter does not fit in one room, and we do not have a preferred answer. Youtopia's candidate concept runs one main conveyor along the pod doors with a kicker at each pod; treat it as one option, not a requirement.

   The options we can see are: span several containers, with transfers through 4 ft doors; place sortation in the warehouse outside the chilled rooms, which breaks REQ-XCT-001 and puts every package on the 10-minute clock; adopt a non-linear topology such as a two-stage or matrix sort; or enclose the pods in a chilled envelope (REQ-FAC-010).

   Modularity decides between them. A single sorter with one divert per pod must either be bought at full size on day one and run at a tenth of capacity for years, or be extended every time a pod is added — which is exactly the rework Section 3 forbids. The architectures that survive the governing principle are:

   • Two-stage sortation. Coarse allocation from receiving to a pod; fine sort to cubbie inside the pod. At one pod the first stage need not exist. At ten it is a small sorter with ten outputs, not a large one with thousands of destinations.
   • Untethered transfer. AMRs, tugs or carts moving totes between receiving and pods rather than fixed conveyor. Adding a pod becomes a map update and a traffic lane, not construction. Under Option A this also avoids welding each container to a fixed spine through one of its two doors.

   REQ-WP3-020MUST

   State the physical length and footprint of your sortation solution and where it sits relative to the pods.

   REQ-WP3-021MUST

   If sortation spans containers or sits outside them, show how REQ-FAC-002 and REQ-FAC-004 are satisfied at every transfer.

   REQ-WP3-022MUST

   Adding a pod must not require extending, re-engineering or re-commissioning shared sortation beyond configuration. State exactly what changes in your sort architecture when pod N+1 is added, and how long it takes.

   The RF problem — read this carefully

   The read environment is a refrigerated metal enclosure — a steel shipping container under Option A, typically a metal-skinned insulated panel room under Option B — with conductive surfaces on all six sides, producing severe multipath and unpredictable nulls. Tags are loose hanging paper/inlay tags, not bonded labels, so their orientation relative to the antenna is uncontrolled. Tag population density at the read point is high.

   REQ-WP3-010MUST, if available

   Provide a measured read and mis-read rate from a comparable enclosure — a metal-walled refrigerated space with a dense tag population. A vendor datasheet figure does not satisfy this. If you do not hold such data, say so plainly and request the RF trial described in Section 17; requesting it is not held against you, and claiming datasheet numbers as measured is.

   REQ-WP3-011MUST

   Describe tag selection, antenna geometry, power and shielding strategy, and how you prevent stray reads from adjacent packages or an adjacent room.

   REQ-WP3-012SHOULD

   Propose a tag specification if the current hanging tag is the wrong choice. The tag is not frozen.

   REQ-WP3-013SHOULD

   State how read performance degrades with condensation, frost, and wet tags.

   What we want to see in your response

   • Reference site with item-level UHF RFID in cold, metal-enclosed space. Name it or describe it under NDA.
   • Read architecture: portal, tunnel, overhead array, on-conveyor, handheld fallback.
   • What happens to throughput when read rate drops below target.
   • A proposed on-site RF survey and tag trial as a paid pre-contract work package, if you recommend one.
4. 4

   WP-04

   Cubbie wall and bag presentation

   Hold up to 3,500 chilled bags open simultaneously and present any one of them on demand. This package, not throughput, sets the size of the facility. Youtopia's working concept is a vertical put wall on each side of the room, with cubbies that present and hide bag positions on demand; challenge it if you have a better one.

   We can do thisInterested

   Invitation scope areas in this package

   • Vertical Put Wall Cubby System for Bag Staging in Packing Rooms

     Design a high-density vertical put-wall/cubby solution that presents and hides bag positions on demand, integrates with robotic and human packing, and maximizes usable capacity inside 36' x 7'6" refrigerated packing rooms. Because the room is insulated, wall, floor or ceiling penetration is not an option.

     We can do thisInterested

   • Automated Bag Loading to Cubbies Pre Meal Packing

     Define the optimal pre-load process to prepare each cubby and thermal insulated bag, including bag presentation and when and how liner bags and ice packs will be inserted into the bag.

     We can do thisInterested

   • Automated Placement of Bag Liner in Delivery Bag

     Define how the inner plastic liner is presented in the insulated bag, managed during packing and prepared for final closure and tamper-evident sealing.

     We can do thisInterested

   What a proposal will need to address 13 requirements

   Governed by BOD-02, BOD-03, BOD-20, BOD-22, BOD-31, BOD-34, BOD-43, BOD-44, BOD-55.

   Why 3,500

   Meals arrive unsorted from many kitchens across many vans. A household's bag cannot be closed until its last package arrives, and the last package may be on the last van. In the worst case every bag is open until the end of the sort. Youtopia's current position is that this worst case is the design case.

   A rough sizing, offered as a starting point and not a requirement. The bag is 14 in high, 16 in long and 10 in wide (BOD-43), and which way it faces is worth roughly a quarter of pod capacity. Narrow face out, at about 12 in pitch, gives around 36 positions along a 36 ft wall but needs 16–17 in of depth; long face out, at about 18 in pitch, gives around 24 positions in 11 in of depth. At 5 tiers that is 120–180 cubbies per wall face. The enclosure then decides the rest. At container width there are two faces, 240–360 cubbies per pod, and 10–15 packing pods for 3,500 bags; ten pods falls short of 20,000 meals in most orientations. At 12 ft wide there are four faces, 480–720 cubbies per pod, and 5–8 pods. The ~300 and ~600 figures in Section 2 are midpoints of these ranges. Tell us if your numbers differ and why.

   The aisle problem

   The same arithmetic creates a difficulty we cannot resolve from our side. A room is 90 in wide internally. Cubbies 16 in deep on both walls leave 58 in. A feed conveyor takes another 18–24 in. That leaves roughly 34 in of working aisle — and the presented bag slides forward into it from both sides (REQ-WP4-002), while REQ-XCT-021 requires safe human access and egress in the same space.

   Thirty-four inches does not accommodate a humanoid, and it may not accommodate much else. This problem is specific to the container. At 12 ft wide it does not arise — which is the strongest argument a module bidder can make against Youtopia's preference.

   REQ-WP4-010MUST

   Provide a dimensioned cross-section of your packing room showing cubbie depth, conveyor, working aisle, presented-bag travel and the egress path.

   REQ-WP4-011MUST

   If the aisle does not close, say so and tell us what has to give: shallower cubbies, single-sided walls, a wider room, fewer bags per container, or a different pick architecture. This is the answer we most want from WP-04 bidders and we would rather hear it now than after award.

   REQ-WP4-012MUST

   Hold the presented bag and its liner open for placement. The liner is pliable film and will collapse on its own. State the mechanism, whether it depends on the insulated bag being rigid enough to stand unsupported, and how the liner stays open through several placements as the bag fills.

   REQ-WP4-013MUST

   Define the pre-load of each cubby: when and how the bag, its liner and, if your design loads them first, the ice packs go in before meals arrive.

   Requirements

   REQ-WP4-001MUST

   Support the concurrent open-bag count your design derives from Section 2. State the number and show the derivation.

   REQ-WP4-002MUST

   Each cubbie presents its bag to the pick position on demand and retracts to a ready state.

   REQ-WP4-003MUST

   Bags stay within BOD-20 for the entire time they are open.

   REQ-WP4-004MUST

   Detect per-bag completion and signal that the household is ready to seal.

   REQ-WP4-005MUST

   Fit within the pod envelope of Section 2 for the enclosure option you propose, including the working aisle and, under Option A, the access constraint of REQ-FAC-002.

   REQ-WP4-006MUST

   A cubbie fault must not strand its bag. State how a bag is recovered from a failed cubbie mid-shift.

   REQ-WP4-007SHOULD

   Support pre-staging of the night's bag plan, given contents are fixed 24 hours ahead (BOD-55).

   REQ-WP4-008TBD

   Bag and ice-pack replenishment into the cubbie wall is undecided. Propose a method (Section 16).

   What we want to see in your response

   • Cubbies per pod, and the layout drawing that achieves it.
   • Total packing pod count at 20,000 meals/day, under the enclosure option you propose.
   • Presentation mechanism and cycle time per present/retract.
   • Completion-sensing method and its false-positive and false-negative rates.
   • Capital cost per cubbie, since this number multiplied by 3,500 is likely the largest line in the project.

   Cubbie turnover

   Cubbie turnover is in scope as an option, and Youtopia wants it considered. The pod's job is to place bags in cubbies, pack them, and release them to loading; nothing requires a cubbie to hold one bag for the whole window. A bag that completes mid-window can be sealed, ejected and replaced by a fresh empty bag, so cubbies stop equalling bags. A bag whose meals all come from early vans completes early; one waiting on the last van completes late. At 30% turnover, 3,500 bags fit in roughly 2,450 cubbies. Turnover costs a bag-eject mechanism, a fresh-bag feed into every pod, and a scheduler to sequence it. How much turnover is available depends on the mix of producers and vans behind each bag, for which Youtopia has only planning assumptions until launch. Pod 1 will generate the real figure (REQ-RMP-013).

   REQ-WP4-020SHOULD

   State whether your design supports cubbie turnover, the cubbie and pod count it saves, and what it costs. If your answer is that turnover does not pay at your cubbie density, show why.

5. 5

   WP-05

   Pick, tag-strip and place

   Take a package, remove its RFID tag, and place it in the right bag. Roughly 67 times a minute across every pod (BOD-07), in a chilled aisle — 7 ft 6 in wide in the preferred container.

   We can do thisInterested

   Invitation scope areas in this package

   • Meal Accumulation, Identification, & Bag Packing

     Design and build the modular refrigerated packing-room system including meal arrival through completed bag release, including buffering, bag/cubby presentation, exception handling, utilities and the division of human, robotic and control-system responsibilities. The room is a 40' refrigerated container, maintained at 35-40°F. We've envisioned a vertical put wall on each side of the room with automated cubbies using robotic suction to place meals in the appropriate bag and we welcome challenges to our thinking. No wall, ceiling, or floor penetrations.

     We can do thisInterested

   • Hanging Label Removal (meal packages)

     Define and provide the automated process for removing hanging RFID meal tags from each meal package at the correct point between identification/sort and final bag packing.

     We can do thisInterested

   • Automated Ice Pack Packing into Bags

     Define the placement method, human or robotic, for adding ice packs to each insulated meal bag. The ice packs are 13" x 9" x .75".

     We can do thisInterested

   What a proposal will need to address 11 requirements

   Governed by BOD-03, BOD-07, BOD-23, BOD-34, BOD-40, BOD-41, BOD-45, BOD-52.

   Input: package delivered to a packing room by WP-03; a cubbie presented by WP-04.

   Output: package in the correct bag, hanging tag removed if your design removes it here; bag marked complete when full.

   Requirements

   REQ-WP5-001MUST

   Confirm package identity at the point of pick, before placement.

   REQ-WP5-002MUST

   Where your design removes the hanging tag in the pick cell (BOD-52), separate it at the perforation without tearing the printed label, disturbing tamper tape, or damaging the package.

   REQ-WP5-003MUST

   Collect removed tags into bins at a defined handover point for disposal or recycling. Tags are single-use label stock printed at the kitchens and are not reclaimed.

   REQ-WP5-004MUST

   Place the package into the presented bag, upright, without dropping or crushing. Bags typically take 3–10 packages, up to 14 lb including ice packs (BOD-03), and every assortment is unique.

   REQ-WP5-005MUST

   Add ice packs per the consumer's request for that delivery (BOD-45, REQ-PKG-021). They are 13 × 9 × 0.75 in and 2.5 lb, and may go in before or after the meals, by robot or by hand; state which.

   REQ-WP5-006MUST

   Handle every package shape in BOD-40, from round bowls to rectangular trays, without a tooling change.

   REQ-WP5-007MUST

   Work within the pod aisle remaining after the cubbie wall and conveyance are installed.

   REQ-WP5-008MUST

   Verify placement — confirm the package actually entered the intended bag, not merely that it was released. This was a SHOULD in an earlier draft and has been promoted. Placement error is the dominant failure mode at the pick cell and the identification chain cannot catch it: the sortation read was right, the pick read was right, and the package still went into the wrong cubbie. Without this verification the detection guarantee in Section 14 is unachievable by construction. Price it as a MUST and show us the cost.

   REQ-WP5-009SHOULD

   Support manual operation at reduced rate when a cell is down.

   The placement concept — challenge it

   Youtopia's working concept is robotic suction placing each meal into its bag from a vertical put wall on each side of the room. It is a concept, not a validated design, and the placement method is the highest-cost and highest-risk decision in the program.

   REQ-WP5-020MUST

   State whether your design uses suction end-effectors as envisioned, another gripper, a gantry, a human operator, or something else — and defend the choice on cost, cycle time, reliability and maintainability.

   REQ-WP5-021SHOULD

   If you believe a different pick architecture would change the cubbie design (WP-04), say so. We would rather redesign the wall than build the wrong one.

   What we want to see in your response

   • Cycle time per pick, and picks per minute per cell.
   • Cells required per packing room and in total.
   • Tag-strip mechanism and its failure modes, with a measured success rate if you have one.
   • Grip strategy across every package shape and material — in particular whether suction holds reliably on porous compostable fiber lids.
   • Mean time between interventions, and who intervenes in a 35–40 °F room.
6. 6

   WP-06

   Bag seal and labelling

   Close every bag and label it with the household it belongs to — about twelve a minute, sustained (BOD-07).

   We can do thisInterested

   Invitation scope areas in this package

   • Automated Internal Liner Bag Closure & Sealing

     Provide a tamper-evident method to close and seal the internal plastic liner after meal placement, compatible with the refrigerated packing workflow and downstream bag handling.

     We can do thisInterested

   • Automated Bag Tag Label Placement System

     Define the best trigger, print moment, on-bag location, and timing for printed customer bag tags, controls and integration with bag completion and staging as well as a reliable method for applying the correct bag tag to the correct completed delivery bag with absolute accuracy.

     We can do thisInterested

   What a proposal will need to address 8 requirements

   Governed by BOD-04, BOD-07, BOD-13, BOD-21, BOD-43, BOD-44, BOD-55.

   Input: a completed bag signalled by WP-04.

   Output: a sealed, labelled bag ready for cart build.

   Requirements

   REQ-WP6-001MUST

   Close the interior liner with a tamper-evident closure. The liner is a pliable film bag; propose the closure method, whether heat seal, tie with a tamper band, or something else. The closure must show visible evidence if opened between the facility and the household.

   REQ-WP6-002MUST

   Close the insulated outer bag.

   REQ-WP6-003MUST

   Print, RFID-encode and apply a 2 × 6 in bag tag (BOD-46) carrying consumer name, delivery address, route and stop, and the bag's position in its household group (for example, 2 of 3) so the driver knows how many bags belong at the door.

   REQ-WP6-004MUST

   The bag tag is applied so it survives handling, cold and condensation, and remains legible at the doorstep.

   REQ-WP6-005MUST

   Reconcile bag contents against the expected inventory before sealing. A bag that is short must not seal silently (REQ-COC-003).

   REQ-WP6-006MUST

   Sealing happens inside the refrigerated envelope, or within the exposure limit (BOD-21).

   REQ-WP6-007SHOULD

   Capture a record of the seal event: time, cell, operator or machine, and the final content list.

   REQ-WP6-008MUST

   The bag tag carries both RFID and a barcode (BOD-46). Read both back after application to confirm the right tag is on the right bag.

   What we want to see in your response

   • Sealing mechanism and cycle time, and whether one cell serves several packing rooms or each room has its own.
   • Print-and-apply hardware, and its reliability at 35–40 °F with condensation present.
   • Label stock and adhesive suited to cold and wet.
   • What happens to a bag that fails reconciliation: held, diverted, sealed-and-flagged.

   Dependency

   Route and stop are not known until after the last pick-up scan (BOD-55). Bag tags therefore cannot be pre-printed the night before. State how quickly your print queue can absorb the route file once it lands, and whether that is on the critical path to 13:30.

7. 7

   WP-07

   Cart build and van load

   Get every sealed bag onto its van in stop order (BOD-06), with every van gone by 13:30 (BOD-13).

   We can do thisInterested

   Invitation scope areas in this package

   • Outbound Staging & Van Loading

     Develop a refrigerated staging and loading system for up to 3,500 completed bags (typically 2,500–3,300), sequenced by delivery route and loaded onto roughly 30 vans through four or fewer dock doors by the dispatch deadline. Temp-controlled rooms are 40' refrigerated shipping containers with interior dimensions of 36' x 7'6".

     We can do thisInterested

   What a proposal will need to address 10 requirements

   Governed by BOD-02, BOD-04, BOD-06, BOD-13, BOD-21, BOD-43.

   Input: sealed, labelled bags from WP-06.

   Output: loaded vans, reconciled against their route manifests.

   Requirements

   REQ-WP7-001MUST

   Place each bag at a designated position on a designated route cart. Position is determined by delivery stop order.

   REQ-WP7-002MUST

   Load carts into vans sequentially and in designated positions, so a driver reaches the next stop's bag without searching.

   REQ-WP7-003MUST

   Reconcile every bag onto its van against the expected route manifest before the van departs.

   REQ-WP7-004MUST

   Complete every van load by the departure deadline (BOD-13), with the last bag sealed no later than your stated cut-off.

   REQ-WP7-005MUST

   Respect the exposure limit (BOD-21) during cart movement and van loading, including time on the dock.

   REQ-WP7-006MUST

   Support the return flow: receive used bags and ice packs back from drivers, count them, and route bags to inspection and Youtopia's wash partner and ice packs to inspection, sanitization and freezing. Washing is out of scope; receiving, counting, inspection and the ice-pack system are in scope (Section 13).

   REQ-WP7-007SHOULD

   Handle a late-arriving bag — one completed after its cart has left the packing area — without breaking sequence.

   REQ-WP7-008TBD

   Whether bags are scanned onto carts, onto vans, or both is undecided. See Section 16.

   REQ-WP7-009MUST

   A household's bags are placed together on the same cart, in adjacent positions, and loaded to the same stop (REQ-COC-011). A cart must not leave loading with part of a household's bags. State how your design holds a cart when one bag of a group is late.

   REQ-WP7-010MUST

   Carts roll onto the van fully stocked and are secured for transit without blocking the driver's aisle (BOD-39, BOD-47). State how many carts and bags each van takes in your design.

   What we want to see in your response

   • Cart design and capacity, or a statement that you would use a cart we supply.
   • Whether carts are built in the packing room, a loading room, or on the dock.
   • Whether Receiving and Loading can share one room in your design (Section 16).
   • Load time per van, and how many vans you can load in parallel.
   • Dock door count and the marshalling area required.

   Constraint reminder

   Under Option A, a cart built inside a container room has to leave through a 4 ft doorway that may already carry a conveyor cut-out (REQ-FAC-002). Cart width and the room's remaining clear opening are a coupled decision. State both. Youtopia's candidate concept sequences finished bags in the cubby wall and returns them to the dock on the same main conveyor, reversed once the last meal is inducted. State whether your design shares conveyance between inbound and outbound and, if it does, how a meal that arrives after the switch reaches its bag.

8. 8

   WP-08

   Controls, integration and data

   One warehouse management and controls layer across every pod, integrated with the Youtopia platform. We own orders, routing and consumer state. You own the floor.

   We can do thisInterested

   Invitation scope areas in this package

   • Warehouse Management System / Controls / Tracking

     Provide the WMS and controls layer that orchestrates receiving, sorting, bagging and movement, maintains real-time package location and status, manages exceptions and creates end-to-end traceability.

     We can do thisInterested

   • Temperature Tracking of Environments

     Provide cold-chain monitoring for pickup, transport, receiving, packing and staging, supporting meal acceptance checks and continuous or scheduled environmental temperature records within the operating range.

     We can do thisInterested

   What a proposal will need to address 15 requirements

   Governed by BOD-51, BOD-53, BOD-54, BOD-55, BOD-56, BOD-60.

   Platform context

   Youtopia runs on .NET on Azure, event-driven, with Azure SQL and Cosmos DB, deployed through Azure DevOps (BOD-56). We will expose and consume versioned APIs and an event stream; we are not asking you to adopt our stack internally.

   Requirements

   REQ-WP8-001MUST

   A single warehouse management system (WMS) and controls layer spanning all rooms and work packages, including any equipment supplied by another vendor.

   REQ-WP8-002MUST

   Consume from Youtopia: the bag plan (BOD-55), the expected inventory per step, the route and stop assignment (morning), and consumer-level ice-pack requests.

   REQ-WP8-003MUST

   Emit to Youtopia, in real time: every scan event, every reconciliation result, every exception, and every state change of a bag.

   REQ-WP8-004MUST

   Exception events must carry enough context for Youtopia to act — package ID, expected location, actual location, step, timestamp, and the reason class.

   REQ-WP8-005MUST

   Versioned API contracts in both directions, with a documented deprecation policy.

   REQ-WP8-006MUST

   Operate degraded when the link to Youtopia is down: continue processing against the last known plan, queue events, and reconcile on reconnect. State the maximum offline duration you support.

   REQ-WP8-007MUST

   Provide an operations view showing live throughput, queue depths, open bags, exceptions and projected completion against the 13:30 deadline.

   REQ-WP8-008SHOULD

   Retain a full event history per package and per bag, queryable, for at least 90 days.

   REQ-WP8-009SHOULD

   Support a simulation or replay mode so Youtopia can test route and volume changes before they hit the floor.

   REQ-WP8-010MUST

   Record room, staging and dock temperatures continuously and link them to each meal's and bag's event history, supporting acceptance checks at receiving.

   Security and data

   Bag tags carry consumer names and delivery addresses, and bag contents are derived from a nutrition plan. Treat all of it as personal data.

   REQ-WP8-020MUST

   Encrypt personal data in transit and at rest. State your key management approach.

   REQ-WP8-021MUST

   Role-based access control with audit logging on any access to consumer data.

   REQ-WP8-022MUST

   No consumer data leaves the facility network or your named cloud region without explicit contractual permission.

   REQ-WP8-023SHOULD

   State your security certifications (SOC 2 Type II, ISO 27001) and your last penetration test date.

   REQ-WP8-024SHOULD

   Describe how you would support a consumer data deletion request reaching your systems.

   What we want to see in your response

   • A real API contract from a previous WMS-to-customer-platform integration, redacted as needed.
   • Your integration model: REST, event bus, file drop, or a mix.
   • Who owns the integration work and how it is priced.
   • Whether the WMS is yours, licensed, or third-party, and what happens to it if we part ways.

What decides the design

Tell what you can do

Your email app opens with everything filled in. Nothing is sent until you press send, and you can attach a capability statement or reference sheet before you do.