BambooForge Saleor Connector
A real connector that imports from Saleor — the open-source GraphQL-first commerce platform — into Odoo 18. Import products (with variants & media), customers and orders over the Saleor GraphQL API, kept in sync by native Saleor webhooks — with a resilient queue, dry-run safety and full source you can audit.
Verified live against a running Saleor
We don't just claim a vague version range. The connector was installed on Odoo 18 and pointed at two live, locally-run Saleor servers — 3.19 and 3.20 — importing products, customers and orders over the GraphQL API with 0 errors on both.
| Saleor version | API | Live result |
|---|---|---|
| 3.20 | GraphQL API (tokenCreate JWT) | ✔ Live-tested — 0 errors |
| 3.19 | GraphQL API (tokenCreate JWT) | ✔ Live-tested — 0 errors |
| 3.x line | GraphQL API | ✔ Supported (same schema) |
The live test imported the seeded Apple Juice product (variant price, category, media, stock), a customer, and a multi-line order through the state mapping — all green. Saleor returns channel-aware decimal prices and Editor.js descriptions, which the connector reads and flattens automatically.
Built to actually sync — not to look busy
Saleor is GraphQL-first, and this connector treats it that way: typed queries pull a product with its variants, media and category in one round-trip. Every model ships with verifiable sync logic, covered by tests — no fake dashboards, no “readiness score” with nothing behind it.
What you actually get
Everything below ships in the box — including a bundled mock Saleor GraphQL API so you can demo without a live store.
Products, variants & options
Saleor products import with name, slug, channel price, category and media; the Editor.js description is flattened to text. Variants are recorded (the attribute grid is on the v2 roadmap).
Customers & addresses
Each Saleor customer becomes a res.partner; their addresses become child partners with billing / delivery type inferred from the default-billing flag.
Orders with state machine
Orders import with line items, shipping and tax totals, and the payment method. Saleor order state maps to Odoo confirm / cancel / draft through an editable mapping table per instance.
Refunds → credit notes
Saleor refunds (under an order's payments) become draft Odoo account.move credit notes linked to the order. Optional auto-post for hands-off workflows.
Native webhook ready
A bundled Saleor native Saleor webhook POSTs HMAC-SHA256-signed events on product / customer / order changes. Real-time — no polling cron required.
Typed GraphQL client
Authenticates with the tokenCreate mutation (email/password → JWT, auto-refreshed) or a pre-issued token, runs typed queries with retry/backoff, and surfaces GraphQL errors cleanly.
Sync Control Tower
A live operations dashboard: a kanban of instances surfacing health status, circuit-breaker state, queue/backlog depth, dead-letter and conflict counts, 24h throughput and failure rate as clickable stat cards that drill straight into the queue, dead-letter and conflict views — at-risk instances flagged in colour.
Bulk dead-letter console
A dedicated view of exhausted-retry jobs grouped by error type, with bulk requeue or discard actions — clear a wave of failures in one move instead of one job at a time.
Conflict-resolution workbench
A triage list with a side-by-side Odoo-vs-Saleor snapshot diff, and bulk resolve: Odoo-wins, remote-wins or mark-reviewed — so divergences are settled deliberately, not silently.
Conditional branching
The multi-step flow engine walks true/false branches from a condition step's boolean result (true_step_id / false_step_id), with a loop guard against cyclic links. Fully backward-compatible — flows with no branch links just fall through to the next step in sequence.
Field-mapping studio
A payload-test wizard: paste a sample JSON payload and see exactly how each field mapping transforms it, in a consolidated studio view — plus one-click mapping suggestions to bootstrap a new instance fast.
Two-way stock service
Real bidirectional inventory. A delta-reconcile cron pushes Odoo on-hand for every bound product to Saleor via the native productVariantStocksUpdate GraphQL mutation — per-variant, per-warehouse, only changed quantities. A 3-layer oversell guard (instance clamp + safety buffer + adapter clamp to ≥0) means the store never oversells, and a guarded opt-in import writes Saleor stock back into real Odoo inventory as an actual adjustment.
A live walkthrough inside Odoo 18
Recorded in a real Odoo 18 connected to a live Saleor 3.20 — the connection cockpit, a synced product and order, the state mapping and the flow engine, all on real data.
Every screen, from a live install
Captured from a running Odoo 18 connected to a live Saleor 3.20 — real data synced through the connector, not mockups.
Run every Saleor store from one Control Tower
A short walkthrough of the operations tooling on real data: the Control Tower board, the side-by-side conflict workbench and the bulk dead-letter console.
Production safety, by default
Resilient queue
Retry with exponential backoff, rate-limit awareness, dead-letter handling and conflict capture for every job.
Circuit breaker
Auto-pauses sync after N consecutive failures so a broken endpoint can never flood your data.
Dry-run mode
Default-ON for every new instance — preview the exact write before anything touches live records.
Pre-flight validation
Blocking and warning findings surfaced before go-live, with auto-fix suggestions.
Rollback snapshots
Capture record state before risky writes and roll back cleanly when needed.
SSRF-safe by default
Internal / loopback hosts are blocked unless you explicitly opt in for a trusted self-hosted Saleor.
Honest feature matrix
No asterisks, no fake checkmarks. Here is exactly what version 1 does — and what is on the v2 roadmap.
| Capability | Status |
|---|---|
| Product import (name, description, enabled, slug) | ✔ Included |
| Variants recorded (price, SKU, stock) | ✔ Included |
| Channel-aware decimal prices | ✔ Included |
| Asset URLs + featured image capture | ✔ Included |
| Facet values → Odoo product category | ✔ Included |
| Customers + addresses | ✔ Included |
| Orders + line items + state mapping | ✔ Included |
| Refunds → draft credit notes (auto-post optional) | ✔ Included |
| Auth: login (bearer, auto-refresh) · pre-issued token | ✔ Included |
| Native Saleor webhooks → Odoo (HMAC-verified endpoint) | ✔ Included |
| Queue: retry · backoff · dead-letter · circuit breaker | ✔ Included |
| Pre-flight validation · rollback snapshots · dry-run | ✔ Included |
| Schema introspection & field mapping (JSON path + transforms) | ✔ Included |
| Sync Control Tower — live instance dashboard (queue · dead-letter · conflict · throughput) | ✔ Included |
| Bulk dead-letter console (requeue / discard, grouped by error) | ✔ Included |
| Conflict-resolution workbench (side-by-side diff · Odoo-wins / remote-wins / reviewed) | ✔ Included |
| Conditional branching in the flow engine (true/false steps, loop-guarded) | ✔ Included |
| Field-mapping studio (payload-test wizard + one-click suggestions) | ✔ Included |
Two-way stock: delta push via native productVariantStocksUpdate + oversell guard + opt-in import | ✔ Included |
| Export Odoo → Saleor | Roadmap (import-first today) |
| Asset binary upload Odoo → Saleor | Roadmap v2 |
| Multi-channel / multi-language sync | Roadmap v2 |
Live in four steps
A guided quick-setup wizard and onboarding checklist walk you from credentials to first safe sync.
Connect
Enter your Saleor URL + admin username/password (or a bearer token). One click tests credentials and reachability.
Map
Run schema introspection and generate suggested field mappings automatically.
Dry-run
Preview exact writes with dry-run + validation on. Clear any blocking findings.
Go live
Point a Saleor webhook at the connector and let the resilient queue keep both systems in sync.
Buy with full clarity
In the box today
- Two-way sync: products, customers + addresses, orders, refunds
- Two-way stock: delta push via native
productVariantStocksUpdate+ 3-layer oversell guard + opt-in import into real Odoo inventory - Sync Control Tower — live instance dashboard (queue, dead-letter, conflict, throughput)
- Bulk dead-letter console + conflict-resolution workbench (side-by-side diff)
- Conditional branching in the flow engine + field-mapping studio (payload-test wizard)
- Native Saleor webhook endpoint (HMAC-verified) — included
- Bundled mock Saleor GraphQL API — demo without a live store
- Full source included — audit and extend every line for your own use
Deferred / beta
- Product export Odoo → Saleor is in beta (import is the primary path)
- Asset binary upload Odoo → Saleor (asset import is read-only today)
- Multi-channel / multi-language sync
- Saleor 2.x is supported — validate on your build
Frequently asked
Which versions are supported?
Odoo 18.0 on the Odoo side. On the store side, the connector was live-tested on Saleor 3.20 (Admin GraphQL API) and supports the 3.x line on the same schema; 2.x is supported — validate it on your specific build.
Do I need to install Saleor to evaluate it?
No. A mock Saleor GraphQL API ships inside, so you can install, explore and demo the full import flow before connecting a real store.
How does authentication work?
Two modes: admin username + password exchanged for a bearer token via the login mutation (auto-refreshed on expiry), or a pre-issued bearer token. Saleor's tokenMethod must include 'bearer' (the default config does).
Is the webhook companion extra?
No. The HMAC-SHA256 signed Saleor native Saleor webhook ships inside this package under phase2/saleor_plugin/, with install instructions.
Is it safe to run against production data?
Dry-run mode is ON by default for new instances, validation blocks risky writes, and rollback snapshots let you undo. You decide when to go live.
What support and refund policy do I get?
Every request is answered within 24 hours, setup help included. If you report a bug within 2 months of purchase and it isn't resolved within 15 days, you're entitled to a full money-back refund.
Connect Odoo and Saleor the honest way
24-hour support · Report a bug within 2 months — unresolved in 15 days = full refund · Full source included
bambooforge.labs@gmail.comMore from BambooForge Labs — one vendor, the same standard: tested, source included, supported.
BambooForge Saleor Connector
A bridge between Odoo 18 and your Saleor store over the Saleor GraphQL API: import products (with variants and media), customers and orders, and reconcile refunds — with a resilient job queue, dry-run safety, validation and rollback so you stay in control.
This page is the complete manual. If you follow it top to bottom you can install, connect, run your first sync, automate it, and fix the common issues without contacting support.
- Overview
- Requirements
- Installation
- Step 1 — Create a Saleor app token
- Step 2 — Create the connection in Odoo
- Step 3 — First sync (dry-run, then live)
- Order status mapping
- Field mapping & customization
- Automation (scheduled actions & webhooks)
- Safety features
- Troubleshooting
- Frequently asked questions
- Data, privacy & limits
- Support & updates
- Upgrading & version compatibility
- Uninstallation
- Changelog
Overview
The connector keeps Odoo aligned with Saleor over Saleor's GraphQL API. Instead of REST endpoints, every read is a typed GraphQL query against a single endpoint (graphql/). It covers:
- Products — import Saleor products (with variants and media) into Odoo product templates, optionally with stock, images and tax group; export Odoo product changes back to the store. Saleor's Editor.js rich-text descriptions are flattened to plain text on import.
- Customers — import Saleor customers (and their billing/shipping addresses) into Odoo contacts.
- Orders — import Saleor orders into Odoo sale orders, mapping each order's Saleor status to a sale-order action (keep draft, confirm, cancel, or ignore).
- Refunds — optionally discover Saleor order slips (credit notes) attached to an order and create matching draft customer credit notes in Odoo.
Direction of sync: Odoo ↔ Saleor (import is the primary flow; product export and webhook-driven updates are supported).
Prices are read per Saleor channel (a configurable channel slug, default default-channel), so amounts match what that sales channel actually charges.
Every remote call goes through a queue: nothing is written to Odoo until a job runs, jobs retry with back-off on transient failures, and a circuit breaker pauses an instance that keeps failing.
Requirements
- Odoo: 18.0, Community or Enterprise.
- Saleor: any Saleor server exposing the standard GraphQL API at /graphql/. Saleor must be reachable from the Odoo server.
- Python: no extra libraries beyond a standard Odoo 18 install.
- Odoo access: any internal user can use the connector screens. Saleor credentials are stored in system-only fields, so only the Settings / Administration user can read or change the admin password and the app / bearer token.
- Network: outbound HTTPS from Odoo to your store. By default the connector refuses internal/loopback/private hosts as an SSRF safeguard (see Safety features).
Installation
- Copy bambooforge_saleor_connector into your Odoo addons path.
- Restart the Odoo service.
- Open Apps, click Update Apps List, search for Saleor, and press Activate / Install. Dependencies (Sales, Contacts, Invoicing) install automatically.
No Saleor store is required to evaluate the connector: a mock Saleor GraphQL API ships inside the module, so you can install, explore and run the full import flow against sample data before pointing it at a real store. To use it, set the instance Base URL to <your-odoo-url>/saleor/mock_api and leave GraphQL Path at graphql/.
Step 1 — Create a Saleor app token
The connector talks to Saleor's GraphQL API as an authenticated app. The recommended way is a pre-issued app token:
- Open the Saleor Dashboard and go to Apps.
- Create a local app (or open an existing one).
- Grant it the permissions the connector needs: read for products, product variants, customers/users and orders; add manage permissions for those resources only if you intend to export products back to Saleor.
- Create / reveal the app's auth token and copy it. This token is used as a Bearer token against the GraphQL endpoint.
Alternatively, the connector can log in with a staff email + password using the Saleor tokenCreate mutation; it then uses (and auto-refreshes) the returned JWT. The app-token approach is preferred for unattended servers because it does not store a password.
Step 2 — Create the connection in Odoo
Open Saleor Connector ▸ Configuration ▸ Instances and create a record.
Key fields:
| Field | What to enter |
|---|---|
| Name | A label for this store, e.g. My Live Store. |
| Base URL | Your Saleor server root, e.g. https://store.example.com. For the bundled mock, use <your-odoo-url>/saleor/mock_api. |
| Authentication | App / Bearer Token (recommended) or Email + Password (tokenCreate). |
| Admin Email / Password | Only for the Email + Password auth type: a Saleor staff/admin email and password (password is visible to administrators only). |
| App / Bearer Token | Only for the App / Bearer Token auth type: the token from Step 1 (visible to administrators only). |
| GraphQL Path | Leave the default graphql/ unless your server differs. |
| Default Channel | The Saleor channel slug used for product pricing, default default-channel. |
| Verify SSL | Keep on for production. Turn off only for self-signed test certificates. |
| Allow internal host | Off by default. Turn on only to reach a Saleor server on localhost or a private network (lowers the SSRF guard — see Safety features). |
Then click Test Connection. A green Connected state means the credentials and URL are correct, and the default order-state mapping is seeded automatically. If it fails, the exact error is shown on the form and recorded in Logs (see Troubleshooting).
Tip: use Quick Setup (button on the instance) to pick a use case (catalog only, B2C full sync, …), seed default field mappings and order-status rules, and apply a recommended schedule in one step.
Step 3 — First sync (dry-run, then live)
New instances start with Dry-run ON. In dry-run, import and delete jobs simulate writes: instead of changing data they produce Validation Results you can review under Saleor Connector ▸ Operations ▸ Validation Results. This lets you confirm what would happen before anything is written.
To run a first import:
- On the instance, click Import Products (and/or Import Customers, Import Orders). This enqueues jobs; it does not block the UI.
- Jobs are processed by the Saleor Queue Processor scheduled action (every minute), or immediately if you run it manually from Operations ▸ Queue Jobs.
- Review Validation Results while still in dry-run.
- When satisfied, open the instance, turn Dry-run OFF, and run the imports again to write the records for real.
Imported records land in the standard Odoo apps: Sales ▸ Products, Contacts, and Sales ▸ Orders. Each carries its Saleor reference so re-imports update the same record instead of duplicating it.
Order status mapping
Saleor exposes each order's status as an UPPERCASE enum on the order's status field. Under Configuration ▸ Order State Mappings each instance gets a default table that decides what happens to the Odoo sale order when an order arrives in a given status:
| Saleor status | Default Odoo action |
|---|---|
| DRAFT | Keep draft |
| UNCONFIRMED | Keep draft |
| UNFULFILLED | Confirm sale order |
| PARTIALLY_FULFILLED | Confirm sale order |
| FULFILLED | Confirm sale order |
| PARTIALLY_RETURNED | Confirm sale order |
| RETURNED | Cancel sale order |
| CANCELED | Cancel sale order |
| EXPIRED | Cancel sale order |
Change any row to Ignore (do nothing), Keep draft, Confirm sale order or Cancel sale order. Unknown/custom statuses default to Ignore, so a status you have not mapped never triggers a destructive transition. Add a row for any custom status using the exact Saleor enum value.
Field mapping & customization
- Field Mappings (Configuration) map Saleor fields to Odoo fields per model. Use Generate suggested mappings on the instance to seed the business-critical ones, then adjust. The mapping board flags fields that need attention.
- Schema Fields lists the discovered Saleor fields per resource. Run Schema Introspection on the instance to refresh it from your live store.
- Stock / images / tax are opt-in toggles on the instance: Sync stock, Sync images (and max images), Upload images on export, Sync taxes (and auto-match taxes on import). They are off by default; turn on only what you need.
- Refunds: Sync refunds discovers Saleor order slips and creates draft credit notes; Auto-post refund (off by default) posts them automatically.
Automation (scheduled actions & webhooks)
The module ships these scheduled actions (Settings ▸ Technical ▸ Scheduled Actions):
| Scheduled action | Default | Purpose |
|---|---|---|
| Saleor Queue Processor | every 1 min | Processes queued import/export/delete jobs. |
| Saleor Reconciliation | every 15 min | Pulls recent remote changes for enabled models. |
| Saleor Maintenance | every 1 hr | Recovers stale/locked jobs and trims old logs. |
| Saleor Flow Scheduler | every 5 min | Runs scheduled sync flows. |
| Saleor Flow Metrics | every 1 hr | Aggregates flow-run metrics. |
| Saleor Auto Recover | every 15 min | Reopens a tripped circuit breaker once the store is healthy. |
Turn on Auto import / Auto reconcile per model on the instance to let the scheduled actions keep things in sync hands-free.
Real-time webhooks (optional): point a Saleor webhook at:
- Target URL: https://<your-odoo-domain>/saleor/webhook
- Secret: the instance Webhook Secret (admin-only field on the instance).
Saleor signs each delivery with an X-Saleor-Signature HMAC-SHA256 header over the raw body; Odoo verifies it (fail-closed: a missing secret or signature is rejected), checks the signed emitted_at timestamp to reject stale/future deliveries, dedupes replays, and enqueues a safe import. Without webhooks the scheduled reconciliation still keeps data current.
Safety features
- Dry-run mode — simulate writes and review Validation Results before going live.
- Business validation profiles — Minimal / Standard / Strict gate risky writes.
- Resilient queue — every remote action is a job with retry and exponential back-off.
- Circuit breaker — after repeated failures an instance auto-pauses (Tripped); the Auto Recover action reopens it once the store responds again.
- Rollback snapshots — when enabled, imports capture a snapshot so you can undo a batch from Operations ▸ Rollback Snapshots.
- SSRF guard — the connector refuses internal/loopback/private hosts unless Allow internal host is explicitly enabled.
Troubleshooting
| Symptom | Cause and fix |
|---|---|
| Test Connection fails with an auth error | Wrong app token, or the token/app lacks permissions; for Email + Password, wrong credentials. Re-check Step 1 and that the token has product/customer/order read permissions. |
| "Username and password are required" / "A bearer token is required" | The fields for the chosen Authentication type are empty. Fill the email+password pair, or the app/bearer token, to match the selected auth type. |
| "Base URL is not allowed … non-public address" | Base URL points at localhost/private IP. Enable Allow internal host on the instance (test/self-hosted only). |
| SSL errors on Test Connection | Self-signed certificate. Use a valid cert, or turn off Verify SSL for testing only. |
| GraphQL endpoint not found / 404 | The GraphQL Path is wrong. Saleor's default is graphql/ under the server root; correct it to match your deployment. |
| Orders import but never confirm | The order's Saleor status is mapped to Keep draft or Ignore. Adjust Order State Mappings (use the exact UPPERCASE enum). |
| Jobs stay in Pending | The Queue Processor is off or the instance is paused. Check Scheduled Actions is active and the instance is not Paused. |
| Instance shows Tripped | Circuit breaker tripped after repeated failures. Fix the store/credentials; Auto Recover reopens it, or click Resume. |
| Webhook returns 401 Invalid signature | The instance Webhook Secret does not match the secret Saleor signs with, or no X-Saleor-Signature header was sent. Set the same secret on both sides. |
| Webhook returns 400 Stale / future emitted_at | The Saleor and Odoo server clocks differ by more than the freshness window. Sync both clocks (NTP). |
| Records imported twice | Imports are keyed by the Saleor reference, so this should not happen. If it does, check that two instances do not point at the same store. |
| Nothing happens after Import | You are in Dry-run. Review Validation Results, then turn dry-run off and re-run. |
For anything else, Operations ▸ Logs records every API call, payload hash and error with a timestamp.
Frequently asked questions
Which versions are supported? Odoo 18.0 on the Odoo side. On the store side the connector targets Saleor's standard GraphQL API at /graphql/. Validate your exact build with the bundled mock first.
Do I need Saleor installed to evaluate it? No. A mock Saleor GraphQL API ships inside, so you can install, explore and demo the full import flow before connecting a real store — point the Base URL at <your-odoo-url>/saleor/mock_api.
How does authentication work? Two options. Create a Saleor app token in Saleor Dashboard ▸ Apps with the needed read (and optional manage) permissions and use it as a Bearer token — recommended. Or use a staff email + password; the connector runs the tokenCreate mutation and auto-refreshes the returned JWT.
How does real-time sync work? Point a Saleor webhook at /saleor/webhook with the shared secret; Odoo verifies the X-Saleor-Signature HMAC-SHA256 over the raw body, rejects stale/replayed deliveries, and enqueues a safe import. Without it, scheduled reconciliation keeps things in sync.
How are prices read? Per Saleor channel. Set the Default Channel slug (default default-channel) so the connector reads the price that channel charges.
Is it safe to run against production data? Dry-run is ON by default, validation blocks risky writes, and rollback snapshots let you undo. You decide when to go live.
What support and refund policy do I get? Every request is answered within 24 hours, setup help included. If you report a bug within 2 months of purchase and it is not resolved within 15 days, you are entitled to a full money-back refund.
Data, privacy & limits
- The connector reads products, customers, orders and order slips from your store and writes the corresponding Odoo records. Credentials are stored in admin-only fields.
- In scope today: product/customer/order import, product variants and media, product export, order-status mapping, refund (order-slip) discovery, scheduled sync, signed webhooks.
- Out of scope / best-effort: tax auto-matching (off by default, name-based, never auto-creates taxes); multi-warehouse stock routing; subscription/booking order types.
Support & updates
- Support: bambooforge.labs@gmail.com — answered within 24 hours, setup help included.
- Refund: report a bug within 2 months of purchase; if unresolved within 15 days, full refund.
- Full source is included. Updates track the supported Odoo 18 / Saleor GraphQL API line.
Upgrading & version compatibility
This build targets Odoo 18.0. Each Odoo major series (17.0, 18.0, 19.0) has its own dedicated build of this module — always install the build that matches your Odoo version. Mixing a build with a different Odoo series is not supported.
Patch upgrades (same series, e.g. 18.0.1.0.0 → later)
Back up your database and filestore first.
Replace the module folder with the newer build.
Restart Odoo with the module updated:
./odoo-bin -c your.conf -u bambooforge_saleor_connector -d your_db
Odoo applies any schema/data changes automatically. Your existing records and configuration are preserved.
Cross-version migration (e.g. Odoo 17 → 18)
Upgrading Odoo itself is a database migration handled by Odoo's standard upgrade tooling. When you migrate the database to the next Odoo series, install the matching build of this module for that series. Data created by this module carries over with the database migration.
After any upgrade the module's scheduled actions resume on their normal cadence — no manual re-activation is required.
Uninstallation
You can remove this module at any time from Apps → (this module) → Uninstall, or from the command line. Uninstalling is clean and reversible by reinstalling — but note what is and is not deleted.
What is removed
- The module's own tables and every record in them (20 models, prefixed saleor.*) — this is the data this module created.
- The menus, actions, views and reports this module installed.
- Its scheduled actions (cron jobs) — they stop immediately on uninstall.
- Connection records, credentials, field mappings, queue jobs and sync logs stored in Odoo.
What is preserved
- Your remote platform is never touched. Uninstalling only removes the Odoo-side connector; products, customers and orders on the external store/service are untouched.
- Records already imported into standard Odoo models (e.g. contacts, products, sales orders) remain — they are ordinary Odoo records once created.
- Attachments and chatter messages on standard records are kept.
As always, take a database backup before uninstalling in production.
Changelog
18.0.1.0.0
Current release for Odoo 18.0. This build includes:
- Odoo 18 <-> Saleor connector over the Saleor GraphQL API: products, variants, customers, orders.
- Two-way stock sync, live Sync Control Tower, resilient queue and dry-run safety.
Feature additions and fixes ship as new builds on the Odoo Apps store; this page and the module's version reflect the current published release. Always keep the build matched to your Odoo series (see Upgrading & version compatibility).
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module