Product Pricing and Distributor Ordering Sample Clauses

Product Pricing and Distributor Ordering. 6.1.1. The Company shall invoice the Distributor for all product orders.
AutoNDA by SimpleDocs

Related to Product Pricing and Distributor Ordering

  • 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 and Marking All material and equipment to be furnished by the Contractor shall be packed, crated or otherwise suitably protected to withstand shipment undamaged to the destination. Each package, crate or part shall be marked plainly with the name of the consignee, shipping destination, the Owner's order number, and such other markings as are required. Complete packing lists, one copy with each package and two (2) copies by mail to the Owner at time of shipment, shall be supplied showing contents and identity of each package.

  • PACKING AND SHIPMENT (a) Unless otherwise specified, all Work is to be packed in accordance with good commercial practice. (b) A complete packing list shall be enclosed with all shipments. SELLER shall mark containers or packages with necessary lifting, loading, and shipping information, including the LOCKHEED XXXXXX Contract number, item number, dates of shipment, and the names and addresses of consignor and consignee. Bills of lading shall include this Contract number. (c) Unless otherwise specified, delivery shall be FOB Place of Shipment.

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

  • Product Pricing Contract Prices are the sum of annual Base Prices and Quarterly fuel surcharges, as detailed below. Pricing for shipments each month should be based on the Contract Prices for the most recent quarter.

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

  • Manufacturing and Marketing Rights The Company has not granted rights to manufacture, produce, assemble, license, market, or sell its products to any other person and is not bound by any agreement that affects the Company's exclusive right to develop, manufacture, assemble, distribute, market, or sell its products.

  • Procurement of Goods and Services (a) If the HSP is subject to the procurement provisions of the BPSAA, the HSP will abide by all directives and guidelines issued by the Management Board of Cabinet that are applicable to the HSP pursuant to the BPSAA. (b) If the HSP is not subject to the procurement provisions of the BPSAA, the HSP will have a procurement policy in place that requires the acquisition of supplies, equipment or services valued at over $25,000 through a competitive process that ensures the best value for funds expended. If the HSP acquires supplies, equipment or services with the Funding it will do so through a process that is consistent with this policy.

  • Limited Product Warranty Repair or Replacement within 12 years

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

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!