跳至內容
Odoo 選單
  • 登入
  • 免費試用
  • 應用程式
    財政
    • 會計
    • 發票
    • 開支報銷
    • 試算表 (BI)
    • 文件管理
    • 電子簽名
    銷售
    • 客戶關係
    • 銷售
    • POS 銷售點管理 - 零售
    • POS 銷售點管理 - 餐廳
    • 訂閱
    • 租賃
    網站
    • 網站製作
    • 電子商務
    • 網誌
    • 討論區
    • 線上客服
    • 網上學習
    供應鏈
    • 庫存
    • 製造管理
    • 產品生命周期
    • 採購
    • 保養維護
    • 品質管理
    人力資源
    • 員工管理
    • 招聘
    • 休假
    • 工作表現評核
    • 內部推薦
    • 車隊管理
    市場推廣
    • 社交媒體推廣
    • 電郵推廣
    • 短訊營銷
    • 活動
    • 自動化推廣
    • 網上調查
    技術支援服務
    • 專案管理
    • 工時管理
    • 外勤服務管理
    • 技術支援
    • 工作規劃
    • 預約管理
    生產力
    • 聊天
    • AI 人工智能
    • 物聯網
    • VoIP
    • 知識庫
    • WhatsApp
    第三方應用程式 Odoo Studio Odoo 雲端平台
  • 行業
    零售
    • 書店
    • 服裝店
    • 家具店
    • 食品雜貨店
    • 五金店
    • 玩具店
    餐飲及款待
    • 酒吧及酒館
    • 餐廳
    • 快餐
    • 賓館
    • 飲品分銷商
    • 酒店
    房地產
    • 地產代理公司
    • 建築師事務所
    • 建造業
    • 物業管理
    • 園藝
    • 業主聯會
    顧問服務
    • 會計公司
    • Odoo 合作夥伴
    • 市場推廣公司
    • 律師事務所
    • 人才招募
    • 審計及認證
    製造管理
    • 紡織
    • 金屬
    • 家具
    • 食品
    • 啤酒廠
    • 企業禮品
    保健與健身
    • 運動俱樂部
    • 眼鏡店
    • 健身中心
    • 健康從業人員
    • 藥房
    • 髮型屋
    技術行業
    • 雜工
    • IT 硬體與支援
    • 太陽能系統
    • 鞋匠
    • 清潔服務
    • 暖通空調服務
    其他
    • 非牟利組織
    • 環境保護機構
    • 廣告板租賃
    • 攝影服務
    • 自行車租賃
    • 軟體經銷商
    瀏覽所有行業
  • 社群
    學習
    • 教學影片
    • 使用說明
    • 認證
    • 培訓
    • 網誌
    • Podcast
    增強教學效能
    • 教育計劃
    • Scale Up! 商業遊戲
    • 到訪 Odoo
    取得軟件
    • 下載
    • 版本對照表
    • 版本說明
    合作
    • GitHub
    • 討論區
    • 活動
    • 翻譯
    • 成為合作夥伴
    • 合作夥伴服務
    • 登記你的會計服務公司
    獲取服務相關資料
    • 尋找合作夥伴
    • 尋找會計服務
    • 預約專家一對一 Demo
    • 安裝及推行服務
    • 客戶案例
    • 支援
    • 軟件升級
    GitHub YouTube Twitter LinkedIn Instagram Facebook Spotify
    +1 (650) 691-3277
    預約示範
  • 定價
  • 技術支援
只限註冊用戶才可與社群互動。
所有帖文 人 獎章
標籤 (查看所有)
odoo accounting v14 pos v15
關於此討論區
只限註冊用戶才可與社群互動。
所有帖文 人 獎章
標籤 (查看所有)
odoo accounting v14 pos v15
關於此討論區
支援

Multi-Warehouse Replenishment Issue

訂閱

此帖文有活動時,接收通知

此問題已被標幟
inventory
2 回覆
2209 瀏覽次數
頭像
Alexis INCORVAIA

Odoo enterprise v 18.4 
Hello,
Let me set the scene:

I have two warehouses:

1. Warehouse SB

This is the main warehouse, which receives and ships goods (see screenshot of warehouse SB).


Entrepôt SB

2. Warehouse DC

This is a secondary warehouse used to store surplus stock.

It is sometimes selected as the delivery location for purchase orders, but it is never used to ship goods to final customers.

Please ignore the third warehouse 3EXT shown in the screenshot. It is not relevant to this scenario and would only add unnecessary complexity.

Entrepôt DC


Configured Routes

For Warehouse SB, I have configured a supply route from Warehouse DC:

  • Pull From 2DC/Stock → 2DC/Output

    (Method: Take from stock; if not available, trigger another rule)

  • Pull From 2DC/Output → Inter-warehouse Transit

    (Method: Trigger another rule)

  • Pull From Inter-warehouse Transit → 1SB/Stock

    (Method: Trigger another rule)


Problem Context

I have a product with:

  • 100 units in SB

  • 100 units in DC

We receive a sales order for 300 units.

What I want Odoo to do:

  • Take 100 from SB

  • Take 100 from DC and transfer them to SB

  • Then purchase 100 for SB to cover the remaining demand

What Odoo actually does:

  • It takes 100 from SB

  • It creates a need for 200 in DC, so it pulls 200 from DC and sends them to SB

  • Since DC only has 100, it creates a purchase of 100 for DC, to fill the artificial shortage created there

Question

Does anyone know how to achieve the intended scenario, where the remaining quantity is purchased for SB, not DC?

Thanks in advance!

1
頭像
捨棄
頭像
Deepak Dwivedi
最佳答案

