Skip to main content
ProductHow it worksPricingFAQContactLog inالعربية
FAQ

Straight answers,
with the reasoning.

01How long does setup actually take?

Days, not months. The wizard captures configuration choices, AI implements the modules, you verify. Most go live in under two weeks.

WhyWe have automated the 80% of Odoo setup that consultants used to do by hand.
02What's a credit, and how many do I actually use?

One credit covers about 10,000 tokens of AI work: input, output, and code-reading combined. A simple change (one field on an existing form) runs 3–8 credits. A medium change (a new model, a scheduled report, a staged workflow) runs 15–30. A complex build (a new module with POS or backend extension) runs 50–100.

Voice queries and generated reports are much lighter: around 1 credit per five. A 2,500-credit plan typically covers 200+ simple changes, 50–100 medium ones, or roughly 25 complex builds.

WhyPer-seat pricing punishes small ops teams who use AI a lot. Per-credit means you pay for the AI work that actually happened, and you can plan the month against concrete numbers.
03What if Plemo's AI breaks something on Live?

It can't. Every change runs in your Test environment first; Live only updates after you click deploy.

WhyBA agent drafts the spec, dev agents ship to Test, you approve. No auto-deploy without your sign-off.
04What if Odoo upgrades break my customizations?

That's exactly what we're built for. Customizations live in your dedicated GitHub repo, and our agents validate and patch them in your Test environment before any Odoo upgrade touches Live.

WhyMost partners hand you the code and walk away. We own the upgrade path because that is where ERP investments usually die.
05Is my Odoo data safe with Plemo?

Yes. Per-customer Kubernetes namespace, encrypted at rest and in transit, GDPR-ready, hosted in EU and MENA regions.

WhyEach customer instance runs in its own isolated namespace with no cross-tenant data access. The same isolation backs every plan, from Starter on up.
06What's a Test environment?

A second Odoo instance where every customization is tested before it touches Live. Comes with every plan, refreshes from Live on demand.

WhyMost Odoo partners debug on Live. We won't.
07What is Odoo?

An open-source ERP covering sales, accounting, inventory, HR, and 30+ other modules.

WhyPlemo is built on Odoo because it is the only ERP whose code we can customize at the depth our AI needs.
08Can I leave Plemo without losing my Odoo?

Yes. The Odoo runs on standard PostgreSQL plus filestore (we'll export both on request), and your customizations are in a GitHub repo you own from day one.

WhyLock-in is a trust-killer. We are betting on monthly value, not switching costs.
09How do backups work?

Every ready instance gets a full database + filestore zip nightly. Backups are encrypted in object storage, retained for 90 days, and downloadable yourself from the backups page, in the canonical Odoo restore format, so you can drop them into any Odoo. A pre-deploy backup is also taken automatically before every customization deploy.

WhyBackups are useless if you cannot use them. Plemo gives you the same zip format Odoo itself uses, so you are never locked into our restore tooling.
10What's the difference between Starter, Professional, and Enterprise?

Starter is self-serve for single-team Odoo. Professional adds advanced customization, voice reporting, and a Test environment refreshed daily. Enterprise covers multi-company setups with dedicated environments and priority support.

WhyPlans are calibrated against real Plementus customer workloads. Starter fits a 1-admin-user pilot; Professional is the SMB envelope; Enterprise is for high-volume or multi-region operations.
11Can I migrate my existing Odoo data into Plemo?

Yes. We import your master data (customers, products, chart of accounts, employees, opening balances) during the wizard, and a Plementus consultant validates the migration before you go live.

WhyMigrations are the riskiest part of any Odoo project. They get human review on every Plemo onboarding, regardless of plan tier.
12Who reviews the AI's spec before any code runs?

You do. The BA agent writes the spec in plain language; you read and approve it before the dev agent writes a single line of code.

WhyThe spec is intentionally readable by an ops lead, not just a developer. If it does not make sense to you, the AI rewrites until it does.
13Where is Plemo hosted?

On managed Kubernetes, with regions in Europe and the Middle East. You choose at signup based on data-residency needs.

WhyGDPR-compliant by default with European data sovereignty guarantees. MENA-hosted customers stay regionally compliant.
14What are Watch findings?

Nightly proactive health-check scans across your Odoo. They look for misconfigured fields, stuck workflows, permission drift, and other quiet breakage you have not noticed yet. Findings surface in your next conversation with Plemo, so the agent can offer to fix what it noticed before you ever filed a ticket.

WhyMost ERP breakage is silent for days before someone reports it. The agents are already inspecting your Odoo every day, and we made the findings visible to you.
15How do I see what I am using each month?

The usage page shows your live credit balance, per-resource bars (AI customizations, voice queries, reports), the monthly refill date, and a one-click Buy Credits button if you want to top up before the next cycle. Every spend is itemised in the credit ledger, so there are no hidden line items.

WhyCustomers asked for the same kind of transparency they expect from cloud bills. Per-resource bars and a ledger make over-spend impossible to hide.

Question not listed?

Talk to our team. We reply within one business day.