Once you run more than one carrier in Odoo, the same configuration gets duplicated everywhere. Each shipping connector re-declares its own credential fields, its own packaging mappings, its own weight-and-dimension logic, and its own error handling on stock.picking. Native Odoo delivery.carrier gives you a delivery method and a price rule, but it was never meant to be a shared services layer — so multi-carrier estates end up with five slightly different ways of storing an API key, three incompatible weight-unit conversions, and no common place to log a rate request or a label failure. Maintenance cost grows with every carrier you add.

Base Shipping Partner is the framework layer ECOSIRE builds to sit underneath your carrier connectors and hold everything they have in common. Technically it ships as an Odoo module that extends delivery.carrier and res.company with a shared configuration model (credentials, environment toggle for test vs production, account/merchant identifiers, default package types), a reusable weight/dimension normalization service, and a common request/response logging model so every carrier call — rate, label, tracking, cancellation — writes to one auditable place. Connectors depend on this base via __manifest__.py depends, call its abstract helper methods instead of reimplementing them, and inherit its security. Access is governed by ir.model.access.csv plus record rules that keep carrier credentials scoped per company, and configuration is surfaced through clean settings views (XML/OWL) rather than scattered technical fields.

Because it is a base, it is deliberately generic: it standardizes how a carrier stores a shared secret, how packages map to carrier package codes, how service levels are represented, and how the outbound API layer (built on Odoo's HTTP/JSON tooling, exposable over XML-RPC/JSON-RPC for external systems) reports success and failure. Individual carrier modules — whether we build them for you next or you write them yourself — then implement only the carrier-specific translation, keeping each connector small and testable. Compute fields with @api.depends keep derived values like billable weight and dimensional weight consistent across every method, and automated actions can flag stale credentials or repeated rate failures for review.

Delivery is build-to-order. After a short scoping call we confirm which carriers and versions this base must support, agree the configuration surface, and write a fixed quote. We develop against your Odoo edition (Community or Enterprise) and version, deliver on a staging database for UAT, then install to production with a rollback plan and hand over the git repository. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company credential isolation, additional carrier connectors built on top, and deeper integration with an existing shipping estate increase the quoted scope.