A buyer sourcing seeds, live plants, cuttings, bulbs, plant material, or other plant-related goods from China may receive a quotation, an item list, a permit copy, a product label, a scientific name, a packing list, and an exporter statement. These documents can look tidy while pointing to different products, origins, lots, or shipment dates. A source map preserves the trail without pretending that a document settles an import question.
This article organizes China supplier plant import permit evidence as factual buyer-side records. It explains how to preserve what sources state about product wording, scientific names, origin, permit references, supplier identity, public information sources, phytosanitary documents, packaging, and commercial shipments. It does not decide whether an item is a plant or seed, whether it is subject to a permit, which permit may be relevant, whether a permit is authentic, valid, current, or applicable, whether a commodity meets conditions, or whether it may enter, be imported, sold, or released.
The Animal and Plant Health Inspection Service, or APHIS, says agricultural import requirements vary by the specific commodity and country of origin and points users to its Agricultural Commodity Import Requirements, or ACIR, database. APHIS identifies APHIS eFile as the online system for applying for and receiving import and transit permits for plants, plant pests, soil, and agricultural products. 1 That context makes source organization important. It does not enable a buyer or supplier to reach a permit or entry conclusion from a file bundle.
Define the document-control boundary first
Start with questions a source can answer. What product name did the supplier use? Which botanical or common name appears on a label? What place of origin does a source state? What permit number, date, or stated holder appears? Which lot or shipment references are printed? What does an email say about the relationship among the documents?
Keep decision questions outside the source packet. Commodity classification, botanical identity, permit necessity, permit selection, permit interpretation, authenticity, phytosanitary status, packing conditions, inspection, entry, importer duties, sale, and release require the appropriate qualified review. A buyer’s source map makes the review possible; it does not replace it.
| Evidence question | Preserve from the source | Keep separate |
|---|---|---|
| What item is named? | Literal product and common-name wording. | Botanical or commodity classification. |
| What scientific name appears? | Exact genus, species, cultivar, or taxa wording. | Whether the identification is correct. |
| What origin is stated? | Country, region, nursery, or supplier statement. | Origin or eligibility conclusion. |
| What permit source exists? | Number, date, holder wording, file, and source date. | Need, authenticity, validity, or scope of a permit. |
| What shipment source exists? | PO, invoice, packing, freight, and lot references. | Entry, import, sale, or release result. |
Build one item and lot record at a time
APHIS says requirements vary with the commodity and country of origin. 1 The practical record-control response is to avoid an all-purpose product line called “plants.” Make a separate item record for each source-stated product, scientific name, common name, variety, quantity unit, origin wording, and lot or shipment reference.
A quotation may say “orchid tissue culture.” A packing list may use a Latin name. A carton may show a project code. Store each phrase with its source. Do not select one phrase as the final identity because it looks more precise. The supplied documents may be compatible, incompatible, or incomplete. The source packet should show which.
| Item-record field | Source-based entry | Do not add |
|---|---|---|
| Supplier product wording | Exact text from quote or invoice. | Classification or eligibility conclusion. |
| Common name | Literal source wording. | Assumed scientific identity. |
| Scientific-name text | Exact spelling, punctuation, and rank shown. | A correction by guesswork. |
| Variety or cultivar | Source text and document location. | A relationship not stated by the source. |
| Lot or batch reference | Literal printed or supplier-provided code. | A conclusion that lots are equivalent. |
| Stated origin | Country, place, or producer wording. | A verified origin conclusion. |
One source may list only a common name. Another may show a scientific name. Preserve both records and record the gap. A sourcing team should not manufacture a complete botanical description from partial source material.
Preserve permit sources exactly as received
A permit source can arrive as a PDF, image, email attachment, spreadsheet row, portal capture, or supplier statement. Save the original object, its file name, the date received, and the person or account that supplied it. If the source displays a permit number, copy it literally and retain the image or document where it appears.
APHIS states that eFile is the online system used to apply for and receive import and transit permits for plants, plant pests, soil, and agricultural products. 1 A buyer may note that a supplier provided a permit-related source. The buyer should not infer that it was issued through a particular system, that it covers a product, or that it authorizes a shipment unless the source itself states the relevant connection and a designated reviewer evaluates it.
| Permit-source field | Capture | Neutral status note |
|---|---|---|
| Source object | Original PDF, image, portal export, or message. | Preserve the original. |
| Stated number | Literal permit or reference string. | Do not normalize characters. |
| Named person or entity | Exact holder or contact wording. | Do not assign a legal role. |
| Date fields | Every displayed issue, expiry, or other date label. | Record label and value together. |
| Commodity wording | Literal product, plant, or taxa wording. | Do not interpret scope. |
| Conditions or attachments | Visible pages and named attachments. | Do not decide applicability. |
An internal status column can say permit source received, source unreadable, source absent, or relationship not stated. Those describe the evidence file, not the permission status of a product or shipment.
Separate APHIS and ACIR references from supplier files
APHIS identifies ACIR as a database containing import requirements for listed agricultural commodity groups and says import requirements vary by commodity and country of origin. 1 A buyer may preserve a link, access date, search term, and page capture as a public-reference source. That is not the same as using the page to decide a result for a supplier item.
Store an ACIR reference in a separate public-reference folder. Record the exact commodity wording and origin wording used in the search. Save the page URL and access date. If the query returns multiple categories or a result with conditions, retain the result list rather than selecting a single line as a product conclusion.
| Public-reference record | Factual information to store |
|---|---|
| Reference location | APHIS or ACIR page URL. |
| Search wording | Exact commodity and origin wording entered. |
| Access date | Date and time observed by the buyer. |
| Page capture | PDF, screenshot, or preserved web capture. |
| Result context | Visible headings, terms, and result list. |
| Supplier comparison | Literal matches or differences, if any. |
Public reference information may be updated. The saved capture does not freeze a database or decide what a buyer should do. It records what was observed at a stated point in time.
Record supplier and producer names as source facts
A product source may name a supplier, farm, nursery, exporter, packing location, brand owner, freight forwarder, or sales entity. Those names can differ across documents. Store each exactly as shown, with its address, email domain, contact line, and original source. Do not merge two names because the logos look related or the cities match.
The eCFR’s plants-for-planting rules define terms such as place of production, production site, lot, consignment, and phytosanitary certificate in their own regulatory setting. 3 Those terms can help a buyer label source fields. They should not be used to assign a source-defined role to an organization without the appropriate review.
| Entity source | Capture | Keep outside the conclusion |
|---|---|---|
| Supplier quotation | Seller name, address, quote number. | Producer, exporter, or importer role. |
| Factory or nursery email | Signature, location, stated site. | Relationship to a permit holder. |
| Permit-related source | Named entity and contact wording. | Ownership, authenticity, or authority. |
| Product label | Brand, supplier, and origin text. | Product identity or eligibility. |
| Invoice or packing list | Seller, consignee, and stated reference. | Entry, import, sale, or release role. |
Treat phytosanitary sources as their own record type
APHIS’s plant and seed guidance discusses a phytosanitary certificate as one of the source items buyers may need to confirm in its online purchasing context. 2 The rule text defines a phytosanitary certificate in the stated plants-for-planting context and includes requirements about description, place of origin, official issuance, inspection or testing statements, and other declarations. 3
The buyer-side method is simple. Keep a supplied phytosanitary certificate separate from any permit source, invoice, or label. Retain all pages, certificate number as shown, issuing organization wording, dates, product or taxon wording, place-of-origin text, shipment description, and any stated additional declarations. Do not decide whether it is complete, genuine, current, applicable, or sufficient.
| Phytosanitary-source field | Preserve | Open item if absent or unclear |
|---|---|---|
| Full document | Original file and every page. | Original unavailable. |
| Certificate reference | Literal number and source location. | No readable source number. |
| Issuing body wording | Exact organization name. | Issuer relationship not stated. |
| Product or taxon text | Exact terms from source. | No stated item link. |
| Place-of-origin text | Literal place or country wording. | Origin source missing. |
| Shipment description | Visible shipment, lot, or package wording. | Shipment connection unclear. |
A certificate-looking PDF should not be assigned a green status merely because it contains a stamp or signature. Preserve the image and write what the document says. Let the designated reviewer decide its significance.
Map labels, packing, and treatment sources
Product labels, nursery tags, bags, cartons, pallets, and package inserts can connect plant material to the supplier’s commercial files. Take full images and close-ups. A full image preserves surrounding context, while a close-up makes codes and product names readable. Store them under separate evidence IDs.
APHIS’s import page notes that regulated wood packaging material used in shipments entering or transiting the United States must meet treatment and certification requirements in its stated context. 1 Do not use a carton image to decide whether packaging material is regulated or whether any mark is sufficient. Record the materials, visible marks, stated packing description, and source date.
| Physical-source item | Capture | Do not conclude |
|---|---|---|
| Plant or seed label | Full tag, close-up, visible names and codes. | Identity or permit eligibility. |
| Inner package | Product wording, quantity, lot, and date text. | Shipment compliance. |
| Outer carton | Full marks, supplier wording, product terms. | Packaging status. |
| Pallet or crate | Full image and visible mark area. | Treatment or certification outcome. |
| Packing instruction | Original file, date, and stated route. | Applicability or adequacy. |
Connect the evidence packet to commercial sources
Purchase orders, quotations, commercial invoices, packing lists, freight documents, and order confirmations show the sourcing context. They can create a trail between buyer and supplier records, but only where a source states a common reference. A matching date alone does not prove that a permit-related file applies to a shipment.
Use a link table. Enter the evidence source ID, commercial source ID, exact matching string, and the document location. If nothing connects two sources, leave the link blank and list it as an open item.
| Commercial source | Capture | Link only when the source states |
|---|---|---|
| Purchase order | PO number, date, product wording. | Product, lot, or source reference. |
| Quotation | Quote number, product terms, version. | Exact stated item relationship. |
| Commercial invoice | Item line, quantity, date, seller. | Named product or shipment link. |
| Packing list | Carton marks, lot text, package count. | Source-coded package link. |
| Freight document | Reference, origin, destination, date fields. | Stated consignment or shipment reference. |
Ask for missing sources, not a permit conclusion
A vague request such as “send permit approval” encourages a supplier to send an unsupported statement. A narrow request names the missing record. Ask for the original source that identifies the product and botanical wording; the readable page containing the stated permit number; the document that links a permit source to the product in a specified quotation; the source that states a producer or place of origin; or the full certificate file referenced in an email.
A helpful request says, “Please provide the original source that states the relationship between the permit reference in your attachment and the product wording in quotation Q-77.” It does not ask the supplier to decide whether a permit is required, valid, or adequate. It asks for the document trail.
Use a contradiction queue
A mismatch is information, not a reason to rewrite a source. If a quotation says one scientific name while a tag says another, retain both. If the origin on a certificate differs from the invoice, preserve the records. If a permit source lists a different entity, write the exact names and source locations.
| Difference | Preserve | Neutral follow-up |
|---|---|---|
| Name mismatch | Every common and scientific name source. | Ask for source-based product relationship. |
| Origin mismatch | Each stated origin and source date. | Request the source that explains the difference. |
| Entity mismatch | Names, addresses, and original files. | Request a stated relationship record. |
| Lot mismatch | Literal lot, carton, and shipment strings. | Ask which source connects to the quote. |
| Date mismatch | Each date and date label. | Preserve without inferring sequence. |
The queue is a list of unresolved source relationships. It is not a scorecard and does not decide a supplier’s status or a shipment’s outcome.
Build China supplier plant import permit evidence into a handoff sheet
A handoff sheet gives the next reviewer a direct route to the original evidence. Include the product and scientific-name sources, supplier and producer sources, permit-related files, APHIS or ACIR public-reference captures, phytosanitary documents, package images, commercial records, and unresolved differences. Link every summary line to an original file.
| Handoff section | Include | Leave to the assigned reviewer |
|---|---|---|
| Item record | Literal product, taxon, lot, and origin wording. | Botanical or commodity determination. |
| Permit record | Original file, reference, entities, and dates. | Permit need, authenticity, status, or scope. |
| Public reference | APHIS or ACIR URL, search terms, and capture. | Requirement or eligibility decision. |
| Phytosanitary source | Full document and stated shipment details. | Document assessment or entry conclusion. |
| Commercial record | PO, quote, invoice, packing, and freight links. | Import, sale, or release decision. |
| Open items | Gaps and contradictions. | Legal, technical, and risk resolution. |
Common record-control errors
One error is treating a supplier-supplied permit number as proof that the number belongs to the purchased product. Preserve the number and source, then identify the missing product link.
Another error is replacing a supplier’s scientific-name text with a guess based on a common name. Record each source literally. A designated reviewer can assess identity where needed.
A third error is saving a public database capture without the search terms or access date. Preserve the path taken, not only a clipped result.
A fourth error is treating a complete-looking evidence folder as an entry decision. The folder may be well organized and still contain gaps or conflicting material. Source completeness is not a permit, phytosanitary, import, sale, or release result.
Frequently asked questions
Does a permit copy from a China supplier prove that the product may be imported?
No. A permit copy is a source object. It may contain a number, entity name, product wording, date, and stated conditions. A buyer should preserve those facts without deciding whether the source is authentic, current, applicable, sufficient, or related to a particular shipment.
Why should a buyer record both common and scientific names?
APHIS says import requirements vary by commodity and country of origin, and its public sources use commodity and plants-for-planting terminology. 1 Keeping both names as supplied preserves the evidence trail without having the sourcing team determine botanical identity or commodity status.
Is an ACIR page capture enough to decide the supplier’s requirements?
No. An ACIR capture records a public reference, search wording, and observation date. It does not decide requirements for a specific product or country, permit need, phytosanitary status, eligibility, or entry outcome. 1
What should a buyer do if product and certificate origins differ?
Save both original sources, record the literal origin wording and dates, and request a document that states the relationship. Do not change one file to make the record look consistent.
Preserve the source trail before assigning meaning
Well-organized evidence begins with original supplier files and exact public-reference captures. Preserve product and scientific-name wording, source-stated origins, permit references, supplier and producer names, phytosanitary files, packaging records, and commercial links. Keep the missing connections visible.
For China supplier plant import permit evidence, use one factual record per item and lot, record the source behind every permit-related statement, and do not resolve contradictions by assumption. Supplier Ally can help buyers organize supplier communications, sourcing documents, and evidence packets so the appropriate reviewer starts with a clear and traceable file.
EN 
ES 