Chatten Sie auf WhatsApp

Produktdetails werden auf Englisch angezeigt. Übersetzungen folgen in Kürze.

Preis: $249.00 USD
Odoo-Versionen: 17, 18, 19
Rüstzeit: 30 Min
Lizenz: Einmalig und unbefristet
Sprachen: 11 Sprachen

Einmalkauf

Guias Electronicas Peru - PSE/OSE Integration

Name: Guias Electronicas Peru - PSE/OSE Integration
Brand: ECOSIRE
SKU: guias-electronicas-peru-pse-ose-nubefact

A build-to-order Odoo module that generates, signs and transmits Peru's electronic delivery guides (guias de remision electronicas) through a PSE/OSE provider, then tracks CDR acceptance back on the stock picking. ECOSIRE builds it to your exact fiscal setup, installs it, and supports it after go-live.

$249.00USD

Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.

Hauptfunktionen

Extends `stock.picking` with the full guia de remision electronica data model (serie, correlativo, motivo de traslado, modalidad de transporte)

Fiscal `serie`/`correlativo` sequence generation per warehouse using dedicated `ir.sequence` records with gap-free correlativo control

UBL 2.1 XML assembly for the electronic delivery guide, built via a compute layer with `@api.depends` on picking, carrier and address fields

XML digital signature application before transmission, with certificate configuration held in encrypted system parameters

PSE/OSE transmission over the provider's JSON/REST endpoint with idempotency keys to prevent duplicate guias

CDR (constancia de recepcion) parsing, storage against the picking, and status badge (draft / signed / sent / accepted / rejected)

SUNAT catalog mapping: transfer reasons, transport modality, units of measure, and document types resolved per line

Carrier, vehicle registration, driver license and ubigeo origin/destination fields with validation constraints

QWeb PDF representation of the guia for the driver, including the CDR reference and QR code

Queued retry service layer with structured logging so transient network or provider failures self-recover

Automated action to transmit on picking validation, or hold for manual review by an accounting role

`ir.model.access.csv` plus record rules restricting guia view/reissue to warehouse and accounting groups

Reissue / annulment (comunicacion de baja) workflow for rejected or superseded guias

XML-RPC/JSON-RPC exposure so an external WMS or portal can trigger and read guia state

Multi-company aware sequences and configuration for groups operating several RUC entities

Über dieses Produkt

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.

Warum Guias Electronicas Peru - PSE/OSE Integration wählen

Extends `stock.picking` with the full guia de remision electronica data model (serie, correlativo, motivo de traslado, modalidad de transporte)

Fiscal `serie`/`correlativo` sequence generation per warehouse using dedicated `ir.sequence` records with gap-free correlativo control

UBL 2.1 XML assembly for the electronic delivery guide, built via a compute layer with `@api.depends` on picking, carrier and address fields

XML digital signature application before transmission, with certificate configuration held in encrypted system parameters

PSE/OSE transmission over the provider's JSON/REST endpoint with idempotency keys to prevent duplicate guias

