Vendor Portal | Supplier Quotes & Deliveries

Vendor Portal / Supplier Quotes & Deliveries. Let a vendor quote a request, decline it, send a shipping notice and send their invoice from the portal - none of it touching your order. Odoo Community gives your vendors a portal where they can look at your requests and orders, and change a delivery date. Everything else comes back by email: the prices, the "we cannot do that one", the shipping notice, the invoice.

Somebody then types it in — and that is where the price that was quoted and the price that was ordered stop being the same number. In the next few minutes: answering a request, then telling you it is on its way, then sending the invoice, then nothing touches the order until you apply it, then what the door refuses. Then what this app deliberately does not do, so you can tell before you buy whether it fits. Everything lives under Vendor Submissions.

1. Copy bambooforge_vendor_portal into your addons path and update the app list, or install the ZIP from the Odoo Apps Store. 2. Install Vendor Portal.

3. Open Vendor Submissions. Answering a request. On the same page the vendor already opens, a line-by-line form: unit price, when they can supply it, and a message.

One button sends it. If they cannot supply it, there is a second button and a box for the reason — so a "no" arrives as a "no", instead of as a silence you chase by telephone a week later. Telling you it is on its way. Date, carrier, tracking reference, and a note for part shipments.

Applying it moves the expected date on the order lines, so when is it coming has an answer inside Odoo rather than in somebody's inbox. Sending the invoice. The document itself — a PDF, or a photograph of one, up to 10 MB — together with the vendor's own reference, date and total. One button in the back office turns that into a draft vendor bill with the file already attached to it.

Draft, never posted: the figures came from outside, and a portal that posts to your ledger without a person reading it first is not a portal, it is a hole. Nothing touches the order until you apply it. This is the design, not a workflow preference. A portal user is an outsider.

If sending a quotation wrote the price onto the purchase order, the document a buyer reads and the document a buyer approves would not be the same document — it could change in between, from outside, at any moment. So everything a vendor sends is stored as a submission sitting beside the order. It can only be read, until a buyer opens it and applies it. What the door refuses A negative price, which falls back to what was asked, and a negative invoice, which is refused outright.

A second copy of something already sent and not yet handled, so a double click is not two submissions a buyer has to choose between. A quotation on a confirmed order, a shipping notice or invoice on one that is not confirmed, and anything at all on an order that is done or cancelled. A file that is not a document — PDF, PNG or JPEG only. Access.

The module widens nothing. Odoo gives portal users read-only rights on purchase orders; they still have exactly that, and there is a test that fails if it ever stops being true. Every route checks the document with Odoo's own _document_check_access before it does anything, and only then acts as superuser to store the submission — the same shape core uses for its own portal write, the one that updates delivery dates. The check is what proves the caller is entitled to this order.

The superuser step is what lets a read-only user leave something behind. Doing the second without the first is how a portal becomes an open door. Series How we make sure it works. Before every release, 26 automated checks run against this app on Odoo 16, 17, 18, 19 and 20.

Among them: The same quotation cannot be sent twice. A submission cannot be applied twice. A portal user still cannot write to a purchase order. A bill is not created twice from one submission.

A confirmed order cannot be re priced. The complete list is in the source you receive. Questions people ask. Which Odoo versions does it run on?

Odoo 16.0, 17.0, 18.0, 19.0, 20.0, on the series you buy it for; each series is its own listing. Community or Enterprise? Both. It needs no Enterprise app.

The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours. Links are in the description.

Vendor Portal / Supplier Quotes & Deliveries. Let a vendor quote a request, decline it, send a shipping notice and send their invoice from the portal - none of it touching your order. Odoo Community gives your vendors a portal where they can look at your requests and orders, and change a delivery date. Everything else comes back by email: the prices, the "we cannot do that one", the shipping notice, the invoice.

Somebody then types it in — and that is where the price that was quoted and the price that was ordered stop being the same number. In the next few minutes: answering a request, then telling you it is on its way, then sending the invoice, then nothing touches the order until you apply it, then what the door refuses. Then what this app deliberately does not do, so you can tell before you buy whether it fits. Everything lives under Vendor Submissions.

Answering a request. On the same page the vendor already opens, a line-by-line form: unit price, when they can supply it, and a message. One button sends it. If they cannot supply it, there is a second button and a box for the reason — so a "no" arrives as a "no", instead of as a silence you chase by telephone a week later.

Telling you it is on its way. Date, carrier, tracking reference, and a note for part shipments. Applying it moves the expected date on the order lines, so when is it coming has an answer inside Odoo rather than in somebody's inbox. Sending the invoice.

