THCA Shipping to Romania

This page is a documentation-first shipping guide for EU-focused wholesale shipments routed to Romania.
It does not promise outcomes and it is not legal advice. Cross-border shipments can be inspected, held, delayed, or returned.
Your best leverage is a coherent shipment packet that matches the physical goods—every time.

Start points: /shipping/ · /compliance/ ·
/documentation/ · /legal-status/ ·
/wholesale/ · /insights/

Shipping posture for Romania (conservative, process-driven)

Don’t build your plan around best-case assumptions. Build around controllables:

  • Shipment packet assembled before dispatch (single coherent set, ready to resend).
  • Batch/lot traceability across COA ↔ invoice ↔ packing list ↔ labels (exact match).
  • COA integrity (complete fields, dates, methods, units).
  • Lab verification documented (authenticity and scope checks).
  • Receiving discipline (photo log + lot checks + quarantine triggers).

Foundation rules:
/compliance/shipping-documents/ and
/compliance/batch-traceability/.

Minimum shipment packet for Romania (assemble before dispatch)

Shipment packet (minimum)

  • Commercial invoice (controlled descriptions, quantities, values)
  • Packing list (package counts, weights, contents)
  • Batch/Lot map (mandatory for multi-lot shipments)
  • COA set (one batch-linked COA per lot included)
  • Lab verification note (internal: who verified, when, how)

Standardize the packet: /documentation/shipping-flow/
Document rules: /compliance/shipping-documents/

Batch/lot identity controls (the #1 failure mode)

Most “shipping problems” are identity problems. If lot IDs drift, your documents become inconsistent.

Identity rules

  • Exact lot ID match across COA, invoice, packing list, and labels (same characters and spacing).
  • No stylized batch IDs (no abbreviations, reformatting, or “friendly names”).
  • Multi-lot shipments require a lot map tied to cartons/cases where applicable.

Enforce: /compliance/batch-traceability/ and
/compliance/packaging-labeling/.

COA and testing discipline (don’t ship “generic paperwork”)

Use a conservative baseline: batch-linked, verifiable, and complete COAs. Potency reporting should avoid ambiguity.

  • COA includes lot ID, dates (received/test/issue), methods, and units.
  • Potency reports THCA and Δ9-THC separately.
  • If “Total THC” appears, it must not be ambiguous (buyer SOP defines interpretation).

COA rules: /compliance/certificate-of-analysis/
Testing baseline: /compliance/thca-testing-standards/
Potency context: /insights/thca-vs-thc-eu/

Lab verification (build proof into the batch file)

Treat lab verification as mandatory buyer due diligence. A COA is not “proof” until the lab/report reference is verifiable.

Minimum verification actions

  • Confirm lab identity using independent channels (don’t trust contact info embedded in PDFs).
  • Validate report IDs/QR/portal references where available.
  • Confirm scope/method context is plausible and complete.
  • Record a verification note and archive it with the shipment packet.

Process: /compliance/lab-verification/ ·
Documentation storage: /documentation/

Handling holds (controlled response, not improvisation)

If a shipment is held, your objective is speed + coherence:

  1. Confirm what is being requested (carrier issue vs paperwork request vs inspection).
  2. Resend the shipment packet as a single coherent set (no mixed versions).
  3. Do not rewrite descriptions midstream unless required and controlled.
  4. Log the event internally (what was requested, what was sent, when, by whom).
  5. Escalate destination-specific decisions to qualified professionals as needed.

Inspection context: /insights/thca-customs-inspections/
Risk posture: /documentation/risk-disclosure/

Receiving in Romania (buyer-side controls that preserve leverage)

The buyer’s receiving process is part of compliance. Without it, disputes become “he said / she said.”

Receiving checklist (minimum)

  • Photo log of outer packaging, labels, seals, and any damage before opening.
  • Document match against invoice and packing list (counts/weights spot-check).
  • Lot ID match between labels and COA set (exact match; no formatting drift).
  • Quarantine triggers for mismatches, missing docs, or compromised packaging.

Storage/handling SOP: /compliance/storage-handling/
QA workflow: /documentation/quality-assurance/

FAQ

Do you guarantee shipping outcomes for Romania?

No. Cross-border outcomes depend on enforcement conditions and carrier handling. This page describes a conservative documentation-first process.
See /shipping/.

What is the single most important control for Romania-bound shipments?

Batch traceability. If the lot ID doesn’t match across COA, invoice, packing list, and labels, you don’t have control.
See /compliance/batch-traceability/.

Can we ship using a COA that isn’t linked to our lot ID?

For professional wholesale procurement, no. Generic COAs break traceability and increase inspection and dispute risk.
Use /compliance/certificate-of-analysis/.

What should we send if the shipment is held?

Send the pre-built shipment packet as a single coherent set and keep descriptions consistent. Avoid midstream edits.
Reference: /compliance/shipping-documents/.

Where do we standardize the full shipping workflow?

Use /documentation/shipping-flow/ and the compliance rules at
/compliance/shipping-documents/.