Auto
Skip to Content

End-to-End Automation in Pickle Manufacturing: The Odoo ERP Journey of HOME Made Love

HOME Made Love: Odoo ERP for Pickle Making | KoderXpert

Food manufacturing · Odoo ERP, farm to jar

HOME Made Love: every jar, batch and channel, preserved in one ERP

secret recipes, now with secret-proof BOMs ✨

HOME Made Love crafts preservative-free pickles and condiments with traditional recipes, sold across retail, a D2C website, Amazon and Shopify. Every variant has its own recipe; every channel had its own chaos. KoderXpert delivered end-to-end Odoo automation: from variant BOMs and batch traceability to GST-ready books.

A pickle kitchen with jars on a shelf, a steaming mixing pot with a swaying spoon, a recipe BOM card and a channel-sync flow, representing the Odoo ERP built for HOME Made Love BOM: mango
the kitchen scales, the love stays ✨
wow!0%variant BOM coverage: every pickle, its exact recipe
0%+inventory turnover gain from batch & expiry tracking
0sales channels synced to one live stock
0Odoo modules covering the whole business
Client
HOME Made Love
Industry
Food manufacturing: pickles & condiments
Platform
Odoo ERP + Amazon, Shopify & Tally
Implementation partner
KoderXpert Technologies
Headline result
25%+ inventory turnover gain

01 · Overview

The 30-second version

  • HOME Made Love makes authentic, preservative-free pickles and condiments with traditional recipes, selling across retail, a D2C website, Amazon and Shopify simultaneously.
  • Rapid growth met complex operations: recipes differed per variant but lived outside any system, marketplace orders were processed by hand, finances sat siloed in Tally, and HR ran on paper.
  • KoderXpert delivered end-to-end automation on 10 Odoo modules: variant-specific BOMs, batch-wise production with FEFO and expiry alerts, Amazon and Shopify connectors with GST auto-invoicing, a full Tally migration and live dashboards.

02 · Pain points before Odoo

What was going wrong before Odoo?

Six ways growth was outrunning the kitchen

A premium brand scaling fast across SKUs, batch variants and channels, on manual systems that treated every new order and recipe as extra chaos.

No variant-specific BOMs

Recipes differed per pickle variant but were managed manually, with no system tracking raw materials by SKU.

The cost → over-ordering & waste

Manual multi-channel orders

Amazon and Shopify orders were processed by hand with no inventory sync.

The cost → overselling & delays

Disconnected Tally accounting

Financial data lived in Tally, completely siloed from operations; reconciling sales, inventory and accounts was manual and error-prone.

The cost → books always behind the business

No batch or expiry control

Batch tracking and shelf-life management for a food product handled informally.

The cost → stock spoiling silently

Unstructured HR processes

Employee records, leave and attendance managed outside any integrated system.

The cost → HR running on paper

No live dashboards

Production, inventory and sales performance invisible until someone compiled it.

The cost → decisions on stale data
multi-channel + manufacturing + manual = the spiciest chaos…

03 · The turnaround

Drag it and see the before & after yourself

Slide the orange handle. Left is the manual, siloed era, right is the automated kitchen.

✗ Before Odoo
  • ✗ Recipes per variant tracked by memory & sheets
  • ✗ Amazon & Shopify orders keyed in by hand
  • ✗ Tally books siloed from operations
  • ✗ Expiry & batches managed informally
  • ✗ HR records outside any system

the manual era 😵

one automated kitchen ✨

✔ After Odoo ERP
  • ✔ Every variant resolves to its exact BOM
  • ✔ Orders auto-sync with GST invoices & live stock
  • ✔ One set of GST-ready books, migrated from Tally
  • ✔ FEFO rotation with automated expiry alerts
  • ✔ HR, leaves, attendance & payroll integrated

← drag toward the chaos · drag toward the automation →

04 · The plan

What "fixed" had to actually mean

Six outcomes agreed with HOME Made Love before the build began. Hover any goal to tick it off.

Recipe integrity: a unique, system-managed BOM for every pickle variant.

Channel automation: Amazon, Shopify and D2C orders syncing without manual entry.

One set of books: a clean Tally-to-Odoo migration with GST-compliant accounts.

