Catalog & SKUs
Products, variations, measurements, weights, hierarchy, and attributes flow from Protheus to e-commerce, with versioning and batch rollback.
Mid-market Brazil runs on Protheus. CCX Company integrates Protheus with VTEX, Shopify, Salesforce Commerce, and Magento, covering catalog, inventory, price, B2C/B2B orders, and invoicing—all with Brazilian tax compliance and end-to-end observability.
Protheus 12+
Cloud or on-prem
4-6
Typical project months
99.9%
Integration SLA
NF-e
End-to-end
Protheus brings decades of maturity in fiscal, financial, and logistics operations in Brazil. Well integrated, it becomes the reliable engine of your digital operation without needing replacement.
E-commerce calls Protheus APIs (FWREST) and vice versa via webhooks. Direct integration, no middleware layer. Simple and fast for up to ~500 orders/day.
Layer on AWS/GCP with queues (SQS, Pub/Sub), idempotent retries, DLQ, and observability. Isolates Protheus from traffic spikes and absorbs transient failures.
For large catalogs or analytical data. Daily/hourly ETL to data lake or warehouse, syncing master records and reports without stressing the ERP.
Products, variations, measurements, weights, hierarchy, and attributes flow from Protheus to e-commerce, with versioning and batch rollback.
Price tables, lists, B2B negotiation, promotions, and discounts calculated in Protheus and published by channel and segment.
Inventory by branch, distribution center, and real-time reservation. WMS integration and split-order for multi-origin orders.
E-commerce order enters Protheus, orchestrates credit, reserves inventory, arranges shipping, and returns status through final delivery.
NF-e issuance via SEFAZ, DANFE attached to order, accounting entry, and sync with accounts receivable in Protheus Finance.
Customers (individual/corporate) with CPF/CNPJ, addresses, contacts, linked price list, and payment terms. Two-way sync when needed.
Issuance, cancellation, correction letter, and status query via SEFAZ integrated into the order cycle.
ICMS calculation, tax substitution, and DIFAL per origin and destination state, right in Protheus.
Customer's tax regime considered in tax calculation and fiscal document generation.
For operations with own logistics, complementary fiscal documents also enter the flow.
Brazilian mid-market operations have nuances: Protheus ERP at the core, complex tax operations, lean IT teams, and budgets sensitive to licensing costs. CCX Company designs integrations that respect this reality. When volume is modest, we use Protheus REST APIs directly against the commerce platform, with webhooks for events. When volume grows or operations gain marketplaces and multiple branches, we introduce middleware with queues and observability, without forcing the client to license an expensive hub like MuleSoft or CPI. The approach is incremental, affordable, and scalable.
Half of Protheus integration success is in field mapping. Each table (SA1, SB1, SC5, SD1) has dozens of columns, many custom. Fiscal fields (CFOP, NCM, CEST, origin) must travel correctly to e-commerce and back. Product attributes (color, size, voltage) often live in free-form fields needing normalization. CCX starts every project with a data mapping workshop alongside your Protheus team or TOTVS partner, producing a living dictionary that guides implementation and avoids surprises at go-live.
The order flow in Brazilian operations has more steps than other markets: credit check, inventory reservation, tax calculation, NF-e issuance, SEFAZ authorization, picking, dispatch, CT-e in some cases, and customer updates. CCX orchestrates this with correlation IDs that let you trace each step in Protheus, e-commerce, and middleware. Each relevant event (authorization, note issued, order invoiced, package posted, delivery completed) updates the order in e-commerce and triggers customer notifications. Failures become operational tasks, not silent stuck orders.
Many mid-market companies get stuck in limbo: Protheus works well at the core, but e-commerce grows and manual integrations can't keep up. Migrating to SAP is expensive and lengthy, CSV exports don't scale, and off-the-shelf connectors deliver only 60% of what's needed. CCX delivers a third way: custom integrations in lean scope, with lightweight middleware, predictable cost, and clear ownership. Many operations go from 2–3 days of order/NF delays to near real-time in 4 months, without touching the ERP or licensing heavyweight new tools.
Sim. Desde a versão 12, Protheus expõe APIs REST nativas via FWREST e ADVPL. Os módulos SIGAFAT, SIGAFIS, SIGACOM e outros possuem endpoints padrão para catálogo, pedido, estoque, preço e financeiro — além de permitir endpoints customizados em ADVPL/TLPP.
Sim, é um dos cenários mais comuns no mercado médio brasileiro. A CCX integra Protheus com VTEX cobrindo catálogo, estoque, preço, pedido B2C e B2B, emissão de NF-e e atualização de status. Usamos APIs REST do Protheus combinadas com APIs e webhooks da VTEX.
Depende do volume e da complexidade. Em operações menores, integração direta API-to-API funciona. Em volumes maiores ou com múltiplas plataformas (ex: Protheus + VTEX + marketplaces), recomendamos middleware com filas e observabilidade — em AWS, GCP ou on-premise.
O pedido entra no ecommerce, é enviado ao Protheus, que reserva estoque, calcula impostos e emite a NF-e via SEFAZ. O XML e DANFE retornam para o ecommerce, são anexados ao pedido do cliente e enviados por email/WhatsApp. Status fiscais (autorizada, cancelada, rejeitada) ficam sincronizados.
Para o escopo core (catálogo, estoque, preço, pedido, NF-e), projetos ficam tipicamente entre 2 e 4 meses. Escopos ampliados com B2B, múltiplas filiais, marketplaces conectados e regras fiscais complexas podem chegar a 6 meses.
Não somos especialistas em ADVPL/TLPP puro, mas trabalhamos junto com o time Protheus do cliente ou parceiro TOTVS. Nosso foco é a camada de integração: APIs, middleware, mapeamento de campos, orquestração de pedido e resiliência. Isso permite dividir escopo claro entre as partes.
Pouca. Protheus Cloud expõe as mesmas APIs REST via TOTVS Fluig/TLPP Web. Em on-premise, é necessário cuidar de acesso de rede (VPN, tunelamento ou exposição segura). Os patterns de integração (pedido, estoque, preço) são idênticos.
VTEX (IO e Classic), Shopify Plus, Salesforce Commerce Cloud, Magento 2, Wake e plataformas custom com APIs. Para marketplaces, conectamos via hub central (ex: Olist, Anymarket) ou diretamente com Mercado Livre, Amazon e Magalu.
In two sessions we map APIs, flows, tax compliance, and deliver scope, timeline, and realistic effort estimate.
+55 (11) 2427-6839 • [email protected]