The problem this app solves

A customer purchase order reference may be needed for fulfillment, invoicing or later payment matching. A blank reference or accidental reuse can create operational queries, while a legitimate blanket PO needs a different treatment from a duplicate.

Use the native Customer Reference field with configured checks at the relevant sales and accounting stages. Preserve the exact supplied reference, control allowed reuse and record manager exceptions without replacing native document numbers.

Features that support your daily work

Use Odoo's native Customer Reference, preserve exactly what the customer supplied, and apply server-authoritative policy before operational mistakes reach fulfilment or invoicing.

• Catch risk. Require a reference at send, confirmation, delivery, invoice creation, or posting. Compare case, whitespace, punctuation, leading zeros, customer scope, period, and state.
• Control reuse. Choose warning, block, or manager override. Support blanket and release POs with order-count, amount, expiry, and release-ID limits.
• Keep evidence. Propagate the exact reference to invoices and optional deliveries, search by PO, and export an access-safe CSV or PDF audit.

A practical example

Illustrative workflow — the available actions depend on your configuration.

A salesperson enters a PO already used for the same customer. The policy flags the apparent reuse. The user corrects it or requests a permitted exception; an accepted exact reference remains searchable on the linked documents.

A focused operational workflow

1 · Configure: A Sales Manager defines the company/customer policy and normalization rules.

2 · Enter: The salesperson uses Odoo's native Customer Reference field.

3 · Decide: Unique references proceed; missing or duplicate references get corrective action.

4 · Approve: A manager records why apparent reuse is legitimate when policy allows it.

5 · Audit: The exact PO remains searchable on linked documents and in audit output.

Security by design

• Manager and company authority rechecked server-side.
• Hidden duplicates do not leak names, counts, values, or links.
• Immutable override snapshots retain decision context.
• Concurrent confirmations of the same reference are checked together.

Native Odoo placement

• Sales > Configuration > Customer PO Policies
• Sales > Orders > Customer PO Exceptions
• Sales > Reporting > Customer PO Reference Audit
• Included optional stock and website bridges

See the workflow in Odoo

Explore the screens in sequence, from configuration to daily work and reporting. Each image includes a caption explaining its place in the workflow.

Configure enforcement, normalization, scope, and controlled reuse. A unique exact customer PO passes the server-side gate. A reasoned manager decision preserves a controlled exception. The customer PO is carried forward without replacing native document numbers. Operational teams can follow missing, duplicate, reused, overridden, and stale states. A bounded PDF and formula-safe CSV provide accessible audit evidence.