Packaging and Labeling Specifications Sample Clauses

Packaging and Labeling Specifications. The packaging and labeling specifications are documents that describe the labeling artwork, container/closure, Product packaging for shipment, shipper specifications and drawings used in the packaging of the Product. These packaging and labeling specifications are Developed and approved by BVL and Customer. This information will be incorporated into the MPR, associated Product Specific SOPs, and raw material specifications, as appropriate.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Packaging and Labeling Specifications. Packaging and labeling specifications for Drug Substance will be incorporated into the MPR, associated standard operating procedures and/or Materials Specifications. These packaging and labeling specifications, the MPR, associated standard operating procedures, and Materials Specifications will be developed and approved by CBSB and Tercica.
Sample 1Sample 2
Packaging and Labeling Specifications. Tibotec shall label and package the Territory Combination Product in accordance with GMP and Applicable Law for the country or region in which such Territory Combination Product will be sold, released or distributed. If any Territory Combination Product intended for release, sale or distribution by Tibotec fails to comply with the labeling and packaging requirements in accordance with the Territory Combination Product Specifications or Applicable Law for the country or region in which such Territory Combination Product will be sold, released or distributed, then Tibotec shall not release, sell or distribute such Territory Combination Product. 14.5
Sample 1Sample 2
Packaging and Labeling Specifications. Xxxxxxx shall label and package the Territory Combination Product in accordance with GMP and Applicable Law for the country or region in which such Territory Combination Product will be sold, released or distributed. If any Territory Combination Product intended for release, sale or distribution by Xxxxxxx fails to comply with the labeling and packaging requirements in accordance with the Territory Combination Product Specifications or Applicable Law for the country or region in which such Territory Combination Product will be sold, released or distributed, then Xxxxxxx shall not release, sell or distribute such Territory Combination Product.
Sample 1

Related to Packaging and Labeling Specifications

  • Packaging and Labeling Seller shall properly xxxx, xxxx, and ship Goods and provide Buyer with shipment documentation showing the Order number, Seller’s identification number for the subject Goods, the quantity of goods in shipment and the number of cartons or containers in the shipment.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Product Specifications The Company agrees that all Products sold to Xxxx hereunder shall conform to the respective specifications set forth on Schedule A or to such other specifications as are from time to time agreed upon by the Parties.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.

  • Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.

  • Labelling The distributor, on behalf of the selected vendor agrees that all supplies of articles should invariably contain the following information on its label and the carton. One information should not be overlapped by any other information needed to be furnished. The label should contain :

  • Class Specifications The Human Resources Division shall determine:

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

Time is Money Join Law Insider Premium to draft better contracts faster.