← All articles

Blog

Odoo Modules Indonesian Retailers Use First (and Which to Skip)

Odoo has 40-plus modules. For Indonesian retailers, four of them matter on day one and most of the rest can wait. Here's the order that actually works.

6 min read
  • mid

Walk into any Odoo demo as a retailer and the consultant will scroll through the app store screen with forty-something tiles. Sales, CRM, Inventory, Purchase, Accounting, POS, Manufacturing, eCommerce, Website, Marketing Automation, Email Marketing, SMS Marketing, Helpdesk, Project, Field Service, Subscriptions, Rental, Studio, Sign, Documents, Discuss, Approvals, Surveys, Appointments, Quality, Maintenance, PLM, Time Off, Recruitment, Appraisals, Fleet, Lunch — the list keeps going. By tile eight you nod politely. By tile twenty you have stopped processing.

You do not need most of them. Probably not ever.

Here is the pattern we have seen across Indonesian retailers — from a five-store Bandung fashion chain to a sixty-store electronics distributor in Jakarta. The same four or five modules carry the weight. A handful are valuable add-ons in year two. Most of the rest are noise for the average retailer.

The day-one core: four modules

These are the modules that, turned on together, replace the first painful spreadsheet stack most Indonesian retailers run.

Inventory. This is the backbone for a retailer. Multi-warehouse, multi-location, lots, barcodes, transfers between stores, cycle counting, inventory valuation. If your business has more than one storage point, you need this from day one. Configure your warehouse hierarchy carefully — main warehouse, each store as a location, transit locations for in-transit stock. Get this right and the rest of Odoo behaves. Get it wrong and every downstream report lies to you.

Point of Sale. This is where Odoo shines for retailers and where it surprises people who expected something basic. POS works in the browser on a laptop, on a tablet, with a receipt printer, with a barcode scanner, with a cash drawer. It handles split payment (cash + GoPay + OVO), discounts, customer lookup, returns, and works offline if your store internet drops. The cashier experience is fast enough that floor staff stop complaining within a week. POS pushes sales directly into Inventory and Accounting in real time.

Purchase. Tracking what you buy, from whom, at what price, with what lead time. Even a 10-store retailer ends up with 30+ active suppliers across categories. Purchase orders, vendor bills, three-way matching against goods receipt — basic but high-value. Skipping this in favour of “we will keep using WhatsApp with suppliers” is the most common cost leak we see.

Accounting. Even if you keep Accurate running in parallel for the first 90 days while your accountant gets comfortable, Accounting needs to be configured from day one because every other module posts to it. Chart of accounts mapped to PSAK, taxes configured (PPN 11%, withholding tax if relevant), bank journals set up. Invoicing flows through here. Vendor bills flow through here.

Those four are the minimum viable Odoo for a retail business. A 12-store fashion retailer in Bandung running just these four covers maybe 80 percent of their daily operational pain.

The fifth, depending on your channels: eCommerce or marketplace connectors

If you sell on Tokopedia, Shopee, Lazada, or TikTok Shop — which is most retailers in Indonesia — you need to connect inventory and orders between Odoo and the marketplaces. Odoo does not ship with native Indonesian marketplace connectors. You have three options.

Use a paid third-party connector from a local vendor — typically Rp 1–3 juta per month per channel. These vary in quality. Test before committing.

Use OCA community modules — free, code quality is variable, may need a developer to keep running through Odoo version upgrades.

Build a custom integration through the marketplace APIs — Rp 30–80 juta for a solid one. Worth it if marketplace volume is your business core.

If you also run your own webstore, Odoo’s built-in eCommerce module is genuinely capable. Many retailers use it as their public storefront with Midtrans or Xendit for payment.

What to add in month four to six

Once the core is stable, three modules earn their weight.

CRM is worth turning on when sales reps start chasing larger customers — wholesale buyers, B2B orders, recurring corporate clients. For a pure walk-in retail store with no sales-led workflow, skip it. For a hybrid retailer who also takes B2B orders from offices and salons, it is useful.

HR with basic employee records and Time Off is genuinely useful once you have more than 20 staff and you are tired of approving leaves through WhatsApp screenshots. Payroll in Odoo is harder — Indonesian payroll (BPJS, PPh 21) is not in standard Odoo and needs a localization module or custom build. Many retailers keep using their existing payroll software and just have Odoo handle attendance and leave.

Manufacturing is worth it only if you actually manufacture. A retailer who repacks bulk products into retail SKUs sometimes needs basic Manufacturing for bill-of-materials handling. A pure retailer should skip it entirely.

What to skip almost always

Some Odoo modules look exciting in the demo but rarely deliver for retailers. Be selective.

Marketing Automation, Email Marketing, SMS Marketing. Indonesian retail marketing happens on WhatsApp, Instagram, and TikTok. Odoo’s marketing modules are competent but built for a different market. Keep your marketing stack outside Odoo unless you have a specific reason.

Subscriptions, Rental. Unless you run a subscription model or rental business, leave them off. Turning them on adds clutter without value.

Field Service, Helpdesk. These solve real problems but not retail problems. Service businesses use them. Retailers do not.

PLM, Quality, Maintenance. Manufacturing-side modules. Skip unless you run a factory.

Documents, Sign, Approvals. Genuinely useful at scale, but for a retailer under 50 staff, you probably do not need them in year one. They are easy to turn on later if needed.

Studio. Powerful, but only useful if you have someone willing to think carefully about workflow before adding fields. Avoid turning it on early — premature customisation is one of the bigger ways to wreck a clean Odoo implementation.

A simple sequencing rule

Inventory + POS + Purchase + Accounting in month one and two. eCommerce or marketplace connectors in month two or three depending on where your revenue lives. CRM and HR in month four to six if the team is ready. Manufacturing only if you actually manufacture. Everything else, leave it until you have a specific reason to turn it on.

The mistake is reversing this — turning on twenty modules at kick-off because “we paid for them anyway” with Enterprise. You did not pay extra for them, but every module you turn on without a real workflow behind it adds confusion. Less is more in year one. You can always add later.

If you are planning your rollout and want a second opinion on the module sequence for your specific retail business, we walk through that on free one-hour calls. Practical, no pitch.