Practical guide
How to Choose Odoo Apps for a General Trading Company
Choose trading apps by following the company’s actual order cycle. Sales records the customer commitment, Purchase organizes supplier procurement, Inventory records physical movements and Accounting handles the financial result. CRM, POS, Project, Field Service or Manufacturing may be relevant when the business also qualifies opportunities, sells at a counter, installs, services or produces goods. Each addition should have a clear operational role.
Official Odoo Partner · Ever Digital
Step 1: choose an order that exposes the whole operation.
Use a recent mixed order with several items, including one taken from stock and one bought for the customer. Add a partial delivery, a changed supplier price or another ordinary exception. Ask the salesperson, buyer, warehouse operator and finance owner to explain what each person records and what they need from the previous department.
Write the handoffs on one page before selecting software. Identify duplicated entry, missing references and decisions made through informal messages. The aim is to decide which business event each application should own, not to reproduce every existing spreadsheet as a new screen.
Step 2: assign the core commercial and stock records.
These applications commonly form a trading foundation, but their configuration should follow the chosen example.
| Application | Role in the order cycle | Decision that changes setup |
|---|---|---|
| Sales | Quotation and confirmed customer order. | Customer prices, units, delivery commitments and invoicing policy. |
| Purchase | Supplier enquiries and purchase orders. | Stock replenishment versus procurement for specific demand. |
| Inventory | Receipts, locations, transfers and deliveries. | Warehouse steps, reservation, units and traceability. |
| Accounting | Invoices, bills, payments and reconciliation. | Company currency, valuation, accounts and finance controls. |
Odoo documentation · CC BY-SA 4.0 · CC BY-SA 4.0
Original documentation image, shown without altering the interface. The screenshot illustrates standard Odoo, not a customer implementation.
Step 3: agree which record proves each event.
A customer order proves the commercial commitment; it does not prove dispatch. A supplier order proves what was requested; it does not prove what arrived. A stock movement and a financial document have different purposes. Keep these distinctions clear when deciding permissions and reporting.
Test a partial transaction. If the customer ordered ten items and received six, staff should be able to explain the outstanding four, the procurement response and the permitted invoice quantity. An app list without this demonstration gives little evidence that the trading workflow is ready.
Step 4: add applications only for work you actually perform.
The additional app should solve a defined handoff or record requirement. It should not be selected simply because it appears in a broad ERP package.
| Business activity | App to assess | Important boundary |
|---|---|---|
| Longer sales qualification | CRM | A pipeline does not replace confirmed orders or revenue records. |
| Walk-in counter sales | Point of Sale | Check devices, session reconciliation and shared stock. |
| Installation projects | Project or Field Service | Agree task creation, acceptance and billing evidence. |
| After-sales support | Helpdesk | Define service coverage and escalation separately. |
| Assembly or production | Manufacturing | Use a real BOM and component-to-output test. |
| Internal authorization requests | Approvals | Verify whether the required transaction is actually blocked. |
Step 5: assess data readiness before expanding scope.
Product identity and units affect nearly every trading app. Agree internal codes, supplier references, variants and fixed conversions. Identify products that need lots, serials or expiry information. Finance and warehouse owners should reconcile the opening position independently.
Customer and supplier data should support the intended commercial process. Duplicate partners, expired pricelists and ambiguous open orders can undermine the rollout even when the applications are configured correctly. Start with the active records the first phase needs and maintain a controlled archive for the rest.
Step 6: resolve company, currency and branch decisions.
An Iraq trader may buy and sell in more than one currency, but the finance team must approve the company currency and rate policy. A warehouse, an operating branch and a legal company are different structures. Choose the model that represents the business rather than creating separate companies merely to distinguish storage sites.
Confirm required customer documents, language needs and any local finance obligations. Payment, supplier or marketplace integrations require evidence for the exact provider and process. Do not include them as assumed standard capability in the app shortlist.
What to bring to a shortlist review.
A small evidence pack makes the assessment more useful than a long feature checklist.
- One mixed customer order with its purchase, receipt, delivery and invoice records.
- A sample of product codes, units and supplier references.
- The operating sites and the legal company structure.
- Current customer pricing rules and an exception needing approval.
- The opening stock and finance reconciliation approach.
Turn the shortlist into a testable first phase.
Use the industry app planner to capture the initial combination, then review it against the example order. Remove apps without an operational purpose and record specialist requirements that remain unverified. A first phase should preserve the complete trading cycle even if additional channels or advanced reporting are deferred.
Ever Digital can help convert the shortlist into an implementation scope with configuration decisions, data responsibilities and acceptance examples. Current package information is maintained on the implementation services page; this guide does not estimate a fee from the number of selected apps.
Questions businesses ask
What is the usual starting stack for a stock-based trader?
Sales, Purchase, Inventory and Accounting commonly cover the core cycle. The exact configuration and any additional apps should follow a representative order and the company’s controls.
Should a trader always install Manufacturing?
No. Assess it when the business transforms components into output or has another production requirement. Buying and reselling finished goods alone does not justify a manufacturing workflow.
Does adding more apps increase implementation quality?
Only when each app has a defined role and a maintained process. Unnecessary applications can add complexity without improving the underlying handoffs.
Can the app planner produce a final scope?
It produces an initial shortlist and considerations. Discovery, data review and acceptance testing are still needed to confirm the implementation scope.
Sources and factual scope
Capabilities checked against official Odoo documentation. These are planning examples, not promises that every feature is included in a Starter package.
- Odoo Sales documentation
- Odoo Purchase documentation
- Odoo Inventory documentation
- Odoo Accounting documentation
- Odoo: companies
Reviewed:
Ever Digital
Bring your real workflow to the conversation.
Tell us how you sell, stock, deliver or service. We will identify the standard apps, decisions and any extensions your implementation needs.
View Starter packages Current implementation fees and included scope are maintained on the Starter package pages. Odoo licences, hosting and custom work are separate.