Skip to Content
Q&A

Purchase requests through a customer or employee portal in Odoo

What works as standard, what Odoo Purchase and Approvals offer, and when custom work is needed

Back to all Q&A
November 4, 2026 by
Purchase requests through a customer or employee portal in Odoo

In short: The standard Odoo 19 portal is built for customers and vendors, and portal users have read access to documents. We found no standard portal page for submitting an internal purchase request. Employees with an internal user can use the Approvals app, and Odoo Purchase can require approval above a minimum amount. Custom work comes into view when requesters must work from the portal itself.

Employee submitting a purchase request through a portal screen, followed by an approval step

Colleagues want to request something, a manager has to approve it, and purchasing then places the order. Preferably without emails and spreadsheets, and preferably through a simple portal page. We regularly get this question at our helpdesk.

Whether that is possible depends on who is requesting and what you want to happen next. This article explains what works as standard in Odoo 19, what Purchase and Approvals add, and when custom work is the better choice. We use the labels of the English interface.

First: who is actually requesting?

The word portal covers three quite different situations. Separate them first, because the solution differs for each one.

  • An employee requests something for the company. This is an internal purchase request. The result is a request for quotation or purchase order.
  • A customer or external party wants something from you. That is usually a sale and not a purchase. The result is a quotation or sales order, and a webshop is often the more logical route.
  • A vendor responds to your question. That is the vendor side of purchasing, for which Odoo already has portal pages.

Does an external party, such as a franchisee or branch with its own login, request something that you then buy in? Then you are in a mixed situation. In practice that mostly points towards custom work.

What the standard portal does

According to the documentation, portal access lets customers and vendors log in to your Odoo user portal. You grant it from the Contacts app, through Action and Grant portal access. Customers can follow and pay orders and invoices, manage payment methods and subscriptions, and maintain addresses.

The documentation also states that portal users have read and view access, and cannot edit documents in the database. Unlike internal users, you cannot choose access rights per application for them. Their permissions are preset.

Vendors can view requests for quotation and purchase orders in the portal, and the Odoo 20 release notes also mention the vendor portal. That is about documents you have sent to the vendor. It is not a place where someone submits a new internal request.

We found no standard page in the portal documentation for submitting and approving purchase requests. Do you see something different in your environment, for example through a module from a third party? Then test how it handles rights and upgrades.

What Odoo Purchase offers

Purchase is where the actual order takes place. A few standard features are relevant here:

  • Requests for quotation and purchase orders: the base of the purchasing process, with statuses such as To Send, Waiting and Late on the dashboard.
  • Purchase Order Approval: under Purchase app, Configuration, Settings you set a Minimum Amount. Orders above it get the status To Approve, unless the person confirming has administrator rights in Purchase.
  • Blanket orders and call for tenders: for fixed agreements with a vendor and for comparing vendors.
  • Reordering rules: for standard items, a request is often unnecessary. See reordering rules in Odoo.

Note that this works for people who already work in Purchase. It approves an order, not the question that comes before it. For many companies that is enough: colleagues ask purchasing, and purchasing creates the order. It is not enough if you want the request itself recorded and approved.

What the Approvals app offers

This is the closest standard answer. In the Approvals app, employees submit requests and management approves or refuses them. The documentation lists nine preconfigured types, including:

  • Procurement: for work-related items such as office supplies and tools, with a Quantity and an Amount.
  • Create RFQ's: for requesting a quote for items from a vendor, with a Products tab.
  • Payment Application: for prior approval of expenses paid by the company.

You open a type, click New Request, fill in the request and add approvers on the Approver(s) tab, where you can mark an approver as Required. Approvers find their work under Approvals app, Manager, Approvals to Review.

There are three things to check beforehand. Approvals is an Enterprise app, so check whether your subscription includes it. The documentation does not describe how a purchase order follows from an approved request, so test that yourself with a real example. And the documentation does not describe use by portal users, so assume that requesters need an internal user until you have tested otherwise. What that means for your subscription costs is something to check in the current Odoo terms.

When custom work makes sense

Custom work is worth considering when one or more of these apply:

  • requesters do not have an internal user and should not get one;
  • you want a simple form with your own fields and a limited catalogue;
  • approval depends on budget, department or cost centre;
  • external parties must be able to follow the status of their request;
  • an approved request must immediately create a request for quotation with the right vendor.

A portal app like this generally consists of a separate request record, a portal page, rules on who sees what, approval logic and a step that creates the request for quotation. An important design choice: do not give portal users direct access to purchase orders. Let them work only on their own requests, and have the server check every action.

Also take maintenance into account. Custom work must go along with every upgrade, as our upgrade checklist explains. In the Odoo 20 release notes we did not find a new portal for purchase requests, so do not count on the next version solving this by itself.

How to choose: a route in four steps

  1. Write down who requests, who approves and what the outcome must be. Include a few real examples from recent months.
  2. Count the requesters. Are they mostly colleagues who already work in Odoo? Then start with the Approvals app.
  3. Test the whole chain in a test environment, from request to approved order, with ordinary users and not as administrator.
  4. Note what is missing. If only a few details are missing, consider a small extension. If requesters need to work outside Odoo, plan a portal app.

At DAADit, AI builds and a consultant checks, at a fixed price of €1,000 per app. See how that works.

Common pitfalls

  • Granting portal access to a company. According to the documentation, every contact linked to that company then gets access. You can remove individuals afterwards, so check the list.
  • Forgetting to revoke access. Use the same menu to click Revoke Access when someone leaves.
  • Approving your own request. Agree that requester and approver are different people, and test whether your setup enforces that.
  • Double entry. If purchasing retypes each approved request, you have only moved the work. Test how the request flows into the order.
  • Prices that have changed. The amount on the request can differ from the final order. Agree what happens with a large difference.

What this means for you

Do not start with the portal, start with the process. If your requesters are colleagues, standard Approvals and Purchase may well be sufficient. Only when people outside the back end have to request something does a portal app become a logical investment.

Frequently asked questions

Can employees submit a purchase request through the Odoo portal as standard?

In the Odoo 19 documentation we find no standard page for this. The portal is intended for customers and vendors, and according to the documentation portal users only have read access to documents. Employees with an internal user can use the Approvals app.

What is the difference between Odoo Purchase and the Approvals app?

Purchase handles requests for quotation and purchase orders, with a setting for approval above a minimum amount. Approvals is a separate Enterprise app in which employees submit requests for the right approvers to assess, including the types Procurement and Create RFQ's.

When do I need custom work for purchase requests through a portal?

When the requester does not or will not have an internal user, when you want your own form or limited catalogue on the portal, or when approval depends on budget or department in a way the standard does not support.

Finally

Would you like to know which route fits your purchasing process? Contact DAADit Group or take the free Business Scan.

in Odoo

Question not answered?

Our Odoo consultants are happy to think along with you. Book a no-obligation intro call.

Book an appointment
Approving vendor bills and payments in two steps in Odoo
Who may prepare, who may approve, and what Odoo 19 offers as standard compared with Studio and custom work