Supply, OEM, and ODM contracts across borders

Buy goods or manufacturing capacity in the destination. OEM is your brand on their plant; ODM is their design under your brand.

A first OEM or supply line is a single matter. A factory program with quality and call-off POs is a module.

Documents in this cluster

Purchase Agreement

A discrete purchase of goods. Incoterms the client already chose are facts in the pack.

A purchase agreement is named before hours start — a discrete purchase of goods; Incoterms already chosen are facts. Parties, language, and governing-law preference sit as facts for local licensed review.

The Matter Pack for a purchase agreement records who signs, which language is the working draft, and which missing names would change the price. Orbid does not fill those gaps with legal advice.

Startups usually buy this purchase agreement as a first single matter. Mid-market teams that issue the same form many times in a quarter put it inside an annual counsel module.

Default for a purchase agreement is one scoped price. A retainer only makes sense when review volume is recurring. If the project changes, a change order states the new price.

Supply Agreement

Ongoing supply, not a one-off PO. Forecasts and price-change triggers belong in the pack.

Cross-border, a supply agreement is paper, not a vibe: ongoing supply, not a one-off PO, with forecast and price-change triggers. A destination professional prices review of that named instrument.

For this supply agreement the pack lists counterparties, term, territory if any, and the files you already have. Unknowns stay gaps, not extra hours.

A startup sees one supply agreement. A mid-market desk sees a template: same skeleton, many counterparties, still reviewed locally per pack.

One supply agreement is a single matter unless you already run a cadence of the same form. Extra unnamed paper is not included.

Vendor Agreement

Vendor onboarding paper: compliance, insurance, and who can receive POs.

If the file crosses a border, write the vendor agreement into the pack first — onboarding paper: compliance, insurance, who can receive POs. Unknowns stay gaps.

A vendor agreement pack asks which entity on the origin side contracts, which destination name appears, and whether a bilingual draft already exists.

If this is the first vendor agreement on the corridor, default is a single matter. If it is the twelfth this quarter, that is a module conversation — Orbid coordinates, and licensed local counsel judges.

Do not stretch one vendor agreement price over a second instrument. That is how surprise bills start. Split, or write a change order.

Framework Supply Agreement

Framework that later POs call off. Mid-market default for factories.

Hours do not start on an unnamed framework supply agreement — a framework that later POs call off — mid-market factory default. Local licensed review sees who signs and which language is the working draft.

What sits in the pack around a framework supply agreement: asserted facts, planned entities, and the triggers that would reopen price. Orbid does not choose the clause.

Founders often over-buy a stack around a framework supply agreement. Mid-market operators under-specify the program. The pack names the actual count.

A retainer that mentions a framework supply agreement still uses a Matter Pack per issuance. Scoped packs, not unlimited advice.

Manufacturing Agreement

Make goods to the buyer’s specification. Site, tooling, and IP leakage sit next to the NDA.

On this corridor the manufacturing agreement is the instrument to price — make goods to the buyer’s specification; site and tooling sit next to the NDA. Orbid records that; it does not advise which form you should have chosen.

The manufacturing agreement line in the pack is a scope, not a draft. Local licensed professionals review what you approved; they are not Orbid employees giving advice in our name.

Startups: one manufacturing agreement, one price, approve before hours. Mid-market: the form lives in a retainer quota, each issuance still a pack.

If this manufacturing agreement grows a neighbour — a DPA, a quality paper, a SHA — name the set or pay a second price.

Contract Manufacturing Agreement

Contract manufacturing with a third-party plant. Quality agreement usually travels with it.

Name the contract manufacturing agreement while talks are still cheap — a third-party plant, usually travelling with a quality agreement. A listed destination still accepts the scope; a standing lawyer there is not promised.

Record the contract manufacturing agreement with the commercial neighbours it actually has — not a dump of every PDF in the folder. Extra unnamed files are a change order.

The first contract manufacturing agreement on a corridor is usually a startup single matter. A net of them is mid-market, and the default flips to an annual module.

Single-matter fits a bounded contract manufacturing agreement. Weekly flow of the same form belongs on an annual counsel module.

