Frozen Raspberry Purchasing: One Grade or Separate SKUs?
Aug 23, 2023

Use one frozen raspberry grade across several recipes only when every intended use fits the same specification and approved handling route. If a dessert needs recognizable whole berries while a sauce is deliberately blended, a shared ingredient may work. The sauce would then use whole berries in a process that breaks them down. If the proposed processing grade fails the dessert requirement, split the purchases. An average requirement across the two recipes solves neither problem.
The useful starting point is the job of the raspberry in each finished product. Record what must remain visible, what happens to the fruit during production, the required ingredient composition and how the stock will be issued. Then test the smallest set of candidate specifications that can serve those jobs. This is a purchasing decision about a product range, rather than a search for the single "best" raspberry grade.
A stock-keeping unit, or SKU, is the item your operation buys and tracks. One raspberry specification can sometimes use more than one pack SKU; conversely, two physically different raspberry ingredients should remain distinguishable even if their commercial names sound similar.

Start with the raspberry's job in each recipe
Group recipes by the result they need from the fruit. A recognizable berry on a finished dessert has a different job from raspberry material dispersed through a cooked preparation. An inclusion in a muffin lies somewhere else again: the product may need identifiable fruit pieces without requiring every incoming berry to remain whole. Write those requirements as observable outcomes. "Premium raspberry quality" is too vague to decide whether the same purchase can serve all three.
List the actual manufacturing route next to each result. Does the fruit enter whole, get chopped, pass through a screen, or become part of a blended base? Is it added before the main process or after it? Use the recipe's real operation rather than a broad label such as bakery or dairy. Two bakery products can place very different demands on the same fruit, while a bakery filling and a cooked dairy preparation may share several ingredient requirements.
Keep the first version of this application sheet compact. For each finished-product code, show the raspberry's job, required incoming form, key acceptance outcome and any restriction that prevents substitution. Add a link to the controlled recipe rather than reproducing its complete formulation. The sheet should expose possible groups quickly; detailed production instructions remain in their existing controlled documents.
We would begin a shared-grade discussion with these application groups before choosing a percentage from a price list. XMSD's whole, whole-and-broken and crumble raspberry options provide different starting points. The useful choice comes from the job the fruit has left to do. A berry that will be deliberately broken down offers a different purchasing opportunity from one whose intact appearance survives to the customer.
| Raspberry job | Requirement to retain | Shared-stock question |
|---|---|---|
| Visible whole berry | Approved intact appearance at use | Can the common specification meet it? |
| Distributed fruit pieces | Approved inclusion result | Does the same incoming form work? |
| Blended preparation | Approved process and ingredient composition | Is whole-fruit appearance needed? |
Find the conflicts that rule out a shared purchase
Separate a negotiable preference from a firm recipe requirement. A slightly different whole-fruit proportion may be workable in a cooked preparation after assessment. An ingredient containing added sugar is a different proposition when the controlled recipe requires unsweetened fruit. A required processing treatment, a destination-specific document or a customer restriction may also prevent consolidation even when two samples look alike. Put these firm conflicts ahead of a discussion about price or convenience.
Check intended use explicitly. FDA explains that freezing generally does not inactivate viruses that can contaminate berries. Accordingly, the food-safety qualification for a fruit ingredient and its use in the finished product need their own review. Moving an ingredient approved for a cooking process into a use after the final pathogen-control step is a process change, not an ordinary stock substitution. Have the responsible technical function approve the intended-use route before treating the recipes as one purchasing group.
Assess safety eligibility and whole-berry appearance in separate approval fields. A candidate must meet both the appropriate safety and compliance requirements and the physical requirements for its intended recipe. A higher appearance grade is irrelevant to an unresolved safety qualification.
Practical example: Take a dessert producer assessing one frozen raspberry candidate for a cooked sauce and a visible berry topping. In this illustrative specification, the topping requires at least 90% whole fruit by the agreed weight method. The candidate sample gives 86%, while its sauce trial meets the separate approved requirements. Keep the candidate eligible for the sauce and obtain a different specification for the topping. Do not lower the topping requirement merely because the sauce consumes most of the raspberry volume. The purchasing group splits at the requirement that the shared candidate fails.
The decision can change if product development formally changes the topping concept to accept broken fruit and validates the revised process. That creates a new approved recipe requirement. It is a different action from purchasing quietly treating the original requirement as optional because a common stock item would be convenient.

