Coffee Degassing: A Wholesale Rest and Dispatch Plan

Turn roast age into a tested service window for Ethiopian coffee and a delivery promise your café customers can use.

Coffee degassing becomes a wholesale problem when a café receives a fresh delivery that is difficult to dial in for the morning rush. The roast date tells the customer how old the coffee is. A tested service window tells your production team when that coffee should arrive, when the café can start using it, and how much time remains to finish the order.

What Does Coffee Degassing Mean for Wholesale Release?

Coffee degassing is the release of gas retained in roasted beans, including carbon dioxide, after roasting. Brewing readiness is the point at which your product meets its agreed sensory and preparation requirements. Establish readiness through product testing rather than waiting for gas release to finish completely.

The SCA explanation of coffee freshness, reviewed in October 2026, connects retained carbon dioxide with post-roast change and notes that grinding accelerates gas release. Its discussion explains why roast age matters; it does not establish a dispatch date for your particular wholesale SKU.

Keep three clocks in the production record: time since roasting, time since packing, and time since a bag was opened. A roast-age trial using unopened whole-bean bags cannot automatically establish an opened-bag service period or a ground-coffee schedule. Specify the product state whenever you record a result.

Packing release also needs its own evidence. Follow the coffee packaging quality control procedure for the bag and filling process. Passing those checks permits the specified packing decision; it does not prove the espresso will perform at the customer's first service.

Avoid assigning a fixed rest period from an Ethiopian regional name. ZHAW's Coffee Excellence Center research overview identifies roast level, roast time, grind size, green coffee type, and moisture among variables studied in gas and aroma release. A lot-specific trial is a more defensible basis for a delivery promise than a universal origin rule.

Build a Service Window From an Actual Production Roast

Test identified production batches at planned ages using the customer's brewing application. Define acceptable taste and operating behavior before the first session. The result should be a usable interval supported by repeated observations, with any untested ages clearly identified.

Choose the trial conditions and retain separate packs

Use the intended batch size, roast profile, whole-bean pack, and roast-to-pack interval. Set aside unopened units for each checkpoint and repeat assessment. Keep their storage conditions recorded so a warm shelf or repeatedly opened bag does not silently become part of the experiment.

An initial exploratory schedule might test days 2, 5, 8, 12, 16, and 21 after roasting. These are proposed planning points, not published optimum ages. Add checks around the apparent beginning and end of the useful interval. If day 5 fails and day 8 passes, you have not established that day 6 passes.

Reserve enough coffee for setup, planned drinks, repeat preparations, and retained material before calculating saleable output. Size the trial around your method and equipment. Log withdrawals against the roast batch so a development program does not appear as unexplained stock loss.

Judge the drink and the work needed to prepare it

Evaluate whether the coffee meets the product brief within the café's permitted adjustments. Record both sensory observations and brewing behavior. A pleasing drink that requires repeated wasteful attempts may not meet the operating promise for a busy wholesale account.

For espresso, document dose, beverage yield, extraction time, grinder setting, water conditions, and the number of setup attempts. Begin with the agreed recipe, then record each permitted adjustment. Include the account's usual milk drink where relevant. For batch brew, use the intended brewer, dose, water volume, and holding practice.

Use the same assessment method across sessions and keep individual tasting notes. The cupping team calibration protocol supports consistent sensory language; application testing supplies the customer-use decision. Excessive crema, bloom size, or one unusual extraction time alone should trigger investigation rather than determine acceptance.

Write the approval boundary

Approve a window only for the conditions actually supported by the trial. Confirm the proposed start and end on additional production batches, including expected café handling. If evidence ends at day 16, label that the latest validated age rather than claiming the coffee necessarily fails on day 17.

Include an opened-pack check that resembles the account's consumption pattern. A café using a bag within one service and an office opening the same bag over several days impose different conditions. Keep those approvals distinct instead of extending an unopened-bag finding by assumption.

Calculate When the Order Can Leave the Roastery

Work backward from the validated service interval and the customer's actual use rate. For an order promised ready on arrival, the fastest delivery must reach the minimum service age. The slowest delivery, plus the planned consumption period, must remain within the latest validated age.

Define all quantities in elapsed days since the roast timestamp. Let R be the earliest approved service age, L the latest validated consumption age, Tmin and Tmax the planned transit bounds, and C the elapsed period from arrival to final consumption. Use documented route experience to set the transit bounds and review exceptional delays separately.

Count the customer's unopened reserve time inside C. An account that receives a carton but finishes its older stock first has a longer arrival-to-final-use interval than its bag consumption rate suggests. Ask for expected first use and final use instead of assuming both follow delivery immediately.

