Sushi Takeout Container Planner: What to Stock & How Much to Order

BUILD A JUSTIFIED ASSORTMENT

How Many Sushi-Container Sizes Should You Carry?

Start with the presentations you must cover, not a predetermined number of sizes. A format earns its place when it covers recurring demand, meets a distinct presentation requirement or supports a confirmed event that the rest of the assortment cannot handle acceptably.

The goal is no unnecessary format and no uncovered packaging requirement. A smaller assortment is only better when it preserves the food fit, handling and presentation your operation needs.

Give each selected product an operating role:

These roles depend on your operation. A party platter can be a core item for a caterer and event-driven packaging for another restaurant.

Before adding a format, ask: What does this product cover that the existing assortment cannot? Before removing one, ask: Which presentations must be reassigned, and has the alternative been approved?

Built on 24 Years of Cross-Manufacturer Sourcing and Purchasing Evidence Covering 3.25B+ Units

Since 2002, Eden Restaurant Supply has worked across sushi-container manufacturers, product systems and restaurant requirements. The ERS Sushi Container Standard brings that cross-manufacturer perspective into a common format reference. This planning method connects that reference to actual products, ordering units and restaurant-specific purchasing decisions.

The sourcing history supports the format and product reference. Your restaurant's usage, stock, receipt dates and reserve determine the order calculation.

Identify formats in the Size & Shape Guide →

MENU TO PRODUCT

Give Every Packout One Packaging Assignment

A packout is the finished presentation prepared for handoff: a single roll, an individual combination, a larger mixed presentation or a party order. One ticket can contain several packouts. One packout can use more than one container.

Record the actual product used and the number of complete packages it consumes. Where a presentation is deliberately split between products, enter explicit assignment shares totaling 100%. An approved alternative receives demand only when you select it.

Do not calculate container demand by dividing sushi pieces by a tray's reference piece count. The Size & Shape Guide helps you shortlist physical formats; your approved arrangement determines the packaging assignment.

Review required uncovered packouts separately from a demand-weighted coverage percentage. A rarely ordered but committed presentation still matters. When demand has not been entered, the planner does not turn missing information into 100% coverage.

Before removing overlapping products, review the entire revised assortment. Two products can each look individually redundant while removing both leaves a gap.

Build my packout coverage matrix →

ORDERING UNITS

From ERS Format to Product, Pack and Case

An ERS format is a comparison class, not an inventory unit. Products in the same class can differ in materials, matching lids, selling packs and master-case quantities.

Use the selected product's ordering unit for purchasing. A 50-package pack and a 600-count tray-with-lid case can occupy a comparable format while creating very different order increments. Keep the product identity and quantity basis attached to every calculation.

Ordering-unit examples from the ERS catalog

Catalog quantity references reviewed 28 September 2026. Product names link to their source listings. A master-case conversion does not establish a separate purchasable case variant or case price.

For a positive need of 320 complete packages, a 50-package selling unit requires 7 packs / 350 packages. A confirmed 600-package case requires 1 case / 600 packages. This is an ordering-unit comparison, not a recommendation to substitute materials or interchange lids.

Choose the format for coverage. Choose the actual product for stock control and ordering.

USABLE STOCK

Count Complete Compatible Packages

Count what can leave the restaurant as a finished package. A complete package includes the selected container and every required matching component. A matched prepacked tray-and-lid set can be counted as one complete package. Imbalanced or separately purchased components need their own records.

For a dedicated one-base/one-lid configuration:

Usable complete packages = the smaller of usable matching bases and usable matching lids.

One thousand compatible bases and six hundred matching lids support six hundred complete packages, not one thousand. Damaged pieces are excluded from usable stock.

When several packouts share a component, combine their requirements and count that stock once. The limiting-component principle is also used in component-based bundle inventory. [M4]

Comparable format does not establish compatible components. The same ERS code or similar dimensions do not authorize pooling lids, substituting products or counting one inventory balance against several requirements.

Keep two records separate:

Incoming supply is not usable stock before receipt. A shipping or dispatch statement alone does not establish a received-and-usable date. [M5] [M6]

For in-scope reservations, include the usable physical stock and place the reserved requirement once in dated demand. Do not remove the reservation from stock and then subtract the same requirement again.

