Scope: This guide is written for qualified wholesale distributors and sourcing teams reviewing empty only Whole Melts routes in markets where allowed. It covers document requests, verification records, packaging proof, carton records, supplier identity, receiving checks and change-control rules. It does not cover oils, contents, formulas, filling steps, dosage claims, potency claims, health claims, medical claims, therapeutic claims or consumption guidance.
Why the documentation pack matters
Distributors do not add a new Whole Melts run to inventory from product photos alone. A stronger process compares the supplier file, verification route, packaging proof, carton record and receiving checklist before the SKU name reaches a catalog, warehouse sheet or reorder plan.
The phrase whole melts verify should be treated as a workflow, not a single code check. A code, QR route or NFC route can help, but a distributor still needs matching documents: approved title, version wording, empty only confirmation, packaging photos, invoice details, carton count and written change approval.
The key idea
A buyer documentation pack protects the distributor from title drift, packaging drift, mixed cartons, weak supplier identity and unsupported claims. It also gives the warehouse team a simple record to compare when the next run arrives.
Quick answer
Before adding a new Whole Melts run to inventory, distributors should request a documentation pack with eight core files: supplier identity, approved product title, empty only statement, verification record, COA or lab-document route where relevant, packaging proof, carton record and change-control note.
For category-level comparison, buyers can start with Whole Melt products and then narrow the file by format, version, quantity basis and warehouse route. For broader sourcing comparison, whole melt extracts wholesale pages can support keyword clustering without forcing the article into a hard-sell format.
Verification file
Record the official check route, code area, NFC path where present, and master-box proof before inventory approval.
Supplier file
Match company name, quote owner, invoice party, packing list and support contact to the same order.
Packaging file
Store front, back, side, inner pack and carton photos with the approved title and revision date.
Receiving file
Check carton count, inner count, outer mark, lot basis and delivery photos before releasing stock internally.
Verification records
The official Whole Melt verification page says silver scratch-off verification stickers are placed on each box, codes verify on the official page, master boxes use NFC tap-to-verify stickers, and some packs use a blacklight security feature. Distributors should record these cues in the buyer file instead of relying on screenshots alone.
A clean verification record should include the verification page used, the exact code area photo, the master-box NFC result where applicable, the date of the check, the staff member who checked it and a note showing whether the verification matched the approved title and packaging file.
| Verification item | What to request | Inventory decision rule |
|---|---|---|
| Official page route | A link or screenshot showing the page used for the verification check. | Do not accept a redirect that cannot be explained in writing. |
| Scratch-off code proof | Readable photo of the code area before and after verification where suitable. | Hold approval if the code area is cropped, blurred or recycled from another run. |
| Master-box NFC proof | Tap result, master-box photo and carton mark in the same file. | Record NFC proof at the master-box level, not only at sample level. |
| Security-feature proof | Visible proof where the supplier claims a blacklight or layered security feature. | Require new proof if the packaging version changes. |
| Check owner | Name or role of the staff member who performed the check. | Every verification should be traceable to a person and date. |
COA and lab-document review
This article is empty only, so distributors should not turn the sourcing page into a contents claim. Still, in regulated markets, buyers often receive customer questions about COA access, batch testing language and supplier claims. When a supplier provides lab-related files, the buyer should check whether the lab route, batch number, product title and packaging record match the same run.
California’s Department of Cannabis Control explains that batches of cannabis goods must be tested before sale and that testing covers cannabinoids, terpenes, residual solvents, processing chemicals, pesticides, heavy metals, microbial impurities and mycotoxins. ISO/IEC 17025 is also relevant when a buyer reviews whether a laboratory can demonstrate competence, impartiality and consistent operation.
Important boundary
Do not write or publish any potency, contents, benefit, medical, therapeutic or usage statement from a supplier unless it has been reviewed by qualified market counsel and matched to the correct run. Keep the public page focused on empty only procurement records.
| Lab-document field | Buyer question | What should match |
|---|---|---|
| Report identity | Is the report tied to the same supplier, title and batch? | Supplier name, product title, batch code and date. |
| Lab identity | Is the laboratory name, address and credential route visible? | Lab name, report number and accreditation details where claimed. |
| Batch basis | Does the batch number match the packaging and carton record? | Batch code, lot basis, carton file and receiving sheet. |
| QR or COA access | Does the QR route resolve to a readable report? | QR result, report file and same run title. |
| Claim control | Are supplier claims separated from verified records? | Only reviewed statements should appear in buyer-facing copy. |
Supplier documents to request
The supplier pack should answer one question: can this exact run be quoted, received and reordered without confusion? That means the distributor should collect more than a product image. The file should connect the trading party, quote owner, invoice party, payment route, warehouse route, order title and support contact.
NIST supplier evaluation material is useful as a neutral reference because it treats supplier evaluation as a documented purchasing process rather than a trust-based message thread. For distributors, the practical lesson is simple: a supplier file should be organized before inventory approval, not reconstructed after a dispute.
| Document | Required details | Why it matters |
|---|---|---|
| Supplier identity | Company name, business contact, quote owner and support route. | Confirms who is responsible for order correction and reorder support. |
| Approved title | Exact title used across product file, quote, invoice and packing list. | Prevents near-match names from replacing the approved run. |
| Empty only statement | Written confirmation that the scope is empty only. | Keeps the buyer file aligned with the site scope and avoids contents claims. |
| Quote and invoice | Quantity basis, unit basis, carton basis, invoice party and validity window. | Helps finance, warehouse and procurement teams use the same record. |
| Packing list | Carton count, inner count, gross weight, carton sequence and title. | Creates the receiving baseline before the order is opened. |
| Change-control note | Written approval rule for title, packaging, carton, route or invoice changes. | Stops silent substitutions after the first approval. |
Packaging and label proof
Packaging proof is where many distributor files become weak. A buyer may approve one box image, but the later shipment may show a different front panel, side panel, inner pack, label position or carton mark. That is why every new run should have a packaging proof folder, not a single social image.
For example, buyers comparing a current 2G route such as Whole Melt V8 Phase 3 2G should keep the approved title, version wording and carton record separate from any other Whole Melts version. If a buyer later compares V9 Whole Melt Phase 4 2G Empty, it should have its own document row and proof folder.
| Packaging proof | What to store | Reorder note |
|---|---|---|
| Front proof | Readable front panel with title and version wording. | Reject replacements that do not match the approved front file. |
| Back proof | Back panel, label area and any code area where present. | Open a new review if the back panel changes. |
| Side proof | Side panel, count wording, version wording and variant mark. | Side-panel drift can create warehouse picking errors. |
| Inner pack proof | Inner count, pack structure and readable title. | Mixed inner packs should pause receiving release. |
| Master carton proof | Carton mark, sequence number, weight and product title. | The carton mark should match the packing list. |
Carton and receiving records
Carton records turn procurement promises into warehouse evidence. The receiving team should photograph each carton, compare carton marks against the packing list, confirm total count and record any difference before stock is released internally.
GS1 traceability guidance is useful here because traceability systems depend on consistent item identity, location identity and event records. A distributor does not need a complex system to start; even a simple receiving sheet should connect carton sequence, title, quantity basis, date and responsible staff member.
| Receiving field | Record to capture | Release rule |
|---|---|---|
| Arrival photo | Photo of all cartons before opening. | Keep photos with date and receiving staff note. |
| Carton sequence | Carton 1 of X, 2 of X and so on. | Pause release if carton sequence is incomplete. |
| Outer mark | Title, count, mark and destination note where present. | Outer mark should match the packing list. |
| Inner count | Pieces per inner pack and inner packs per carton. | Record shortage or overage before stock is moved. |
| Exception log | Damaged carton, mixed packaging, unclear mark or count mismatch. | Do not add exceptions to active stock until reviewed. |
New-run change control
A new run is not only a new quantity. It can mean a revised title, packaging change, new code area, different carton mark, new warehouse route, different invoice party or updated proof folder. Without change control, the distributor may not notice the difference until receiving or customer support flags it.
The easiest rule is this: no title, format, packaging, carton, invoice or route change should move forward without revised proof and written approval. That rule is not aggressive sales language. It is a procurement safeguard.
New-run approval rule
Every new run should have a dated approval record. If the supplier says the change is minor, the buyer should still ask for revised proof before adding the run to inventory.
| Change type | File to request | Approval action |
|---|---|---|
| Title change | Revised product file, quote and packing list. | Create a new approved-title row. |
| Packaging change | New front, back, side, inner pack and carton files. | Update the proof folder before ordering. |
| Verification change | New code proof, NFC proof or official route note. | Repeat the verification check from the new file. |
| Route change | Warehouse route, destination note and expected receiving timeline. | Confirm before dispatch. |
| Supplier-party change | Invoice party, payment route and support contact. | Escalate for finance and compliance review. |
Red flags before inventory approval
A documentation pack is useful only if the distributor knows when to stop. The goal is not to reject every small difference. The goal is to pause any order where the difference could affect authenticity review, receiving accuracy, customer copy or reorder planning.
| Red flag | Why it matters | Buyer response |
|---|---|---|
| Unclear verification route | The code or NFC route does not match the supplier explanation. | Request official-route proof and a dated verification record. |
| Blurred packaging proof | The title, code area or version wording cannot be checked. | Request new photos before approving the run. |
| Mixed title wording | Quote, invoice, packing list and box file use different names. | Choose one approved title and revise every document. |
| Missing carton record | Receiving cannot confirm carton sequence or total count. | Hold warehouse release until the packing list is reconciled. |
| Unsupported marketing claim | The supplier provides benefit, safety or outcome claims without review. | Remove the claim from public copy and request qualified support. |
| Silent substitution | The supplier changes packaging, route or invoice details after approval. | Restart the change-control review before the order continues. |
RFQ email template
Use this message when asking a supplier for a documentation pack before adding a new Whole Melts run to inventory.
Subject: Documentation request before Whole Melts new-run inventory approval
Hello,
Before we approve this new Whole Melts run for inventory, please send the full documentation pack for review.
Scope: empty only.
Please include:
- Supplier company name, quote owner, invoice party and support contact.
- Exact approved product title for quote, invoice, packing list and carton mark.
- Written empty only confirmation.
- Verification record, including official check route, code-area proof and master-box NFC proof where present.
- Packaging proof: front, back, side, inner pack and master carton photos.
- Packing list with carton count, inner count, gross weight, quantity basis and carton sequence.
- Any lab-document or COA route that is relevant to the destination market, matched to the correct run.
- Written change-control note confirming that no title, packaging, carton, invoice or route change will ship without revised proof and written approval.
Please keep all files tied to the same run title and send them before dispatch.
Thank you.
Official references
These sources support a neutral documentation workflow. They do not replace qualified legal, customs, tax, trademark, labeling or regulated-market advice.
| Reference area | How to use it in the buyer file | Source |
|---|---|---|
| Whole Melt verification | Use for code, NFC and security-feature review where applicable. | official Whole Melt verification page |
| Batch testing context | Use for regulated-market COA and batch-testing vocabulary. | California DCC testing laboratories |
| Laboratory competence | Use when reviewing whether a lab route is credible and documented. | ISO/IEC 17025 laboratory competence |
| Packaging and label checklist | Use when a buyer needs packaging, label and shipment acceptance context. | New York OCM Part 128 guidance |
| Special packaging context | Use when reviewing child-resistant and senior-friendly packaging documents. | CPSC guide to special packaging |
| Traceability planning | Use when building lot, carton, location and receiving records. | GS1 Global Traceability Standard |
| Supplier evaluation | Use as a neutral reference for documented purchasing and supplier review. | NIST supplier evaluation procedure |
| IPR import risk | Use when explaining why source control and supplier identity matter. | CBP IPR seizure statistics |
| Claim review | Use before copying benefit, safety or outcome statements from supplier material. | FTC health products compliance guidance |
| Structured data | Use when planning snippet markup outside the procurement text. | Google product structured data |
FAQ
What should distributors request before adding a new Whole Melts run to inventory?
They should request supplier identity, approved title, empty only confirmation, verification record, packaging proof, carton record, packing list, relevant lab-document route and written change-control terms.
Is a verification code enough for inventory approval?
No. A verification code can support the review, but distributors should also compare the supplier file, packaging proof, carton record, invoice title and receiving file.
Why does empty only confirmation matter?
It keeps the procurement file aligned with the article scope and prevents the distributor from publishing contents, formula, dosage, potency, health or consumption claims.
When should a buyer pause a new run?
A buyer should pause the run if title wording, packaging proof, verification route, carton count, invoice party or route record differs from the approved buyer file.
How should distributors handle supplier claims?
Supplier claims should stay out of public copy until they are reviewed, supported and matched to the correct run. Unsupported benefit, safety, legality or outcome claims should be removed.
Should each version have its own documentation row?
Yes. V7, V8, V9, Phase 3, Phase 4 or any other version wording should have its own row when the title, packaging, carton record or verification route differs.
Is this legal advice?
No. This is an educational B2B documentation guide. Buyers should seek qualified legal, customs, tax, trademark, labeling and regulated-market support before final approval.
```
0 Comments