Omie

Name: Omie
Brand: Omie
Rating: 3.8 (4 reviews)

Leader

Impulsione a economia do Brasil, seja um Omielover! #VemPraOmie https://carreirasomie.gupy.io/

Est 2013|Valuation $856.2M|Raised $296.1M|36 Ref Customers

LinkedIn 278K|Web traffic 1.9M|FTEs 1,613|HQ Sao Paulo, Brazil

MarketsERP Invoicing & Payment Processing Sales Tax & VAT Automation

Published Oct 15, 2026

01Common complaints

- You require deep, in-product customization of workflows and reporting formats: multiple reviews describe the system as constrained in customization. - You operate high-volume retail/PDV environments where performance and immediate issue resolution are non-negotiable: complaints describe PDV freezing and production disruption in some cases. - You require fully transparent, static pricing published online (including onboarding and integration fees): the main pricing page appears dynamic and some add-ons list additional fees. - You require public documentation of SOC 2 or other enterprise attestations beyond ISO 27001 for procurement: these were not located in the reviewed sources. - You prefer a lightweight invoicing-only tool: simpler products may deliver faster time-to-value with lower operational overhead.

Deal disqualifiers (poor fit)

Requirements for deep customization of data models, forms, or reports within the ERP
Mission-critical, high-throughput retail/PDV where any latency or downtime is unacceptable without extensive pilot validation
Procurement that requires public documentation of attestations beyond ISO 27001 (for example, SOC 2) that are not available in the reviewed materials

Limitations acknowledged by users

Customization constraints: several reviews and complaints highlight limited ability to customize reports and system behavior.
Service/OS field flexibility: users request more configurable fields for service orders and related processes.

Reliability/performance risks (from complaints)

Reports of PDV crashes, latency, and pricing table synchronization issues that can directly affect revenue operations.
Reports of inconsistent reporting data (for example, duplicated values) are high severity; procurement teams should validate reporting accuracy during pilots with representative transactional data.

API/Integration constraints

APIs include SOAP and JSON support; integration work may be heavier than REST-first ecosystems and could require partner or engineering resources.

Roadmap visibility

Vendor communications referenced ongoing improvements and webinars but did not disclose a detailed public roadmap for specific customer-requested features.

02Why they buy

Differentiators supported by evidence

- Brazil-specific ERP functionality covering invoicing, services, stock, and finance, with an ecosystem approach that includes marketplace apps and integration components. - Developer ecosystem and documentation: public developer portal and help docs describe APIs (SOAP/JSON), webhooks, testing tools, and logging history, which supports integration-heavy implementations. - Vendor-stated ISO 27001 certification (2025): a security-related statement that may be relevant for SMB/mid-market buyers; certificate scope and verifying details were not located in the captured sources.

Where competitors may have advantages

Pricing clarity: competitors can present clearer published pricing for entry-level packages.
Perceived operational reliability and simplicity: some users report simpler ERPs were more reliable for specific reporting tasks.
Customization and configurability: heavier ERPs typically provide more in-product configurability at higher cost.

Why customers chose Omie (inferred from reviews)

Reasons cited in reviews and vendor messaging include:

Cloud ERP capabilities for Brazil, including NF-e/NFS-e and integrated financial routines.
Desire for a consolidated platform that includes ERP functions and bank integration.
Competitive pricing compared with larger enterprise ERPs.

03Field reports

Review platform feedback (Capterra)

Capterra contains a mix of positive and negative experiences. Positive examples (Capterra): - Users praise efficient data exchange, integrated bank connectivity, and an intuitive layout. - Other comments highlight ease of interpretation and direct generation of core financial statements. Critical examples (Capterra): - Some reviewers report platform instability and a range of operational issues. - Other reviewers cite limited ability to modify system behavior or reports. Patterns from Capterra: - Positive comments frequently mention price/value, an intuitive UI, and integrations. - Negative comments frequently mention limited customization and platform issues.

Community/social and complaint forums (Reclame Aqui)

Reclame Aqui contains operationally detailed complaints useful for understanding failure modes. Company-level view: - The vendor shows a generally favorable reputation on the platform with many complaints answered and a high resolution rate; response times on some cases are measured in days. Example complaint themes (Reclame Aqui): - Support/post-sale gaps and operational disruption: Complaints describe issues after going live, such as imported stock/prices not appearing correctly, manual pricing required at checkout, PDV slowness/freezing, and limited remote troubleshooting. - Data/reporting trust issues: Some complaints allege duplicated invoice values and unreliable reports. - Pricing/onboarding surprise: Complaints describe being notified after activation of an onboarding fee in cases where it was not clear during procurement.

Why some customers leave (inferred from complaints)

Common reasons for churn include:

Concerns about reliability and trust in reporting (reconciliation and accuracy issues).
Limitations on customization and system flexibility.
Support responsiveness when PDV/invoicing issues cause operational impact.