The document itself — a PDF, or a photograph of one, up to 10 MB — together with the vendor's own reference, date and total. One button in the back office turns that into a draft vendor bill with the file already attached to it. Draft, never posted: the figures came from outside, and a portal that posts to your ledger without a person reading it first is not a portal, it is a hole. Nothing touches the order until you apply it.

This is the design, not a workflow preference. A portal user is an outsider. If sending a quotation wrote the price onto the purchase order, the document a buyer reads and the document a buyer approves would not be the same document — it could change in between, from outside, at any moment. So everything a vendor sends is stored as a submission sitting beside the order.

It can only be read, until a buyer opens it and applies it. What the door refuses A negative price, which falls back to what was asked, and a negative invoice, which is refused outright. A second copy of something already sent and not yet handled, so a double click is not two submissions a buyer has to choose between. A quotation on a confirmed order, a shipping notice or invoice on one that is not confirmed, and anything at all on an order that is done or cancelled.

A file that is not a document — PDF, PNG or JPEG only. Access. The module widens nothing. Odoo gives portal users read-only rights on purchase orders; they still have exactly that, and there is a test that fails if it ever stops being true.

Every route checks the document with Odoo's own _document_check_access before it does anything, and only then acts as superuser to store the submission — the same shape core uses for its own portal write, the one that updates delivery dates. The check is what proves the caller is entitled to this order. The superuser step is what lets a read-only user leave something behind. Doing the second without the first is how a portal becomes an open door.

Series The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours. Links are in the description.

Vendor Portal / Supplier Quotes & Deliveries. Let a vendor quote a request, decline it, send a shipping notice and send their invoice from the portal - none of it touching your order. Odoo Community gives your vendors a portal where they can look at your requests and orders, and change a delivery date. Everything else comes back by email: the prices, the "we cannot do that one", the shipping notice, the invoice.

Somebody then types it in — and that is where the price that was quoted and the price that was ordered stop being the same number. In the next few minutes: answering a request, then telling you it is on its way, then sending the invoice, then nothing touches the order until you apply it, then what the door refuses. Then what this app deliberately does not do, so you can tell before you buy whether it fits. Everything lives under Vendor Submissions.

Answering a request. On the same page the vendor already opens, a line-by-line form: unit price, when they can supply it, and a message. One button sends it. If they cannot supply it, there is a second button and a box for the reason — so a "no" arrives as a "no", instead of as a silence you chase by telephone a week later.

Telling you it is on its way. Date, carrier, tracking reference, and a note for part shipments. Applying it moves the expected date on the order lines, so when is it coming has an answer inside Odoo rather than in somebody's inbox. Sending the invoice.

The document itself — a PDF, or a photograph of one, up to 10 MB — together with the vendor's own reference, date and total. One button in the back office turns that into a draft vendor bill with the file already attached to it. Draft, never posted: the figures came from outside, and a portal that posts to your ledger without a person reading it first is not a portal, it is a hole. Nothing touches the order until you apply it.

This is the design, not a workflow preference. A portal user is an outsider. If sending a quotation wrote the price onto the purchase order, the document a buyer reads and the document a buyer approves would not be the same document — it could change in between, from outside, at any moment. So everything a vendor sends is stored as a submission sitting beside the order.

It can only be read, until a buyer opens it and applies it. What the door refuses A negative price, which falls back to what was asked, and a negative invoice, which is refused outright. A second copy of something already sent and not yet handled, so a double click is not two submissions a buyer has to choose between. A quotation on a confirmed order, a shipping notice or invoice on one that is not confirmed, and anything at all on an order that is done or cancelled.

A file that is not a document — PDF, PNG or JPEG only. Access. The module widens nothing. Odoo gives portal users read-only rights on purchase orders; they still have exactly that, and there is a test that fails if it ever stops being true.

Every route checks the document with Odoo's own _document_check_access before it does anything, and only then acts as superuser to store the submission — the same shape core uses for its own portal write, the one that updates delivery dates. The check is what proves the caller is entitled to this order. The superuser step is what lets a read-only user leave something behind. Doing the second without the first is how a portal becomes an open door.

Series The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours. Links are in the description.

Vendor Portal / Supplier Quotes & Deliveries. Let a vendor quote a request, decline it, send a shipping notice and send their invoice from the portal - none of it touching your order. Odoo Community gives your vendors a portal where they can look at your requests and orders, and change a delivery date. Everything else comes back by email: the prices, the "we cannot do that one", the shipping notice, the invoice.

Somebody then types it in — and that is where the price that was quoted and the price that was ordered stop being the same number. In the next few minutes: answering a request, then telling you it is on its way, then sending the invoice, then nothing touches the order until you apply it, then what the door refuses. Then what this app deliberately does not do, so you can tell before you buy whether it fits. Everything lives under Vendor Submissions.