Food-safe traceability: batch tracking, FEFO rotation and expiry alerts.

People on the platform: HR, attendance, leave and payroll integrated.

Day-one insight: real-time dashboards across production, inventory and sales.

05 · What we delivered

What did KoderXpert build?

Six capabilities, one connected kitchen

Full Odoo module coverage: Sales, Purchase, Inventory, Manufacturing, Accounting, HR & Payroll, plus Amazon, Shopify, Tally migration and custom dashboards.

Block 01

Variant-specific BOMs

Each pickle variant (mango, lemon, garlic and more) carries a unique bill of materials: ingredients, quantities and spice ratios tracked per SKU, eliminating guesswork and over-procurement.

every recipe, exact
Block 02

Batch-wise production & traceability

Production orders run batch by batch with full raw-material-lot to finished-product traceability, FEFO rotation and automated expiry alerts, critical for food safety and recalls.

from lot to jar, accountable
Block 03

Work centres & routing

Washing, mixing, bottling and labeling mapped as operations across work centres with time estimates, powering MRP-driven demand forecasts from confirmed orders and reorder rules.

peak season without stockouts
Block 04

Amazon & Shopify connectors

Orders sync in real time to Odoo Sales, inventory deducts on confirmation, and GST invoices auto-generate with correct HSN codes across channels.

channels that run themselves
Block 05

Tally-to-Odoo GST migration

Ledgers, vouchers and balances extracted, cleaned and imported; chart of accounts rebuilt with GST tax groups; multi-rate HSN auto-selection and GSTR-1/GSTR-3B data ready for direct filing.

GST-ready from day one
Block 06

HR & live dashboards

Employees, leave, attendance and payroll on the same platform, with real-time KPI dashboards across production, inventory, sales and receivables.

the whole brand, one screen
marketplace orderrecipe BOMbatch + FEFOGST invoicelive books
an Amazon order cooks, ships and books itself ✨

06 · Functional deep dive

How the automated kitchen actually works

The delivery summary says what was automated. This is the functional detail underneath: how a recipe becomes a BOM, how a batch stays safe and traceable, and how four channels bill correctly by themselves.

Recipes as variant BOMs

Every pickle variant (mango, lemon, garlic and more) carries a unique, system-managed bill of materials.

  • Per-SKU ingredients: quantities and spice ratios are locked per variant, so procurement and production follow the exact recipe, not memory.
  • MRP from demand: confirmed orders and reorder rules drive material requirements, so peak season arrives without stockouts or panic buying.
  • Work centres & routing: washing, mixing, bottling and labeling run as timed operations, making capacity and bottlenecks visible.

Batch discipline: FEFO, expiry, recall

Food safety runs on structure, not vigilance.

  • Lot-to-jar traceability: every raw-material lot maps to the finished batches it entered, so a recall query answers in minutes.
  • FEFO rotation: first-expired-first-out picking is enforced by the system, with expiry alerts driving priority dispatch before stock spoils.
  • Batch-wise production: each run carries its own quality and date data, keeping shelf-life management out of people's heads.

Marketplace sync & GST invoicing

Amazon, Shopify, D2C and retail sell from one live stock and bill themselves correctly.

  • Real-time order sync: marketplace orders land in Odoo Sales automatically and deduct inventory on confirmation, ending overselling.
  • GST auto-invoicing: invoices generate with correct HSN codes and IGST/CGST/SGST splitting per transaction, channel by channel.
  • Channel analytics: sales performance by channel reads from the same records, so pricing and promotion decisions use live data.

One set of GST-ready books

The Tally-to-Odoo migration turned siloed bookkeeping into books that keep themselves.

  • Rebuilt chart with GST groups: multi-rate HSN auto-selection applies the right tax without user choices.
  • Filing-ready data: GSTR-1 and GSTR-3B figures assemble from live transactions, ready for direct filing.
  • Live financial visibility: receivables, cash flow and P&L update with every order, ending month-end surprises, alongside HR, attendance and payroll on the same platform.
every variantlocked reciperight materialsthe recipe leaves nobody's head

Recipes as system-managed BOMs