DEMAND AND EVENTS

Estimate Usage Without Counting Demand Twice

Choose one routine-demand basis for the orders represented by your plan:

Observed product usage: enter how many complete packages or component units you use, with the applicable service calendar.

Assigned packouts: enter how often each approved presentation occurs; the planner multiplies occurrences by the packaging assigned to it.

Product demand = packout occurrences × assignment share × packages used per occurrence.

Do not add both methods for the same population of orders. Purchasing frequency alone does not establish consumption; quantity purchased, stock carried and other supply sources affect that interpretation.

Put known events on the preparation date

Add catering, training and other known requirements on the date the packaging will be used. The preparation date may come before the customer's event.

State how much event demand is already included in routine demand for that date and stream. Add only the remaining quantity. Forecast-consumption methods address the same need to avoid counting an actual order and its overlapping forecast twice. [M3]

For a baseline of 100 packages and an event of 40 packages:

Use separate event IDs so the same event is not entered twice. If your observed usage already includes damaged or wasted packaging, do not add another default loss allowance. Enter additional losses only when they are separate from the usage forecast.

Forecast assigned packaging requirements—not tickets, raw sushi pieces or purchase intervals in isolation.

Research connection

Purchasing research can identify assortment questions worth reviewing. It does not substitute for your stock count, menu assignment or usage forecast.

Review the purchasing evidence →

REPLENISHMENT METHOD

Set the Review Period—and Check Receipt Timing

This planner uses scheduled review and top-up replenishment. At a review, calculate enough supply to protect demand until the following replenishment can become usable.

A reorder point is a trigger. A scheduled-review target is the inventory position to restore at a review. They are not interchangeable meanings of “par.” In a fixed schedule, the protected period includes the review interval and replenishment lead time. [M1]

Name the dates

Protect demand through the day before the following order becomes usable. Receipts on that boundary belong to the next cycle, not the current one.

Keep the restaurant's service calendar separate from supplier and carrier schedules. Closed service days have zero routine demand; a confirmed preparation event on a closed date remains a requirement after you explicitly confirm it.

The simple calculation

For uniform demand and appropriately timed supply:

Target = daily usage × (review interval + lead time) + selected ending reserve

Endpoint need = max(0, target − usable stock − relevant confirmed incoming supply)

Then round to the actual product's selling unit. Netting stock and relevant incoming supply before applying purchasing constraints is also used in established replenishment systems. [M2]

Why the planner also checks every date

A later shipment can reduce the total you need without preventing an earlier shortage. The planner checks the daily inventory path before calling an order sufficient.

For each day:

Balance without this order = starting stock + receipts usable so far − demand so far.

The required order must cover the larger of the ending-reserve requirement and the greatest shortfall after the selected new receipt. If supply is required before that receipt, the result is Earlier supply required, not an ordinary order recommendation presented as a complete solution.

A larger order arriving late does not solve an earlier shortage.

Choose the reserve deliberately

Enter reserve units or convert a selected number of future service days into units. The planner's reserve is an end-of-period target, not a promised minimum on every intermediate day. Days below that target remain visible as reserve warnings.

A manually chosen reserve is an operating assumption—not a statistical service guarantee. Days-based reserve and service-level-based safety stock are distinct methods. [M7]

Round once—to the order unit

Keep fractional demand through the calculation. Round the purchase quantity to complete selling units, then apply any entered minimum or lot multiple. Show the resulting order and remaining stock; do not round every day's forecast upward.

When no order is needed, an entered minimum does not create demand. When a maximum order or storage limit prevents adequate coverage, show the conflict rather than silently reducing the order.

YOUR PLANNING INPUTS

Build Your Assortment & Reorder Plan

Start with your packaging requirements or go directly to the products you already use. Both paths produce the same dated replenishment calculation and purchase worksheet.

Build or review my assortment Assign approved packouts to products and review coverage before calculating quantities.

Replenish products I already use Select products, enter actual usage and stock, and calculate the next order.

This planner does not place an order or reserve stock. Use Print or Download CSV to keep your calculated worksheet.

EXPLAINABLE RESULTS

Your Assortment & Replenishment Plan

