agentleFS
actinon-comactinon-com/brass-monkey/skills/odoo-purchasing/SKILL.md

odoo-purchasing

Skill2 starsChanged 3 months agoMITView on GitHub

MANDATORY for RFQs and Purchase Orders (purchase.order). Expertise in Odoo's procurement engine and vendor pricing.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Data Pulling: When adding a product to a PO line, Odoo automatically retrieves the price, discount, and lead time from the best-matching …

    line 17
  2. Very specific:

    Mandate: Always verify if a supplierinfo record exists before manually overriding prices.

    line 18
  3. Distinctive:

    Received Quantities: ONLY bill for what has been physically received in the warehouse.

    line 23
  4. Very specific:

    Mandate: Use the qty_received field to verify arrivals before suggesting the creation of an account.move (Vendor Bill).

    line 24
  5. Very specific:

    Workflow: If the customer's address is used as the dest_address_id, the vendor ships directly to the customer.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Odoo Purchasing & Procurement

This skill provides the agent with high-level functional expertise in Odoo's Purchasing engine, covering Requests for Quotation (RFQs), Purchase Orders (POs), and Vendor Price management.

Core Mandates

1. The Procurement Lifecycle

  • States: draft (RFQ) -> sent (RFQ Sent) -> purchase (Confirmed PO) -> done (Locked) -> cancel.
  • Confirmation Trigger: Confirming a PO (button_confirm) is a critical event that automatically triggers incoming Receipts (stock.picking) in the Inventory module.

2. Vendor Pricing & Lead Times

  • Pricelists: Supplier pricing is managed via Vendor Pricelists (product.supplierinfo).
  • Data Pulling: When adding a product to a PO line, Odoo automatically retrieves the price, discount, and lead time from the best-matching supplierinfo record for that Vendor.
  • Mandate: Always verify if a supplierinfo record exists before manually overriding prices.

3. Billing Control (3-Way Matching)

Understand when a vendor bill should be recorded:

  • Ordered Quantities: Bill the vendor for the full amount as soon as the PO is confirmed.
  • Received Quantities: ONLY bill for what has been physically received in the warehouse.
  • Mandate: Use the qty_received field to verify arrivals before suggesting the creation of an account.move (Vendor Bill).

4. Advanced Fulfillment (Dropshipping)

  • Workflow: If the customer's address is used as the dest_address_id, the vendor ships directly to the customer. The agent must understand that no internal stock move occurs, but the qty_received must still be validated to trigger billing.

Available Resources

  • purchasing-logic.md: Deep-dive into Billing Control, Supplierinfo evaluation, and Dropshipping.
  • purchasing-fields.json: Dense technical map of fields for Order, Line, and Supplierinfo models.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.