Discover and Map
I run workshops with each department to capture how work actually flows today, workarounds and side spreadsheets included.
- As-is maps, pain-point log
Shiropha Kawsar Choudhury, Techno-Functional Odoo Consultant
Architecting Agile Enterprise Ecosystems.
With 12+ years of corporate strategy and 17 full-cycle ERP implementations, I bridge complex operational gaps by engineering intuitive, standardized Odoo workflows that drive measurable business value.
I bring order to sales workflows, procurement, inventory, bills of materials, production planning, legacy data and go-live day.
Shiropha Kawsar Choudhury Techno-Functional Odoo Consultant
- Functional meets technical
- End-to-end Odoo configuration
- Trading and manufacturing flows
Track record at a glance
-
17 full-cycle implementations
Full cycle: from process mapping through go-live support.
-
12+ years of corporate experience
Corporate strategy experience, brought into Odoo workflow design.
-
100% project delivery rate
Every project carried through to delivery.
-
8 industries
From apparel and textiles to real estate, healthcare and retail.
Hello, I’m Shiropha
Where business logic meets system logic.
I approach ERP projects through a corporate-strategy lens: a business decision first, a software project second. So I start with how your operation really runs (the orders, stock, production and approvals that keep it moving) and only then work out how Odoo should model it.
ERP projects often stall in the gap between the people who know the business and the people who configure the system. I work on both sides of that gap. With your purchasing team, I can map how approvals should flow, write that into the Software Requirements Specification (SRS), then configure it in Odoo and lead its testing.
Functional: how your business runs
- Map as-is and to-be processes with the people who run them
- Lead requirement workshops and fit-gap analysis
- Capture requirements in a signed-off SRS
- Train teams and prepare them for change and go-live
Odoo
one integrated system
Technical: how Odoo will run it
- Configure Odoo apps, user roles and access rights
- Structure products, bills of materials (BOMs), work centers and warehouse routes
- Migrate, cleanse and audit legacy data
- Write user acceptance test (UAT) scenarios and lead testing to sign-off
I translate in both directions: business needs into Odoo configuration, and the configured system back into the language your teams use.
Core expertise
Eight competencies. One full cycle.
An implementation succeeds only when all of its phases do, so I’ve grouped the eight by what each phase must achieve.
Clarity
A shared, written picture of what the business needs.
Business Process Mapping and Gap Analysis
I map the handoffs and approvals in your current process, then compare it with standard Odoo to show what fits, what changes and what needs a decision.
Requirement Gathering and Plotting SRS
I turn department workshops into a Software Requirements Specification (SRS): one agreed reference for scope, priorities, workflows, data and roles, with acceptance criteria for each requirement.
Foundation
A correctly configured system, running on clean, audited data.
End-to-End Odoo Module Configuration
I configure Odoo’s apps as one connected system (company settings, products, warehouses, approvals, user roles and access rights), so departments work from the same live data.
Strategic Data Migration, Cleansing and Audit
Bad data can sink a good system. I plan what moves, then cleanse, deduplicate and map it to Odoo, auditing each load, so you go live on data your teams recognize.
Flow
Orders, stock and production moving through one connected chain.
Streamlining Trading, Procurement and Sales Workflows
I configure the chains that move goods and money (buying, stocking and selling), so orders, receipts, deliveries, invoices and bills stay connected, approved where it matters and traceable.
Manufacturing (BOM) and Production Optimization
I structure bills of materials, operations and work centers, then connect production to stock and purchasing, so manufacturing orders show component availability and progress, with capacity planned per work center.
Adoption
A system tested, signed off and owned by your teams.
User Acceptance Testing (UAT) Leadership
Before go-live, your key users test the system against real business scenarios. I write test scripts from the SRS, track issues to closure and guide the team to sign-off.
Corporate Change Management and Go-Live Support
Software doesn’t change companies; people do. I prepare teams with role-based training, plan the cutover and support them after go-live, so early issues can be resolved before they become workarounds.
Odoo in motion
Flows, not silos.
In Odoo, each document builds on the last. A confirmed sales order can trigger delivery, purchasing and production, then be invoiced without re-keying. I configure and test these chains.
-
Sales: quote-to-cash
One thread from first quote to final payment, visible to sales, warehouse and finance.
- Quotation: Products, prices and terms, sent to the customer for confirmation
- Sales Order: The confirmed quotation; for goods (not services) it creates the delivery order
- Delivery Order: Picked from stock and shipped; stock updates on validation
- Customer Invoice: Created from the order, on ordered or delivered quantities per your invoicing policy
- Payment: Registered and reconciled against the invoice
-
Purchase: procure-to-pay
Buy what you need, receive what you ordered, pay for what actually arrived.
- Request for Quotation: Prices requested from a vendor; reordering rules can draft RFQs automatically
- Purchase Order: The confirmed RFQ; manager approval can be required above a set amount
- Receipt: Goods checked in against the order; stock updates on validation
- Vendor Bill: Controlled against ordered or received quantities
- Payment: Registered and reconciled against the bill
-
Trading: back-to-back orders
Customer demand triggers the purchase order, so you buy against real orders, not guesses.
- Sales Order: The customer orders a product set up with the Buy and make-to-order (MTO) routes
- Automatic RFQ: Drafted for the product’s vendor as soon as the sale is confirmed
- Purchase Order: The RFQ, confirmed with the vendor
- Receipt: Goods arrive already reserved for that customer
- Delivery Order: Shipped to the customer
-
Manufacturing: plan-to-produce
Manufacturing orders consume the right components and turn them into stock you can sell.
- Bill of Materials: Components, quantities and operations for one product
- Manufacturing Order: Created manually, from a sales order (MTO) or from a reordering rule; closing it consumes the components and produces the finished goods
- Pick Components: Components moved from stock to the production area
- Work Orders: Operations carried out at work centers, step by step
- Store Finished Product: Finished goods moved from production to stock
Standard Odoo flows, shown for illustration. Actual configurations follow your requirements.
How I work
A clear path from blueprint to go-live.
Eight steps, each ending in an output your team can review, so progress stays visible and decisions stay yours. The tags on a step show the competencies behind it.
-
-
Fit-Gap Design
I design the to-be process around standard Odoo and recommend the simplest way to close each gap.
- To-be design, gap resolution plan
-
Write the SRS
I write the agreed design into the SRS, review it with your process owners and get it signed off before full configuration starts.
- Signed-off SRS
-
Configure Odoo
I configure each app against the SRS, requirement by requirement, documenting as I go, so your team can see how it was set up.
- Configured Odoo, matching the SRS
-
Streamline Flows
I walk through each end-to-end flow (sales, purchasing, inventory, manufacturing) and tune routes, BOMs and approvals until it runs cleanly.
- Connected flows, ready to test
-
Migrate Data
Alongside configuration, I run trial loads of your legacy data and reconcile each against the source, so the final load is already rehearsed.
- Reconciled master data, open orders, stock
-
UAT and Sign-Off
I lead UAT on migrated data: defects are resolved and retested until the business formally signs off.
- UAT sign-off, closed defect log
-
Go-Live and Hypercare
Cutover follows the agreed plan. I support the first live transactions, then hand over documentation your team can rely on.
- Live system, documented handover
Change management, throughout
Change management doesn’t wait for step 08. I involve key users from the first map, so go-live feels familiar, not foreign.
A typical sequence. Each engagement is scoped to the business it serves, so steps can overlap or repeat.
It starts with a map. Let’s draw yours.
Discuss your Odoo projectIndustries
Different industries. The same discipline.
Every sector asks something different of the same Odoo apps. Here are the eight, with the process areas that typically matter most in each.
-
Trading and Manufacturing
Buy-to-sell cycles, landed costs, multi-warehouse stock and BOM-driven production.
-
Property and Real Estate
Project-level costing and procurement, unit sales and installment payment terms.
-
Energy and Automotive
Serialized parts and equipment, multi-location stock and controlled procurement of technical items.
-
, Textiles and Apparel
Size and color variants, multi-level BOMs, subcontracting and order-based production planning.
-
Electronic Appliances
Serial-number traceability, assembly and kit BOMs, and dealer pricelists for distribution.
-
Healthcare and Retail
Lot and expiry tracking, Point of Sale, consistent pricing and replenishment across outlets.
-
Corporate Public Services
Approval workflows, controlled procurement and a clear audit trail on key transactions.
-
Lifestyle and Fashion
Seasonal collections, variant-level stock, markdown pricing and sales across stores.
Typical focus areas by sector. Your own processes come first.
Don’t see your industry? Tell me about itWhy work with me
Five principles I hold myself to.
-
Standardized by design
I engineer workflows to a common standard, so any exception becomes a deliberate, visible decision rather than a habit.
-
Intuitive or unfinished
If the people entering orders every day find a workflow confusing, it isn’t finished yet.
-
Value you can measure
Every workflow has to earn its place with a visible outcome: cleaner data, clearer approvals, fewer manual steps.
-
Traceable end to end
Configuration traces back to signed-off requirements, and UAT tests those requirements against real business scenarios.
-
Start to finish
The context from your first workshop stays with me through configuration, testing and go-live support.
FAQ
Questions worth asking before you start.
How long does an Odoo implementation take?
It depends on scope, and I’d rather not guess before I understand yours. The biggest drivers are the number of companies, warehouses and apps involved, how much data moves and how clean it is, and how quickly decisions get made. Discovery and a signed-off SRS turn those drivers into a realistic plan.
Will we need custom development?
Not necessarily, and I don’t start from that assumption. For each gap, I first check whether configuration or a process change closes it, because standard workflows are easier to learn, support and upgrade. If a requirement needs development, I document it in the SRS, so it is scoped and approved as a deliberate decision, not discovered as a surprise.
We’re already live on Odoo, but it isn’t working as hoped. Where would you start?
With the same first step as a new implementation: mapping how your teams work today. Comparing that with how Odoo is configured shows where workflows break, get bypassed or were never standardized. From there, I recommend focused fixes in configuration, data and training, prioritized by business impact.
How do you verify our migrated data?
Before go-live, not after. I reconcile each trial load against the source, comparing record counts and totals, then spot-check what matters most: products, customers, vendors, open orders and stock quantities. Your team reviews the results, and the final load happens only after a trial run reconciles cleanly.
What will you need from our team?
Three things. A sponsor who can make decisions when trade-offs come up. A key user from each department, who joins the workshops, reviews the SRS, tests in UAT and later helps train colleagues. And early access to your current data and documents, because migration starts alongside configuration, not after it.
Will we be able to run Odoo on our own after go-live?
That is the goal from day one. Role-based training gives each person what their job needs, and hypercare covers the first live transactions. At handover, you get documentation of how your Odoo is configured and why, so the knowledge stays with your team, not with me.
Contact
Ready to optimize your operations?
Let’s deploy an ERP system that elevates your business efficiency.
Start the conversation
Opens your email app with a short outline to fill in.
info@shiropha.com
No forms, no sign-ups. Just email.
What to include in your first email
- Your company and industry, in a line or two.
- Where you are with Odoo, and what you want it to do.
- The processes causing the most friction, such as re-keying, stock mismatches or slow approvals.
- What you run on today, from spreadsheets to a legacy ERP.
- Any milestones or deadlines, and who will be involved on your side.