Vendor testimonials (official site)

The vendor site includes customer testimonial excerpts describing operational benefits, for example: - A customer quote describing daily bank reconciliation and reduced manual effort compared with a previous process. - A customer quote emphasizing that an online platform enabled remote work. Critical evaluation: - These testimonials are selected by the vendor and do not include disclosed methodology, baseline metrics, sample size, or independent verification. They illustrate use cases (bank/finance integration and cloud access) but should not be interpreted as representative performance guarantees.

Quantified claims (vendor-stated)

Public messaging includes claims of large-scale invoice volume and a substantial customer base; supporting methodology or independent audit was not located in the captured sources.

Mixed/negative “case” signals (from complaints)

Complaint forums include detailed go-live problems (pricing tables not syncing, PDV instability) that serve as informal failure case studies and indicate time-to-value can be negative if critical commerce workflows fail.

04Best fit

Company sizes

Best fit appears to be small to mid-sized Brazilian firms—tens to a few hundreds of employees—with packaging aligned to multiple SMB revenue bands.

Industries / verticals

Services companies (contracts, service orders, NFS-e)
Commerce/e-commerce and retail (NF-e, stock, marketplace integrations; optional PDV)
Light industry/distribution where stock and invoicing are central

Roles/personas

Decision makers: owners, finance managers, operations managers
Influencers: accountants and external implementation partners/franchise
End users: billing/invoicing clerks, sales operations, purchasing/stock teams

Pain points addressed

Brazil fiscal and invoicing complexity (NF-e/NFS-e)
Consolidation of sales, finance, and stock systems
Bank reconciliation and operational visibility

Qualification criteria (good fit)

Needs a cloud ERP with Brazilian invoicing and integrated finance
Accepts relatively standardized processes and limited in-product customization
Willing to engage with partner/franchise-led onboarding and potential setup fees

05The pitch

What the product does (core value proposition)

Omie is a Brazil-focused cloud ERP platform intended for small and mid-sized companies. The product centralizes operational and financial routines—sales and invoicing (NF-e), services and service invoicing (NFS-e), purchasing/stock, and financial management—and offers related capabilities such as a digital business account and other financial services within the same ecosystem. Omie provides integrations via an app marketplace (Omie Store) and APIs/webhooks for connecting external tools and automating workflows (for example, BI tools, integration platforms, and e-commerce connectors).

Target market and positioning

Primary target: Brazilian SMBs (PMEs) and growing mid-market firms that require fiscal-compliant invoicing and integrated finance/operations.
Positioning themes on official site: ERP, CRM, financial services, education/community; online/remote access; a higher-tier support offering; and messaging about readiness for Brazil’s evolving fiscal/tax landscape.
Go-to-market: Includes a franchise/partner network.

Get a comprehensive analysis of Omie including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 15, 2026

01Common complaints

You require deep, in-product customization of workflows and reporting formats: multiple reviews describe the system as constrained in customization.
You operate high-volume retail/PDV environments where performance and immediate issue resolution are non-negotiable: complaints describe PDV freezing and production disruption in some cases.
You require fully transparent, static pricing published online (including onboarding and integration fees): the main pricing page appears dynamic and some add-ons list additional fees.
You require public documentation of SOC 2 or other enterprise attestations beyond ISO 27001 for procurement: these were not located in the reviewed sources.
You prefer a lightweight invoicing-only tool: simpler products may deliver faster time-to-value with lower operational overhead.

Deal disqualifiers (poor fit)

Requirements for deep customization of data models, forms, or reports within the ERP
Mission-critical, high-throughput retail/PDV where any latency or downtime is unacceptable without extensive pilot validation
Procurement that requires public documentation of attestations beyond ISO 27001 (for example, SOC 2) that are not available in the reviewed materials

Limitations acknowledged by users

Customization constraints: several reviews and complaints highlight limited ability to customize reports and system behavior.
Service/OS field flexibility: users request more configurable fields for service orders and related processes.

Reliability/performance risks (from complaints)

Reports of PDV crashes, latency, and pricing table synchronization issues that can directly affect revenue operations.
Reports of inconsistent reporting data (for example, duplicated values) are high severity; procurement teams should validate reporting accuracy during pilots with representative transactional data.

API/Integration constraints

APIs include SOAP and JSON support; integration work may be heavier than REST-first ecosystems and could require partner or engineering resources.

Roadmap visibility

Vendor communications referenced ongoing improvements and webinars but did not disclose a detailed public roadmap for specific customer-requested features.

02Why they buy

Differentiators supported by evidence

Brazil-specific ERP functionality covering invoicing, services, stock, and finance, with an ecosystem approach that includes marketplace apps and integration components.
Developer ecosystem and documentation: public developer portal and help docs describe APIs (SOAP/JSON), webhooks, testing tools, and logging history, which supports integration-heavy implementations.
Vendor-stated ISO 27001 certification (2025): a security-related statement that may be relevant for SMB/mid-market buyers; certificate scope and verifying details were not located in the captured sources.