Mango, lemon, garlic: each variant carries its own bill of materials with ingredients and spice ratios locked per SKU. Confirmed demand pulls exact material requirements, so peak season arrives without stockouts or panic buying.

07 · How we built it

How was the Odoo project delivered?

From family recipes to a 7-phase rollout

A structured delivery journey, compressed into the six moves that mattered, from process mapping to hypercare.

1

Requirement gathering taste the process

Process mapping and gap analysis across manufacturing, channels, accounting and HR.

2

Manufacturing setup write down the recipes

Variant BOMs, work centres, routings and batch production configured for every SKU.

3

Data migration & cleanup move the pantry

Tally and Excel data extracted, deduplicated, GST-aligned and imported with opening balances intact.

4

Channel integration plug in the shops

Amazon and Shopify connected: order sync, stock deduction and GST auto-invoicing.

5

Training & SOPs train the kitchen

Team onboarding with SOPs, driving high user adoption across departments.

6

Go-live & hypercare serve it fresh

Supported go-live with post-launch hypercare and dashboards live from day one.

08 · Engineering notes

The technical decisions behind the automation

For the technically curious: how the work was engineered so it survives upgrades, audits and time.

Custom addons, zero core edits

Everything KoderXpert built lives in namespaced custom modules (kx_recipe_bom · kx_batch_fefo · kx_channel_gst · kx_tally_bridge) on Python and the Odoo ORM.

  • Inheritance, not modification: models and views are extended through Odoo's inheritance mechanisms, never edited in core, so future Odoo upgrades do not bury the work.
  • Configuration as data: variant matrices, FEFO rules, tax groups with HSN mappings and connector settings ship as XML data records, reproducible and reviewable.
  • PostgreSQL underneath: one database as the single source of truth, so no exports or reconciliation jobs exist between the moving parts.

The data migration pipeline

The riskiest part of the project was the data: Tally ledgers, vouchers and balances plus Excel stock and recipe sheets. It moved through a staged pipeline, not a bulk import.

  • Extract & cleanse: legacy records exported, deduplicated and normalized in a staging environment before anything touched production.
  • Ordered loading: imports run in dependency order: chart of accounts with GST groups, products with variants, opening stock as dated lots, then open receivables and payables, via the ORM with opening balances posted as auditable entries.
  • Verified before sign-off: record counts and key balances checked against the source system, with every opening figure posted as an auditable entry.

Reports, automation & performance

Dashboards and documents are native Odoo artifacts reading live data, so they inherit access rules and never go stale.

  • QWeb & OWL: printable documents render through QWeb templates; on-screen dashboards read aggregated, indexed queries that stay fast as volume grows.
  • Scheduled automation: scheduled jobs pull marketplace orders, refresh expiry alerts and channel dashboards, and snapshot inventory turnover metrics.
  • Filters built in: period, location and team filters are part of the report definitions, so answering a leadership question is one click, not a new spreadsheet.

Testing, cutover & hardening

The rollout landed on a live business, so it was engineered to be boring.

  • Staging mirror: every change proven on a copy of the real database before reaching production.
  • Role-based UAT: production, dispatch, accounts and the online team walked scripted scenarios end to end, including a full marketplace-order-to-GST-invoice cycle, before go-live with post-launch hypercare.
  • Access hardening: group permissions and record rules reviewed role by role, so each team sees exactly what its job requires.
  • Documented handover: configuration, roles and workflows documented so the system's logic belongs to the client, not to anyone's memory.
dated batchFEFO pickingexpiry alertsrecalls answer in minutes

Batches that rotate themselves

Every jar belongs to a dated batch mapped back to its raw-material lots. First-expired-first-out picking is enforced by the system and expiry alerts drive priority dispatch, which is where the 25%+ inventory turnover gain lives.

09 · The impact

What changed after go-live?

The results, in numbers

the part clients screenshot ↓
0%+inventory turnover gain from batch & expiry tracking
0%real-time financial visibility: receivables, cash flow & P&L
0%FEFO batch rotation policy applied
GSTR-1 & -3B data ready for direct filing
  • Every variant's raw materials tracked by SKU, ending over-ordering
  • Orders from Amazon, Shopify, D2C & retail on one live stock
  • GST invoices auto-generated with correct HSN codes
  • Expiry alerts driving priority dispatch before stock spoils
  • HR, attendance and payroll integrated with operations
  • Live receivables, cash flow and P&L with no month-end surprises