CDR (constancia de recepcion) parsing, storage against the picking, and status badge (draft / signed / sent / accepted / rejected)

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 2-4 weeks from confirmed scope. Pricing starts from $249 (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.

Was Sie bekommen

Installable source code of your version of the module, packaged as a standard Odoo addon with `__manifest__.py`
Installation and configuration on your instance (provider credentials, certificate, fiscal series, warehouse mapping)
Technical documentation: model/field reference, security model, transmission flow and configuration guide
End-user guide plus a live training session for warehouse and accounting staff
Post-go-live support window for defect fixes and configuration adjustments
UAT on a staging instance with a documented rollback plan before production cutover
Private git repository handover with full commit history and tagged release
SUNAT catalog and mapping reference sheet specific to your product and route set

Für wen das ist

Warehouse & Logistics Manager

Runs daily dispatch and needs every shipment to leave with a valid, provider-accepted guia de remision without re-keying data into a separate portal. Wants transmission and CDR status visible directly on the Odoo picking.

Accounting / Fiscal Compliance Lead

Accountable to SUNAT for correct fiscal numbering, transfer motives and annulments. Needs correlativo control, audit trail, and a clean reissue/baja workflow inside the same ERP their invoicing lives in.

IT / Odoo Administrator

Owns the Odoo instance and wants a maintainable localization addon that follows Odoo conventions (ORM, security CSV, XML views) rather than portal copy-paste, with an API surface and a git repo they can extend.

Finance Director / ERP Owner

Sponsors the project and wants a fixed-scope quote, a predictable 2-4 week delivery, and confidence that the Peru delivery-guide obligation is handled end to end across their company or group of RUC entities.

Installationsübersicht

Von ECOSIRE herunterladen
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei des Guias Electronicas Peru - PSE/OSE Integration-Moduls von Ihrem Konto-Dashboard herunter.
Auf Odoo hochladen
Extrahieren Sie die ZIP-Datei in Ihren Odoo-Ordner für benutzerdefinierte Add-ons auf dem Server (oder laden Sie sie über „Apps“ > „Aus Datei installieren“ auf Odoo.sh/Runbot hoch).
Installieren Sie das Modul
Aktivieren Sie den Entwicklermodus, öffnen Sie „Apps“, klicken Sie auf „Apps-Liste aktualisieren“, suchen Sie nach „Guias Electronicas Peru - PSE/OSE Integration“ und klicken Sie auf „Installieren“.
Einstellungen konfigurieren
Öffnen Sie das neue Menü, fügen Sie Ihren ECOSIRE-Lizenzschlüssel ein, verbinden Sie alle externen Anmeldeinformationen (Shopify, Amazon, Stripe usw.) und speichern Sie.
Verifizieren und live gehen
Führen Sie den integrierten Verbindungstest aus, synchronisieren Sie Ihre ersten 10 Datensätze und planen Sie den wiederkehrenden Cron. Wenden Sie sich an den Support, wenn etwas fehlschlägt.

Wie Guias Electronicas Peru - PSE/OSE Integration im Vergleich abschneidet

Kriterium	ECOSIRE	Benutzerdefinierter Build	Konkurrent
Peru electronic delivery guide (guia de remision)	Full UBL 2.1 guia built, signed and transmitted from the picking	Possible but you design the whole fiscal model yourself	Generic coverage, often not matched to your provider or routes
Fiscal serie/correlativo numbering	Gap-free per-warehouse sequences with reissue control	Hand-built sequences, easy to get correlativo logic wrong	Basic sequence, rarely warehouse-aware
PSE/OSE transmission & CDR	Provider JSON/REST integration with idempotent retries and CDR parsing	You build and maintain the integration and retry logic	Fixed to specific providers, limited retry handling
SUNAT catalog mapping	Transfer reasons, modality, UoM and product catalogs mapped to your data	Mapped manually during your own project	Partial catalogs, may need extra configuration
Fit to your setup	Built to your provider, series, RUC entities and edge cases	Fully bespoke but at full bespoke cost and timeline	One-size-fits-all, you adapt your process to it
Delivery & timeline	2-4 weeks from confirmed scope, UAT on staging	Often months depending on in-house capacity	Instant install but then long configuration and fixes
Support & ownership	Post-go-live support window plus full git repo handover	You own all maintenance	Vendor support varies; you rarely get the source
Cost model	Indicative from $249, fixed quote after scoping	High bespoke development cost	Low license fee plus hidden integration effort

Häufig gestellte Fragen zu Guias Electronicas Peru - PSE/OSE Integration

Is this an existing app I can download and install today?

No. It is a build-to-order service. ECOSIRE builds the module to match your PSE/OSE provider, fiscal series, warehouse setup and edge cases, then installs and supports it. You are not buying a pre-existing marketplace download.

How long does delivery take?

Typical delivery is 2-4 weeks from confirmed scope. After the scoping call we agree the exact data model, provider integration and warehouse mapping, then build on staging with UAT before the production cutover. Larger multi-company or migration work can extend the timeline, which we state in the quote.

How does pricing and scoping work?

Pricing starts from $249 as an indicative single-company base scope. The final figure is a fixed quote issued after a short scoping call, once we know your provider, number of RUC entities and branches, catalog depth and any data migration. There is no firm price before scoping and no surprise invoice after.

What about support and updates after go-live?

Every build includes a post-go-live support window for defect fixes and configuration adjustments. Because you receive the full source in a git repository, your team can maintain it, and ECOSIRE offers ongoing support and version upgrades (for example moving from Odoo 17 to 18 or 19) as a separate engagement.

Which Odoo versions and editions are supported?

We build for Odoo 17.0, 18.0 and 19.0, on Community or Enterprise. The module uses standard ORM, `ir.model.access.csv` security and XML/OWL views so it works on Community; where Enterprise accounting hooks exist we use them, but they are never required.

Do you support our specific PSE or OSE provider?

Yes. The transmission layer is built against your chosen certified provider's JSON/REST API, including its authentication, signing and CDR-return format. If you later switch providers, adapting the integration is a scoped change rather than a rebuild.

How do you prevent duplicate guias or lost transmissions?

The transmission service uses idempotency keys and a queued retry mechanism with structured logging. A network blip or provider timeout retries safely without generating a second correlativo, and every attempt and CDR response is recorded against the picking for audit.

Angebot anfordern