Case Study · E-Comm

Building a WooCommerce Trade Store Connected to Odoo

Build in progress

A B2B commerce build in progress, connecting WooCommerce ordering with Odoo.

In progress

Website build

WooCommerce

Storefront

Odoo

Stock and pricing source

Client

Sow Easy

Industry
B2B Distribution
Services
WooCommerce Website DevelopmentOdoo IntegrationTrade OrderingSEOAI Search
BB

Bhavesh: Founder, FactoryJet

Hi, I'm Bhavesh, founder of FactoryJet. I run every discovery call myself, so by minute 10 we already know whether what you need pays for itself, and how fast.

In short

The Sow Easy project in four lines.

FactoryJet is building Sow Easy’s B2B ecommerce website on WooCommerce, with Odoo integration for stock, pricing, and product identifiers. Website development, SEO, and AI search work are ongoing.

Client
Sow Easy, a B2B distributor that sells to trade buyers and runs its stock, pricing and product data in Odoo.
Problem
Trade buyers need accurate stock, account pricing and ordering online, and the team cannot keep a second, conflicting copy of that data in the website.
What we built
A WooCommerce trade store that reads stock, pricing and SKUs from Odoo, with trade ordering and product pages, plus SEO and AI search work alongside the build.
Status
Build in progress. The store and the Odoo link are being tested on staging, and launch is still ahead.

Last updated

At a glance

The vitals.

  • STATUS

    Build in progress

  • PLATFORM

    WooCommerce

  • ERP

    Odoo

  • SERVICES

    Website + SEO + AI Search

The Challenge

The problem to solve.

Trade buyers need product information, account pricing, and ordering tools that reflect the systems used by the supplier. The store also needs to support the team managing products and orders without creating conflicting copies of stock and price data.

Our Approach

How we approached it.

The current project uses WooCommerce for the storefront and Odoo as the source of stock, pricing, and SKU data. Development and validation take place on staging before launch. The work includes product presentation, trade ordering, and the integration between the store and ERP.

What We Built

What we built.

FactoryJet is implementing the website and its commerce workflows while testing product data and ordering behavior against Odoo staging. SEO and AI search work run alongside the build. The public case study describes the current engagement, rather than treating staging functionality as a completed launch.

Results

Results and where it stands.

The website build is in progress. Launch results, traffic changes, and sales outcomes are not reported for this unfinished build.

Want results like this?

BB

Bhavesh: Founder, FactoryJet

“If your trade store needs to work with an existing ERP, we can scope the storefront and integration together. Hi, I'm Bhavesh, founder of FactoryJet. I run every discovery call myself, so by minute 10 we already know whether what you need pays for itself, and how fast.”

Services on this project

The services behind the Sow Easy work.

Frequently asked

Questions about the Sow Easy project.

Is the Sow Easy website build complete?

The build is in progress. FactoryJet is developing and testing the WooCommerce website and Odoo integration on staging, alongside ongoing SEO and AI search work.

Which system owns stock and pricing?

Odoo is the source of stock, pricing, and SKU data in the current project. WooCommerce uses that data in the storefront rather than becoming a separate source of truth.

Does this case study report sales results?

No. It describes an active implementation. It does not present staging activity as customer sales or claim a completed launch.

Why connect WooCommerce to Odoo instead of managing stock in WooCommerce?

Because two places that both hold stock and prices will drift apart. If Odoo already runs purchasing, stock and accounts, it should stay the single source. The store reads from it, so a price or stock change made in Odoo shows up on the website without anyone retyping it.

Why test the integration on staging first?

An ERP link touches real stock and real prices. Testing against Odoo’s staging system lets us check product data, prices and orders end to end without affecting live stock or sending real orders into the business.

What does a B2B WooCommerce store need that a retail store does not?

Trade pricing per account, larger order quantities, reorder from past orders, and often quotes before orders. Retail WooCommerce shows one price to everyone and expects a quick card checkout, which does not match how trade buyers purchase.

Does FactoryJet work with other ERPs besides Odoo?

Yes. FactoryJet has worked on Odoo, NetSuite, SAP Business One, ERPNext and custom ERPs. The approach is the same: decide which system owns each piece of data, and make every other system read from it.

When will results be published for Sow Easy?

After launch, once the store has been live long enough to measure. Until then this page describes the work in progress and does not report sales or traffic.

Free quote
Founder replies in 24h