Featured Project
Gibson Farms Custom Odoo ERP Workflow
A staff facing control layer for complex wholesale distribution rules inside Odoo.sh.
TrueSite built the product setup and pricing control layer of a custom Odoo.sh ERP workflow for Gibson Farms, replacing confusing native product fields with staff facing tabs, pricing references, customer type overrides, sale tools, future cost scheduling, warehouse foundations, histories, and diagnostics. The next integration phase connects those rules to live transaction workflows.
.png)
PROJECT SNAPSHOT
Timeline
Live client relationship
The public project showcases built Odoo.sh product and pricing controls while clearly treating deeper workflow integration as the next active phase.
Industry
Wholesale foodservice distribution
The system is shaped around distributor product rules, pricing behavior, warehouse handling, customer types, and future sales and invoice workflows.
Project Type
Custom Odoo.sh ERP workflow
TrueSite built a Gibson specific control layer using Odoo.sh, Python models, XML views, SCSS styling, histories, scheduled jobs, and test tools.
Capabilities
Wholesale pricing engine
The work translates case, each, pound, catch weight, fixed weight, sale, cost, override, and customer type logic into staff friendly controls.
PROJECT OVERVIEW
Wholesale rules
converted into controlled ERP workflow
Gibson Farms has product behavior that changes by selling unit, invoice basis, weight method, customer type, sale timing, market cost, and warehouse handling. TrueSite shaped those rules into an Odoo.sh control layer that staff can manage through purpose built tabs, validation, reference tables, history tools, and diagnostic tests instead of relying on scattered native ERP fields.
MAIN GOAL
Create a business system foundation that lets staff control complex wholesale product and pricing behavior with less confusion, stronger validation, and a clear path to sales, picking, invoices, inventory, purchasing, and ecommerce integration.
What TrueSite Built
TrueSite developed the Gibson specific Odoo.sh module structure, product entry workflow, pricing engine, customer type pricing preview, override history tools, sale controls, future market cost scheduling, warehouse location foundation, transaction history foundation, and pricing test runner.
1
Gibson Product Entry workflow
The product form was reorganized around internal setup tasks so staff can work from Gibson specific tabs instead of hunting through native ERP fields.
2
Selling units and weight setup
Toggle based controls support sold by case, sold by each, sold by pound, catch weight, and fixed weight combinations while blocking invalid setups.
3
Wholesale pricing engine
The pricing layer handles case cost, each cost, pound cost, cost plus, gross margin, case break fees, manual overrides, and valid selling setup math.
4
Customer type pricing and overrides
Staff can preview pricing across customer groups, apply product level customer type overrides, and see which rows are using special pricing logic.
5
Sale and market cost controls
The system supports time bound sales, sale history, future market cost scheduling, activation behavior, cleanup logic, and cost change history.
6
Pricing test runner and diagnostics
Automated pricing tests create temporary products, check core pricing scenarios, validate sale and future cost logic, and reduce regression risk.
PROJECT HIGHLIGHTS
Complex product behavior made usable
The interface turns distributor rules into plain staff controls that separate selling unit, invoice basis, price basis, weight method, and inventory behavior.
Staff friendly tabs
Invalid setup blocking
Plain language results
Pricing logic tied to operations
Case, each, pound, catch weight, and fixed weight products are handled as different operational behaviors instead of being forced into one generic price field.
Case and pound logic
Catch weight support
Fixed weight conversion
Histories built into the workflow
Override history, sale history, future cost history, and transaction foundations give the system an audit trail that supports operational review.
Override records
Sale history
Future cost logs
Foundation before transaction integration
The built rules layer prepares the next phase for sales orders, invoices, picking, actual weight capture, inventory, purchasing, and ecommerce.
Product rules layer
Pricing controls tested
Integration path defined