01 / Planning the purchase
Label every component
List each fiber by name before adding percentages. An unlabelled ratio can be interpreted differently when a colleague changes the order of the names. “Polyester” and the other component should stay beside their respective shares wherever the recipe is copied, including internal notes and inquiry emails.
02 / Planning the purchase
Agree on the basis
State whether the ratio refers to the intended fiber input mixture. Do not mix a mass-based blend plan with a count of finished articles or packages. The blend calculator on this site uses mass shares, so its output is a component quantity derived from the total input mass you enter.
03 / Planning the purchase
Separate recipe from purchasing allowance
A planned blend and a production allowance answer different questions. Keep the recipe unchanged when discussing process loss or purchasing buffers. Record any allowance separately in your own production plan, rather than quietly changing a component’s percentage to make the buying quantity fit.
04 / Planning the purchase
Keep alternatives as separate options
When comparing two blend concepts, give each one a name and a complete component list. Avoid sending a chain of corrections that leaves the reader unsure which recipe is current. If a blend is still open, describe it as a development choice and identify who will make the decision.
05 / Planning the purchase
Prepare the message
Include the material form, end use, labelled blend, estimated total mass and destination. Add the reason for considering the blend, expressed as a project objective. Have questions? Please email us directly. The calculator can assist with arithmetic after you decide which recipe to discuss.
Your practical checklist
- Write each component name beside its percentage.
- Confirm that the percentages describe mass shares.
- Keep production allowances outside the recipe.
- Give alternative blend concepts separate names.
Keep this checklist beside your current project brief and revisit it when the buying context changes.