Peruvian companies that move goods are legally required to accompany every shipment with an electronic delivery guide (guia de remision electronica) that has been signed, transmitted to a certified provider, and acknowledged with a CDR before the truck leaves the yard. Odoo core will happily confirm a stock.picking and print a generic delivery slip, but it has no concept of a serie-correlativo fiscal numbering sequence, no UBL 2.1 guia document, no XML digital signature, no PSE/OSE transmission channel, and no SUNAT catalog logic for transfer reasons, transport modality, carrier data, or units of measure. Teams end up re-keying every shipment into a separate provider portal, which is slow, error-prone, and breaks the link between the warehouse operation and the fiscal record.

This is a productized service, not an off-the-shelf download. ECOSIRE builds a localization module that extends stock.picking with the full Peruvian guia data model: fiscal serie/correlativo sequences per warehouse, transfer motive (motivo de traslado), transport modality (public vs private), carrier and vehicle registration, driver license data, origin/destination addresses geocoded to ubigeo codes, gross weight, and per-line SUNAT unit-of-measure and product catalog mapping. On validation, an @api.depends-driven compute layer assembles the UBL 2.1 XML, applies the digital signature, and transmits it to your chosen PSE or OSE integration endpoint over its JSON/REST API. The returned CDR (constancia de recepcion) is parsed, stored against the picking, and surfaced as a state badge, with a QWeb PDF representation of the guia available for the driver.

Technically the build follows Odoo conventions end to end. New models and fields live in properly declared Python (models.Model, typed fields, compute/@api.depends for derived fiscal values), access is governed by ir.model.access.csv plus record rules so only warehouse and accounting roles can view or reissue guias, and the transmission runs through a resilient service layer with queued retries, structured logging, and idempotency keys so a network blip never produces a duplicate submission. Views are delivered as XML/OWL extensions of the picking form and a dedicated guia list/filter view; automated actions can trigger transmission on validation or hold it for manual review. Everything is exposed through Odoo's XML-RPC/JSON-RPC API so upstream systems or a headless WMS can drive the flow. We target Odoo 17.0, 18.0 and 19.0, and adapt to Community or Enterprise (Enterprise's accounting and studio hooks are used where present, never required).

Delivery is build-to-order. After a short scoping call we confirm your provider, fiscal series, warehouse topology and edge cases, then build on a staging instance with UAT before anything touches production. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); additional companies or branches, extra provider/carrier integrations, deeper SUNAT catalog coverage, and historical data migration volume increase the quoted scope. You receive a fixed quote after the scoping call, never a surprise invoice.