Store integrated with the ERP: what changes day to day

For the administrator: what changes day to day with the store integrated with the ERP, such as credit, last paid price, stock and order sending.

For: Administrator · Supplier

Updated on 2026-10-12

Why this guide exists

In a store connected to an ERP, the usual screens change, and the difference almost never shows up as a new button: it shows up as data that's already there when you open a customer or build a quote.

Three caveats apply to the whole guide:

not every ERP offers everything. Each integration exposes its own set, and Vendria only uses what your store's ERP offers. That's why each section below says under what condition the feature appears. Which ERPs have a ready integration is in Com quais ERPs a Vendria se integra;
connecting doesn't turn everything on at once. Customer data, the intake of sellers and customers and order sending are enabled store by store by the Vendria team, after checking with you that the ERP records are ready. Stock depends on Company manages stock, which you turn on in Catalog and exports, Product page tab, Stock block. The last paid price comes with the connection. See What syncs with the ERP, and when;
when the store's connection is off, none of what's described here happens in that store.

How to connect the store is in another guide. See Connect a store's ERP.

What Vendria starts knowing about the customer

With the customer recognized in the ERP, Vendria looks up what your store's ERP offers among this data:

credit limit: how much they can still buy;
open receivables: what they already owe;
how they usually pay: the payment terms, installments and payment method of their latest orders, read from the history;
order history: what they bought and when;
last paid price: how much they paid last time, product by product;
branches and companies of the same group, when the customer has more than one CNPJ or more than one delivery destination and the ERP organizes the records that way;
the customer's contacts registered in the ERP, when the ERP provides them.

The credit limit is the most common data among the integrations. The rest depend on the ERP: when it doesn't offer one of them, that information simply doesn't appear, and that's not a defect.

Credit in the quote

When your store's ERP provides credit, the seller sees the customer's situation before closing the quote, instead of finding out later: "Verified in the ERP" when the record checks out, and next to it "Available credit" with the amount, "No credit available" or "Customer blocked in the ERP".

When the ERP has no limit registered, the quote says so ("Credit: no data in the ERP"), and not that the customer has no credit. Those are different things.

Last paid price

The last paid price appears when your store's ERP keeps the price history per customer. It has no separate enablement: it comes with the store's connection, but it only appears after the quote's customer has been recognized in the ERP.

With the customer recognized, each quote row gets a Last paid: label next to it with the amount that customer paid last time for that product. ⚠️ The row's price still comes from the table. The last paid price only comes in when the seller clicks Use, and then it fixes the row's price. Nothing is applied on its own.

Stock

Vendria checks stock in the ERP in real time, without copying anything, when three things hold together: your store's ERP provides balances, the store works with stock control (Company manages stock, in Catalog and exports, Product page tab) and the connection is on. That balance is what feeds the shortage warning on the quote row: when an item has no balance, the row says so before the order goes out, not after.

What the seller does about the shortage is in another guide. See Estoque na cotação: o aviso de falta e as saídas.

Product fields on the product page

The ERP sends each product's fields, such as NCM, CEST, weights, part and packaging dimensions, line and group. The product page shows all of them. To hide one, open Catalog and exports, Product page tab, Attributes block: the list shows every field the store's products have, with how many products have it, and a switch to show it on the product page or not. A new field the ERP starts sending appears turned on. The choice applies to the store of your session, and the hidden field is also removed from the product list, from search and from the product card Dri shows. Exported lists follow the list template, not this choice.

Price tables and rules that come from the ERP

When your store's ERP defines an adjustment percentage per customer, that rule appears in Prices, Price tables tab, marked as coming from the ERP. The percentage is what the ERP declares for that customer: it isn't editable there, and if deleted it comes back on the next read. To change it, change it in the ERP.

In a store whose ERP doesn't work with per-customer adjustments, no rule appears with that mark, and the rules on the screen all belong to your team.

When your store sends orders to the ERP

Not every ERP receives orders from Vendria: some are only read from. When your store's ERP receives them, order sending is the last feature to be enabled: it's the only one where Vendria writes to your company's ERP, instead of only reading. While it isn't on, confirming an order in Vendria writes nothing to the ERP.

With sending on, the confirmed order is written to the ERP, and the number the ERP returns is recorded in Vendria: that's how both sides refer to the same order. The order's ERP page shows what was written there, such as items, invoices and settlement, as the ERP provides. See O pedido como ele ficou no ERP and O pedido confirmado vai para o ERP?.

In some ERPs, sending has particularities the screen shows when they happen:

an order allocated across branches may become one order per branch inside the ERP, each with its own page;
a part sold for future delivery may be written separately, as a pre-sale, and the regular order carries the rest.

Sellers and customers

Both can come in on their own, and both depend on being turned on for your store. What's automatic, what isn't and what to check before turning it on are in another guide. See What the ERP brings on its own, and what stays manual.

In a store where sellers come from the ERP, a customer-to-seller assignment that came from there is locked in Vendria: the fix is made in the ERP, and the sync brings the change.

⚠️ What remains yours

The integration brings data, not decisions. These stay with you:

Vendria's commercial and discount rules: they don't come from the ERP;
who each customer's seller is, while the sync isn't on;
what goes into the catalog the customer sees;
whether or not to apply the last paid price on each row.

When something doesn't match

The first place to look is whether the information exists in the ERP for that customer or product. Vendria shows what the ERP answers: when a field comes back empty, it's almost always empty there too.

Common questions

Does every integrated ERP bring credit, stock and last paid price? No. Each integration offers its own set, and Vendria only shows what your store's ERP provides. Data the ERP doesn't offer doesn't appear on the screen.

I connected the ERP. Why didn't everything show up? Because, besides the ERP offering the feature, each one has its own condition. Customer data, the intake of sellers and customers and order sending are enabled store by store by the Vendria team, after checking the records. Stock only appears with Company controls stock turned on in Catalog and exports, Product page tab. The last paid price only appears after the quote's customer is recognized in the ERP. See What syncs with the ERP, and when.