ERPNext CRM in Portugal

Quotations, pro formas and the Portuguese document rules

Portuguese rules on invoicing software reach beyond the invoice itself. Depending on how a document is used, quotations, pro formas, order confirmations and similar documents may also be expected to come from approved software, with series and identification codes. Where the line falls for your business must be settled by your accountant, and it may depend on what the document says, who receives it and whether it is used to request payment.

ERPNext produces quotations and sales orders as standard. Whether those documents, or an app built on ERPNext, may be used for anything the rules cover must be confirmed in writing by the app publisher and reviewed by your accountant; I do not assume it. Practical designs I work through:

• Internal proposals only: ERPNext quotations used for negotiation, worded and handled as your accountant advises, while anything regulated comes from the approved program.
• Pro formas from the approved program: when a buyer needs a pro forma for prepayment or import formalities, ERPNext requests it and stores the reference.
• Order confirmations: handled in whichever system your accountant indicates, with the ERPNext sales order as the operational record.

The aim is that salespeople never have to decide, case by case, which system to use. The broader split between ERPNext and the invoicing program is explained on ERPNext in Portugal.

Export pipelines in several currencies and languages

A Portuguese exporter of furniture, textiles, wine, cork or industrial parts may deal with buyers in Spain, France, Germany, the United Kingdom and further afield, each with its own currency, price expectations and language. The CRM inside ERPNext handles the commercial basics well: leads from fairs, web forms and agents; opportunities with expected value and stage; quotations in the buyer's currency from market price lists.

What I design with the sales director:

• Market price lists: one per currency or channel, with pricing rules for volume and distributor discounts, checked against the spreadsheets they replace.
• Delivery terms: the agreed trade terms recorded on quotation and order, so logistics and pricing stay consistent.
• Agents abroad: sales partners with commission rates and territories, and user permissions if agents log in.
• Language templates: a quotation layout for each buyer language. Since the engagement runs in English, Portuguese or other local text is supplied by your staff or a translator you choose.
• Samples: sample requests tracked on the opportunity with follow-up dates, since many export deals start there.

Sample shipments are goods movements, so the transport document question your accountant answers for production also applies here. I connect the sample flow to the same rule rather than inventing a separate one. See multi-currency ERP for the general method.

NIF, customer records and the handoff to invoicing

In a split design, a customer may be created by a salesperson in ERPNext and invoiced weeks later by the approved Portuguese program. If the two systems hold different names, tax numbers or addresses, invoices go out wrong and the SAF-T data disagrees with what sales sees. Customer data needs one owner.

Rules worth starting from, adjusted to your setup:

• Owner: ERPNext creates and maintains customer records; the invoicing program receives them through the integration and does not allow local edits, or the reverse if your accountant prefers.
• Tax numbers: NIF mandatory for Portuguese business customers at conversion, EU VAT numbers for intra-community buyers, with format checks where available.
• Consumers: if you sell to private individuals, how a sale without a tax number is handled is agreed with your accountant and reflected in both systems.
• Addresses: billing and delivery kept separate, since mainland, Azores and Madeira deliveries can carry different tax.
• Errors: failed syncs shown on a list that one named person clears, not buried in a log.

Before go-live, a staging run follows one record from lead, through customer and quotation, to the invoice the program issues. The ledger implications are covered on ERPNext Accounting in Portugal, and the integration method on my system integration page.

Consent and data protection for Portuguese contacts

Portuguese outreach is governed by GDPR, national data protection law and specific rules on unsolicited electronic communications, with the national data protection authority overseeing them. Whether you need prior consent for a given email or message, or can rely on an existing customer relationship, depends on the recipient and the channel; your data protection lead or lawyer makes that call. My role is to make ERPNext capture and enforce the decision.

The setup I propose:

• Per lead and contact: the source of the data, the purpose agreed, the channel and when consent was given or withdrawn.
• Email campaigns that leave out opted-out contacts automatically and carry an unsubscribe link.
• Trade fair and partner lists imported only when their legal basis is recorded.
• A review routine for leads that never progressed, in line with your retention policy.
• Permissions limiting who can export contacts, which matters when agents abroad have access.

Exporters also hold contacts from buyers in other countries, where local rules may differ; your lawyer decides whether one policy covers all markets. Consent wording on web forms and emails, in Portuguese and other languages, is drafted by your team and approved by your lawyer. The Portugal CRM consultant page looks at CRM governance more broadly.

WhatsApp, Frappe CRM and when ERPNext CRM is the wrong choice

Messaging apps are part of everyday selling in Portugal and with buyers abroad. ERPNext does not provide WhatsApp business messaging in the core product. Connectors from the community and from vendors exist, built on the official business messaging interfaces; ask Frappe or your partner who keeps a given connector alive, whether your release supports it, and what the messaging provider allows and bills. Consent for messaging must be settled too.

Frappe CRM is another option: its own app, maintained by the Frappe team, with a sales-centered screen design. Its current features and how it links to ERPNext should be confirmed for your version before you choose it.

ERPNext CRM is the wrong choice when:

• Marketing campaigns, scoring and attribution drive most of your pipeline.
• Sales teams need dialers, sequences or conversation tracking.
• A parent group already runs a CRM the Portuguese entity is expected to use.
• Nobody will maintain the integration with the invoicing program, which a CRM change would also affect.

Then a specialist CRM feeding ERPNext, along the lines of Zoho CRM in Portugal, is likely the better route. I receive no commission from any vendor and hold no Frappe partnership, so the recommendation follows your requirements. Product details are on ERPNext CRM, and the work is delivered remotely.