odoo-inventory-optimizer
Expert guide for Odoo Inventory: stock valuation (FIFO/AVCO), reordering rules, putaway strategies, routes, and multi-warehouse configuration.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- odoo-inventory-optimizer
- risk
- safe
- source
- self
- description
- Expert guide for Odoo Inventory: stock valuation (FIFO/AVCO), reordering rules, putaway strategies, routes, and multi-warehouse configuration.
03 SKILL.md 正文
Odoo Inventory Optimizer
Overview
This skill helps you configure and optimize Odoo Inventory for accuracy, efficiency, and traceability. It covers stock valuation methods, reordering rules, putaway strategies, warehouse routes, and multi-step flows (receive → quality → store).
When to Use This Skill
- Choosing and configuring FIFO vs AVCO stock valuation.
- Setting up minimum stock reordering rules to avoid stockouts.
- Designing a multi-step warehouse flow (2-step receipt, 3-step delivery).
- Configuring putaway rules to direct products to specific storage locations.
- Troubleshooting negative stock, incorrect valuation, or missing moves.
How It Works
- Activate: Mention
@odoo-inventory-optimizerand describe your warehouse scenario. - Configure: Receive step-by-step configuration instructions with exact Odoo menu paths.
- Optimize: Get recommendations for reordering rules and stock accuracy improvements.
Examples
Example 1: Enable FIFO Stock Valuation
Menu: Inventory → Configuration → Settings
Enable: Storage Locations
Enable: Multi-Step Routes
Costing Method: (set per Product Category, not globally)
Menu: Inventory → Configuration → Product Categories → Edit
Category: All / Physical Goods
Costing Method: First In First Out (FIFO)
Inventory Valuation: Automated
Account Stock Valuation: [Balance Sheet inventory account]
Account Stock Input: [Stock Received Not Billed]
Account Stock Output: [Stock Delivered Not Invoiced]
Example 2: Set Up a Min/Max Reordering Rule
Menu: Inventory → Operations → Replenishment → New
Product: Office Paper A4
Location: WH/Stock
Min Qty: 100 (trigger reorder when stock falls below this)
Max Qty: 500 (purchase up to this quantity)
Multiple Qty: 50 (always order in multiples of 50)
Route: Buy (triggers a Purchase Order automatically)
or Manufacture (triggers a Manufacturing Order)
Example 3: Configure Putaway Rules
Menu: Inventory → Configuration → Putaway Rules → New
Purpose: Direct products from WH/Input to specific bin locations
Rules:
Product Category: Refrigerated Goods
→ Location: WH/Stock/Cold Storage
Product: Laptop Model X
→ Location: WH/Stock/Electronics/Shelf A
(leave Product blank to apply the rule to an entire category)
Result: When a receipt is validated, Odoo automatically suggests
the correct destination location per product or category.
Example 4: Configure 3-Step Warehouse Delivery
Menu: Inventory → Configuration → Warehouses → [Your Warehouse]
Outgoing Shipments: Pick + Pack + Ship (3 steps)
Operations created automatically:
PICK — Move goods from storage shelf to packing area
PACK — Package items and print shipping label
OUT — Hand off to carrier / mark as shipped
Best Practices
- ✅ Do: Use Lots/Serial Numbers for high-value or regulated items (medical devices, electronics).
- ✅ Do: Run a physical inventory adjustment at least quarterly (Inventory → Operations → Physical Inventory) to correct drift.
- ✅ Do: Set reordering rules on fast-moving items so purchase orders are generated automatically.
- ✅ Do: Enable Putaway Rules on warehouses with multiple storage zones — it eliminates manual location selection errors.
- ❌ Don't: Switch stock valuation method (FIFO ↔ AVCO) after recording transactions — it produces incorrect historical cost data.
- ❌ Don't: Use "Update Quantity" to fix stock errors — always use Inventory Adjustments to maintain a proper audit trail.
- ❌ Don't: Mix product categories with different costing methods in the same storage location without understanding the valuation impact.
Limitations
- Serial number tracking at the individual unit level (SN per line) adds significant UI overhead; test performance with large volumes before enabling.
- Does not cover landed costs (import duties, freight allocation to product cost) — that requires the
stock_landed_costsmodule. - Cross-warehouse stock transfers have routing complexities (transit locations, intercompany invoicing) not fully covered here.
- Automated inventory valuation requires the Accounting module; Community Edition installations without it cannot post stock journal entries.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.