OEM Agreement

OEM: your brand, their plant. Non-use NDA and quality paper are the usual neighbours.

A OEM agreement belongs in the pack — your brand, their plant; non-use NDA and quality paper sit beside it. Thailand is live review; other corridors stay listed.

Gaps on a OEM agreement — missing signatory, missing language, missing term — stay written. They do not convert into silent hourly work.

Do not put a startup OEM agreement on a retainer because it feels safer. Retainer is for recurring review volume, not for nerves.

You approve the OEM agreement pack before hours. You approve again if the facts move. The price does not jump in silence.

ODM Agreement

ODM: their design, your brand. Tooling ownership and residual IP are pack facts.

Do not paste an origin ODM agreement across the border unmarked — their design, your brand; tooling ownership is a pack fact. The pack asks which language controls and which entity signs.

The pack treats the ODM agreement as one priced module unless you name a defined set. A pile of related attachments is not a defined set.

Mid-market counsel modules still scope each ODM agreement. Unlimited chat about the form is not the product.

Listed-corridor ODM agreement work is still scoped as a single matter or a module. Scope is accepted; a named lawyer standing by is not promised.

Quality Agreement

Quality agreement: specs, audits, nonconforming lots. Common in medical-device and electronics supply, still a contract, not a licenses hub.

The first priced Matter Pack is often this quality agreement, given that specs, audits, nonconforming lots — still a contract, not a licenses hub. Local licensed professionals review; Orbid does not draft as counsel.

Who already signed a previous quality agreement, and who still has to, is a fact. Orbid records it. Enforceability is not an Orbid opinion.

If the startup does not yet have a destination entity, the quality agreement may still be scoped — as paper, not as incorporation.

A quality agreement change order is the exception path: new scope, new price, your yes. It is not a vibe adjustment on the old invoice.

Purchase Order Terms

The reverse of an order form: terms that sit on every PO. Conflicts with a framework must be listed as gaps.

Before anyone bills, the purchase-order terms is a line in the pack — terms on every PO; conflicts with a framework stay listed as gaps. Price-change triggers stay visible.

Working draft versus filing draft for a purchase-order terms are two fields. Mixing them in one unmarked file is a gap.

A mid-market purchase-order terms program lists which affiliates may sign. A startup pack usually names one origin company.

Retainer quota can include purchase-order terms review. It cannot include “whatever else appears.” That is a new pack.

Logistics / Warehousing Agreement

Warehousing and freight. Bonded vs domestic storage is a fact the pack asks.

A logistics agreement on a cross-border file is scoped, not improvised — warehousing and freight; bonded versus domestic storage is a asked fact. Gaps do not become silent hours.

Price-change triggers for a logistics agreement are written before hours: new party, new territory, new language. If those appear later, a change order states the new price.

Buy the logistics agreement you have, not the library you fear. Startups default small. Mid-market defaults to systems.

Price the logistics agreement you named. Related PDFs without names are gaps, not free add-ons.

Import / Export Services Agreement

Broker or forwarder services, not the import licence itself. That licence question is a gap, not this cluster’s hub.

Put the import/export services agreement on the list with the counterparties you already have — broker or forwarder services, not the import licence itself. Review is priced after you approve.

The import/export services agreement is in the pack so a local licensed professional can see the job. Orbid organizes. It does not replace that review.

The same import/export services agreement is a one-off for a seed company and a workstream for a regional HQ. The pack says which.

Orbid does not discount a import/export services agreement by drafting it as counsel. Local licensed review prices the work that is in.

Questions

OEM versus ODM?

OEM is your brand, their plant. ODM is their design, your brand. Tooling ownership and residual IP are facts.

Do Incoterms belong in the pack?

If you already chose them, they are facts on a purchase or supply line. Orbid does not pick CIF versus FOB.

Is a quality agreement a licenses hub?

No. Specs, audits, and nonconforming lots are contract facts.

Bring us a deal.

A contract, a distributor, a supplier, a first hire or a new market.

Orbid will tell you what it takes and what it costs.

Supply, OEM, and ODM Contracts Across Borders | Orbid