10 · Under the hood

Technologies & core skills

Backend · Python 3, Odoo ORM (variant engine, FEFO rules, MRP) Frontend · XML views, QWeb templates, OWL (JavaScript), HTML5, CSS3 Database · PostgreSQL (lot-indexed inventory, one source of truth) Integrations · Amazon Connector · Shopify Connector · Tally migration bridge Tax engine · GST groups, multi-rate HSN auto-selection, GSTR-1/3B data Reports · channel dashboards, expiry & turnover analytics, QWeb documents Automation · order-sync crons, expiry alerts, dashboard snapshots DevOps · Git version control · dev → staging → production · HTTPS behind reverse proxy Custom addons · kx_recipe_bom · kx_batch_fefo · kx_channel_gst · kx_tally_bridge
Food manufacturing ERP Variant BOM design Batch & shelf-life management Marketplace integration GST accounting migration HR & payroll integration
straight from the project lead ✨
"Partnering with KoderXpert Technologies for our Odoo ERP implementation was one of the best decisions we have made. Their team understood our unique challenges as a food manufacturing brand and delivered a solution that truly fits our business. Everything now runs smoothly and transparently. We are not only more efficient but also better equipped to scale our operations."
HOME Made Love, Premium Pickle & Condiment Brand

11 · Quick questions, honest answers

Thinking about a similar build?

Each variant (mango, lemon, garlic and so on) carries its own bill of materials with ingredients, quantities and spice ratios locked per SKU, so procurement and production follow the exact recipe instead of guesswork.

Yes. Orders flow into Odoo Sales in real time via connectors, inventory deducts on confirmation across one shared stock, and GST invoices generate automatically, which ends overselling between channels.

First-expired-first-out picking is enforced by the system: every batch carries its dates, expiry alerts drive priority dispatch before stock spoils, and the policy applies to 100% of movements.

Every raw-material lot maps to the finished batches it entered, so a recall query identifies affected jars and their destinations in minutes rather than days of paperwork.

Ledgers, vouchers and balances are exported, deduplicated and GST-aligned, then imported into a rebuilt chart of accounts with GST tax groups and HSN mappings, leaving GSTR-1 and GSTR-3B data ready for direct filing.

Yes. Employees, attendance, leave and payroll live on the same Odoo platform as production and sales, so labour data and operations finally share one record.

A 25%+ inventory turnover gain driven by batch and expiry tracking, 100% real-time financial visibility across receivables, cash flow and P&L, and high user adoption backed by training and SOPs.

Directly. Any brand with recipes, batches and multiple sales channels benefits from the same trio: variant BOMs for recipe integrity, FEFO batch discipline for safety, and connector-driven GST billing for scale.

Yes, by design. All of KoderXpert's work for HOME Made Love lives in namespaced custom addons that extend Odoo through inheritance; the core is never edited, and configuration ships as data records, making the setup reproducible and upgrade-safe.

It is the riskiest part, which is why it runs as a staged pipeline: extract and cleanse in a staging environment, load in dependency order through the Odoo ORM so business rules still apply, then verify counts and balances against the source before sign-off.

It depends on scope, which is why delivery ran in structured phases from discovery to supported go-live. Mapping the real process first fixes the scope before any build starts, and phased rollout keeps the business running throughout.

KoderXpert is an Odoo partner that maps the real process before building, engineers upgrade-safe custom modules with zero core edits, and delivers measurable outcomes: for HOME Made Love, a 25%+ inventory turnover gain and 100% real-time financial visibility across four channels. Talk to KoderXpert about your project.

operational chaos, pickled into automation ✨

Scaling a food brand across channels?

Tell us about your recipes, batches and marketplaces. KoderXpert will show you what end-to-end automation looks like for a food manufacturing business on Odoo.



the story continues...

More client stories

All case studies

Your business could be the next story here.

Same process, already proven across 20+ industries.

Your business is not a template. Your ERP should not be either.

Every project on this page started the same way: a conversation about how the business actually runs today, and where the manual hand-offs are. That is a good place to start yours too.