Warehousing Agreement

A warehousing agreement governs storage and care of identified goods, receipts, inventory accuracy, access, liens, insurance, loss claims, and removal.

A useful document turns the parties' actual arrangement into measurable duties, approvals, timing, remedies, and a reliable execution record. Its terms should be reconciled to the transaction rather than copied from an unrelated form.

• An importer stores pallets before distribution
• A manufacturer holds seasonal inventory offsite
• A business uses a temperature-controlled facility

The document name alone does not determine the right structure. Consider a different instrument or qualified legal review when any of these conditions applies:

• Not for a lease giving the customer exclusive possession of space
• Not for pick-pack shipping services without separate fulfillment terms

Record exact facts before clauses are written. Names, authority, dates, amounts, defined terms, dependencies, and incorporated materials should be verifiable and consistent.

• Goods, value, hazards, and storage conditions
• Facility and permitted relocation sites
• Receipt and inventory system
• Storage, handling, accessorial, and release fees

These decisions shape the allocation of responsibility and should not be left for boilerplate to decide:

• Whether warehouse receipts are negotiable
• Who bears shrinkage and unexplained loss
• What lien rights apply to stored goods
• When goods may be moved or disposed of

• Receipt, custody, and standard of care
• Storage conditions and inventory controls
• Warehouse lien, charges, and payment
• Insurance, loss claims, and limits
• Release, removal, and termination

Every provision should use the same parties, dates, standards, defined terms, and document hierarchy. A clause that is reasonable by itself can still create a conflict when it is not reconciled with payment, default, termination, or another exhibit.

1. 01Describe the intended result and the relationship in plain language.
2. 02Confirm parties, authority, governing jurisdiction, dates, money, property, services, and approvals.
3. 03Resolve the key decisions and identify every schedule, exhibit, disclosure, consent, or filing.
4. 04Draft the provisions as one consistent system, then review the complete execution set before signature.

Warehouse liens and statutory sale procedures may operate beyond contract language. Inventory systems must reconcile receipts, moves, and releases; a certificate of insurance does not itself prove coverage.

The main agreement may establish the framework while schedules, exhibits, disclosures, consents, or operational records supply transaction-specific details.

• Warehouse receipt and SKU inventory
• Temperature or security specification
• Insurance certificate and stock count

Each incorporated document should be identified precisely, use the same names and effective date, and follow a stated order of precedence if terms conflict.

Perform intake count and condition record, monitor exceptions, audit stock, and obtain a signed release reconciliation at exit.

• Confirm legal names, roles, capacity, addresses, and signing authority
• Reconcile dates, amounts, definitions, cross-references, schedules, and exhibits
• Confirm that duties, deadlines, approvals, acceptance standards, and payment triggers are measurable
• Check that default, termination, remedies, and surviving obligations work together
• Complete jurisdiction-specific forms, notices, witnesses, notarization, filings, or professional review when applicable
• Deliver and preserve the complete signed package with its incorporated documents

These sources provide federal, state-resource, regulatory, or institutional context. They do not replace checking the law and required forms applicable to the parties, transaction, and governing jurisdiction.

1. Source 1

   D.C. Code, Article 7 — Documents of title

   D.C. Council. Enacted warehouse receipt, bailee duty, and warehouse lien rules.

2. Source 2

   D.C. Code § 28:9-203 — Attachment of security interests

   D.C. Council. Enacted prerequisites for enforceable security interests.

3. Source 3

   D.C. Code § 28:9-322 — Priorities

   D.C. Council. Enacted priority rules among competing secured interests.