To achieve the behaviour you want, you will need to adjust the Buy route configuration so that Odoo purchases stock directly for Warehouse SB, not for DC.

1. Update the Buy Route

Right now, the “Buy” rule of Warehouse DC is pointing to DC Receipt as its operation type.

Because of this, whenever DC faces a shortage, even an artificial one created by the pull rules, Odoo triggers a purchase for DC, not SB.

To correct this:

Change the operation type of the Buy rule for DC to SB’s Receipt operation type.

This ensures that any shortage created while fulfilling SB’s demand results in a Purchase Order for SB, not DC.

If you want to avoid confusion, you can archive the DC Receipt operation type.

This makes sure Odoo does not try to purchase for DC at all.

2. Adjust the Resupply Route From DC → SB

In your route “Resupply from DC”, for the third rule (Inter-warehouse Transit → SB/Stock):

Make sure the rule is configured as:

Take from stock ,if unavailable, trigger another rule

This ensures proper flow:

If SB does not have enough stock, Odoo first checks DC.

DC sends whatever is available (100 units in your example).

The remaining shortage (100 units) triggers the Buy rule—but now for SB, not DC.

3. What Happens After Fixing the Rules

With the corrected routing:

SO of 300 units creates demand at SB.

SB supplies its 100 units.

Odoo pulls 100 units available in DC and moves them to SB.

The remaining 100-unit shortage now triggers a Purchase Order for SB, because the Buy route is configured to replenish SB.

You may still see a backorder request in DC because the system originally generated demand for 200 from DC, but DC only had 100 available. This is normal behaviour based on pull rules and can be safely managed or ignored depending on the process.

If you have any follow-up questions or want me to check your exact routing configuration, feel free to ask!

2
頭像
捨棄
頭像
Rishu, Niyu Labs
最佳答案
For this setup, I would separate two questions:

1. Which warehouse should satisfy the sales demand?
2. Which warehouse should be purchased into when stock is not available?

Your DC is surplus/storage and should not ship to customers. SB is the operational warehouse. That means SB should remain the demand-facing warehouse, and DC should only act as an internal resupply source when stock exists there.

The route logic should usually look like this:

1. Sales demand is created for SB.
2. SB checks its own stock.
3. If SB is short, SB tries to resupply from DC.
4. If DC has stock, create an internal transfer DC → SB.
5. If DC does not have stock, purchase should replenish SB, not DC.

The common mistake is configuring DC as part of the chain in a way that creates a “shortage” in DC, so Odoo tries to buy into DC. That is usually not what you want if DC is only surplus storage.

I would check:

- The Buy route operation type:
  Make sure purchase receipts are going to SB if SB is the warehouse that needs to be replenished.

- The resupply route:
  The route from DC to SB should take from DC stock when available, not force DC to become the purchasing warehouse.

- The procurement group:
  Make sure the demand stays linked to the SB need, otherwise Odoo may plan supply in the wrong warehouse.

- Reordering rules:
  Create/test rules per product and warehouse. A rule on DC can cause Odoo to replenish DC. A rule on SB should replenish SB.

A clean test:
- Pick one product.
- Put stock only in DC.
- Create demand from SB.
- Confirm whether Odoo creates internal transfer DC → SB.
- Then set DC stock to 0 and repeat.
- Confirm whether Odoo creates PO receipt into SB.

If the second case creates a PO into DC, the buy/resupply route chain is pointing to the wrong operation type/location.

0
頭像
捨棄
喜歡這則討論?不要只閱讀,加入發表意見吧!

今天就建立帳戶,享受獨家功能,與我們精彩的社群互動!

註冊
相關帖文 回覆 瀏覽次數 活動
Productos vendidos almacenados físicamente: sin impacto en inventario y contabilidad
inventory
頭像
頭像
頭像
2
5月 26
1602
Change Location for Physical Inventory Adjustment
inventory
頭像
頭像
1
2月 26
2220
revalue the stock 已解決
inventory
頭像
頭像
頭像
2
2月 26
2183
Return on inventory transfers V18
inventory
頭像
頭像
頭像
2
1月 26
2028
How to print all product labels at once, including quantities in stock?
inventory
頭像
頭像
頭像
2
12月 25
2028
社群
  • 教學影片
  • 使用說明
  • 討論區
開源
  • 下載
  • GitHub
  • Runbot 測試環境
  • 翻譯
服務
  • odoo.sh 網頁寄存
  • 支援
  • 升級
  • 自訂功能開發
  • 教育及培訓
  • 尋找會計服務
  • 尋找合作夥伴
  • 成為合作夥伴
關於我們
  • 關於 Odoo 公司
  • 品牌資產
  • 聯絡我們
  • 招聘
  • 活動
  • Podcast
  • 網誌
  • 客戶
  • 法律 • 私隱政策
  • 安全性
الْعَرَبيّة Català 简体中文 繁體中文 (台灣) Čeština Dansk Nederlands English Suomi Français Deutsch हिंदी Bahasa Indonesia Italiano 日本語 한국어 (KR) Lietuvių kalba Język polski Português (BR) română русский язык Slovenský jazyk Slovenščina Español (América Latina) Español Svenska ภาษาไทย Türkçe українська Tiếng Việt

Odoo 是一套開放源碼的商業管理系統,涵蓋你公司全部的營運需要,包括客戶關係管理(CRM)、電子商務、會計、庫存管理、POS(銷售點管理)、專案管理等應用程式。

Odoo 的獨特價值是非常簡單易用,同時將不同應用程式完美整合。

Website made with

Odoo Experience on YouTube

1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.

Live support on Youtube
Watch now