Answering a request. On the same page the vendor already opens, a line-by-line form: unit price, when they can supply it, and a message. One button sends it. If they cannot supply it, there is a second button and a box for the reason — so a "no" arrives as a "no", instead of as a silence you chase by telephone a week later.

Telling you it is on its way. Date, carrier, tracking reference, and a note for part shipments. Applying it moves the expected date on the order lines, so when is it coming has an answer inside Odoo rather than in somebody's inbox. Sending the invoice.

The document itself — a PDF, or a photograph of one, up to 10 MB — together with the vendor's own reference, date and total. One button in the back office turns that into a draft vendor bill with the file already attached to it. Draft, never posted: the figures came from outside, and a portal that posts to your ledger without a person reading it first is not a portal, it is a hole. Nothing touches the order until you apply it.

This is the design, not a workflow preference. A portal user is an outsider. If sending a quotation wrote the price onto the purchase order, the document a buyer reads and the document a buyer approves would not be the same document — it could change in between, from outside, at any moment. So everything a vendor sends is stored as a submission sitting beside the order.

It can only be read, until a buyer opens it and applies it. What the door refuses A negative price, which falls back to what was asked, and a negative invoice, which is refused outright. A second copy of something already sent and not yet handled, so a double click is not two submissions a buyer has to choose between. A quotation on a confirmed order, a shipping notice or invoice on one that is not confirmed, and anything at all on an order that is done or cancelled.

A file that is not a document — PDF, PNG or JPEG only. Access. The module widens nothing. Odoo gives portal users read-only rights on purchase orders; they still have exactly that, and there is a test that fails if it ever stops being true.

Every route checks the document with Odoo's own _document_check_access before it does anything, and only then acts as superuser to store the submission — the same shape core uses for its own portal write, the one that updates delivery dates. The check is what proves the caller is entitled to this order. The superuser step is what lets a read-only user leave something behind. Doing the second without the first is how a portal becomes an open door.

Series The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours. Links are in the description.

Vendor Portal / Supplier Quotes & Deliveries. Let a vendor quote a request, decline it, send a shipping notice and send their invoice from the portal - none of it touching your order. Odoo Community gives your vendors a portal where they can look at your requests and orders, and change a delivery date. Everything else comes back by email: the prices, the "we cannot do that one", the shipping notice, the invoice.

Somebody then types it in — and that is where the price that was quoted and the price that was ordered stop being the same number. In the next few minutes: answering a request, then telling you it is on its way, then sending the invoice, then nothing touches the order until you apply it, then what the door refuses. Then what this app deliberately does not do, so you can tell before you buy whether it fits. Everything lives under Vendor Submissions.

Answering a request. On the same page the vendor already opens, a line-by-line form: unit price, when they can supply it, and a message. One button sends it. If they cannot supply it, there is a second button and a box for the reason — so a "no" arrives as a "no", instead of as a silence you chase by telephone a week later.

Telling you it is on its way. Date, carrier, tracking reference, and a note for part shipments. Applying it moves the expected date on the order lines, so when is it coming has an answer inside Odoo rather than in somebody's inbox. Sending the invoice.

The document itself — a PDF, or a photograph of one, up to 10 MB — together with the vendor's own reference, date and total. One button in the back office turns that into a draft vendor bill with the file already attached to it. Draft, never posted: the figures came from outside, and a portal that posts to your ledger without a person reading it first is not a portal, it is a hole. Nothing touches the order until you apply it.

This is the design, not a workflow preference. A portal user is an outsider. If sending a quotation wrote the price onto the purchase order, the document a buyer reads and the document a buyer approves would not be the same document — it could change in between, from outside, at any moment. So everything a vendor sends is stored as a submission sitting beside the order.

It can only be read, until a buyer opens it and applies it. What the door refuses A negative price, which falls back to what was asked, and a negative invoice, which is refused outright. A second copy of something already sent and not yet handled, so a double click is not two submissions a buyer has to choose between. A quotation on a confirmed order, a shipping notice or invoice on one that is not confirmed, and anything at all on an order that is done or cancelled.

A file that is not a document — PDF, PNG or JPEG only. Access. The module widens nothing. Odoo gives portal users read-only rights on purchase orders; they still have exactly that, and there is a test that fails if it ever stops being true.

Every route checks the document with Odoo's own _document_check_access before it does anything, and only then acts as superuser to store the submission — the same shape core uses for its own portal write, the one that updates delivery dates. The check is what proves the caller is entitled to this order. The superuser step is what lets a read-only user leave something behind. Doing the second without the first is how a portal becomes an open door.

Series The complete manual is at docs dot bambooforge dot dev, the demo database is linked from the store page, and support answers within twenty-four hours. Links are in the description.