Skip to Content
Custom Engineering

Custom Engineering / Nimex Solutions

Business Partner Portals

Dealers and corporate customers should not have to phone in every order. Nimex builds portals on Odoo where partners quote, order and follow up at their own prices and terms, and everything they do lands in the same sales, delivery and invoice records the back office works with.

The problem

The public shop shows everyone the same prices; dealers are not everyone.

A wholesaler’s dealers buy at negotiated prices and terms, from a catalogue limited to what they may sell. Odoo’s customer portal lets them see quotations and invoices, and eCommerce sells to anyone — but neither gives a dealer a private catalogue, a tier with its own pricelist and terms, and a way to build and confirm a quotation alone.

So orders arrive by e-mail and phone, the sales team re-keys them, and the dealer still calls to ask what is open, what is unpaid and what is overdue.

What we engineered

A partner layer in the back office, a portal in front of it.

  • Partner programs

    Benefits, default pricelist, payment term, currency, credit-limit field, product, warehouse and company scopes, and the portal features each tier may use.

  • Partner profiles

    One per dealer: program, state, partner manager, portal users, last login and login count, pricelist, terms and scopes, with KPIs mirrored on the contact.

  • Catalogue and prices

    Products restricted per partner in bulk (add, remove, replace); dealer price tiers generated as formula rules from a reference pricelist, a discount and a minimum quantity.

  • Dashboard

    KPIs from live records — open quotations, open orders, unpaid and overdue invoices — and the order statistics split into waiting, confirmed and cancelled.

  • Quote builder

    Delivery address, filtered catalogue with attribute filters and partner prices, preview, confirm: the draft sales order is created or kept in sync; the quotes list confirms it into a Sales Order.

  • Closed and logged

    Standard quotation routes are blocked for partner users; every portal action is written to an audit log with IP and user agent; manager and admin groups with record rules.

How it works

From a partner profile to a confirmed order.

  1. Define the programs

    Silver, Gold or any tiers you need, each with its default pricelist, payment term and allowed portal features.

  2. Create the partner profile

    Program, partner manager, portal users, pricelist, terms, allowed categories and warehouses; Set Active opens the portal.

  3. Shape the catalogue

    Allow products per partner from the product list and generate the tier’s price rules in one action.

  4. The dealer signs in

    The dashboard shows open quotations, open orders, unpaid and overdue amounts, and the order statistics.

  5. Build the quotation

    Address, products at partner prices, preview with lines, totals, address and payment term, then Confirm: a draft sales order is created in Odoo.

  6. Confirm the order

    From the quotes list (sort, filter, search, last invoice link) the dealer confirms the quotation and it becomes a Sales Order.

  7. Back office follows

    Delivery and invoicing run on the standard order; the profile’s KPIs update and the audit log records each step.

Another portal pattern

Customer order links: a portal without a login.

For a contract caterer’s corporate customers, the right portal was no portal at all: a secret, bilingual link to tomorrow’s order, opened from the phone. The customer changes quantities, cancels a day or marks days off until the deadline; Odoo keeps the quotation in step, creates the delivery and bundles every delivered day into one weekly invoice per customer.

Odoo 18. Links can be sent over WhatsApp through the WhatsApp Web protocol, not the official Business API.

Explore catering operations

Integration points

The portal is a window onto standard records.

Chat with us