Where competitors may have advantages

Pricing clarity: competitors can present clearer published pricing for entry-level packages.
Perceived operational reliability and simplicity: some users report simpler ERPs were more reliable for specific reporting tasks.
Customization and configurability: heavier ERPs typically provide more in-product configurability at higher cost.

Why customers chose Omie (inferred from reviews)

Reasons cited in reviews and vendor messaging include:

Cloud ERP capabilities for Brazil, including NF-e/NFS-e and integrated financial routines.
Desire for a consolidated platform that includes ERP functions and bank integration.
Competitive pricing compared with larger enterprise ERPs.

03Field reports

Review platform feedback (Capterra)

Capterra contains a mix of positive and negative experiences.

Positive examples (Capterra):

Users praise efficient data exchange, integrated bank connectivity, and an intuitive layout.
Other comments highlight ease of interpretation and direct generation of core financial statements.

Critical examples (Capterra):

Some reviewers report platform instability and a range of operational issues.
Other reviewers cite limited ability to modify system behavior or reports.

Patterns from Capterra:

Positive comments frequently mention price/value, an intuitive UI, and integrations.
Negative comments frequently mention limited customization and platform issues.

Community/social and complaint forums (Reclame Aqui)

Reclame Aqui contains operationally detailed complaints useful for understanding failure modes.

Company-level view:

The vendor shows a generally favorable reputation on the platform with many complaints answered and a high resolution rate; response times on some cases are measured in days.

Example complaint themes (Reclame Aqui):

Support/post-sale gaps and operational disruption: Complaints describe issues after going live, such as imported stock/prices not appearing correctly, manual pricing required at checkout, PDV slowness/freezing, and limited remote troubleshooting.
Data/reporting trust issues: Some complaints allege duplicated invoice values and unreliable reports.
Pricing/onboarding surprise: Complaints describe being notified after activation of an onboarding fee in cases where it was not clear during procurement.

Why some customers leave (inferred from complaints)

Common reasons for churn include:

Concerns about reliability and trust in reporting (reconciliation and accuracy issues).
Limitations on customization and system flexibility.
Support responsiveness when PDV/invoicing issues cause operational impact.

Vendor testimonials (official site)

The vendor site includes customer testimonial excerpts describing operational benefits, for example:

A customer quote describing daily bank reconciliation and reduced manual effort compared with a previous process.
A customer quote emphasizing that an online platform enabled remote work.

Critical evaluation:

These testimonials are selected by the vendor and do not include disclosed methodology, baseline metrics, sample size, or independent verification. They illustrate use cases (bank/finance integration and cloud access) but should not be interpreted as representative performance guarantees.

Quantified claims (vendor-stated)

Public messaging includes claims of large-scale invoice volume and a substantial customer base; supporting methodology or independent audit was not located in the captured sources.

Mixed/negative “case” signals (from complaints)

Complaint forums include detailed go-live problems (pricing tables not syncing, PDV instability) that serve as informal failure case studies and indicate time-to-value can be negative if critical commerce workflows fail.

04Best fit

Company sizes

Best fit appears to be small to mid-sized Brazilian firms—tens to a few hundreds of employees—with packaging aligned to multiple SMB revenue bands.

Industries / verticals

Services companies (contracts, service orders, NFS-e)
Commerce/e-commerce and retail (NF-e, stock, marketplace integrations; optional PDV)
Light industry/distribution where stock and invoicing are central

Roles/personas

Decision makers: owners, finance managers, operations managers
Influencers: accountants and external implementation partners/franchise
End users: billing/invoicing clerks, sales operations, purchasing/stock teams

Pain points addressed

Brazil fiscal and invoicing complexity (NF-e/NFS-e)
Consolidation of sales, finance, and stock systems
Bank reconciliation and operational visibility

Qualification criteria (good fit)

Needs a cloud ERP with Brazilian invoicing and integrated finance
Accepts relatively standardized processes and limited in-product customization
Willing to engage with partner/franchise-led onboarding and potential setup fees

05The pitch

What the product does (core value proposition)

Omie provides integrations via an app marketplace (Omie Store) and APIs/webhooks for connecting external tools and automating workflows (for example, BI tools, integration platforms, and e-commerce connectors).

Target market and positioning

Primary target: Brazilian SMBs (PMEs) and growing mid-market firms that require fiscal-compliant invoicing and integrated finance/operations.
Positioning themes on official site: ERP, CRM, financial services, education/community; online/remote access; a higher-tier support offering; and messaging about readiness for Brazil’s evolving fiscal/tax landscape.
Go-to-market: Includes a franchise/partner network.

Get a comprehensive analysis of Omie including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →