Selected work

Project 1 of 4

Backend ownership · Invoice systems & compliance · Zweidevs · 2025–2026

Tranero

I wrote Tranero’s backend, including its invoice, compliance, and support integrations.

Role
Backend owner at Zweidevs
Deliverable
Tranero’s backend, four invoice-system connectors, NRS integration, and Frappe Helpdesk ticketing
Focus
Invoice management · Compliance · Support
Live site

Overview

At Zweidevs, I wrote Tranero’s backend. The work connected account access, subscriptions, administrative APIs, and invoice-management workflows with Odoo, QuickBooks, ERPNext, and Microsoft Dynamics. I also built its Nigerian NRS integration and connected self-hosted Frappe Helpdesk for ticketing.

  • Python
  • Django
  • Invoice integrations
  • Nigerian NRS
  • Odoo
  • QuickBooks
  • ERPNext
  • Microsoft Dynamics
  • Frappe Helpdesk
Tranero's published dashboard preview showing ERP connections, invoice submission, and demo activityView full screenshot
Published product preview with demo data. My contribution: backend.Visit Tranero

Public product context

Tranero: invoicing, compliance, and API integration

Tranero · Public product pages · Inspected October 2026

The invoicing, API-integration, and compliance pages describe invoice creation and tracking, ERP connections, digital invoice formats, and tax-authority submission workflows. Their marketing performance and certification claims are not used as portfolio results.

testing.tranero.com

Visit the product site

Scope

Work completed and source material.

Scope and evidence

Scope and contribution.

This study describes the backend I owned and the integrations I implemented. The public product pages provide context for invoice management, ERP connections, and compliance workflows. Backend ownership and the named implementation scope are confirmed by me; the application source remains private. The public website is presented as product context rather than evidence of marketing-interface authorship.

  1. Backend ownership: I wrote Tranero’s backend at Zweidevs.

  2. Invoice-management scope: Odoo, QuickBooks, ERPNext, and Microsoft Dynamics integrations.

  3. Compliance and support scope: Nigerian NRS integration and self-hosted Frappe Helpdesk ticketing.

  4. Public product context: the invoicing page describes invoice creation, tracking, PDF/XML generation, and ERP integration.

  5. Public product context: the API and compliance pages show ERP-to-tax-authority workflows; the site currently uses FIRS terminology, while my implementation scope uses the NRS name I confirmed.

Problem

Main technical constraint.

Problem framing

One backend, several external workflows.

Invoice management needed to connect four business systems with a regulatory service, while account access, subscriptions, administration, and support ticketing remained part of the same product. Each integration had its own boundary and purpose.

Implementation

4 implementation steps.

Implementation

Own the product backend and its integration boundaries.

  1. Step1

    Implemented the backend supporting account access, subscriptions, administrative operations, and invoice-management workflows.

  2. Step2

    Built invoice-management integrations with Odoo, QuickBooks, ERPNext, and Microsoft Dynamics.

  3. Step3

    Integrated the Nigerian NRS service into Tranero’s compliance workflow.

  4. Step4

    Connected the self-hosted Frappe Helpdesk ticketing system to support the product’s support workflow.

Result

A complete backend ownership scope.

My contribution covered Tranero’s backend and the named invoice, NRS, and ticketing integrations. The public site gives reviewers a product to inspect; the contribution map shows my implementation scope without publishing private source or client records.

What I learned

The central engineering responsibility was owning the backend across invoice systems, regulatory integration, administration, and support, rather than delivering a single isolated connector.