Overview
Sasmar’s Odoo Experience 2026 session, “Choosing Odoo Over SAP: The 10-Year Transformation Journey of a Global Pharmaceutical Group,” is positioned as a business transformation case study. The official event page states that Sasmar evaluated traditional enterprise platforms including SAP in 2014, selected Odoo and grew from six to 22 companies. It also highlights four global regions, an evolution from Odoo 7 to Odoo 19 Enterprise and more than 25 Shopify stores alongside Amazon and other digital commerce operations. The session is scheduled for 24 September 2026 in Hall 6.A. View the official session details.
This guide answers one narrow question: what should an ERP leader watch for in the talk and record for their own transformation decision? Use it as a live checklist. It helps turn an inspiring customer story into questions about architecture, governance, rollout risk and measurable operating value.
Start With the Correct Frame: This Aas An ERP Choice, Not An SAP Migration
One detail matters. Sasmar evaluated SAP and chose Odoo. It did not migrate from SAP to Odoo. That distinction changes the lessons to look for. The session can help buyers understand how a global pharmaceutical ERP is selected and sustained over time, not how a legacy SAP estate is technically converted.
The useful question is therefore not “Could we copy Sasmar’s configuration?” Every organisation has different products, legal entities, distribution channels, quality obligations and data maturity. The useful question is “Which decision patterns would make our ERP architecture able to survive the next ten years?”
| Confirmed Context to Listen For | Why it Matters to An ERP Buyer | Question to Write Down |
|---|---|---|
| Six companies growing to 22 | Tests whether the organisation could scale without separate systems | What was standard before new companies were onboarded? |
| Odoo 7 to Odoo 19 Enterprise | Shows whether change was managed as a continuous roadmap | How were upgrades prepared and accepted? |
| Multiple global regions | Brings currency, localisation, access and reporting questions | What remained global and what varied by country? |
| Shopify stores, Amazon and websites | Tests how digital channels connect to core transactions | Which system owned stock, price and customer data? |
Watch the Business Model Before the Technology Model
Pharmaceutical operations connect many decisions that are often separated in smaller systems. A commercial team needs accurate product availability and price terms. Supply chain teams need purchase, production and warehouse information they can trust. Finance needs invoices, tax treatment, payments and group reporting to reconcile. Leadership needs a view that is comparable across companies without hiding local accountability.
As you watch the Sasmar Odoo story, listen for the operating model first. Who owns the process from demand to fulfilment? Where does a new product record begin? How is a new market launched? Which data is centrally controlled? These answers are more revealing than the names of installed modules.
A global pharmaceutical ERP needs transactions with a governed path. An illustrative order-to-cash flow may look like this:
A commercial user creates or imports a customer order in the correct company context.
Odoo validates the customer, price, credit or approval conditions and product availability.
The warehouse reserves or replenishes stock. An intercompany rule can create linked purchasing and sales documents.
Delivery confirms the movement. Invoicing uses the company’s fiscal rules and posts to the appropriate ledger.
Payment allocation, credit notes, returns and reporting follow a controlled exception process.
The key point is traceability from original demand through logistics and finance. Note how the speakers connect commercial operations, manufacturing, supply chain, finance and digital commerce rather than presenting isolated deployments.
The Five Areas to Watch Closely
1. Architecture Designed For Expansion
The official session description says Sasmar designed an ERP architecture for future expansion rather than only current requirements. Listen for what that meant in practice. Strong answers usually cover company structures, currencies, warehouses, master-data conventions, security roles and reporting dimensions. They also explain which parts were deliberately not standardised.
An organisation might standardise product identifiers, customer data rules, reporting dimensions and core approval evidence while allowing local tax setup, language and statutory reports. The architecture is coherent when those boundaries are documented and reviewed when a new company joins.
2. Governance That Makes Standards Practical
Governance can sound abstract until it decides whether a change can go live. In a ten-year transformation, the key question is who can approve a new requirement, configuration change, customisation or integration. Look for the roles that connect business policy with system changes.
A practical governance model needs decision rights that are understood before a business unit creates its own workaround.
| Governance Signal | What to Listen For | Why it Matters |
|---|---|---|
| Process ownership | Named owner for order-to-cash, procure-to-pay or inventory movement | Prevents a change being approved only for one department |
| Data ownership | Clear stewardship for products, customers and company mappings | Reduces duplicate records and reporting disputes |
| Change control | Assessment, testing, approval and release path | Protects critical transactions from rushed changes |
| Local variation | A rule for approving country-specific requirements | Keeps standards realistic rather than rigid |
If the talk describes a difficult decision or a failed approach, record it. The official description says the speakers intend to share what worked, what failed and what they would do differently. Those lessons are especially useful because they expose the trade-offs that simple case studies can hide.
3. Upgrade Discipline From Odoo 7 to Odoo 19
A journey from Odoo 7 to Odoo 19 Enterprise raises questions about testing, custom development, integrations, data compatibility and user adoption. Ask whether each upgrade had business acceptance criteria. A robust approach tests full transaction paths in staging, proving that orders, receipts, production, invoices, payments, returns and reporting still behave as expected.
The best lesson may be about customisation restraint. Standard Odoo changes over time. A custom module that duplicates a standard feature can become an unnecessary upgrade burden. Conversely, a well-documented extension with clear business ownership and regression tests can be a sensible long-term choice. Listen for how Sasmar and its delivery team separated those cases.
4. Digital Commerce Without Losing ERP Control
More than 25 Shopify stores and Amazon channels create a useful test of data ownership. Digital commerce can increase order volume quickly. It can also create overselling, duplicate customer records, cancelled orders, refund mismatches and confusing stock positions if interfaces are not governed.
In the talk, listen for the connection between the channel and the ERP. Which system holds sellable stock? When does an online order become a fulfilment commitment? How are product changes and price changes approved? What happens if an API call fails or a marketplace order is duplicated? How are returns and payments reconciled?
| Commerce Control Point | Evidence a Buyer Should Seek | Risk If Unclear |
|---|---|---|
| Inventory availability | One rule for stock publication and reservation | Overselling or failed fulfilment |
| Product information | Clear product identifier and publishing owner | Incorrect listings or duplicate SKUs |
| Order status | Reconciled status mapping between channel and Odoo | Missed cancellations or duplicate dispatch |
| Refund and payment data | Exception queue and financial reconciliation | Revenue and customer-service disputes |
Some flows can run on a schedule if the business can tolerate the delay. The design must match operational impact and include an exception owner.
5. Multi-Company and Multi-Currency Control
The move from six to 22 companies is a lens for judging whether Odoo supports growth through a shared operating model rather than a collection of local databases. Watch for how company context is maintained in orders, stock, accounting entries, approvals and reporting. A user should see the information needed for their role without gaining unnecessary access to another entity’s data.
For group reporting, ask how local transactions become comparable through common mappings, reporting dimensions, closing procedures and controlled consolidation adjustments. Intercompany trade should be traceable from selling-company sales order through buying-company purchase order, fulfilment, invoicing and reconciliation.
A 15-Minute Readiness Checklist Before You Watch
Bring a concise view of your own situation. You do not need a full requirements document. You do need enough context to identify what matters in the talk.
List each legal entity, country, warehouse and sales channel in scope.
Identify the two transaction flows that create the most manual work or control risk.
Note your current ERP version, major customisations and critical integrations.
Record who owns product, customer, pricing and finance master data.
Write the three reports that leadership cannot reliably receive today.
State the next likely growth event: acquisition, new market, website, warehouse or product range.
Agree which outcomes you would measure, such as close duration, fulfilment accuracy, exception volume or duplicate data rate.
This list makes the session more valuable because it connects what you hear to a real decision. It also exposes missing information. If nobody can name the owner of product data or a key integration, governance may need attention before a wider Odoo rollout.
Questions To Ask After The Session
If you speak with the presenters or begin your own discovery workshop, ask questions that uncover the decision process instead of requesting a feature tour.
What standards were established before Sasmar added new companies and which were refined later?
How did the team decide that a local requirement justified configuration or custom development?
What was tested before each upgrade and who provided business acceptance?
Which data domains were centrally governed and which remained locally maintained?
How were digital-commerce exceptions monitored and reconciled?
What change-management practices helped users adopt new global processes?
What would the team design differently if it were beginning its global pharmaceutical ERP transformation today?
These questions do not seek confidential detail. They seek reusable decision rules. A useful answer describes ownership, evidence, exceptions and trade-offs rather than presenting a smooth success narrative.
How to Use the Takeaways After Odoo Experience
Within a week, hold a 60-minute review with finance, operations, IT and process owners. Compare your notes with your current operating model. Select one high-value gap, such as unmanaged product data, a weak integration reconciliation process or unclear ownership of change requests. Define the current baseline, an accountable owner, a practical target and a first decision date.
Avoid launching a broad transformation programme from a single event session. The stronger next step is a focused architecture and process discovery. Map representative end-to-end transactions, record data owners and distinguish requirements from legacy habits. Then sequence the roadmap around risk and business value.
For wider background on the transformation, visit the Sasmar pharma case study. Use the session to ask whether your own Odoo pharma ERP roadmap has the foundations needed for the next expansion, not merely for the next go-live.
Conclusion
The key thing to watch in Sasmar’s Odoo Experience 2026 transformation talk is not a single module or integration. It is the discipline behind a decade of change: an architecture built for expansion, governance that makes standards workable, upgrades treated as business releases and connected commerce controlled through reliable data.
For any global pharmaceutical ERP buyer, those are the practical lessons worth carrying into discovery. Take structured notes, challenge assumptions and turn the session’s insights into one well-defined improvement for your own roadmap.
FAQs
1. Is Sasmar’s Odoo Experience 2026 session about moving from SAP to Odoo?
No. Sasmar evaluated SAP and other traditional enterprise options before selecting Odoo. The talk focuses on the ten-year Odoo transformation journey rather than an SAP migration.
2. What confirmed topics will the Sasmar Odoo session cover?
The official description includes ERP selection, future-ready architecture, multi-company and multi-currency operations, manufacturing and supply chain, digital commerce, Odoo 7 to Odoo 19 upgrades and governance principles.
3. Why should a pharmaceutical ERP buyer watch a customer story?
A long-running customer story can reveal how architecture, data ownership, change control and user adoption work after go-live. Those operating choices are usually more important than a feature comparison.
4. What should I record during the talk?
Capture specific examples of what was standardised, what remained local, how changes were approved, how upgrades were tested and how commerce or reporting exceptions were handled.
5. Can a smaller business use the same lessons?
Yes. A smaller business does not need 22 companies to benefit from data ownership, controlled customisation, integration monitoring and a roadmap based on business outcomes. The scale changes but the principles remain useful.
6. What is the biggest multi-company ERP risk to look for?
The biggest risk is uncontrolled local variation. It can create duplicate masters, inconsistent reporting, excessive access and difficult upgrades. A clear global baseline with approved local exceptions reduces that risk.
7. What should we do immediately after the session?
Hold a short cross-functional review, compare the notes with your own architecture and choose one evidence-based gap to address. Use that result to scope a focused discovery rather than starting with a broad feature list.
