Multi-Branch in Odoo
Businesses with multiple locations (retail stores, warehouses, offices) need: location-specific inventory, branch-specific pricing, inter-branch transfers, and consolidated reporting. Odoo supports this via multi-warehouse, multi-company, or a combination.
Two Approaches
| Approach | When to Use | Complexity |
|---|---|---|
| Multi-Warehouse | Same legal entity, multiple locations | Simple |
| Multi-Company | Separate legal entities per location | Complex |
Approach 1: Multi-Warehouse (Most Common)
# One company, multiple warehouses:
# Warehouse: Main Store (New York)
# - Location: Stock
# - Location: POS Counter
# - Location: Storage Room
#
# Warehouse: Branch Store (Chicago)
# - Location: Stock
# - Location: POS Counter
#
# Warehouse: Online Fulfillment (New Jersey)
# - Location: Receiving
# - Location: Stock
# - Location: Packing
# - Location: Shipping
# All share one accounting, one customer database
# Stock tracked per warehouse
# Orders fulfilled from nearest warehouseBranch-Specific Pricing
# Use pricelists per location:
# Pricelist: New York Pricing
# - Widget A: $120 (higher rent → higher prices)
#
# Pricelist: Chicago Pricing
# - Widget A: $100
#
# Assign pricelist to POS per branch
# Or assign based on customer's locationInter-Branch Transfers
# Transfer stock between branches:
# Inventory → Operations → Transfers → Create
# Type: Internal Transfer
# Source: New York / Stock
# Destination: Chicago / Stock
# Products: Widget A × 50
# Or use replenishment rules:
# Chicago stock < 20 → auto-transfer from New York
# Source: New York warehouse
# Quantity: up to 50Approach 2: Multi-Company
# Separate legal entities:
# Company: Retail Inc. - New York
# Company: Retail Inc. - Chicago
# Company: Retail Inc. - Online
# Each has:
# - Own chart of accounts
# - Own tax configuration
# - Own bank accounts
# - Own invoicing sequences
# Shared:
# - Product catalog
# - Customer database
# - User accounts (with company access)
# Inter-company transactions:
# Sale from NY to Chicago = inter-company sale/purchaseConsolidated Reporting
# Multi-Warehouse:
# All data in one company → standard reports show everything
# Filter by warehouse for branch-specific reports
# No consolidation needed
# Multi-Company:
# Each company has its own P&L and Balance Sheet
# Consolidation module (Enterprise) combines them
# Eliminates inter-company transactionsPOS Per Branch
# Each branch has its own POS config:
# Settings → POS → Create
# Branch POS Configuration:
# - Name: "NYC Store POS"
# - Warehouse: New York
# - Pricelist: New York Pricing
# - Payment Methods: Cash, Card
# - Receipt Header: "NYC Store - 123 Broadway"
# - Receipt Footer: store-specific return policy
# Each POS session operates independently
# Sales from each location update their warehouse stockBest Practices
- Start with multi-warehouse — simpler, sufficient for most businesses
- Use multi-company only if locations are separate legal entities or different countries
- Centralize purchasing — bulk buying from HQ, distribute to branches
- Standardize processes — same workflows across all locations
- Monitor per-branch KPIs — revenue, costs, inventory turnover per location
DeployMonkey for Multi-Branch
Deploy Odoo for your multi-branch business on DeployMonkey. The AI agent configures warehouses, branch pricing, inter-branch transfers, and consolidated reporting. One ERP for all your locations.