ERPNext CRM in the Philippines

When ERPNext's own CRM is enough, and when it is not

ERPNext includes leads, opportunities, quotations, customers, contacts, territories and sales partners. For a distributor or manufacturer whose sales cycle runs from inquiry to quotation to sales order within days or weeks, that set is usually sufficient, and the advantage of one database is large: a rep quoting a hardware chain sees stock across warehouses, the customer's credit limit and their overdue invoices without asking finance.

The built-in CRM is a weaker choice when:

• Your team runs long consultative deals, such as outsourcing contracts with overseas buyers, where a dedicated CRM's sequences and forecasting matter more than stock data.
• Marketing needs campaigns, scoring and web forms beyond simple email groups.
• Many sales users never touch stock or invoicing and would be better served by a lighter interface.

Frappe also publishes Frappe CRM, a standalone app with a cleaner pipeline screen, which links back to ERPNext. Whether it suits your version and hosting is worth confirming with Frappe or your implementer. Where a third-party CRM wins, the work becomes an integration: customers, items, prices and quotations synced in one direction, with a clear system of record for each. The global product view is on ERPNext CRM, and the trade-offs are discussed on sales and ERP integration.

Territories, dealers and provincial coverage

A Philippine distributor's coverage map rarely matches a neat sales org chart. Metro Manila key accounts may be handled by a head-office team, while provinces are served through dealers, sub-distributors or reps who visit monthly. ERPNext models this with three linked ideas:

• Territories arranged as a tree, for example by island group, then region, then province or city cluster, so reports can roll up at any level.
• Sales persons attached to territories and to customers, with targets by item group if management wants them.
• Sales partners for dealers or distributors who sell on your behalf and earn commission, with the commission rate recorded on the partner and calculated on invoices.

The design questions are practical. Who owns a customer that buys from a dealer but sometimes orders direct? Do provincial dealers get access to ERPNext through a portal, or do your reps enter orders for them? How are freight and inter-island shipping reflected in quoted prices? I settle these with the sales head before configuring anything, because changing territory rules after a year of history makes reports unreliable.

For organizations running reps in the field with patchy connections, I test the mobile experience in the provinces before rollout, not only in the head office. Related distribution patterns are on distribution ERP.

Messenger, Viber and chat inquiries reaching the pipeline

Inquiries in the Philippines can arrive through Facebook Messenger, Viber or WhatsApp as easily as through email or a web form. When those conversations live only on a rep's phone, the company loses the lead history whenever the rep leaves, and managers cannot see how many inquiries turn into quotations.

ERPNext does not include these chat channels as standard. Options to evaluate, in order of effort:

• Manual capture with discipline: a short lead form reps fill on mobile after each new inquiry, with the source channel required. Cheap, and often enough to start.
• Community apps: open source Frappe apps exist for some messaging channels, WhatsApp in particular. Check maintenance activity, compatibility with your ERPNext version and the messaging provider's terms before installing.
• Integration platforms: a middleware tool that creates leads in ERPNext through its API when a new chat starts.
• Custom connector: built by your developer or implementer, with a named owner for upgrades.

Whatever the route, templates in Filipino, Cebuano or another local language need a review by native-speaking staff before they go live, because the engagement runs in English. The approach to vetting connectors is on my system integration page.

Quotations with VAT, price lists and the handoff to invoicing

A Philippine seller may quote differently by channel: VAT-inclusive prices for retail and small business buyers, VAT-exclusive prices with tax shown separately for corporate accounts, and special prices for dealers. ERPNext supports this with multiple price lists, pricing rules for volume or promotional discounts, and tax templates applied on the quotation. Which display your documents need, and how VAT-exempt or zero-rated buyers are treated, is for your tax advisor to confirm.

What I configure and test:

• Price lists for each channel, with the customer group selecting the right one automatically.
• Pricing rules that reps cannot override without approval, so margin decisions stay with management.
• Quotation print formats in English, with any local-language terms provided by your team.
• Conversion from quotation to sales order to delivery and sales invoice, keeping the price, tax and terms intact, so the invoice issued by your registered system matches what the customer accepted.
• Credit checks at sales order stage for dealers with open balances.

Lost quotations get a required reason, so management can see whether price, stock or delivery time is costing deals. The design method follows my CRM consulting service.

Data Privacy Act consent and what to confirm before rollout

The Philippine Data Privacy Act applies to the personal data your CRM holds about contacts at customers, dealers and prospects. Your data protection officer decides what consent is needed for marketing messages, how long records are kept and how access requests are handled. My part is making ERPNext follow those decisions.

In practice that means:

• Custom fields on leads and contacts recording the consent basis, the channel and the date consent was given, without which no marketing list should include them.
• An unsubscribe route on email groups, and a manual process for chat channels.
• Role permissions and user permissions limiting reps to their own territories and customers.
• A retention rule for old leads that never converted.

Before rollout, confirm a few things with Frappe or your implementer: whether your version includes Frappe CRM or only the classic CRM screens, which messaging apps are maintained for that version, and how hosting location fits your officer's guidance. No Frappe affiliation or referral fee shapes this advice. The broader platform picture is on ERPNext Philippines, an Odoo alternative is on Odoo CRM Philippines, and the Philippines hub covers how my remote work runs here.