Use the whole-fruit ratio as one field, not the whole specification
A commercial whole-and-broken ratio is useful when its definitions and measurement basis are clear. Record what counts as whole fruit, what falls into broken fruit or crumble, how the sample is selected and whether the fractions are assessed by mass. Avoid interpreting the two numbers as a complete quality certificate. They leave other purchasing requirements unresolved, including defects, ingredient status and the preparation route for the finished food.
USDA's published standards distinguish frozen raspberry grades from grades for manufacturing. Their quality descriptions address several attributes, including color, defects and character. A supplier's commercial whole-fruit ratio is therefore not, by itself, an assignment of a named U.S. grade. If the order requires a particular standard, identify that standard and its applicable requirements separately from the supplier's ratio description.
For a shared specification, write the acceptable interval for each relevant characteristic against all included recipes. Where the intervals overlap, a common specification may be possible. Where they do not, return to the application decision. Do not create a broad compromise interval that admits material one of the recipes already rejects. Consolidation works by finding a shared acceptable region, not by averaging incompatible limits.
A whole-fruit percentage also leaves the distribution of individual berry sizes open. If a decoration process selects berries by size or a depositing route has a physical restriction, add the appropriate measurement and application check. Keep that extra field proportionate to the job. A recipe that blends the fruit may have little reason to pay for the same presentation control as a dessert assembled with visible berries.
When comparing bulk frozen raspberry specifications, ask for the actual candidate specification and sample identity together. A grade label on a quotation and a photograph from another product are insufficient to establish the shared range. The approval file should show which specification was evaluated and the product codes it is allowed to serve.

Test the demanding applications before widening the group
Start with the recipes most likely to exclude the candidate. One may be sensitive to broken appearance, another to the preparation needed before addition, and another to the packing or issue method. Testing these demanding uses first can expose a split early. The purpose is to avoid a long sequence of easy trials that ends with failure in the application that actually sets the common requirement.
Use the same identified candidate lot across the initial comparison where practical, and retain the existing approved ingredient as a reference for each recipe. Hold the recipe and relevant preparation conditions stable. If a candidate needs a different handling route, record and assess that route explicitly. A positive result after several unrecorded adjustments provides little guidance for routine purchasing or production.
Define an outcome for each application before the trial. The decoration evaluation might examine recognizable berry appearance at the point of service; a processed preparation might use its existing finished-product criteria. Record the result against that specific use rather than awarding the raw fruit a universal pass. A single application can approve its own use without proving that the candidate serves the rest of the range.
The bakery-filling application checks cover the detailed testing needed for that particular route. Here, the purchasing task is to connect that result to a shared-use decision. Put the bakery approval alongside, rather than in place of, results for the other recipes. Existing formulation and process criteria remain the starting point; the consolidation project should not erase them.
After the demanding uses pass, establish which remaining recipes need their own trial and which can be covered by a documented technical justification. Similar product names alone are weak grounds for grouping. Relevant similarities include the fruit's role, preparation, equipment path and acceptance outcome. Keep a reason for the grouping so a future change to one recipe can be assessed against the same logic.
Calculate demand from approved uses, not total raspberry sales
Calculate ingredient demand for each recipe on its own stated basis, then add only the recipes the candidate is approved to serve. A finished-product sales forecast and a frozen-fruit purchase quantity are different numbers. Use the recipe's raspberry input fraction, planned production quantity and any validated yield or handling allowance. Keep the first calculation free of assumed losses; add justified adjustments visibly so they can be checked.
Worked example: Suppose a manufacturer plans 4,000 kg of total batch input for a fruit preparation containing 18% frozen raspberries, plus 2,000 kg of total batch input for a dessert base containing 6%. The raspberry inputs are 4,000 × 0.18 = 720 kg and 2,000 × 0.06 = 120 kg. If both recipes approve the same processing specification, their shared demand is 840 kg. A separate decoration program requires another 160 kg under a whole-berry specification, so the total purchase plan is 1,000 kg split into 840 kg and 160 kg. These are illustrative planning inputs before handling allowances, not XMSD order quantities or minimums.
The processing specification covers 84% of that plan by mass. The remaining 16% stays in its own purchasing group because the decoration requirement is different. If the decoration recipe changes, update its approval and forecast separately. A weighted average of all recipe requirements would lose the distinction that justified the split.
Now consider the alternative: buy one whole-berry specification for all 1,000 kg. If it is approved for every use, that can simplify stocking. Compare the actual quotations and operating consequences of that route with the split plan. Include the work of maintaining two item codes, pack handling, stock exposure and any required preparation. There is no need to assume that two grades always save money or that one grade always improves service. The relevant comparison is between two approved supply plans.
Keep forecast timing visible. Monthly totals can conceal a decoration campaign that needs its stock earlier than the processing production run. Confirm availability, packing and delivery terms for each proposed purchase; combine schedules only where the supplier and receiving operation can support them. A neat spreadsheet total is useful only when the ingredient is available in the correct form at the point it is needed.
Distinguish a second pack code from a second fruit specification
One fruit specification may need two pack formats. A factory that empties a full industrial liner into a batch and a smaller production area that issues limited quantities may need different handling formats. First ask whether the proposed pack supports each operation's approved issue and storage procedure. Then decide whether a second pack code is enough or whether the fruit itself also needs a separate specification.
We keep those two decisions separate in a raspberry order discussion. Changing pack size can solve an issue-quantity problem while leaving whole-fruit ratio and other ingredient requirements unchanged. Changing the fruit grade changes the ingredient approval itself. If both changes are recorded under one vague "raspberry replacement," the receiving operation has to guess which part of the old approval still applies.
Map the pack codes to the underlying approved specification. Each code should show its contents, net quantity, identification and permitted uses. Link commercial pack details to the recipe issue instruction, especially where part-packs are involved. The frozen-food packing options help frame the format discussion, while the actual order confirmation establishes which format is being supplied.
Compare the complete handling route during a trial. Record how packs are brought to the line, identified, opened and issued, and how any remainder is handled under the approved procedure. A pack that is manageable in a sample room may create extra operations in routine production. Record that as a pack-handling finding and assess the format change it requires. Keep the fruit's application result in its own field.

