Duration: 24:09
🧾 Analytical Summary
A tour of the revamped Purchase app in Odoo 19 focused on speed, clarity, and fewer mistakes in upstream supply workflows. The release blends a redesigned dashboard, smarter replenishment, vendor acknowledgment tracking, EDI-powered data entry, and packaging/price refinements to reduce back-and-forth and hidden blockers.
🚦 New dashboard and team flow
- Fresh dashboard with color cues and actionable counters (team vs. “assigned to me”).
- KPIs: vendor on‑time delivery, personal performance, and average time‑to‑order.
- Quick filters for late RFQs and non‑acknowledged POs to prioritize calls/emails.
✅ Vendor acknowledgment tracking
- Email POs include an acknowledge button; “Not acknowledged” shows confirmed POs lacking supplier confirmation.
- Inline updates to expected dates without blocking downstream work.
🧠 “Suggest” to complete orders and plan buys
- New Suggest panel in the catalog proposes quantities to reach vendor minimums or to cover X days.
- Demand basis is configurable: last 7/30 days or same period prior year for seasonality; growth uplift supported.
- Works both for topping up (avoid delivery fees) and periodic buying (weekly/monthly order runs).
💼 Price, packaging, and UoM improvements
- Price comparison smart button aggregates past prices for quick negotiation.
- Manual unit prices are no longer auto‑recomputed when you change quantity (prevents accidental overrides).
- Packaging and UoM are unified: define multiple packagings per product; per‑vendor prices by packaging; automatic conversions on lines.
🔗 Odoo EDI: drag‑and‑drop vendor quotes
- Drop a vendor quotation (PDF with embedded UBL 3.0 or XML) to auto‑fill PO lines; unmatched items are highlighted for quick create/match.
- If UBL is present, no OCR credits are used; without UBL, OCR processes the file (uses credits).
📦 Replenishment and grouped RFQs
- Replenishment view shows which vendor price will be used; choose cheapest by reordering vendor lines or selecting explicitly (lead times still matter).
- Per‑vendor “Group RFQs” (e.g., weekly on Monday) consolidates MTO and replenishment requests into fewer, larger POs to optimize freight and admin.
🛠️ Admin details and limitations
- Default grouping can be pre‑set for new vendors via default values; bulk update existing vendors with export/import.
- Vendor portal acknowledgement/date entry isn’t available yet (planned future improvements).
- Quantity precision can be increased globally; alternatively, model finer units, noting accounting/rounding impact.
🧠 Viewpoint: Odoo Perspective
⚠️ Disclaimer: AI-generated creative perspective inspired by Odoo’s vision.
Purchasing is where delays cascade. We focused on removing invisible friction: vendor acks in one glance, suggestive replenishment that respects seasonality and growth, and UBL‑powered data entry that eliminates retyping. The result: fewer calls, fewer surprises, and faster, cleaner buys.
By unifying packaging/UoM and preserving intentional prices, we help buyers negotiate with context and avoid “system fights.” Grouped RFQs and clear vendor selection keep costs predictable without sacrificing SLA awareness.
🏢 Viewpoint: Competitors (Procure-to-Pay)
⚠️ Disclaimer: AI-generated fictional commentary. Not an official corporate statement.
The suggest engine and UBL ingestion are practical wins for SMB/mid‑market teams. Enterprises will watch for deeper vendor‑portal collaboration (ack dates, changes), configurable approval workflows, and granular audit of price/packaging changes across multi‑plant setups.
Consolidation policies at vendor level are useful; global policies, lead‑time simulation, and landed‑cost optimization would push this further for complex supply networks.
Disclaimer: This article contains AI-generated summaries and fictionalized commentaries for illustrative purposes. Viewpoints labeled as "Odoo Perspective" or "Competitors" are simulated and do not represent any real statements or positions. All product names and trademarks belong to their respective owners.