Packaging Specification Sample Clauses

A Packaging Specification clause defines the standards and requirements for how goods must be packaged before delivery. It typically outlines the materials, labeling, and methods to be used, ensuring that products are protected during transit and meet regulatory or contractual obligations. By setting clear packaging expectations, this clause helps prevent damage, ensures compliance, and reduces disputes between parties regarding the condition of delivered goods.
Packaging Specification. Packaging to be agreed by ▇▇▇▇▇ and Seller at the time of entering into this contract and in all cases to be fit for export. Faulty and dirty packing is not permitted.
Packaging Specification. 2.4.1 Packaging must be able to withstand normal industry shipping (air, ship, rail and truck) requirements for vibration, shock, temperature and humidity 2.4.2 All Arm packages must have exterior markings in English which show Adept logo, part number and serial number.
Packaging Specification. Each delivered product shall be clearly marked with the applicable HP product number plus HP order number in both human-readable and barcode form (Standard 3/9 with barcode identifier). A single separately packaged product shall be delivered for each HP product number; i.e., multiple HP product numbers shall not be supplied in a single package. The delivered products shall be marked such that they can be identified without opening or removing protective packaging.
Packaging Specification. Any changes to the current specification set forth in this Agreement can only be made with the consent and agreement of both parties.
Packaging Specification. Labeling and packaging of Drug Substance will comply with the Batch Record, SOPs and as provided in Section 5.5 of the Agreement.
Packaging Specification the unit package weight is 1.5 metric ton per sack, with the sack to be provided by the Buyer and to be packaged in accordance the Buyer’s requirements. If the positive or negative allowance of the unit package weight exceeds 1% (exclusive of 1%), such unit package shall be deemed disqualified and the Buyer shall have the right to refuse to accept such package. Should any problem occur with the sack, the Seller shall contact the Buyer in time, otherwise any liability arising out of the delay in delivery shall be borne by the Seller.
Packaging Specification. 2.3.1. Labeling and packaging of Starting Materials and Product will comply with the batch records, SOPs and written instructions, as recommended by Ash S▇▇▇▇▇▇ and agreed to by “Company”, as appropriate.

Related to Packaging Specification

  • 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 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.

  • Product Specifications (a) Supplier shall manufacture all Products according to the Specifications in effect as of the date of this Agreement, with such changes or additions to the Specifications of the Products related thereto as shall be requested by Buyer in accordance with this Section or as otherwise agreed in writing by the Parties. All other Products shall be manufactured with such Specifications as the Parties shall agree in writing. (b) Buyer may request changed or additional Specifications for any Product by delivering written notice thereof to Supplier not less than one hundred twenty (120) days in advance of the first Firm Order for such Product to be supplied with such changed or additional Specifications. Notwithstanding the foregoing, if additional advance time would reasonably be required in order to implement the manufacturing processes for production of a Product with any changed or additional Specifications, and to commence manufacture and delivery thereof, Supplier shall so notify Buyer, and Supplier shall not be required to commence delivery of such Product until the passage of such additional time. (c) Supplier shall be required to accommodate any change of, or additions to, the Specifications for any Product, if and only if (i) in Supplier’s good faith judgment, such changed or additional Specifications would not require Supplier to violate good manufacturing practice, (ii) the representation and warranty of Buyer deemed made pursuant to Subsection (e) below is true and correct, and (iii) Buyer agrees to reimburse Supplier for the incremental costs and expenses incurred by Supplier in accommodating the changed or additional Specifications, including the costs of acquiring any new machinery and tooling. For the avoidance of doubt, such costs and expenses shall be payable by Buyer separately from the cost of Products at such time or times as Supplier shall request. (d) Supplier shall notify Buyer in writing within thirty (30) days of its receipt of any request for changed or additional Specifications (i) whether Supplier will honor such changed or additional Specifications, (ii) if Supplier declines to honor such changed or additional Specifications, the basis therefor and (iii) if applicable, the estimated costs and expenses that Buyer will be required to reimburse Supplier in respect of the requested changes or additions, as provided in Subsection (c) above. Buyer shall notify Supplier in writing within fifteen (15) days after receiving notice of any required reimbursement whether Buyer agrees to assume such reimbursement obligation. (e) By its request for any changed or additional Specifications for any Product, Buyer shall be deemed to represent and warrant to Supplier that the manufacture and sale of the Product incorporating Buyer’s changed or additional Specifications, as a result of such incorporation, will not and could not reasonably be expected to (i) violate or conflict with any contract, agreement, arrangement or understanding to which Buyer and/or any of its Affiliates is a party, including this Agreement and any other contract, agreement, arrangement or understanding with Supplier and/or its Affiliates, (ii) infringe on any trademark, service ▇▇▇▇, copyright, patent, trade secret or other intellectual property rights of any Person, or (iii) violate any Applicable Law. Buyer shall indemnify and hold Supplier and its Affiliates harmless (including with respect to reasonable attorneys’ fees and disbursements) from any breach of this representation and warranty.

  • 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.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-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.