Write substitution permissions in both directions
If two raspberry specifications remain in the range, define which may replace the other and in which recipes. Permission is often directional. A whole-berry ingredient may be technically acceptable in a preparation that breaks it down, but that still requires approval and a commercial decision. Keep a broken-fruit ingredient restricted to uses that accept its appearance. The two item codes need explicit permissions rather than an unrestricted substitute flag.
Write the permission against the destination recipe. Include the candidate specification, approved preparation route, required authorization and any label or document review. A supply shortage is a reason to consult that record, not a reason to improvise a new equivalence. If no alternative is approved, identify the specific trial or review needed before stock is issued to that use.
Set rules for the stock already on site when a change is approved. Record the lot and quantity covered, whether the permission is temporary or ongoing, and how production will identify the issued material. Keep the original lot identity through the finished-product records. A temporary acceptance for one recipe should remain visibly limited rather than becoming a permanent permission for every raspberry product.
For a food-processing ingredient discussion, the most useful starting material is this application list and its approved alternatives. It shows which specification gaps would stop production and which uses have flexibility. That makes an alternative-sample request more precise: it asks for evidence against a defined use rather than a promise that another raspberry product is "similar."

Keep the shared specification aligned with the product range
Review the purchasing group when a recipe, presentation, processing route or customer requirement changes. Adding a dessert with visible berries may introduce a constraint absent from the original group. Removing that dessert may create an opportunity to reconsider a more processing-oriented specification. The common stock item should follow the approved product range, not force new recipes to inherit a historical purchasing choice without review.
Keep the group small enough to explain. A useful shared specification has a list of approved uses, the constraints that define it and a record of the relevant trials. If every recipe needs its own exception, the apparent consolidation may be creating more administration than a clear split. Compare that burden with the actual benefits of common stock before expanding the group further.
Revisit demand after the first production period using actual ingredient issues and finished-product plans. Look for stock assigned to the wrong application group, unplanned substitutions or quantities that accumulate because a campaign moved. These observations can reveal a forecasting or authorization problem even when the raspberry conforms to specification. Correct the planning record before changing the supplier requirement to solve the wrong issue.
The final recommendation should fit into a short purchasing instruction: one specification for the named approved uses, or separate specifications with defined pack codes and substitution permissions. Attach the application records and forecast behind it. Purchasing then has a usable order plan, production has a clear issue rule, and changes can be reviewed against named approved uses. Fewer item codes are worthwhile when the products still receive the ingredient they were approved to use.

For a raspberry purchasing discussion with XMSD, share the recipes the ingredient must serve, the firm application requirements, expected demand by use and preferred packs. We can review candidate specifications for a common purchasing group or a clearly defined split.
References
- USDA Agricultural Marketing Service: Frozen Raspberries Grades and Standards
- FDA: Works to Enhance the Safety of Berries - freezing and enteric-virus control context
- XMSD operational perspective: matching whole-fruit specifications, application requirements, purchasing groups and commercial packing; current product and application pages linked in the body.

