Product Forms Clause Samples

The 'Product Forms' clause defines the specific types, versions, or configurations of a product that are covered under an agreement. It typically outlines which models, packaging, or variations of a product are included, and may specify any limitations or exclusions regarding product features or formats. By clearly identifying the applicable product forms, this clause ensures both parties understand exactly what is being supplied or purchased, thereby reducing the risk of disputes over product scope or expectations.
Product Forms. The default delivery form of the Product shall be raw placer gold whose Assumed Fineness shall be documented by the Seller.
Product Forms. The Product is available in either (a) a 100 L labeled vial containing approximately 80 USP units of recombinant human hyaluronidase in the solution describe above (the “Vial Form”), or (b) a bottle containing approximately 80,000 USP units of the solution described above (the “Bulk Form”). The parties acknowledge and agree that the Vial Form shall not be available to Distributor under this Agreement for distribution in any country unless and until Halozyme has received the required marketing approval (if any) from the FDA or its foreign equivalent in such country. Distributor shall only re-sell the Vial Form.
Product Forms. The Product is available in either (a) a 100 L labeled vial containing approximately 80 USP units of recombinant human hyaluronidase in the solution describe above (the “Vial Form”), or (b) a bottle containing approximately 80,000 USP units of the solution without the addition of recombinant HSA (rHSA) (the “Bulk Form”). The parties acknowledge and agree that the Vial Form shall not be available to Distributor under this Agreement for distribution in any country unless and until Halozyme has received the required marketing approval (if any) from the FDA or its foreign equivalent in such country. Distributor shall only re-sell the Vial Fo rm.
Product Forms. (a) The Distributor acknowledges that any application for a Policy submitted by a Client or proposed Client may only be accepted or rejected by the Product Issuer. (b) The Distributor must on request from the Product Issuer use its best endeavours to obtain any additional Policy Holder information required by the Product Issuer, and otherwise do all things reasonably required to enable the Product Issuer to issue the Policy on request from the Product Issuer.

Related to Product Forms

  • Product Labeling The labeling of all Licensed Products sold or offered for sale under this Agreement shall expressly state that the Licensed Product is manufactured under a license from the Medicines Patent Pool.

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work. 4.12.2 Product Data are illustrations, standard schedules, performance charts, instructions, brochures, diagrams and other information furnished by the Contractor to illustrate a material, product or system for some portion of the Work. 4.12.3 Samples are physical examples which illustrate materials, equipment or workmanship and establish standards by which the Work will be judged. 4.12.4 The Contractor shall review, approve and submit, with reasonable promptness and in such sequence as to cause no delay in the Work or in the work of the State or any separate contractor, all Shop Drawings, Product Data and Samples required by the Contract Documents. 4.12.5 By approving and submitting Shop Drawings, Product Data and Samples, the Contractor represents that he / she has determined and verified all materials, field measurements, and field construction criteria related thereto, or will do so, and that he / she has checked and coordinated the information contained within such submittals with the requirements of the Work and of the Contract Documents. 4.12.6 The Contractor shall not be relieved of responsibility for any deviation from the requirements of the Contract Documents by the Architect's approval of Shop Drawings, Product Data or Samples under Subparagraph 2.2.7 of these General Conditions unless the Contractor has specifically informed the Architect and the State in writing of such deviation at the time of sub- mission and the Architect and the State has given written approval to the specific deviation. The Contractor shall not be relieved from responsibility for errors or omissions in the Shop Drawings, Product Data or Samples by the Architect's approval thereof. 4.12.7 The Contractor shall direct specific attention, in writing or on resubmitted Shop Drawings, Product Data or Samples, to revisions other than those requested by the Architect on previous submittals. 4.12.8 No portion of the Work requiring submission of a Shop Drawing, Product Data or Sample shall be commenced until the submittal has been approved by the Architect as provided in Subparagraph 2.2.7 of these General Conditions. All such portions of the Work shall be in accordance with approved submittals.

  • 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 Data Illustrations, standard schedules, performance charts, instructions, brochures, diagrams, and other information furnished by Developer to illustrate a material, product, or system for some portion of the Work.

  • API If the Software offers integration capabilities via an API, your use of the API may be subject to additional costs or Sage specific policies and terms and conditions (which shall prevail in relation to your use of the API). You may not access or use the API in any way that could cause damage to us or the Software, or in contravention of any applicable laws. We reserve the right in our sole discretion, to: (i) update any API from time to time; (ii) place limitations around your use of any API; and (iii) deny you access to any API in the event of misuse by you or to otherwise protect our legitimate interests.