What did Brainvire deliver for Ecommerce Accounting?

The client desires full Odoo accounting implementation with Saudi localization and integration with their unique e-commerce platform and drop shipping business strategy.

What results did the Ecommerce Accounting project achieve?

Clear Idea of Accounts; Easy Multi-store Management; Consolidated Vendor-Customer data.

What industry does the Ecommerce Accounting case study cover?

Retail. Browse more Retail work in the Brainvire case study library.

Home / Case Studies / Ecommerce Accounting

/ Case Study · Retail

Odoo Accounting for a Custom Ecommerce Platform. Saudi Localization, Built In.

/ The engagement

Odoo Accounting, Wired to a Custom Store.

A full Odoo accounting implementation with Saudi localization, connected to the client's in-house ecommerce platform and drop-shipping flow, with a hierarchical chart of accounts and automated data creation.

Odoo AccountingSaudi LocalizationREST APIDrop Shipping

OdooFull accounting suite implemented

KSASaudi localization built in

REST APICustom ecommerce platform connected

AutomatedChart of accounts and data

/ About the client

Ecommerce Accounting

The client is an expanding software company known for expertly staffed teams building high-caliber, industry-standard applications for customers worldwide, serving large corporations, SMEs, and startups from planning through development and beyond.

They wanted a full Odoo accounting implementation with Saudi localization, tied to their own ecommerce platform and drop-shipping strategy. Brainvire delivered it with a hierarchical chart of accounts and automatic data production.

/ The approach

Design, architecture, and features, shipped as one program.

/01Accounts

A chart with hierarchy

We built a hierarchy-wise chart of accounts that honors KSA local rules, so the books reflect Saudi accounting requirements out of the box.

/02Integration

Store meets Odoo

Postman REST APIs connect the client's custom ecommerce platform to the Odoo database, so orders and records flow between the two systems.

/03Data

Created, not keyed

Automated data creation brings proprietary ecommerce data, including vendor and customer details, into Odoo without manual entry.

/04Payments

Vendors and commission split

We modified the journal entry to place vendor payments in the expense account and commission in the income account, matching how the business actually runs.

/ What stood in the way

Four problems, solved without a maintenance window.

Select a challenge to see how it shaped the build.

/01 Hierarchical chart of accounts →

/02 Custom ecommerce integration →

/03 Automated data creation →

/04 Vendor payment and commission →

Hierarchical chart of accounts

The client needed a hierarchy-wise chart of accounts with KSA localization. We built one that considers the local rules in Saudi Arabia.

Custom ecommerce integration

Their custom-built ecommerce platform had to talk to Odoo. We used Postman REST APIs to connect the platform to the Odoo database.

Automated data creation

Data had to appear in Odoo without manual keying. We added automated data creation that pulls proprietary ecommerce data, including vendors and customers, into the system.

Vendor payment and commission

Vendor payments and commissions were tangled in a single entry. We split the journal entry so payments hit the expense account and commission hits the income account.

/ Product screens