A packaging team can start designing a custom container when an existing reusable product would solve the problem with less development work. The opposite mistake is forcing a standard product into an operation that has already outgrown it. Start with the existing-product path. Move toward custom development only when a repeatable constraint remains and solving it can create enough operational or financial value to justify the work.
SPF Groups supports both paths. We manufacture established reusable product families and develop new rigid returnable packaging through New Product Development. The commercial decision is not which path sounds more sophisticated. It is which path fits the application without creating unnecessary compromise.
Start with existing SPF Groups reusable product families.
Standard Reusable Products Usually Win on Simplicity
An established product has one immediate advantage: the design already exists, giving the buyer something concrete to evaluate before starting development. A standard tote, tray, dolly, or rack can be compared with the product being handled, surrounding equipment, storage practices, and the way packaging moves through the operation. If the fit is good, custom development may add complexity without solving a meaningful problem.
A standard product can also keep the decision focused. Procurement and operations can evaluate a known option against the requirement instead of expanding the project into design, prototyping, testing, tooling, and commercialization before that work is justified.
None of that means a standard product is automatically cheaper, faster to obtain, or better for every application. Those outcomes depend on the product, order, supplier, and project. The advantage is narrower: an established product allows the buyer to test whether an existing solution already meets the operating requirement.
SPF Groups currently offers reusable product families that include handheld totes and containers, trays and baskets, plastic and metal dollies, and metal racks. At this stage, the question is not which model to buy. It is whether an established product family can credibly meet the requirement before the company commits to developing something new.
Before defaulting to custom, define exactly why the existing route fails.
Custom Becomes Relevant When the Mismatch Keeps Reappearing
A one-time inconvenience is a weak reason to create a new packaging product. What changes the decision is a mismatch that keeps returning.
The problem may sit in product geometry, handling equipment, storage, transportation, the working environment, material requirements, or product protection. A new design is easier to justify when the same constraint continues to surface and an established option does not resolve it.
If employees can use the existing packaging without unusual workarounds, product protection is acceptable, the package fits the handling system, and the operation is meeting its objectives, a unique design may have little business value. A development case gets stronger when the same constraint appears repeatedly and the operation can tie that mismatch to measurable cost, lost capacity, product damage, handling burden, wasted space, process interruption, or another supportable consequence.
New packaging introductions can create the same decision. A company may add a product whose geometry no longer fits the current transport packaging. A regulatory or sustainability initiative may change a material or operating requirement. A process change may expose a constraint that did not exist when the current packaging was selected.
In New Product Development, SPF Groups considers project specifications, design, material, and working environment. Those categories matter because a new solution should respond to the application that actually exists, not merely to a preference for something unique.
A custom-design idea is not required before starting that conversation. A clearly defined operating mismatch is the better starting point.
Separate Business-Case Customization From Nice-to-Have Customization
Customization can be visually appealing without being commercially important. Some existing SPF Groups product families already offer branding and color options, so those requests do not automatically require a new packaging design. Full product development needs a stronger reason: a requirement that the existing product cannot satisfy without meaningful compromise.
Ask what changes if the custom solution works.
A new geometry might need to remove a recurring handling problem, protect the product more effectively, or improve another measurable operating condition enough to justify development.
The answer does not have to be expressed only as direct cost savings. A project can create value through capacity, handling, product protection, compatibility, waste reduction, or another measurable outcome. The important discipline is to define the result before treating the design work itself as the objective.
Financial logic belongs in the decision without turning every custom project into a spreadsheet exercise: target success measures in our NPD approach can include ROI, IRR, or NPV. Subsequent work gathers the relevant data, weighs alternatives, and defines measurable success criteria. Those measures do not impose one financial threshold on every custom packaging opportunity. The work should still have a success condition that can be discussed and evaluated.
A credible custom business case begins with two statements:
• the operating constraint the existing solution does not resolve; and
• the measurable improvement that would make solving that constraint worthwhile.
If those statements are difficult to make, the project may still be interesting, but the business case for new product development is not yet clear.
Existing Products and Custom Development Belong in the Same Decision
Standard and custom packaging are two routes to the same objective: move and protect the product in a way that fits the operation and its economics. Our existing portfolio gives buyers established rigid reusable options to evaluate. New Product Development provides another route when the operating requirement calls for a solution that does not already exist in the needed form. For the buyer, the requirement should control the choice rather than a preference for either route.
A practical comparison can look like this:
| Decision signal | Existing-product route is stronger when… | Custom-development route deserves evaluation when… |
|---|---|---|
| Operational fit | An established option fits the product, handling pattern, and surrounding workflow without material compromise | Available options leave the same meaningful mismatch unresolved |
| Workarounds | Normal handling can continue without recurring exceptions | Employees or equipment repeatedly compensate for poor fit, orientation, protection, or movement |
| Configuration | Supported options such as branding or color address the requirement without changing the underlying design | The application needs a materially different geometry, material choice, or operating behavior |
| Business value | A new design would not create a clearly measurable improvement | Solving the mismatch can be tied to a supportable operational or financial outcome |
| Validation need | The buyer can evaluate an established item directly against the application | A new design needs prototype or beta evaluation before broader rollout |
The table is a decision aid, not an SPF Groups qualification procedure. It keeps the buyer focused on the requirement without implying that every custom inquiry follows a mandatory standard-product screening process.
Suppose an operation finds a tote that fits the product, works with the handling process, and supports the required storage and transport pattern. Developing a new tote solely because a different geometry is possible adds work without a defined gain.
Now change one condition: every available option forces the product into a poor orientation that repeatedly creates handling or protection problems. The development conversation now has a concrete job. The design is not being asked to be different. It is being asked to remove a repeatable constraint.
The strongest standard-vs-custom decision is therefore not based on preference. It is based on whether the existing route leaves a material problem unsolved.
Custom Does Not Skip Validation
A justified custom project is still unproven until the design earns confidence in the real application. Within SPF Groups’ Stage/Gate sequence, Validation follows Discovery and comes before Development. Our NPD capabilities include rapid prototyping and working prototypes that can move into beta testing on-site, helping evaluate whether a new design addresses the constraint that made an established option insufficient.
Choosing custom therefore does not mean moving directly from idea to broad rollout. The relevant validation question is whether the new design actually improves the operating condition that justified development in the first place. If it does not, the business case for custom should be reconsidered.
Route the Requirement to the Simpler Viable Path
The best outcome of a standard-vs-custom review is not a custom project. It is a packaging solution that fits the operation with no more complexity than the requirement deserves.
If an established reusable product already meets the need, use that route. The existing product has solved the commercial problem without asking the company to create a new one.
When standard options leave a persistent mismatch, the next question is whether removing that mismatch creates enough value to justify development. That is the point where custom reusable packaging becomes a business decision rather than a design preference.
Our New Product Development capabilities cover new rigid plastic containers and returnable packaging for applications that need a new solution. We can evaluate the requirement, operating environment, alternatives, and success measures without assuming that development is automatically the right answer.
The dividing line is simple: do not develop a new reusable package merely because custom is possible. Develop one when the operation can explain what existing products fail to solve and what successful development needs to improve.
For a persistent packaging constraint that existing products cannot resolve, explore New Product