Siddham Group on Odoo 19 Community: two companies, one system
Process blueprint for Siddham PolyIndia (trading) and Siddham Polyplast (manufacturing), with CRM, business telephony, call recording, transcription and official WhatsApp built in.
One Odoo database, two companies, one view of every customer and supplier
Built on Odoo 19 Community, as your RFP prefers. Every part is marked as standard Community, configuration, OCA (open-source community module), custom, or third party, as Section 1 asks.
What comes in
Sell
- Pipeline in your 7 stages
- Owner and next activity on every opportunity
- Samples and supplier mapping
- Quotation to Sales Order
Run
- Two companies, intercompany SO and PO
- Lots, UoM, locations, barcode
- Manufacturing and quality at Polyplast
- Invoicing, GST, intercompany accounts
People
- Attendance and leave
- Payroll per company
- Timesheets, KPIs, incentives
What goes out
Two companies, one database
Shared customers, vendors and products. Separate journals, warehouses, GSTINs and record rules per company.
| Siddham PolyIndia | Siddham Polyplast | |
|---|---|---|
| Model | Trading and aggregation | Manufacturing |
| Purchase | Yes | Yes |
| Sales | Yes | Yes, to customers and to PolyIndia |
| Manufacturing | No | Yes |
| Key records | RFQ, Purchase Order, Receipt, Sales Order, Delivery | Bill of Materials, Manufacturing Order, Work Order, Quality inspection |
| Shared | Customers, vendors, products and categories, pricelists, CRM, users | |
Every report splits by these, per company or for the group.
Odoo 19 Community: what is standard and what we add
Section 27 asks for every Community limitation. Here they are, with how each one is covered.
| Requirement | In Community | We add |
|---|---|---|
| Multi-company, record rules | Standard | Configuration |
| CRM, sales, purchase, inventory, lots, UoM | Standard | Configuration and Section 8.1 fields |
| Manufacturing: BOM, MO, work orders, work centres | Standard | Design after the process study |
| Multi-level approvals by value and role | Single PO approval level | OCA tier validation |
| Intercompany SO and PO, invoice and bill | Not in Community | OCA inter-company modules |
| Barcode scanning operations | Not in Community | OCA barcode module |
| Quality checks, hold and release | Not in Community | OCA quality control |
| Bank reconciliation, P&L, Balance Sheet | Invoicing only | OCA accounting and reports |
| GST return reports | Not in Community | Custom reports |
| Payroll, appraisals | Not in Community | OCA payroll, custom KPIs |
| VoIP, WhatsApp, AI summaries | Not in Community | Custom modules, third-party APIs |
No Odoo Enterprise, Odoo.sh or Odoo Online dependency. OCA modules are open source with no licence fee. Where one is not yet released for version 19, we port it and hand the code over.
Enquiry to Sales Order
Every enquiry becomes a lead with an owner and a next activity. Duplicates are caught on phone, mobile, email and company name. The opportunity moves through Initial Contact, Need Analysis, Qualification, Negotiation and Dispatch / Fulfilment to Closed Won or Closed Lost, and the quotation is made from it without re-entry.
Checks and approvals in this flow
What Siddham wants to achieve
Taken from your RFP, section by section. Each card ends with how it is met on Odoo.
One source of truthSection 2, 4
- One record for customers, vendors, products, transactions and employees
- Strict company-wise accounting, stock and access
- Intercompany trading between the two companies
CRM disciplineSection 8
- Your 7-stage pipeline
- Owner and next action on every opportunity
- Overdue activities escalated, stage ageing visible
- Duplicates controlled on phone, email and company
Central business callingSection 9
- Official company number, not personal numbers
- Click-to-call and inbound caller match
- Recording, transcript and AI summary
- Salesperson validates before it is logged
Official WhatsAppSection 10
- Company number, not personal accounts
- Templates from quotation to payment reminder
- Internal alerts and consent-based broadcasts
Stock, UoM and lotsSection 11, 12
- Jumbo bags and standard bags
- KG, Gram, Ton, Piece, Bag, Box, Roll, Meter
- Lot traceability from supplier to customer
Manufacturing and qualitySection 13, 14
- BOMs, MOs, work orders and work centres
- Scrap, by-products and production costing
- Incoming, in-process, FG and dispatch checks
- Hold and release tied to stock
Finance and GSTSection 17
- Separate books for each company
- Intercompany accounting and reconciliation
- GST quoted explicitly, never assumed excluded
People and incentivesSection 18, 19
- Attendance, leave and payroll
- Timesheets, KPIs and reviews
- Incentives on value, margin, collections and targets
Ownership, no lock-inSection 3, 29
- Siddham owns its data and Siddham-specific work
- No AI training on Siddham data
- Full export and exit assistance
Your RFP, straight answers
The items your RFP asks every vendor to state, in the order of its sections. Click a question to open it.
Odoo 19 Community is the base, as you prefer. Where Community stops, we use OCA modules first, custom modules second, and third-party services only where a service is needed.
No Odoo Enterprise, Odoo.sh, Odoo Online or proprietary module is needed. Nothing is replaced with a different workflow without saying so.
A third-party Indian cloud telephony provider, connected to Odoo CRM through a custom module. VoIP is an Enterprise app in Odoo, so we build the integration on the provider's API.
Recording consent: a recording notice plays on the provider IVR. Recordings sit behind role-based access, with retention set by company and role, and can be exported or deleted by policy.
Fallback: if the API is down, calls still route on the provider side. Call logs sync once it is back, and missed calls are listed for callback.
Every recorded call is transcribed and summarised. The salesperson validates the note before it becomes an official log note on the opportunity.
| Item | What we propose |
|---|---|
| Approach | Custom Odoo module on a third-party speech-to-text and AI engine. Odoo's own AI features are Enterprise-only. |
| Languages | English and Hindi, plus Gujarati where the chosen engine supports it, confirmed at GAP |
| Summary | Customer requirement, pricing discussed, objections, commitments and next action, written into opportunity fields |
| Billing | Separate line, per audio minute and per summary, at actuals |
| Your data | Engines on no-training, no-retention terms. Processing location disclosed. API keys in Siddham's name |
| Accuracy | Good on clear audio. Expect edits early on for grade names and numbers, which improve as your vocabulary is added |
One official company number on the WhatsApp Business API through a BSP, connected to Odoo by a custom module. WhatsApp is an Enterprise app in Odoo.
Template approval, delivery and read status, and failure reports are logged. Customer replies land on the chatter of that customer or opportunity.
Quoted explicitly, as the RFP asks. Both companies, both GSTINs.
We accept Section 29 as written. Your data, recordings, transcripts and Siddham-specific work belong to Siddham.
Odoo.sh is for Enterprise, so Community runs on Siddham's own cloud account in an India region, managed by us.
Indicative six months, in four phases, following your delivery cycle. Training starts in week 1.
| Track | M1 | M2 | M3 | M4 | M5 | M6 |
|---|---|---|---|---|---|---|
| Requirement confirmation, GAP, Polyplast process study | ||||||
| Phase 1: companies, purchase, sales, inventory, barcode, accounting, GST, intercompany | ||||||
| Phase 1: CRM pipeline, fields, follow-up and duplicate rules | ||||||
| Phase 2: telephony, recording, transcription, AI notes, WhatsApp | ||||||
| Phase 3: Polyplast manufacturing and quality | ||||||
| Phase 4: HR, payroll, timesheets, incentives, dashboards | ||||||
| Training, UAT per module, go-live, stabilisation | ||||||
Delivery cycle: GAP, solution design, configuration and development, integration, functional testing, UAT, training, data migration, go-live, stabilisation. BOMs and manufacturing workflow are finalised only after the process study, as Section 13 asks.
Every mandatory output in Section 23.1:
Clean masters plus opening balances, loaded twice on UAT before the real cutover.
Go-live is on a month start for a clean period in each company. Nothing goes live until stock, receivables, payables and the trial balance tie out with your current records.
Your acceptance criteria become the test plan, and each module is signed off on its own.
Role-based training from week 1, and an internal administrator who can run the system day to day.
Sessions are recorded where permitted. Each process map becomes an SOP for that team.
Support comes directly from our team. Bugs in delivered work are fixed free for 60 days after go-live.
| Severity | Example | Response | Target fix or workaround |
|---|---|---|---|
| P1 Critical | Invoicing, dispatch or calling stopped for everyone | 1 hour | 4 hours |
| P2 High | One module or one company blocked | 4 working hours | 1 working day |
| P3 Normal | Error with a workaround, report issue | 1 working day | 3 working days |
| P4 Change request | New field, report or workflow | Logged and estimated | Planned in the next cycle |
Support is remote, with on-site visits when needed. Bug fixes are free, changes are change requests. After warranty, an AMC or monthly support pod with fixed hours, unused hours carried forward. Escalation runs from support engineer to project lead to delivery head. Backup checks and incidents are reported monthly.
Every external service, what it costs, how it connects and what happens if it fails.
| Service | Provider | Charges | Auth | If it fails |
|---|---|---|---|---|
| Telephony and recording | Indian cloud telephony, chosen at GAP | Rental, per minute, storage | API key, webhook secret | Calls route on provider, logs sync later |
| Transcription and AI summary | Speech-to-text and AI engine | Per minute, per summary | API key | Recording kept, job retried, manual note allowed |
| WhatsApp BSP on Meta API | Per message | API token | Queued and retried, failure report | |
| e-invoice and e-way bill | Localisation e-invoicing service | Per transaction | GSP credentials | Invoice saved, upload retried |
| Your mail server | None from us | SMTP / IMAP | Mail queue retried | |
| Biometric | Your device vendor | Device dependent | Device API | Manual attendance with approval |
| Hosting | Siddham cloud account, India region | Monthly, at actuals | Siddham owned | Restore from off-site backup |
Stated openly, nothing silently excluded.
In the commercial proposal, in your Section 25 format, with one-time and recurring kept apart.
A named team for the whole project, and reference calls with trading and manufacturing clients.
Your project gets a project lead, a functional consultant for trading and accounts, a functional consultant for manufacturing and quality, an Odoo developer, and an integration engineer for telephony, WhatsApp and AI. A second consultant shadows the lead, so a change in people is never a loss of knowledge. Support is delivered directly, without subcontractors.
Compliance matrix, Section 26
Every requirement ID with the vendor status terms from Section 1, where the solution comes from, and whether its cost is one-time or recurring. Amounts are in the commercial proposal.
| Req. ID | Area | Requirement | Vendor Status | Source | Proposed Solution / Module | Cost type |
|---|---|---|---|---|---|---|
| Platform and structure | ||||||
| F-01 | Platform | Odoo 19 Community as base platform | Included | Standard | Odoo 19 Community Edition. No Enterprise, Odoo.sh or Odoo Online dependency. | One-time |
| F-02 | Multi-Company | Two-company architecture with security | Included | StandardConfiguration | Two companies, company-wise record rules, journals, warehouses and GSTINs. | One-time |
| F-03 | Intercompany | PO / SO linked intercompany workflow | Included | OCACustom | OCA inter-company SO / PO and invoice / bill modules, plus partials, returns and cancellations. | One-time |
| Sales, purchase and CRM | ||||||
| F-04 | Purchase | Purchase lifecycle and approvals | Included | StandardOCA | RFQ, Purchase Order, vendor pricelists, receipts, returns. Multi-level approvals with OCA tier validation. | One-time |
| F-05 | Sales | Quotation to order to delivery | Included | StandardConfiguration | Quotation, Sales Order, pricelists, delivery, credit notes. Freight and loading as order lines. | One-time |
| F-06 | CRM | Configured pipeline, activities and governance | Included | StandardCustom | Odoo CRM with your 7 stages, activities, lost reasons. Escalation and next-action rules custom. | One-time |
| F-07 | CRM Data | Requirement, pricing, supplier and sample fields | Custom | Custom | Section 8.1 fields, sample tracking and supplier mapping. | One-time |
| Telephony and WhatsApp | ||||||
| T-01 | Telephony | Central inbound / outbound calling with CRM | Third Party | Third partyCustom | Indian cloud telephony provider, custom Odoo integration module. | One-time + recurring |
| T-02 | Telephony | Automatic call logging | Custom | Custom | Call log with the Section 9.3 fields, on contact, lead and opportunity. | One-time |
| T-03 | Telephony | Call recording | Third Party | Third party | Provider recording, secure link on the call log, role access and retention. | Recurring |
| T-04 | Telephony | Speech-to-text transcription | Third Party | Third partyCustom | Third-party engine through a custom module, searchable transcript. | One-time + recurring |
| T-05 | Telephony | AI / automated call summary | Third Party | Third partyCustom | Summary into opportunity fields, billed separately at actuals. | One-time + recurring |
| T-06 | Telephony | CRM note creation from call | Custom | Custom | Draft log note, validated by the salesperson before posting. | One-time |
| T-07 | Telephony | Call analytics and agent productivity | Custom | Custom | Calls, connected calls, duration, missed calls, conversion and follow-up compliance. | One-time |
| W-01 | Official WhatsApp integration | Third Party | Third partyCustom | WhatsApp Business API through a BSP, custom Odoo module. | One-time + recurring | |
| W-02 | Transactional alerts and templates | Custom | Custom | Templates and triggers, delivery, read and failure status, internal alerts. | One-time | |
| Operations | ||||||
| I-01 | Inventory | Warehouse and stock management | Included | StandardOCA | Warehouses, Section 11 locations, routes, reordering rules, valuation. Stock ageing report via OCA. | One-time |
| M-01 | Manufacturing | BOM / MO / WO / work centres | Included | StandardConfiguration | BOM, Manufacturing Order, Work Orders, Work Centers, by-products, scrap, MO costing. | One-time |
| Q-01 | Quality | Incoming / in-process / FG quality | Included | OCAConfiguration | OCA quality control, Quality location as hold and release, disposition. | One-time |
| B-01 | Barcode | Scanning and warehouse operations | Included | OCA | OCA barcode scanning for receipt, lot, transfer, pick, pack, delivery and count. Hardware by Siddham. | One-time |
| Finance and people | ||||||
| A-01 | Accounting | Finance and intercompany accounting | Included | StandardOCA | Odoo Invoicing with OCA bank reconciliation and financial reports, intercompany reconciliation. | One-time |
| A-02 | Tax | GST / tax scope explicitly quoted | Included | StandardCustomThird party | Indian localisation for GST. GSTR-1 and 3B reports custom. e-invoice and e-way bill credits at actuals. | One-time + recurring |
| H-01 | HR | Employee / attendance / leave | Included | Standard | Employees, Attendance, Time Off. Biometric integration if applicable. | One-time |
| H-02 | Payroll | Payroll and statutory scope | Included | OCACustom | OCA payroll with Indian salary rules for PF, ESI, PT and TDS. | One-time |
| R-01 | Reporting | Management / MIS dashboards | Included | StandardCustom | Odoo pivot, graph and dashboard views plus custom MIS reports. No BI licence cost. | One-time |
| Data, security and delivery | ||||||
| D-01 | Migration | Master / opening / historical data migration | Included | Configuration | Templates, cleansing rules, two mock loads, reconciliation before go-live. | One-time |
| S-01 | Security | Roles, record rules, audit and export control | Included | StandardOCA | Access groups, record rules, admin-only export, OCA audit log. | One-time |
| X-01 | Integration | API / integration architecture | Included | StandardCustom | Odoo external API, webhooks, integration dependency register. | One-time |
| P-01 | Delivery | Testing / UAT / training / go-live | Included | Configuration | Your Section 23 delivery cycle and every Section 23.1 output. | One-time |
| P-02 | Support | Warranty / SLA / AMC | Included | Configuration | 60-day warranty, severity SLA, AMC or monthly support plan. | Recurring |
Enquiry to Sales Order
Every enquiry becomes a lead with an owner and a next activity. Duplicates are caught on phone, mobile, email and company name. The opportunity moves through Initial Contact, Need Analysis, Qualification, Negotiation and Dispatch / Fulfilment to Closed Won or Closed Lost, and the quotation is made from it without re-entry.
Outbound call to CRM log note
Section 9.2 outbound flow. The salesperson clicks a number in Odoo, the customer sees the official company number, and the call is recorded, transcribed and summarised. The salesperson validates the note before it becomes an official log note with the next activity.
Inbound call and missed call
Section 9.2 inbound flow. The caller is matched to the contact, routed to the owner or a queue, and the call lands on the same timeline. Unknown callers become suggested leads. Missed calls create callback activities and alerts.
WhatsApp notifications and replies
Odoo documents trigger approved templates from the official company number. Delivery, read and failed status is logged, and replies land on the customer chatter. Internal alerts for approvals, POs, goods received, low stock, production completion and delays use the same module.
Purchase: RFQ to vendor payment
Vendors quote against RFQs, price history and validity stay with the vendor pricelist, and approvals follow company, value, department and role. Every lot is weighed and scanned into Incoming before it moves to Main Stock.
Order to cash
Sales Order to collection, using your PolyIndia locations: Main Stock, Packing and Dispatch. Lots are scanned at picking, transporter and vehicle are captured, and e-invoice and e-way bill are generated with the invoice.
Intercompany order
Your Section 5 flow: customer requirement at PolyIndia, availability check, intercompany PO, Polyplast SO, stock or Manufacturing Order, delivery to PolyIndia, receipt, customer delivery. Partial quantities, backorders, cancellations and returns follow the same links.
Production and costing
Using your Polyplast locations: Raw Material, Production, Quality, Finished Goods, Scrap and Rejected. Components are picked by lot, each work centre records its work orders, and every finished lot keeps the link to its raw material lots. BOMs and routes are finalised only after the process study.
Quality hold and release
Any lot at a check point is held until tested against its parameters. Failures go to a disposition: rework, scrap or return. Reports show quality by supplier, batch, product and production order.
Month-end close
Each company closes its own books. GST data is checked, intercompany balances are matched, and management sees P&L, Balance Sheet, cash and outstanding for each company.
Attendance, payroll and incentives
Check-ins become attendance, leave and corrections go through approvals, and incentives are calculated from your rules before the payslip batch runs for each company.