Review three outputs together: the packaging requirements covered, the stock needed across the selected dates, and the actual products and ordering units to purchase.

Assortment coverage

See required uncovered packouts and distinguish format count, selected product count and separately managed component count. Approved alternatives remain outside routine demand until assigned.

Dated replenishment

For each product, review demand, usable stock, confirmed receipts, raw requirement, rounded order and projected ending balance. Check earlier-supply gaps and ordering constraints before treating the plan as executable.

Purchase worksheet

Keep the model, ERS class, chosen order unit, quantity, usable receipt date and assumptions together. Open the corresponding product page to confirm the exact item before ordering.

Review the dates as well as the quantity. A positive ending balance alone does not establish uninterrupted coverage.

FOLLOW THE CALCULATION

Opening, Routine and Catering Examples

These worked examples show the method using stated inputs. They are not restaurant averages, default recommendations or observed customer outcomes.

Example 1 — A routine 50-package pack order

A restaurant counts stock before service on 1 October 2026. It uses 80 complete packages per day. The new order is usable before service on 6 October; the next review is 8 October, and the following order is usable on 13 October. Protect 1–12 October.

Target: 960 + 160 = 1,120 Raw need: 1,120 − 600 − 200 = 320 Order: ceil(320 ÷ 50) = 7 packs / 350 packages Projected ending stock: 600 + 200 + 350 − 960 = 190 packages

The dated check also passes. ED-07 / YP-1.5 is a catalog example of a 50-count tray-and-lid selling pack; the usage and dates above are example inputs, not product attributes.

Example 2 — The same need in a different ordering unit

With the same 320-package raw requirement and a confirmed 600-complete-package case, order one case / 600 packages. The ending balance becomes 440 packages.

PH-07 is listed as a 600-count tray-with-lid case. Confirm the complete-package basis used in the active plan. This example compares ordering increments; it does not establish interchangeable lids or an automatic material substitution.

Example 3 — An ending total hides an earlier shortage

Keep the same 1–12 October demand and 160-package ending reserve, but start with 400 packages and an existing 600-package receipt on 11 October. The new order is usable on 6 October.

An ending-total calculation produces:

960 + 160 − 400 − 600 = 120 packages, rounded to 3 packs / 150 packages.

But through 10 October, demand reaches 800 packages. Starting stock plus that proposed order would provide only 550. The restaurant would be short before the later receipt.

The dated method instead requires 400 packages / 8 packs on 6 October. Projected ending stock is 440 after the later receipt. The additional ending stock is a consequence of timing. Rescheduling the existing shipment is a separate decision.

Check the days before delivery—not only the final stock total.

Example 4 — A dated party order

Assume 40 approved party packouts, seven matching platters on hand, no reserve and receipt before the preparation date.

ED-65 and HP-65 are respective 20- and 50-count P15 offerings. This is a comparison of two separate product scenarios. Their stock and lids are not automatically interchangeable.

Example 5 — Opening with no packaging stock

A restaurant plans to open on 3 October, with packaging arriving on 2 October. It forecasts seven service days at 30 packages per day, no pre-opening routine usage and a 60-package ending reserve.

Demand: 7 × 30 = 210 packages Target: 210 + 60 = 270 packages 50-package order unit: 6 packs / 300 packages Ending stock: 90 packages

Add training or preparation use separately on its actual dates. Do not prescribe the same opening quantity to every restaurant.

Example 6 — Bases are plentiful; lids are limiting

For 300 approved one-base/one-lid presentations, assume 500 matching bases and 120 lids. Separate procurement is explicitly selected, with a 50-count base pack and 100-count lid pack.

Base order: zero. Lid requirement: 300 − 120 = 180 lids. Lid order: 2 packs / 200 lids.

Those component pack sizes are stated example inputs, not undocumented ERS offers. Buying extra complete sets would be a different procurement route and is not automatically selected.

REVIEW THE WHOLE PLAN

Review the Assortment, Storage and Alternatives

Review the assortment when menu presentations change, demand moves, ordering units change or a replacement becomes necessary. Keep a record of the requirement each specialty item serves before judging it by volume alone.

Count formats, products and components separately. Two products in ERS-R3 still create two product lines to count and purchase. Separately managed matching lids can add another inventory line.