Where the interval is empty, change the plan: reduce order size, improve delivery predictability, use another approved roast batch, or agree a customer-held rest period. A later first-use instruction needs an explicit handoff and still must leave sufficient time before L. Faster delivery can make coffee arrive too young if dispatch age stays unchanged.

Worked Example: An Ethiopian Espresso Order for a Café

A feasible dispatch date must protect both ends of the customer's service period. The fictional example below shows why reducing order quantity can solve a timing problem that changing roast day alone cannot fix. All quantities and acceptance ages are illustrative Ethio Coffee calculations prepared in October 2026, not reported customer results.

Assume a roaster has validated one Ethiopian espresso SKU for the modeled handling conditions from day 8 through day 18. A café orders 24 kg and uses 4 kg per day, beginning on arrival. The planner reserves six elapsed days for consumption, conservatively including the final service. The route normally takes between one and three days.

• Earliest dispatch: 8 - 1 = day 7.
• Latest dispatch: 18 - 3 - 6 = day 9.
• Dispatching on day 8 produces arrival at ages 9 through 11 days.
• Final consumption falls no later than day 17 under these assumptions.

Now increase the order to 40 kg at the same use rate. Consumption requires ten elapsed days, so the latest dispatch age becomes 18 - 3 - 10 = day 5. The earliest remains day 7. No dispatch date satisfies both conditions; scheduling the same quantity for a different roast date does not remove that conflict.

Separate deliveries or a smaller standing order can restore a workable interval. Before accepting either change, check freight cost, café storage, handling capacity, and the revised consumption assumption. Do not extend the validated age merely to make a spreadsheet return a convenient answer.

The same model exposes inventory tied up in planned rest. At steady output of 40 kg roasted per day and eight days held before dispatch, the simplified pipeline contains about 320 kg awaiting dispatch. That is an average-flow estimate, excluding buffers and production peaks. Carry this finished-stock requirement alongside the green coffee inventory plan so bags on a shelf are not mistaken for coffee ready to cover an urgent order.

Recheck the Window When the Ethiopian Lot Changes

Connect the rest trial to a named green lot and its production roast. An exporter's sample assessment establishes information about that sample; your production and service trials establish the wholesale readiness window. Agree the following origin records with the supplier before transferring an existing schedule to a replacement.

• Identify the final preparation represented by the sample. Ask whether the approved sample reflects the final dry-milled lot offered for delivery. Preserve the sample code and prepared-lot reference together; a regional description alone cannot identify the material used in the trial.
• Attach preparation details to tasting feedback. Send the roast reference, elapsed roast age, brewing application, and observed issue when asking the origin team to investigate. A complaint about an unstable espresso without its preparation history leaves the supplier unable to separate green-lot questions from downstream handling.
• Confirm the allocation covered by approval. Establish which quantity and lot code the trial qualifies. A later allocation needs identification and a decision on requalification before production assumes the previous service window still applies.

These are recommended handoff questions, not claims that every Ethiopian supplier maintains identical records. Add the agreed evidence to the sample approval record. Ethio Coffee can discuss available lot information through its sourcing relationships; the roaster remains responsible for validating the finished product's service conditions.

Send a First-Use Instruction With the Delivery

Give the customer a roast date, batch identifier, agreed first-use date, and relevant storage and brewing instructions. Keep first-use advice separate from any best-before marking. A service-readiness window describes tested performance under stated conditions and does not establish a legal labeling rule.

For standing orders, record the usual consumption rate and how much older stock remains on delivery day. Ask the café to identify bags before opening them and to flag a change in expected use. A holiday closure can consume the remaining service window even when the carrier delivers exactly on time.

Make the instruction specific enough for the opening shift: which batch may enter service, which batch should remain sealed, and whom to contact if the approved recipe cannot produce the agreed drink. If roast ages differ within a delivery, identify the batches separately rather than giving the entire carton one implied age.

Resolve Exceptions Without Guessing a New Rest Period

Review the batch history and customer schedule whenever the original assumptions fail. Record whether the issue concerns age, storage, brewing, or package condition before deciding the remedy. Extra rest is one possible trial variable, not a universal correction for an unsatisfactory cup.

If delivery is early, confirm whether the café can hold the identified batch until its approved first-use date. If delivery is late, recalculate final consumption age before asking the café to accept the original quantity. Use an agreed smaller release or replacement when the planned window no longer fits.

If brewing remains inconsistent inside the approved window, check actual roast and opening timestamps, grinder and water conditions, preparation records, package integrity, and retained-batch results. Do not change the roast profile and rest schedule together unless the investigation requires both; doing so makes the cause harder to establish.

Coffee degassing becomes manageable when readiness is a tested product attribute and dispatch is a calculation. Establish the service window, account for the full customer consumption period, and keep lot identity attached to every trial. That gives a wholesale team a defensible answer to the practical question: when can this café use this batch successfully?