Retail partnerships CRM · Odoo, customised
Pathfinder Global: every mall, brand and partner deal on one connected pipeline
Published · Updated
Pathfinder Global connects 150+ shopping malls with 1,600+ retail brands and the service partners around them. When spreadsheets, inboxes and individual memory stopped scaling, KoderXpert built a customised Odoo CRM that gives all three audiences one pipeline, and does the follow-up chasing automatically.
Designed, built and delivered by KoderXpert Technologies Pvt. Ltd.
Official Odoo Ready Partner · Ahmedabad & Gandhinagar, India
- Client
- Pathfinder Global
- Industry
- Retail technology & mall partnerships
- Platform
- Odoo CRM & Accounting, customised
- Implementation partner
- KoderXpert Technologies
- Headline result
- One pipeline for 150+ malls & 1,600+ brands
01 · Overview
The 30-second version
- Pathfinder Global sits at the centre of a retail partnership network: mall operators filling space, brands expanding their footprint, and service partners supporting both, across 150+ malls and 1,600+ brands.
- Past a certain scale, the systems holding it together (spreadsheets, inboxes and individual memory) stopped scaling: leads scattered, stages meant different things to different teams, and leadership had zero reliable visibility.
- KoderXpert delivered a customised Odoo CRM with three-audience pipelines, automated follow-ups, onboarding and renewal workflows, subscription billing and executive dashboards, across 9 modules and 8 delivery phases.
02 · Where the process broke down
What was going wrong before Odoo?
Six cracks, multiplied by 1,750+ partners
The retail partnership lifecycle ran through five manual stages: prospecting, outreach, negotiation, onboarding, service and renewal. Every crack below got wider with each new mall, brand and region.
Scattered lead data
Lead information lived across spreadsheets, inboxes and channels, with no single source of truth.
The cost → nobody trusted the numbersNo standard pipeline
Malls, brands and service partners were tracked differently by different people; stages meant different things to different teams.
The cost → stages nobody could compareZero visibility
Leadership had no reliable view of conversion rates, onboarding progress or account performance at any point in time.
The cost → decisions made on gut feelSlow follow-ups
Every reminder and task was manual, so high-intent leads went cold while the team chased whatever was loudest that day.
The cost → hot leads going coldRenewals chased by memory
Contracts were serviced and renewals pursued from personal memory, not from a system that never forgets.
The cost → revenue slipping quietlyA scaling ceiling
Adding regions, malls and partner networks multiplied the manual effort instead of being absorbed by the system.
The cost → growth that hurt to win03 · The turnaround
Drag it and see the before & after yourself
Slide the orange handle. Left is the spreadsheet-and-memory era, right is life on the connected CRM.
- ✗ Leads scattered across sheets, inboxes & memory
- ✗ Each team tracking stages its own way
- ✗ Follow-ups manual, high-intent leads going cold
- ✗ Leadership blind on conversion & performance
- ✗ Renewals chased from personal memory
the spreadsheet era 😵
one connected pipeline ✨
- ✔ Every mall, brand & partner in one pipeline
- ✔ Standard stages that mean the same thing to everyone
- ✔ Reminders & tasks triggered automatically
- ✔ Executive dashboards for conversion & pipeline health
- ✔ Onboarding & renewals running on workflows
← drag toward the chaos · drag toward the pipeline →
04 · The plan
What "fixed" had to actually mean
Six outcomes agreed with the Pathfinder team before configuration began. Hover any goal to tick it off.
One CRM for three audiences: malls, brands and service partners, without forcing them into the same box.
A standard pipeline where every stage means the same thing to every team.
Automated follow-ups so no high-intent lead goes cold from a missed reminder.
Onboarding & renewal workflows that run on the system, not on memory.
Unified billing: subscription invoicing, approvals and reconciliation in the same ecosystem.
Executive dashboards for pipeline health, conversion and regional performance.
05 · What we delivered
What did KoderXpert build?
Six building blocks of the partnership CRM
Built on Odoo CRM and Accounting, customised around how a three-audience partnership network actually sells, onboards, services and renews.
Three-audience pipelines
Dedicated pipelines for malls, brands and service partners, with custom Kanban stages built around each sales motion: long committee-based mall cycles, fast high-volume brand deals, contract-driven partner renewals.
three motions, zero collisionsCentralised lead capture
Leads from email, events, referrals and the website flow into one CRM record, ending the era of spreadsheets, inboxes and local notes.
one source of truthAutomated follow-ups
Reminders and task assignments trigger themselves at the right moments, so the team responds fast and consistently instead of chasing whatever is loudest.
the CRM does the chasingOnboarding workflows
Partner documents, account setup and team introductions run as structured workflows with clear owners and visible progress.
no partner left half-onboardedSubscription billing & approvals
Automated recurring invoicing, approval workflows, vendor payments and bank reconciliation, cutting manual accounting activity by 80%.
finance on autopilotExecutive dashboards
KPI dashboards for pipeline health, conversion rates and regional performance give leadership a live, reliable view at any point in time.
visibility leadership can trust06 · Functional deep dive
How the partnership CRM actually works
The delivery summary says what was built. This is the functional detail underneath: how three sales motions share one database, how the chasing is automated, and how the money side connects.
Three pipelines, one database
Each audience runs its own pipeline tuned to its real sales motion, while sharing one CRM record base, one activity system and one reporting layer.
- Mall pipeline: long, committee-based cycles with stages for site evaluation, commercial negotiation and agreement, tracking multiple stakeholders per deal.
- Brand pipeline: faster, higher-volume stages from enquiry to space confirmation, built for parallel deals across many properties.
- Partner pipeline: contract-driven stages for service partners, oriented around scope, SLA and renewal rather than one-off wins.
- Shared taxonomy: stage names mean the same thing to every team, which is what makes cross-network reporting honest.
Lead capture & routing rules
Every enquiry channel lands in the same intake, then routing rules place it on the right pipeline with the right owner.
- Source tracking: website forms, referrals, events and email each stamp their origin on the lead, powering channel-level conversion reporting.
- Deduplication: incoming leads match against existing companies and contacts, so one mall never becomes three records.
- Assignment rules: region and audience determine ownership automatically, ending the era of leads waiting in a shared inbox.
The automation layer that does the chasing
Follow-up discipline is enforced by the system, not by memory: every stage carries scheduled activities that trigger themselves.
- Stage-driven activities: moving a deal schedules its next actions automatically, with owners and deadlines attached.
- Idle-deal alerts: opportunities that sit untouched surface to managers before they go cold.
- Onboarding & renewal workflows: won deals hand off into structured onboarding checklists, and contracts trigger renewal activities well before expiry.
The connected money side
The same ecosystem that wins the deal bills it, which is where the 80% reduction in manual accounting came from.
- Subscription invoicing: recurring partner and brand fees generate automatically on their cycles.
- Approval workflows: spend and vendor payments route through defined approvers instead of email threads.
- Bank reconciliation: statements match against open invoices and payments inside Odoo, keeping receivables live.
- Deal-to-cash visibility: leadership sees pipeline and revenue in the same reporting layer, from first touch to reconciled payment.
Three motions, one database
Malls, brands and partners each get a pipeline shaped like their real sales motion, but every deal lands in the same records and the same reporting layer. That shared taxonomy is why a cross-network conversion number can be trusted at a glance.
07 · How we built it
How was the Odoo project delivered?
From first workshop to a scaling network
Eight delivery phases, compressed here into the six moves that mattered: understanding the partnership business first, then building the system around it.
Discovery workshops learn the network
KoderXpert mapped how mall, brand and partner deals really move, before writing a single line of code.
Pipeline & data design draw the pipeline
Three sales motions translated into pipelines, stages, fields and automation rules everyone would share.
CRM configuration & customisation build the machine
Odoo CRM configured and extended: custom Kanban stages, activity automation, onboarding workflows.
Billing & accounting setup wire the money
Subscription invoicing, approval workflows and reconciliation connected to the same ecosystem.
Migration, training & UAT move everyone in
Legacy lead data migrated, teams trained, and every flow validated end to end.
Go-live & scale support open new regions
Phased go-live with support tuned for adding regions and partners without adding chaos.
08 · Engineering notes
The technical decisions behind the CRM
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_crm_pipelines · kx_lead_routing · kx_subscriptions · kx_dashboards) 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: pipelines, stages, activity plans, routing rules and approval chains ship as XML data records, so the whole setup is 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: years of leads, accounts and deal history scattered across spreadsheets and inboxes. 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: companies, contacts, then opportunities with stage mapping and owner assignment, via the ORM so validation rules apply to every record.
- 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 surface idle deals, refresh dashboard aggregates and generate recurring invoices on their billing cycles.
- 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: mall, brand and partner teams each walked scripted deal scenarios end to end, including onboarding handoff and a full billing cycle, before go-live.
- 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.
From won deal to reconciled cash
A closed deal hands off to onboarding, billing generates on its cycle, approvals route themselves and bank statements reconcile inside the same system, which is where the 80% drop in manual accounting activity came from.
09 · The impact
What changed after go-live?
The results, in numbers
the part clients screenshot ↓- One source of truth for every mall, brand and partner relationship
- Standard stages that mean the same thing across every team
- Faster, more consistent responses to high-intent leads
- Leadership visibility into conversion, onboarding and performance
- Renewals and onboarding running on workflows, not memory
- New regions absorbed by the system instead of multiplying manual effort
10 · Under the hood
Technologies & core skills
"KoderXpert took the time to understand how our partnership business actually works before writing a single line of code. The Odoo CRM they built gave us one place for every mall, brand and service partner, and it does the chasing for us. Our team responds faster, our leadership finally has real visibility, and we can add new regions without adding chaos. A genuinely professional, well-communicated delivery from start to finish."
11 · Quick questions, honest answers
Thinking about a similar build?
Yes. Pathfinder Global runs dedicated pipelines for malls, brands and service partners, each with stages tuned to how those deals actually move, while sharing one database, one activity system and one reporting layer.
Every pipeline stage carries an activity plan: moving a deal schedules its next actions automatically with owners and deadlines, and idle deals surface to managers before they go cold. The team works from a queue the system maintains.
All channels (website, referrals, events, email) land in one intake with source stamped, deduplicate against existing records, and route to the right pipeline and owner by rule, so no lead waits in a shared inbox.
Yes. Won deals hand off into structured onboarding workflows with visible progress, and contracts trigger renewal activities ahead of expiry, so revenue retention runs on the system instead of memory.
Subscription invoicing, approval workflows, vendor payments and bank reconciliation were automated in the same Odoo ecosystem as the CRM, removing roughly four fifths of the manual accounting activity the finance team previously carried.
Live pipeline health, conversion rates by channel and audience, regional performance and revenue views, all reading the same records the sales teams work in, so the numbers need no reconciliation.
Very much so. Any business managing many relationship types across regions benefits from the same pattern: audience-specific pipelines on one shared CRM with automated follow-up and connected billing.
Pathfinder's ecosystem spans nine modules: CRM, Sales, Purchase, Accounting, Invoicing, Projects, Timesheets, Approvals and Dashboards, delivered across eight phases from discovery workshops to scaled go-live.
Yes, by design. All of KoderXpert's work for Pathfinder Global 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 Pathfinder Global, one pipeline for 150+ malls and 1,600+ brands with 80% less manual accounting activity. Talk to KoderXpert about your project.
Planning an Odoo CRM for your partner network?
Tell us how your deals move today, across malls, brands, franchises or partners. KoderXpert will show you what one connected pipeline looks like for your network.
Related case studies
- Ethereum Infracon: Odoo CRM implementationConstruction CRM on a single tracked pipeline
- Unicorn Petro: Odoo ERP and export documentationMarketplace leads and export documents automated
- ReNew TechMart: Odoo eCommerce implementationCatalog, orders and after-sales for refurbished tech
Retail partnerships CRM · Odoo, customised
Pathfinder Global: every mall, brand and partner deal on one connected pipeline
Published · Updated
Pathfinder Global connects 150+ shopping malls with 1,600+ retail brands and the service partners around them. When spreadsheets, inboxes and individual memory stopped scaling, KoderXpert built a customised Odoo CRM that gives all three audiences one pipeline, and does the follow-up chasing automatically.
Designed, built and delivered by KoderXpert Technologies Pvt. Ltd.
Official Odoo Ready Partner · Ahmedabad & Gandhinagar, India
- Client
- Pathfinder Global
- Industry
- Retail technology & mall partnerships
- Platform
- Odoo CRM & Accounting, customised
- Implementation partner
- KoderXpert Technologies
- Headline result
- One pipeline for 150+ malls & 1,600+ brands
01 · Overview
The 30-second version
- Pathfinder Global sits at the centre of a retail partnership network: mall operators filling space, brands expanding their footprint, and service partners supporting both, across 150+ malls and 1,600+ brands.
- Past a certain scale, the systems holding it together (spreadsheets, inboxes and individual memory) stopped scaling: leads scattered, stages meant different things to different teams, and leadership had zero reliable visibility.
- KoderXpert delivered a customised Odoo CRM with three-audience pipelines, automated follow-ups, onboarding and renewal workflows, subscription billing and executive dashboards, across 9 modules and 8 delivery phases.
02 · Where the process broke down
What was going wrong before Odoo?
Six cracks, multiplied by 1,750+ partners
The retail partnership lifecycle ran through five manual stages: prospecting, outreach, negotiation, onboarding, service and renewal. Every crack below got wider with each new mall, brand and region.
Scattered lead data
Lead information lived across spreadsheets, inboxes and channels, with no single source of truth.
The cost → nobody trusted the numbersNo standard pipeline
Malls, brands and service partners were tracked differently by different people; stages meant different things to different teams.
The cost → stages nobody could compareZero visibility
Leadership had no reliable view of conversion rates, onboarding progress or account performance at any point in time.
The cost → decisions made on gut feelSlow follow-ups
Every reminder and task was manual, so high-intent leads went cold while the team chased whatever was loudest that day.
The cost → hot leads going coldRenewals chased by memory
Contracts were serviced and renewals pursued from personal memory, not from a system that never forgets.
The cost → revenue slipping quietlyA scaling ceiling
Adding regions, malls and partner networks multiplied the manual effort instead of being absorbed by the system.
The cost → growth that hurt to win03 · The turnaround
Drag it and see the before & after yourself
Slide the orange handle. Left is the spreadsheet-and-memory era, right is life on the connected CRM.
- ✗ Leads scattered across sheets, inboxes & memory
- ✗ Each team tracking stages its own way
- ✗ Follow-ups manual, high-intent leads going cold
- ✗ Leadership blind on conversion & performance
- ✗ Renewals chased from personal memory
the spreadsheet era 😵
one connected pipeline ✨
- ✔ Every mall, brand & partner in one pipeline
- ✔ Standard stages that mean the same thing to everyone
- ✔ Reminders & tasks triggered automatically
- ✔ Executive dashboards for conversion & pipeline health
- ✔ Onboarding & renewals running on workflows
← drag toward the chaos · drag toward the pipeline →
04 · The plan
What "fixed" had to actually mean
Six outcomes agreed with the Pathfinder team before configuration began. Hover any goal to tick it off.
One CRM for three audiences: malls, brands and service partners, without forcing them into the same box.
A standard pipeline where every stage means the same thing to every team.
Automated follow-ups so no high-intent lead goes cold from a missed reminder.
Onboarding & renewal workflows that run on the system, not on memory.
Unified billing: subscription invoicing, approvals and reconciliation in the same ecosystem.
Executive dashboards for pipeline health, conversion and regional performance.
05 · What we delivered
What did KoderXpert build?
Six building blocks of the partnership CRM
Built on Odoo CRM and Accounting, customised around how a three-audience partnership network actually sells, onboards, services and renews.
Three-audience pipelines
Dedicated pipelines for malls, brands and service partners, with custom Kanban stages built around each sales motion: long committee-based mall cycles, fast high-volume brand deals, contract-driven partner renewals.
three motions, zero collisionsCentralised lead capture
Leads from email, events, referrals and the website flow into one CRM record, ending the era of spreadsheets, inboxes and local notes.
one source of truthAutomated follow-ups
Reminders and task assignments trigger themselves at the right moments, so the team responds fast and consistently instead of chasing whatever is loudest.
the CRM does the chasingOnboarding workflows
Partner documents, account setup and team introductions run as structured workflows with clear owners and visible progress.
no partner left half-onboardedSubscription billing & approvals
Automated recurring invoicing, approval workflows, vendor payments and bank reconciliation, cutting manual accounting activity by 80%.
finance on autopilotExecutive dashboards
KPI dashboards for pipeline health, conversion rates and regional performance give leadership a live, reliable view at any point in time.
visibility leadership can trust06 · Functional deep dive
How the partnership CRM actually works
The delivery summary says what was built. This is the functional detail underneath: how three sales motions share one database, how the chasing is automated, and how the money side connects.
Three pipelines, one database
Each audience runs its own pipeline tuned to its real sales motion, while sharing one CRM record base, one activity system and one reporting layer.
- Mall pipeline: long, committee-based cycles with stages for site evaluation, commercial negotiation and agreement, tracking multiple stakeholders per deal.
- Brand pipeline: faster, higher-volume stages from enquiry to space confirmation, built for parallel deals across many properties.
- Partner pipeline: contract-driven stages for service partners, oriented around scope, SLA and renewal rather than one-off wins.
- Shared taxonomy: stage names mean the same thing to every team, which is what makes cross-network reporting honest.
Lead capture & routing rules
Every enquiry channel lands in the same intake, then routing rules place it on the right pipeline with the right owner.
- Source tracking: website forms, referrals, events and email each stamp their origin on the lead, powering channel-level conversion reporting.
- Deduplication: incoming leads match against existing companies and contacts, so one mall never becomes three records.
- Assignment rules: region and audience determine ownership automatically, ending the era of leads waiting in a shared inbox.
The automation layer that does the chasing
Follow-up discipline is enforced by the system, not by memory: every stage carries scheduled activities that trigger themselves.
- Stage-driven activities: moving a deal schedules its next actions automatically, with owners and deadlines attached.
- Idle-deal alerts: opportunities that sit untouched surface to managers before they go cold.
- Onboarding & renewal workflows: won deals hand off into structured onboarding checklists, and contracts trigger renewal activities well before expiry.
The connected money side
The same ecosystem that wins the deal bills it, which is where the 80% reduction in manual accounting came from.
- Subscription invoicing: recurring partner and brand fees generate automatically on their cycles.
- Approval workflows: spend and vendor payments route through defined approvers instead of email threads.
- Bank reconciliation: statements match against open invoices and payments inside Odoo, keeping receivables live.
- Deal-to-cash visibility: leadership sees pipeline and revenue in the same reporting layer, from first touch to reconciled payment.
Three motions, one database
Malls, brands and partners each get a pipeline shaped like their real sales motion, but every deal lands in the same records and the same reporting layer. That shared taxonomy is why a cross-network conversion number can be trusted at a glance.
07 · How we built it
How was the Odoo project delivered?
From first workshop to a scaling network
Eight delivery phases, compressed here into the six moves that mattered: understanding the partnership business first, then building the system around it.
Discovery workshops learn the network
KoderXpert mapped how mall, brand and partner deals really move, before writing a single line of code.
Pipeline & data design draw the pipeline
Three sales motions translated into pipelines, stages, fields and automation rules everyone would share.
CRM configuration & customisation build the machine
Odoo CRM configured and extended: custom Kanban stages, activity automation, onboarding workflows.
Billing & accounting setup wire the money
Subscription invoicing, approval workflows and reconciliation connected to the same ecosystem.
Migration, training & UAT move everyone in
Legacy lead data migrated, teams trained, and every flow validated end to end.
Go-live & scale support open new regions
Phased go-live with support tuned for adding regions and partners without adding chaos.
08 · Engineering notes
The technical decisions behind the CRM
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_crm_pipelines · kx_lead_routing · kx_subscriptions · kx_dashboards) 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: pipelines, stages, activity plans, routing rules and approval chains ship as XML data records, so the whole setup is 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: years of leads, accounts and deal history scattered across spreadsheets and inboxes. 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: companies, contacts, then opportunities with stage mapping and owner assignment, via the ORM so validation rules apply to every record.
- 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 surface idle deals, refresh dashboard aggregates and generate recurring invoices on their billing cycles.
- 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: mall, brand and partner teams each walked scripted deal scenarios end to end, including onboarding handoff and a full billing cycle, before go-live.
- 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.
From won deal to reconciled cash
A closed deal hands off to onboarding, billing generates on its cycle, approvals route themselves and bank statements reconcile inside the same system, which is where the 80% drop in manual accounting activity came from.
09 · The impact
What changed after go-live?
The results, in numbers
the part clients screenshot ↓- One source of truth for every mall, brand and partner relationship
- Standard stages that mean the same thing across every team
- Faster, more consistent responses to high-intent leads
- Leadership visibility into conversion, onboarding and performance
- Renewals and onboarding running on workflows, not memory
- New regions absorbed by the system instead of multiplying manual effort
10 · Under the hood
Technologies & core skills
"KoderXpert took the time to understand how our partnership business actually works before writing a single line of code. The Odoo CRM they built gave us one place for every mall, brand and service partner, and it does the chasing for us. Our team responds faster, our leadership finally has real visibility, and we can add new regions without adding chaos. A genuinely professional, well-communicated delivery from start to finish."
11 · Quick questions, honest answers
Thinking about a similar build?
Yes. Pathfinder Global runs dedicated pipelines for malls, brands and service partners, each with stages tuned to how those deals actually move, while sharing one database, one activity system and one reporting layer.
Every pipeline stage carries an activity plan: moving a deal schedules its next actions automatically with owners and deadlines, and idle deals surface to managers before they go cold. The team works from a queue the system maintains.
All channels (website, referrals, events, email) land in one intake with source stamped, deduplicate against existing records, and route to the right pipeline and owner by rule, so no lead waits in a shared inbox.
Yes. Won deals hand off into structured onboarding workflows with visible progress, and contracts trigger renewal activities ahead of expiry, so revenue retention runs on the system instead of memory.
Subscription invoicing, approval workflows, vendor payments and bank reconciliation were automated in the same Odoo ecosystem as the CRM, removing roughly four fifths of the manual accounting activity the finance team previously carried.
Live pipeline health, conversion rates by channel and audience, regional performance and revenue views, all reading the same records the sales teams work in, so the numbers need no reconciliation.
Very much so. Any business managing many relationship types across regions benefits from the same pattern: audience-specific pipelines on one shared CRM with automated follow-up and connected billing.
Pathfinder's ecosystem spans nine modules: CRM, Sales, Purchase, Accounting, Invoicing, Projects, Timesheets, Approvals and Dashboards, delivered across eight phases from discovery workshops to scaled go-live.
Yes, by design. All of KoderXpert's work for Pathfinder Global 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 Pathfinder Global, one pipeline for 150+ malls and 1,600+ brands with 80% less manual accounting activity. Talk to KoderXpert about your project.
Planning an Odoo CRM for your partner network?
Tell us how your deals move today, across malls, brands, franchises or partners. KoderXpert will show you what one connected pipeline looks like for your network.
Related case studies
- Ethereum Infracon: Odoo CRM implementationConstruction CRM on a single tracked pipeline
- Unicorn Petro: Odoo ERP and export documentationMarketplace leads and export documents automated
- ReNew TechMart: Odoo eCommerce implementationCatalog, orders and after-sales for refurbished tech