A current-versus-revised comparison should show coverage, demand reassignment, ordering quantities and remaining stock. Compare the same requirements and dates. If those change, the comparison is no longer solely an assortment change.

For example, assume the operator has approved N2 for 60 daily single-roll packouts, R3 for 30 combinations and R5 for 10 larger presentations. If a verified R3 product also handles the single-roll presentation acceptably, the operator can evaluate moving that demand to R3.

The revised R3 demand is 90 packages, not 30. The comparison should show retained coverage and changed purchasing requirements—not automatically declare the smaller assortment better.

Storage must have its own basis

Use documented carton dimensions, nesting information or an explicit storage limit. A tray's footprint multiplied by the number purchased is not a bulk-storage model.

V1 checks an optional maximum quantity for each inventory line. It does not optimize shared shelf volume or invent carton dimensions. Where ordering increments exceed a stated limit, resolve the conflict instead of hiding the excess.

Costs belong to a stated scenario

Optional costs use the prices and currency you enter for the chosen order units. They are not live quotations and do not include unentered freight, tax or other charges. Compare costs only when both scenarios have complete, comparable inputs.

Save a calculated baseline, change the assignment deliberately, then recalculate the full plan.

METHOD AND PROVENANCE

Method, Sources and Limits

This planner applies scheduled-review inventory principles to sushi packaging. ERS contributes the format/product reference, the packout-to-product method and the packaging-specific treatment of ordering units and components. Restaurant usage, stock, receipt dates and reserve choices remain inputs. [M1] [M2]

The dated coverage calculation checks the stock path as well as the ending requirement. For baseline daily balances B, selected order-usable day a, final protected day h−1 and ending reserve S:

Raw order = max(0, S − B[h−1], greatest shortfall from day a through h−1).

Before using that quantity, require no unresolved shortage before day a. A negative baseline balance records an unmet requirement; it is not physical negative stock. The method assumes one new receipt per inventory line and does not choose expedited freight or multiple staggered purchases.

Keep the evidence types distinct

Scope

The planner supports one location, multiple products, approved packout assignments, explicit components, dated routine/event demand, dated receipts and product-specific ordering increments.

It does not perform physical food-fit testing, infer interchangeable lids, guarantee delivery, estimate consumption from purchasing cadence, claim a statistical service level, place orders or reserve supplier stock. It does not automatically choose the least-cost mixture of complete sets and replacement components.

Version and maintenance

Method: ERS Sushi Packaging Planning Method Version: 1.0 Maintained by: Eden Restaurant Supply Method documented: 28 September 2026

Keep the method version and product-source review dates with an exported plan. Later revisions may update calculations, product records or supported workflows. Recalculate saved assumptions against the version in use; do not silently reinterpret an old result as a current calculation.

Referencing the method

Suggested citation: Eden Restaurant Supply. Sushi Container Assortment & Reorder Planner: ERS Sushi Packaging Planning Method. Version 1.0.

When citing a calculated result, include its input assumptions and planning dates. A worked example is not a restaurant benchmark.

Sources

• [M1] NC State Supply Chain Resource Cooperative — Periodic Review System. Basis for the scheduled-review protection interval. Source → Return to explanation ↑
• [M2] Oracle — How Min-Max Planning Replenishment Quantities Are Calculated. Inventory netting, supply/demand cutoffs and quantity modifiers; not an endorsement of this ERS interface. Source → Return to explanation ↑
• [M3] Oracle — Overview of Forecast Consumption. Distinguishing actual requirements from overlapping forecasts. Source → Return to explanation ↑
• [M4] Shopify — Bundle eligibility and inventory considerations. Component-limited bundle inventory. Source → Return to explanation ↑
• [M5] Shopify — Understanding inventory states. Distinctions among physical, committed, unavailable and incoming stock. Source → Return to explanation ↑
• [M6] Shopify — Transit time versus processing time. Dispatch/processing is separate from transit. Source → Return to explanation ↑
• [M7] Oracle — How Safety Stock Is Calculated. Days-of-cover and service-level approaches are different methods. Source → Return to explanation ↑

Product names in the ordering-unit reference and examples link to their specific ERS sources.

OPERATING QUESTIONS

Frequently Asked Questions