Inbound ASN & Supplier Receiving Portal for Odoo

This is where native Odoo runs out of road, and it is exactly what we build. ECOSIRE delivers a custom Odoo module that introduces a first-class ASN document. A new stock.asn model (with stock.asn.line children) is authored the Odoo way — models.Model, typed fields, and @api.depends computes for received-vs-expected roll-ups and short/over flags. Suppliers log into the standard Odoo portal (extending portal.mixin and the /my controller routes) to submit an ASN against an open purchase order: they declare quantities, lot/serial numbers, expected arrival date, carrier, and pallet/license-plate structure. Every ASN gets an expected-receipt date that feeds a dock-planning view (calendar and Gantt on Enterprise, list/kanban fallback on Community) so your team sees the inbound wave before it arrives. Access is locked down with ir.model.access.csv plus ir.rule record rules so a portal supplier only ever sees their own ASNs, never another vendor's.

At the dock, receiving flips from "count against the PO" to "verify against the ASN." We extend the incoming stock.picking / stock.move.line flow (and the OWL Barcode client where you use it) so a receiver scans each carton or pallet barcode and the system matches it to the declared ASN line in real time — green when it matches, a blocking discrepancy prompt when the scanned quantity, lot, or SKU does not. Short and over receipts are captured as structured data on the ASN line at the moment of receipt, not reconstructed afterward, and can trigger an automated action (base.automation) to notify purchasing or open an activity. License-plate/pallet receiving lets a single scan of a pallet ID confirm all the cartons declared on it, and a QWeb PDF gives you a receiving discrepancy report and a printable pallet manifest. Where you want machine-to-machine integration — a 3PL or supplier WMS pushing ASNs — the same models are exposed over Odoo's XML-RPC / JSON-RPC API so an ASN can be created programmatically instead of through the portal.

Because this is build-to-order, nothing ships until we agree on scope. After a short scoping call we confirm your Odoo version (17.0, 18.0, or 19.0), Community vs Enterprise, your PO and inbound workflow, and which capabilities you actually need. ECOSIRE then builds the module against your edition, validates it on a staging copy of your database through UAT, and installs it in production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. You receive the full installable source, documentation, a training session, and a post-go-live support window — plus the git repository, so the code is yours.