PRD Peppol Route Doctor Belgium-first delivery diagnosis
Issue page

Odoo suddenly says all customers are not on Peppol

If Odoo marks every customer as not on Peppol all at once, treat it as an environment or provider incident first, not a data-cleanup job on every partner record.

Global Odoo Peppol outage symptom Belgium-first Self-serve remediation
Symptoms

What this usually looks like

Every customer suddenly shows as not on PeppolKnown-good partners stop resolving at the same timeThe change happened all at once rather than partner by partner
Likely cause

What is usually actually broken

The issue is more likely a DNS, provider, or environment-wide lookup problem than dozens of customer records breaking at once.

Next steps

Do these before you resend

  1. Test one known-good participant outside Odoo before editing any customer records.
  2. Check whether the incident coincided with a DNS, network, or provider change.
  3. Treat the problem as global until one clean external lookup proves otherwise.

The fastest path from this page is a prefilled diagnosis. It opens the analyzer with this exact issue pattern already loaded and immediately prepares the EUR 9 fix-pack preview when the route looks blocked or risky.

Open prefilled diagnosis See the fix pack
Direct help

Buy the rescue kit for this exact issue

If this page matches the exact blocker, you can unlock the issue-specific rescue kit directly without running the analyzer first.

Recent operator reports

Current public evidence for this exact failure

Odoo 18 CE / Enterprise users reporting all customers suddenly changing to 'not on Peppol'

r/Odoo · April 2026

Open source
FAQ

What people ask right before they get blocked

Should I start fixing every customer record?

No. If the failure appeared everywhere at once, the safer assumption is an environment or provider incident until proven otherwise.

What evidence makes this look global?

Known-good customers failing at the same time, especially after a platform or network change, points away from isolated data errors.

Operator guides

Go one level deeper before you resend

Odoo Peppol triage for Belgium

A calm, ordered checklist for Belgian Odoo users when Peppol starts failing without a clear explanation.

Read the guide
When to resend a Peppol invoice and when to escalate

A fast decision guide for operators who need to know whether the next step is a resend, a partner-record fix, or a provider ticket.

Read the guide
Related issues

Similar failure patterns worth checking

Odoo says 'PEPPOL is not valid' even though the customer looks registered

This exact Odoo message usually means the ERP is validating the wrong participant identity, stale evidence, or the wrong identifier scheme rather than proving the customer is truly unavailable.

Open issue page
Recipient is on Peppol, but Odoo still says no valid Peppol ID

This contradiction usually means Odoo has the wrong identifier, wrong scheme, or stale participant evidence. This page breaks down the mismatch clearly.

Open issue page
My customer has a GLN in Odoo, but I still get 'no valid Peppol ID'

A stored GLN or alternate identifier does not guarantee Odoo will resolve the exact Peppol participant the recipient expects. This page shows where the mismatch happens.

Open issue page