Skip to content
Light
English

What Demander sends to Meu ERP Online

Send uses the Meu ERP Online public API and only inserts records (this integration does not update customers or orders).

How to configure and trigger: Integration setup.

Endpoint: api/pessoa/v1.

Queued customers have:

  • codigo = 0 (no ERP code yet)

On success, Demander writes pessoa.codigo from the API into Cliente.codigo. That customer is not exported again.

Main data sent:

  • Legal name, trade name, CPF/CNPJ
  • Fixed type A (both — customer and supplier)
  • Contact (phone 1, phone 2, buyer email)
  • Main address (street, number, district, city/IBGE, state, ZIP, region)
  • Price list (idTabelaPreco)
  • Active S

State tax ID is sent as ISENTO in this flow.

Endpoint: api/documento/v1.

Queued orders:

  • are not cancelled
  • are finalized (podeExportar = 1 and not being edited)
  • have type and status with Send return to ERP (enviaPedidoRetorno = 1)
  • are released for export (codStatusLiberacao null or 1)
  • have not been integrated to the ERP yet (numPedidoERP empty)

On success, Demander writes:

  • numPedidoERP = returned idDocumento
  • codStatus = status configured in Código status pedido exportado

On timeout or after the failure limit, it applies the status and integration note configured on the Integração do Pedido tab.

Main JSON blocks:

Block Content
documento ERP user, person (customer), model (type mapping), status (mapping), operation nature, dates
pessoa Customer and delivery address
transporte Freight type, carrier, amount and weights
pedido Demander order code (idExterno), representative (seller), dates
mercadoriaLista Items (product, quantities, amounts, stock location, price list)
pagamentoLista Payment method (codFormaPagamento → idPagamento) and amounts
parcelaLista Payment-condition installments

The intermediador field is not sent.