{"id":81,"date":"2026-10-28T01:00:08","date_gmt":"2026-10-27T18:00:08","guid":{"rendered":"https:\/\/cavemekar.com\/blog\/?p=81"},"modified":"2026-10-28T01:00:08","modified_gmt":"2026-10-27T18:00:08","slug":"sampel-acuan-produk-plastik","status":"publish","type":"post","link":"https:\/\/cavemekar.com\/en\/blog\/sampel-acuan-produk-plastik\/","title":{"rendered":"Plastic Product Reference Samples: Separate Approved Examples from Reference Images"},"content":{"rendered":"\n

Updated: 28 October 2026<\/em><\/p>\n

Is a reference image the same as an approved product sample?<\/h2>\n

Not always. A reference image explains an intended direction, while a working reference sample needs a clear identity, version, and approval record. Mark the aspects that remain proposals, then discuss required dimensions and functions with the relevant team. Keep a change record so an old image is not treated as a final specification when discussions move between products or companies.<\/p>\n

Start by assigning a status to every example<\/h2>\n

A plastic product reference sample is useful when the person receiving it understands which aspects are being discussed. A photograph may show the shape without revealing thickness, the reverse side, or how a closure fits. A physical example is not automatically final either. Someone may have brought it to illustrate a colour, or simply to show a shape that needs changing. Write down the purpose before requesting a quotation or forwarding the example to another team.<\/p>\n

Separate three practical statuses: an idea reference, a sample for evaluation, and an approved reference for explicitly named aspects. This is a suggested purchasing workflow, rather than a statement about the internal procedures of every group company. Agree the terms together so a casual \u201clooks fine\u201d does not obscure what was actually checked.<\/p>\n

\"Catalogue
Catalogue illustration; not evidence of sample approval or a particular packing service.<\/figcaption><\/figure>\n

Give the object an identity that stays with it<\/h2>\n

Mark the example with a product name, a temporary code, a version number, and a recording date. Put the label on its storage packaging if direct attachment could interfere with a surface examination. Photograph the label together with the item from a useful angle. Record who holds the original and who receives a copy. A photograph in a conversation can then be traced to a particular physical object.<\/p>\n

Avoid identifiers that mean only \u201cthe last one sent\u201d. After several discussions, two parties may both believe they hold the latest example. If a sample is divided into parts, add a part identifier without removing the original code. Do not overwrite the old identity when making a revision: the new record should explain its relationship with the previous version.<\/p>\n

Separate approved aspects from open questions<\/h2>\n

An approval should name the aspects assessed. A pouch discussion may cover only the basic shape and closure position; material, printing, and use conditions may still be undecided. A container discussion may focus on the body and lid pairing. Write this boundary in ordinary language, then seek confirmation from the person responsible for that requirement.<\/p>\n

A useful note might say: \u201cThe external shape is a reference; dimensions still await joint measurement.\u201d That is clearer than a single unexplained tick. Visual approval is not evidence that a product meets use, performance, or food-contact requirements. Any necessary documentation and evaluation should be discussed separately for the particular project. Keep those open requirements attached to the sample record rather than assuming that general approval resolves them.<\/p>\n

What should a reference photograph show?<\/h2>\n

Take an overall view, relevant side views, and a close-up of the detail that motivated the choice. Include a suitable scale reference when dimensions need explaining, but do not treat measurements from a photograph as a substitute for actual dimensions. Camera angle and object position can change the apparent length or width. If using a supplier image, keep its origin and any statement that it is illustrative.<\/p>\n

For colour or clarity, explain the photographic conditions and their limitations. Screens, backgrounds, and lighting can make two photographs look different. If colour is a significant requirement, discuss the assessment method and physical reference with the relevant parties. A useful photograph supports a conversation; it does not guarantee that every product characteristic has been examined.<\/p>\n

Use a separate sheet for each product family<\/h2>\n

A single enquiry may cover bags, containers, and film. These do not need exactly the same checklist. A bag may require notes about the opening and handles. A container needs the identity of its matching body and lid. Film should be described in the required format, rather than only through a photograph of a finished pack. Connect each sheet to the same enquiry code so the overall project remains traceable.<\/p>\n

The Cave Mekar Group product directory<\/a> helps identify product families before a discussion is directed to the relevant company. Readers considering bags and PE film can also review the Mekar Plastik catalogue<\/a>. A catalogue introduces products; it does not replace final specifications or confirmation of capabilities for a particular order.<\/p>\n

\"Catalogue
Catalogue illustration; not evidence of sample approval or a particular packing service.<\/figcaption><\/figure>\n

Build an approval table that can be read later<\/h2>\n

The following table is an example recording format, not an approval document already in force for an order. Fill every row with information actually examined. If something is unknown, write \u201cnot confirmed\u201d instead of copying a number from another product. Keep photographs and documents in a location accessible to the people authorised to see them.<\/p>\n
Record section<\/th>Information to explain<\/th><\/tr><\/thead>
Sample identity<\/td>Code, version, date, and storage location<\/td><\/tr>
Approved aspects<\/td>Shape, component pairing, or another explicitly named feature<\/td><\/tr>
Open aspects<\/td>Dimensions, material, printing, documentation, or use still to agree<\/td><\/tr>
Changes<\/td>Previous version, requested change, and confirming party<\/td><\/tr><\/tbody><\/table>\n

Do not fill an approval field merely because someone received a photograph. Receipt, examination, and approval are different events. If a response is unclear, record the unanswered question and seek a specific confirmation.<\/p>\n

Record changes without erasing the discussion trail<\/h2>\n

A small change can affect something previously considered complete. If a container rim changes, for example, its lid pairing needs to be discussed again. If a bag size changes, an old print-position drawing should not automatically remain valid. State the original version, the reason for revision, and the aspects requiring reassessment. Keep the earlier example as history with a label that prevents it being selected as the active reference.<\/p>\n

Not everyone needs the entire conversation archive. They need a summary of the active version and the decisions still open. When sharing a file again, include its version in both the filename and its contents. Do not rely only on a message date because an older image can be forwarded on a different day.<\/p>\n

Explain the reference boundary during handover<\/h2>\n

Before an example moves to purchasing or a supplier, check the list of objects and attachments. Make sure the code in the photograph matches the code on the sample packaging. Explain anything not included, such as a matching lid still held by another team. The recipient should know whether the object is for quotation, evaluation, or follow-up on explicitly agreed aspects.<\/p>\n

For container discussions, the group thinwall page<\/a> and CSB container page<\/a> provide product context. Still include the sample code and actual requirements. This recording approach supports coordination across products without assuming that one catalogue or one approval applies to every type of packaging.<\/p>\n

Send an enquiry that can be acted on<\/h2>\n

Prepare a short message naming the product, the active sample code, the aspect requiring confirmation, and its attachments. State missing information openly. The receiving team can then ask relevant questions without guessing whether a photograph represents dimensions, material, or just a design direction. Price, order quantity, and scheduling still require confirmation for the specific need.<\/p>\n

Cave Mekar Group comprises five companies and seven plants according to owner-confirmed group facts. This article suggests a way to organise purchasing information; it is not a new service announcement or a claim that every product follows an identical approval process. Follow @cavemekargroup<\/a> for group information and use the relevant product page as the starting point for a conversation.<\/p>\n

Frequently Asked Questions<\/h2>\n

Is a physical example always the final sample?<\/h3>\n

No. A physical example may illustrate only one aspect. Record its status, version, and approved aspects before using it as a reference.<\/p>\n

What belongs on a sample label?<\/h3>\n

Record the product name, sample code, version, and date. Keep the relationship between the label, photographs, and storage location so the recipient can trace the object.<\/p>\n

Can dimensions be confirmed from a photograph?<\/h3>\n

A photograph explains shape, but camera angles can change apparent dimensions. Actual measurements and the measurement method need joint confirmation.<\/p>\n

How should an older image version be handled?<\/h3>\n

Keep it as history with an inactive label. Record the replacement version and changed aspects so the old image is not treated as the latest specification.<\/p>\n

Does visual approval prove suitability for use?<\/h3>\n

No. Use, performance, and product documentation require evaluation for the intended requirement. Visual approval covers only the explicitly named aspects.<\/p>\n